Comparison
Decagon vs Fin
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
Decagon
Decagon connects agents to existing support systems through prebuilt connectors and custom API or MCP integrations. The required setup depends on the systems and actions in scope.Vendor-reported
- Source
- Integrations (Decagon)
- Checked
- History
- First published
- Correct this
- Request a correction with a public source. Claim ID
decagon-deployment
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
Actions in backend systems
Decagon
APIs, custom tools and MCP connections provide access to data and actions. The integration must expose the operation the workflow requires.Vendor-reported
- Source
- Integrations (Decagon)
- Checked
- History
- First published
- Correct this
- Request a correction with a public source. Claim ID
decagon-actions
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
Human handoff
Decagon
Documented options include chat escalation, email routing and transfer of voice calls to a human agent.Vendor-reported
- Source
- Integrations (Decagon)
- Checked
- History
- First published
- Correct this
- Request a correction with a public source. Claim ID
decagon-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
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
The independent evidence behind these states comes mainly from practitioner forums and buyer reviews.States rest on 1 independent source across practitioner forums and buyer reviews. 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 | Decagon | Fin |
|---|---|---|
| Review basis | Source-based review | Source-based review |
| Deployment model | Decagon connects agents to existing support systems through prebuilt connectors and custom API or MCP integrations. The required setup depends on the systems and actions in scope.Vendor-reported
| Vendor-hosted service used with Intercom or a supported existing help desk. Configuration and integration work depend on the task.Vendor-reported
|
| Channels | Decagon’s homepage lists chat, email and voice. SMS appears in its Curology customer story; confirm whether that channel is available for your proposed deployment.Vendor-reported
| 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
|
| Languages | The voice page advertises 70+ languages, automatic detection and switching. Confirm language support for each required channel and evaluate real conversations in those languages.Vendor-reported
| 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
|
| Help desk and CRM integrations | The integration page names Salesforce, Intercom and Zendesk for tickets and customer data, and Amazon Connect and RingCentral for telephony.Vendor-reported
| Intercom, Zendesk, Salesforce, Freshdesk, and HubSpot are documented deployment options. Confirm the connector supports the required channel and actions.Vendor-reported
|
| Knowledge sources | Decagon documents knowledge synchronization from Confluence, Contentful and Kustomer.Vendor-reported
| Help articles, internal support content, PDFs, and webpages; audience settings control which content Fin can use for a customer.Vendor-reported
|
| Actions in backend systems | APIs, custom tools and MCP connections provide access to data and actions. The integration must expose the operation the workflow requires.Vendor-reported
| 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
|
| Human handoff | Documented options include chat escalation, email routing and transfer of voice calls to a human agent.Vendor-reported
| 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
|
| Target customer size | Decagon presents an enterprise offering and publishes customer stories for Chime, Notion and Rippling. That focus does not establish a minimum team size or exclude smaller deployments.Vendor-reported
| Fin has an explicit enterprise offering. Assess required integrations and operating controls instead of using company size as a proxy for fit.Vendor-reported
|
| Vendor-reported performance claims | Decagon reports a 65% reduction in support operating costs at Curology. This is a customer-specific vendor claim, not a resolution rate or a benchmark result; the page does not provide a common basis for cross-vendor comparison.Vendor-reported
| 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
|
| 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 evaluation: ask about a duplicate subscription charge. Verify access to the billing record, policy for credits and approvals, and whether the final action is recorded in the billing system. 1 cited claim for billing on DecagonDecagon’s technology page lists billing management, plan upgrades and account updates. It does not specify which billing operations are prebuilt for a particular payment or subscription system.Vendor-reported
| 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
|
| 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 evaluation: a customer requests an address change after dispatch. Check the carrier and order-system state, then distinguish an allowed update from a request that needs human help. 1 cited claim for orders on DecagonDecagon’s Curology case study lists shipment-status checks, order replacements and shipment cancellation or postponement. These are specific examples from Curology’s configured service workflows.Vendor-reported
| 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
|
| 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 evaluation: return one item from a discounted bundle. Check eligibility, refund calculation, approval rules and the recorded return state. A refund request alone is not proof that a physical return was completed. 1 cited claim for returns on DecagonDecagon’s retail article describes answering return-eligibility questions and taking actions through systems such as Shopify while following company policies. It does not define a universal policy for refunds or exchanges.Vendor-reported
| 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
|
| 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 evaluation: ask whether a plan includes a feature and whether that feature works in a particular integration. Check that the answer uses current product documentation and distinguishes missing information from a confirmed limitation. 1 cited claim for product questions on DecagonDecagon’s technology offering describes surfacing relevant documentation during onboarding and troubleshooting. This supports a documented product-information workflow, not a measured accuracy result.Vendor-reported
| 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
|
| 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 evaluation: a user who cannot sign in requests an email-address change. Verify identity checks, permission boundaries and escalation when verification fails. 1 cited claim for account issues on DecagonDecagon’s financial-services page lists password resets, balance inquiries and dispute workflows. Those examples require a configured identity and account-access flow; the page does not prove that a given deployment implements it correctly.Vendor-reported
| 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
|
| 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 evaluation: a customer repeats an unresolved refund complaint. Check recognition of prior attempts, escalation rules and the promised follow-up. A sentiment flag alone does not resolve the issue. 1 cited claim for complaints on DecagonWatchtower documents identifying frustration and other conversation flags for team review. This is monitoring capability; the source does not demonstrate an agent completing a complaint remedy.Vendor-reported
| 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
|
| 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. | External report Illustrative evaluation: request a human after an unsuccessful troubleshooting step. Check queue routing, transcript transfer, repeated questions and the offline fallback. 2 cited claims for human handoff on DecagonDecagon documents live-chat escalation, email handoff and voice transfer to human agents.Vendor-reported
Krishan Y.’s August 12, 2026 review says their team can step in when human attention is needed. This corroborates takeover in one self-reported deployment, without measuring routing accuracy or waiting time.Independent report
| 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
|
| 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. | Not established The reviewed sources do not establish suitability for every small team. Illustrative buying scenario: a two-person support team needs one channel and basic FAQ answers. Ask what setup, integration access and ongoing maintenance that scope requires. No supporting source is recorded here. Validate it with the vendor; absence of evidence does not establish a missing capability. | 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
|
| 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. | Not established Enterprise marketing does not exclude mid-market use. Illustrative buying scenario: a growing subscription business needs account updates and refunds. Confirm the specific connectors, implementation effort and responsibility for maintaining policies. No supporting source is recorded here. Validate it with the vendor; absence of evidence does not establish a missing capability. | 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
|
| 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 buying scenario: several brands share a support operation but use different policies. Evaluate permissions, policy separation, reporting and escalation under that actual structure. 1 cited claim for enterprise on DecagonDecagon publishes customer stories for companies including Chime, Notion and Rippling. These are vendor-published examples of enterprise use, not independent confirmation of every security, scale or workflow requirement.Vendor-reported
| 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
|
| Industry evidenceRetail and e-commerce | Vendor-documented Decagon publishes a retail offering describing order and return actions through systems such as Shopify. The source is the vendor's own; it names no retailer and reports no outcome. 1 cited claim for retail and e-commerce on DecagonDecagon’s retail article describes answering return-eligibility questions and taking actions through systems such as Shopify while following company policies. It does not define a universal policy for refunds or exchanges.Vendor-reported
| 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
|
| 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 Decagon’s homepage lists chat, email and voice. SMS appears in its Curology customer story; confirm whether that channel is available for your proposed deployment. 1 cited claim for web and in-app chat on DecagonDecagon’s homepage lists chat, email and voice. SMS appears in its Curology customer story; confirm whether that channel is available for your proposed deployment.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 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 Decagon’s homepage lists chat, email and voice. SMS appears in its Curology customer story; confirm whether that channel is available for your proposed deployment. 1 cited claim for email on DecagonDecagon’s homepage lists chat, email and voice. SMS appears in its Curology customer story; confirm whether that channel is available for your proposed deployment.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
| |
| Voice and phone | Vendor-documented Decagon’s homepage lists chat, email and voice. SMS appears in its Curology customer story; confirm whether that channel is available for your proposed deployment. 1 cited claim for voice and phone on DecagonDecagon’s homepage lists chat, email and voice. SMS appears in its Curology customer story; confirm whether that channel is available for your proposed 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. |
| SMS | Vendor-documented Decagon’s homepage lists chat, email and voice. SMS appears in its Curology customer story; confirm whether that channel is available for your proposed deployment. 1 cited claim for sms on DecagonDecagon’s homepage lists chat, email and voice. SMS appears in its Curology customer story; confirm whether that channel is available for your proposed deployment.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 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
|
| Not established No supporting source is recorded here. Validate it with the vendor; absence of evidence does not establish a missing capability. | 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
| |
| Social messaging | Not established No supporting source is recorded here. Validate it with the vendor; absence of evidence does not establish a missing capability. | 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
|
| Help desks | ||
| Zendesk | Vendor-documented The integration page names Salesforce, Intercom and Zendesk for tickets and customer data, and Amazon Connect and RingCentral for telephony. 1 cited claim for zendesk on DecagonThe integration page names Salesforce, Intercom and Zendesk for tickets and customer data, and Amazon Connect and RingCentral for telephony.Vendor-reported
| 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
|
| Salesforce | Vendor-documented The integration page names Salesforce, Intercom and Zendesk for tickets and customer data, and Amazon Connect and RingCentral for telephony. 1 cited claim for salesforce on DecagonThe integration page names Salesforce, Intercom and Zendesk for tickets and customer data, and Amazon Connect and RingCentral for telephony.Vendor-reported
| 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
|
| 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 | Not established No supporting source is recorded here. Validate it with the vendor; absence of evidence does not establish a missing capability. | 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
|
| Intercom | Vendor-documented The integration page names Salesforce, Intercom and Zendesk for tickets and customer data, and Amazon Connect and RingCentral for telephony. 1 cited claim for intercom on DecagonThe integration page names Salesforce, Intercom and Zendesk for tickets and customer data, and Amazon Connect and RingCentral for telephony.Vendor-reported
| 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
|
| HubSpot | Not established No supporting source is recorded here. Validate it with the vendor; absence of evidence does not establish a missing capability. | 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
|
| 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
Decagon: 7 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
- Help desk · ZendeskNot established→Vendor-documented
- Help desk · SalesforceNot established→Vendor-documented
- Help desk · IntercomNot established→Vendor-documented
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
· Catalog
Launch: 22 AI customer service agents and 532 claims, every one sourced and dated
Decagon: Added to the catalog with 26 claims and 9 rows with evidence.
Fin: Added to the catalog with 28 claims and 11 rows with evidence.
Recorded before launch
Notes the profile carried when it went live, from research before launch.
Decagon: Added editorial product positioning with its scope, rationale, and vendor source. Source
Decagon: Rechecked public sources and added the Curology order-workflow example. Scoped customer reports, removed unsupported business-size exclusions and relayed marketing treated as independent evidence, and added evaluation examples for every use case.
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