Comparison
Fin vs Sierra
Compare documented workflows and implementation requirements using attributed public sources. Facts last checked , the earlier of the two records. Machine-readable record.
Start with your setup
These are documented product differences and requirements. A feature list or a single customer report does not establish which agent will perform better for your team.
Deployment model
Fin
Vendor-hosted service used with Intercom or a supported existing help desk. Configuration and integration work depend on the task.Vendor-reported
- Source
- Fin pricing and deployment options
- Checked
- History
- First published
- Correct this
- Request a correction with a public source. Claim ID
fin-deployment
Sierra
Sierra documents configuration through Agent Studio and custom integrations for proprietary systems. Deployment work includes defining journeys and connecting the systems those journeys use.Vendor-reported
- Source
- Agent Studio (Sierra)
- Checked
- History
- First published
- Correct this
- Request a correction with a public source. Claim ID
sierra-deployment
Actions in backend systems
Fin
Configured Procedures can combine conditions, code, and data connectors or MCP access to external systems. Actions execute sequentially and require the appropriate integration permissions.Vendor-reported
- Source
- Fin Procedures explained (Intercom Help)
- Checked
- History
- First published
- Correct this
- Request a correction with a public source. Claim ID
fin-actions
Sierra
The SDK lists subscription updates and warranty submissions as examples of actions through connected systems. Required permissions and workflow configuration depend on the implementation.Vendor-reported
- Source
- Agent SDK (Sierra)
- Checked
- History
- First published
- Correct this
- Request a correction with a public source. Claim ID
sierra-actions
Human handoff
Fin
Escalation rules and guidance control handoff; workflows set the human destination. A bot-only workflow without a human routing target does not offer escalation.Vendor-reported
- Source
- Manage Fin AI Agent's escalation guidance and rules (Intercom Help)
- Checked
- History
- First published
- Correct this
- Request a correction with a public source. Claim ID
fin-handoff
Sierra
The SDK documents routing to a team member with an automatic conversation summary.Vendor-reported
- Source
- Agent SDK (Sierra)
- Checked
- History
- First published
- Correct this
- Request a correction with a public source. Claim ID
sierra-handoff
Side by side
Product attributes first, then what the sources establish for each customer workflow, then the industries they place each agent in. Open any claim to see its source, the date it was checked, and how to request a correction. Two agents are rarely documented to the same depth, so read a difference between the two columns as a difference in the public record before reading it as a difference in the products.
What this agent was judged by
No independent source has been found for any fit area, so every state here rests on vendor material or nothing.States rest on 0 independent sources. This is not the same yardstick for every agent, and that asymmetry is a known limitation.
What this agent was judged by
No independent source has been found for any fit area, so every state here rests on vendor material or nothing.States rest on 0 independent sources. This is not the same yardstick for every agent, and that asymmetry is a known limitation.
| Attribute | Fin | Sierra |
|---|---|---|
| Review basis | Source-based review | Source-based review |
| Deployment model | Vendor-hosted service used with Intercom or a supported existing help desk. Configuration and integration work depend on the task.Vendor-reported
| Sierra documents configuration through Agent Studio and custom integrations for proprietary systems. Deployment work includes defining journeys and connecting the systems those journeys use.Vendor-reported
|
| Channels | The FAQ lists web and mobile Messenger, email, WhatsApp, SMS, Facebook, and Instagram. Confirm separate voice or other channel access and feature coverage for the intended deployment.Vendor-reported
| Vendor-listed channels include phone, website and app chat, WhatsApp, Apple Business Chat, SMS and email. Live Assist supports staff, and Sierra also documents publishing selected agent journeys to ChatGPT.Vendor-reported
|
| Languages | Intercom lists supported languages and regional variants, including Polish, French, Japanese, and Arabic. Enable the required workspace languages; cross-language knowledge fallback requires real-time translation.Vendor-reported
| The current Channels page describes voice models tuned for 60+ locales. A locale is not the same as a language; verify the exact language, accent and channel required for your deployment.Vendor-reported
|
| Help desk and CRM integrations | Intercom, Zendesk, Salesforce, Freshdesk, and HubSpot are documented deployment options. Confirm the connector supports the required channel and actions.Vendor-reported
| Agent Studio lists 40+ prebuilt integrations for knowledge, systems of record and contact centers, but this page does not identify the help-desk connectors. Confirm your help desk and required handoff behavior with Sierra.Vendor-reported
|
| Knowledge sources | Help articles, internal support content, PDFs, and webpages; audience settings control which content Fin can use for a customer.Vendor-reported
| The SDK documents ingestion of company FAQs, policies and documentation into its knowledge engine.Vendor-reported
|
| Actions in backend systems | Configured Procedures can combine conditions, code, and data connectors or MCP access to external systems. Actions execute sequentially and require the appropriate integration permissions.Vendor-reported
| The SDK lists subscription updates and warranty submissions as examples of actions through connected systems. Required permissions and workflow configuration depend on the implementation.Vendor-reported
|
| Human handoff | Escalation rules and guidance control handoff; workflows set the human destination. A bot-only workflow without a human routing target does not offer escalation.Vendor-reported
| The SDK documents routing to a team member with an automatic conversation summary.Vendor-reported
|
| Target customer size | Fin has an explicit enterprise offering. Assess required integrations and operating controls instead of using company size as a proxy for fit.Vendor-reported
| Sierra’s public customer examples include AOL, Minted and Ramp. These show deployments in established businesses; they do not define a minimum viable team size.Vendor-reported
|
| Vendor-reported performance claims | Fin's homepage reports a 76% average resolution rate across 12,000+ customers. This is a vendor aggregate, not our result or a forecast for a particular workload.Vendor-reported
| Sierra reports 90% case resolution at Ramp. This is a vendor-published customer result with no common benchmark population supplied here; it should not be compared directly with another vendor’s deflection or resolution figure.Vendor-reported
|
| Workflow evidenceBilling Illustrative scenario I was charged twice for the same order. Can you refund the extra payment? What to verify: Verify identity, inspect payment records, apply the refund policy, and confirm the payment-system result. If no authorized refund action is connected, hand off with the evidence. | Vendor-documented Illustrative scenario: a customer asks for an invoice copy. Give the workflow authenticated access to the correct account and a permitted retrieval action. A disputed charge needs separate policy and escalation rules; the source does not demonstrate reliable dispute adjudication. 1 cited claim for billing on FinFin advertises invoice requests and subscription management through connected systems on its enterprise page. This is a configured workflow capability, not access to a buyer's billing account by default.Vendor-reported
| Vendor-documented Illustrative evaluation: ask why a subscription charge increased, then request a card update. Verify identity checks, the source of the billing explanation and the permitted update path. 1 cited claim for billing on SierraSierra’s AOL case study describes explanations of outstanding balances, billing history and payment-method updates. The example is AOL’s configured agent, not a guarantee that every Sierra deployment includes billing access.Vendor-reported
|
| Workflow evidenceOrders Illustrative scenario My order has not arrived. Where is it? What to verify: Retrieve the correct order and current carrier status. Distinguish a real tracking update from an estimate; do not invent a delivery date. | Vendor-documented Illustrative scenario: a shopper asks where an order is. The reply needs a verified customer-to-order match and current delivery data. Check that lookup in the intended channel; shopping features in web Messenger do not establish equivalent functionality elsewhere. 1 cited claim for orders on FinFin for Ecommerce documents a native Shopify connection for catalogue and order data, plus APIs and draft Procedures for post-purchase requests.Vendor-reported
| Vendor-documented Illustrative evaluation: use a split shipment with one delayed item. Require the agent to distinguish production status from carrier status and avoid promising a delivery date that the connected system does not provide. 1 cited claim for orders on SierraSierra’s Minted case study describes order updates across design approval, printing and shipping, plus priority-shipping changes for delayed orders. This supports an order-management use case in that deployment.Vendor-reported
|
| Workflow evidenceReturns Illustrative scenario I bought this 12 days ago and opened the box. Can I return it? What to verify: Check the actual return window, product exclusions, and order record. A policy answer and an executed return are different capabilities. | Vendor-documented Illustrative scenario: a customer returns an eligible item. Configure the return window, exclusions, permitted refund action, and human review for exceptions. Listing a returns capability does not establish that a particular store policy is implemented correctly. 1 cited claim for returns on FinFin for Ecommerce lists returns, refunds, and order changes as supported conversational workflows. These rely on the connected store and configured post-purchase actions.Vendor-reported
| Vendor-documented Illustrative evaluation: request an exchange for an item outside the normal return window. Check the configured exception policy, approval requirement and final state in the order system. 1 cited claim for returns on SierraSierra’s retail page lists refund requests and exchanges among supported workflows. It does not specify a universal return-policy configuration or prove that a particular refund reaches the payment processor.Vendor-reported
|
| Workflow evidenceProduct questions Illustrative scenario Does this adapter work with my exact laptop model? What to verify: Use a current, approved compatibility source. Ask for the model when missing and distinguish documented compatibility from an assumption. | Vendor-documented Illustrative scenario: a customer asks whether their subscription includes an export feature. Supply current plan-specific documentation and check that Fin distinguishes plans rather than combining incompatible answers. Documentation establishes the answering mechanism, not an accuracy rate. 1 cited claim for product questions on FinFin builds answers from help articles, internal support content, PDFs, and webpages. Audience rules can limit which content applies to a customer.Vendor-reported
| Vendor-documented Illustrative evaluation: ask whether an accessory works with an older product model. Supply an approved compatibility source and check that missing information leads to clarification rather than an invented answer. 1 cited claim for product questions on SierraSierra describes grounding answers in company knowledge, policies and brand guidance. That provides a route to product answers based on supplied content; it does not establish accuracy for a buyer’s catalog.Vendor-reported
|
| Workflow evidenceAccount issues Illustrative scenario I lost access to my email. Change the address on my account. What to verify: Follow the approved identity-recovery process before accessing or changing account data. Escalate when identity cannot be verified. | Vendor-documented Illustrative scenario: an authenticated customer changes an account detail. Restrict which fields the workflow may update and route failed identity checks to a human. A support article explaining a password reset is different from permission to change credentials. 1 cited claim for account issues on FinIntercom describes account troubleshooting and identity verification as Procedure use cases, with configurable system access and branching logic.Vendor-reported
| Vendor-documented Illustrative evaluation: an authenticated cardholder requests a replacement card and address change. Check permissions, address confirmation and the resulting card state before considering the journey complete. 1 cited claim for account issues on SierraSierra’s Ramp case study describes card locking and replacement, address validation and transaction explanations. These are account actions in Ramp’s configured implementation; password recovery and other account workflows require their own evidence.Vendor-reported
|
| Workflow evidenceComplaints Illustrative scenario I have contacted you three times and the problem is still unresolved. What to verify: Recognize the repeat complaint, retain relevant history, and route it to the right team. Do not promise compensation outside the policy. | Vendor-documented Illustrative scenario: a customer says repeated answers have not helped. Check that the configured guidance triggers handoff and preserves the issue history. Detecting frustration does not demonstrate that the complaint was resolved. 1 cited claim for complaints on FinFin documents escalation for explicit human requests, detected frustration, and repeated loops. Custom guidance can override default escalation behavior.Vendor-reported
| Vendor-documented Illustrative evaluation: a customer repeats a cancellation request after rejecting a retention offer. Check that the configured flow respects the refusal and provides the agreed cancellation or human-escalation path. 1 cited claim for complaints on SierraSierra says its agents can recognize frustration and adapt their responses. This is a vendor claim about conversational behavior, not a measured result for complaint resolution or customer satisfaction.Vendor-reported
|
| Workflow evidenceHuman handoff Illustrative scenario Please connect me to a person who can approve this exception. What to verify: Transfer to an available team with the conversation and relevant records. Outside working hours, explain the actual follow-up path rather than promise immediate contact. | Vendor-documented Illustrative scenario: a customer asks for a person after an unsuccessful answer. Verify the destination inbox, transcript transfer, and after-hours response. A handoff event alone does not show how quickly a human replies. 1 cited claim for human handoff on FinFin uses configured workflows to route escalations. Intercom states that no escalation offer is shown when no human routing target exists.Vendor-reported
| Vendor-documented Illustrative evaluation: request a person during a failed account update. Check queue routing, transcript and summary delivery, plus what the customer sees when the team is offline. 1 cited claim for human handoff on SierraSierra’s SDK page documents routing an escalated conversation to a team member with a generated summary. It does not establish how quickly a human answers in a particular contact center.Vendor-reported
|
| Workflow evidenceSmall businesses Illustrative scenario A two-person support team wants to launch without a dedicated engineer. What to verify: Validate setup effort, existing help-desk support, required integrations, and ongoing maintenance. A small customer's story alone does not establish suitability for every small business. | Vendor-documented Illustrative scenario: a small team starts with common support questions and one monitored human inbox. Compare expected use and ongoing content maintenance with available staff. Programme eligibility and a product trial do not prove affordability or suitability for every small business. 1 cited claim for small businesses on FinFin publishes an early-stage startup programme with eligibility requirements. This establishes an offer for some small teams, not an exclusion of other small businesses.Vendor-reported
| Not established Business size alone does not establish suitability. Illustrative buying scenario: a small team needs one FAQ channel; ask for the implementation work and ongoing maintenance required for that scope before deciding whether the platform is proportionate. No supporting source is recorded here. Validate it with the vendor; absence of evidence does not establish a missing capability. |
| Workflow evidenceMid-market Illustrative scenario A growing support team needs separate queues and connected order and account systems. What to verify: Validate routing, permissions, integration ownership, and handling of each team's policies in the intended configuration. | Vendor-documented Illustrative scenario: a growing team keeps its help desk and adds one authenticated order lookup. Confirm connector coverage, ownership of failed actions, and routing before expanding. Team size alone is not evidence of a successful deployment. 1 cited claim for mid-market on FinFin is sold with Intercom or for use with an existing help desk; the deployment options do not impose a single published company-size category.Vendor-reported
| Not established The reviewed sources do not establish a universal mid-market fit. Illustrative buying scenario: a growing retailer needs order support across two brands; evaluate connector coverage, ownership of policy updates and support capacity for that deployment. No supporting source is recorded here. Validate it with the vendor; absence of evidence does not establish a missing capability. |
| Workflow evidenceEnterprise Illustrative scenario A multi-brand support organization needs controlled access across regional teams. What to verify: Validate data boundaries, audit records, escalation ownership, and the specific deployment requirements. A vendor's enterprise positioning is not proof of these controls. | Vendor-documented Illustrative scenario: several brands need different knowledge access and approval rules. Evaluate those boundaries and operational reporting in the planned workspace structure. An enterprise offering does not establish that all data-residency, retention, or approval requirements are met. 1 cited claim for enterprise on FinFin markets an enterprise offering with workspace permission controls, activity logs, deployment services, and integrations with existing help desks.Vendor-reported
| Vendor-documented Illustrative buying scenario: multiple business units need separate permissions and policies. Request a demonstration using those boundaries and review the operational and security requirements of the proposed deployment. 1 cited claim for enterprise on SierraSierra publishes customer stories for AOL, Minted and Ramp, including connected service workflows. These are vendor-published deployment examples, not proof that every enterprise requirement is met.Vendor-reported
|
| Industry evidenceRetail and e-commerce | Caveat documented Fin for Ecommerce is a documented product with a native Shopify connection, and the same vendor documentation states the ecommerce features are limited to the web Messenger. Read the capability and the channel limit together before assuming coverage of an email or social queue. 2 cited claims for retail and e-commerce on FinFin for Ecommerce documents a native Shopify connection for catalogue and order data, plus APIs and draft Procedures for post-purchase requests.Vendor-reported
Full ecommerce shopping features are documented for web Messenger. Mobile receives support-only responses; email, social, voice, and Slack are not currently supported for the ecommerce role. This limit does not describe every Fin service capability.Vendor-reported
| Vendor-documented Sierra's retail and consumer goods page lists refunds and exchanges among supported workflows. Vendor documentation only; no retail deployment is independently reported. 1 cited claim for retail and e-commerce on SierraSierra’s retail page lists refund requests and exchanges among supported workflows. It does not specify a universal return-policy configuration or prove that a particular refund reaches the payment processor.Vendor-reported
|
| Industry evidenceFinancial services | Not established No supporting source is recorded here. Validate it with the vendor; absence of evidence does not establish a missing capability. | Not established No supporting source is recorded here. Validate it with the vendor; absence of evidence does not establish a missing capability. |
| Industry evidenceTelecommunications | Not established No supporting source is recorded here. Validate it with the vendor; absence of evidence does not establish a missing capability. | Not established No supporting source is recorded here. Validate it with the vendor; absence of evidence does not establish a missing capability. |
| Industry evidenceTravel and hospitality | Not established No supporting source is recorded here. Validate it with the vendor; absence of evidence does not establish a missing capability. | Not established No supporting source is recorded here. Validate it with the vendor; absence of evidence does not establish a missing capability. |
| Industry evidenceHealthcare | Not established No supporting source is recorded here. Validate it with the vendor; absence of evidence does not establish a missing capability. | Not established No supporting source is recorded here. Validate it with the vendor; absence of evidence does not establish a missing capability. |
| Industry evidencePublic sector and education | Not established No supporting source is recorded here. Validate it with the vendor; absence of evidence does not establish a missing capability. | Not established No supporting source is recorded here. Validate it with the vendor; absence of evidence does not establish a missing capability. |
| Industry evidenceLogistics and delivery | Not established No supporting source is recorded here. Validate it with the vendor; absence of evidence does not establish a missing capability. | Not established No supporting source is recorded here. Validate it with the vendor; absence of evidence does not establish a missing capability. |
| Channels | ||
| Web and in-app chat | Vendor-documented The FAQ lists web and mobile Messenger, email, WhatsApp, SMS, Facebook, and Instagram. Confirm separate voice or other channel access and feature coverage for the intended deployment. 1 cited claim for web and in-app chat on FinThe FAQ lists web and mobile Messenger, email, WhatsApp, SMS, Facebook, and Instagram. Confirm separate voice or other channel access and feature coverage for the intended deployment.Vendor-reported
| Vendor-documented Vendor-listed channels include phone, website and app chat, WhatsApp, Apple Business Chat, SMS and email. Live Assist supports staff, and Sierra also documents publishing selected agent journeys to ChatGPT. 1 cited claim for web and in-app chat on SierraVendor-listed channels include phone, website and app chat, WhatsApp, Apple Business Chat, SMS and email. Live Assist supports staff, and Sierra also documents publishing selected agent journeys to ChatGPT.Vendor-reported
|
| Vendor-documented The FAQ lists web and mobile Messenger, email, WhatsApp, SMS, Facebook, and Instagram. Confirm separate voice or other channel access and feature coverage for the intended deployment. 1 cited claim for email on FinThe FAQ lists web and mobile Messenger, email, WhatsApp, SMS, Facebook, and Instagram. Confirm separate voice or other channel access and feature coverage for the intended deployment.Vendor-reported
| Vendor-documented Vendor-listed channels include phone, website and app chat, WhatsApp, Apple Business Chat, SMS and email. Live Assist supports staff, and Sierra also documents publishing selected agent journeys to ChatGPT. 1 cited claim for email on SierraVendor-listed channels include phone, website and app chat, WhatsApp, Apple Business Chat, SMS and email. Live Assist supports staff, and Sierra also documents publishing selected agent journeys to ChatGPT.Vendor-reported
| |
| Voice and phone | Not established No supporting source is recorded here. Validate it with the vendor; absence of evidence does not establish a missing capability. | Vendor-documented Vendor-listed channels include phone, website and app chat, WhatsApp, Apple Business Chat, SMS and email. Live Assist supports staff, and Sierra also documents publishing selected agent journeys to ChatGPT. 1 cited claim for voice and phone on SierraVendor-listed channels include phone, website and app chat, WhatsApp, Apple Business Chat, SMS and email. Live Assist supports staff, and Sierra also documents publishing selected agent journeys to ChatGPT.Vendor-reported
|
| SMS | Vendor-documented The FAQ lists web and mobile Messenger, email, WhatsApp, SMS, Facebook, and Instagram. Confirm separate voice or other channel access and feature coverage for the intended deployment. 1 cited claim for sms on FinThe FAQ lists web and mobile Messenger, email, WhatsApp, SMS, Facebook, and Instagram. Confirm separate voice or other channel access and feature coverage for the intended deployment.Vendor-reported
| Vendor-documented Vendor-listed channels include phone, website and app chat, WhatsApp, Apple Business Chat, SMS and email. Live Assist supports staff, and Sierra also documents publishing selected agent journeys to ChatGPT. 1 cited claim for sms on SierraVendor-listed channels include phone, website and app chat, WhatsApp, Apple Business Chat, SMS and email. Live Assist supports staff, and Sierra also documents publishing selected agent journeys to ChatGPT.Vendor-reported
|
| Vendor-documented The FAQ lists web and mobile Messenger, email, WhatsApp, SMS, Facebook, and Instagram. Confirm separate voice or other channel access and feature coverage for the intended deployment. 1 cited claim for whatsapp on FinThe FAQ lists web and mobile Messenger, email, WhatsApp, SMS, Facebook, and Instagram. Confirm separate voice or other channel access and feature coverage for the intended deployment.Vendor-reported
| Vendor-documented Vendor-listed channels include phone, website and app chat, WhatsApp, Apple Business Chat, SMS and email. Live Assist supports staff, and Sierra also documents publishing selected agent journeys to ChatGPT. 1 cited claim for whatsapp on SierraVendor-listed channels include phone, website and app chat, WhatsApp, Apple Business Chat, SMS and email. Live Assist supports staff, and Sierra also documents publishing selected agent journeys to ChatGPT.Vendor-reported
| |
| Social messaging | Vendor-documented The FAQ lists web and mobile Messenger, email, WhatsApp, SMS, Facebook, and Instagram. Confirm separate voice or other channel access and feature coverage for the intended deployment. 1 cited claim for social messaging on FinThe FAQ lists web and mobile Messenger, email, WhatsApp, SMS, Facebook, and Instagram. Confirm separate voice or other channel access and feature coverage for the intended deployment.Vendor-reported
| Not established No supporting source is recorded here. Validate it with the vendor; absence of evidence does not establish a missing capability. |
| Help desks | ||
| Zendesk | Vendor-documented Intercom, Zendesk, Salesforce, Freshdesk, and HubSpot are documented deployment options. Confirm the connector supports the required channel and actions. 1 cited claim for zendesk on FinIntercom, Zendesk, Salesforce, Freshdesk, and HubSpot are documented deployment options. Confirm the connector supports the required channel and actions.Vendor-reported
| Not established No supporting source is recorded here. Validate it with the vendor; absence of evidence does not establish a missing capability. |
| Salesforce | Vendor-documented Intercom, Zendesk, Salesforce, Freshdesk, and HubSpot are documented deployment options. Confirm the connector supports the required channel and actions. 1 cited claim for salesforce on FinIntercom, Zendesk, Salesforce, Freshdesk, and HubSpot are documented deployment options. Confirm the connector supports the required channel and actions.Vendor-reported
| Not established No supporting source is recorded here. Validate it with the vendor; absence of evidence does not establish a missing capability. |
| ServiceNow | Not established No supporting source is recorded here. Validate it with the vendor; absence of evidence does not establish a missing capability. | Not established No supporting source is recorded here. Validate it with the vendor; absence of evidence does not establish a missing capability. |
| Freshdesk | Vendor-documented Intercom, Zendesk, Salesforce, Freshdesk, and HubSpot are documented deployment options. Confirm the connector supports the required channel and actions. 1 cited claim for freshdesk on FinIntercom, Zendesk, Salesforce, Freshdesk, and HubSpot are documented deployment options. Confirm the connector supports the required channel and actions.Vendor-reported
| Not established No supporting source is recorded here. Validate it with the vendor; absence of evidence does not establish a missing capability. |
| Intercom | Vendor-documented Intercom, Zendesk, Salesforce, Freshdesk, and HubSpot are documented deployment options. Confirm the connector supports the required channel and actions. 1 cited claim for intercom on FinIntercom, Zendesk, Salesforce, Freshdesk, and HubSpot are documented deployment options. Confirm the connector supports the required channel and actions.Vendor-reported
| Not established No supporting source is recorded here. Validate it with the vendor; absence of evidence does not establish a missing capability. |
| HubSpot | Vendor-documented Intercom, Zendesk, Salesforce, Freshdesk, and HubSpot are documented deployment options. Confirm the connector supports the required channel and actions. 1 cited claim for hubspot on FinIntercom, Zendesk, Salesforce, Freshdesk, and HubSpot are documented deployment options. Confirm the connector supports the required channel and actions.Vendor-reported
| Not established No supporting source is recorded here. Validate it with the vendor; absence of evidence does not establish a missing capability. |
| Kustomer | Not established No supporting source is recorded here. Validate it with the vendor; absence of evidence does not establish a missing capability. | Not established No supporting source is recorded here. Validate it with the vendor; absence of evidence does not establish a missing capability. |
| Gorgias | Not established No supporting source is recorded here. Validate it with the vendor; absence of evidence does not establish a missing capability. | Not established No supporting source is recorded here. Validate it with the vendor; absence of evidence does not establish a missing capability. |
| Gladly | Not established No supporting source is recorded here. Validate it with the vendor; absence of evidence does not establish a missing capability. | Not established No supporting source is recorded here. Validate it with the vendor; absence of evidence does not establish a missing capability. |
| Help Scout | Not established No supporting source is recorded here. Validate it with the vendor; absence of evidence does not establish a missing capability. | Not established No supporting source is recorded here. Validate it with the vendor; absence of evidence does not establish a missing capability. |
| Front | Not established No supporting source is recorded here. Validate it with the vendor; absence of evidence does not establish a missing capability. | Not established No supporting source is recorded here. Validate it with the vendor; absence of evidence does not establish a missing capability. |
| Microsoft Dynamics 365 | Not established No supporting source is recorded here. Validate it with the vendor; absence of evidence does not establish a missing capability. | Not established No supporting source is recorded here. Validate it with the vendor; absence of evidence does not establish a missing capability. |
Change history
Open the changelogEvery change to this record is in the public changelog, with what it changed and why.
· Structure
Channels and help desks become evidence rows, and records gain bylines
Fin: 10 evidence states moved
- Channel · Web and in-app chatNot established→Vendor-documented
- Channel · EmailNot established→Vendor-documented
- Channel · SMSNot established→Vendor-documented
- Channel · WhatsAppNot established→Vendor-documented
- Channel · Social messagingNot established→Vendor-documented
- Help desk · ZendeskNot established→Vendor-documented
- Help desk · SalesforceNot established→Vendor-documented
- Help desk · FreshdeskNot established→Vendor-documented
- and 2 more
Sierra: 5 evidence states moved
- Channel · Web and in-app chatNot established→Vendor-documented
- Channel · EmailNot established→Vendor-documented
- Channel · Voice and phoneNot established→Vendor-documented
- Channel · SMSNot established→Vendor-documented
- Channel · WhatsAppNot established→Vendor-documented
· Catalog
Launch: 22 AI customer service agents and 532 claims, every one sourced and dated
Fin: Added to the catalog with 28 claims and 11 rows with evidence.
Sierra: Added to the catalog with 23 claims and 9 rows with evidence.
Recorded before launch
Notes the profile carried when it went live, from research before launch.
Fin: Added editorial product positioning with its scope, rationale, and vendor source. Source
Fin: Rechecked the profile against current product documentation. Replaced broad fit claims with scoped workflows and illustrative examples, corrected billing and Procedure limitations, and removed unsupported acquisition and anecdotal verdict claims. Source
Sierra: Added editorial product positioning with its scope, rationale, and vendor source. Source
Sierra: Rechecked public sources; replaced broad fit verdict evidence with specific deployment examples and evaluation conditions. Removed unverified attribution, relayed marketing treated as independent confirmation, and business-size exclusions without evidence.