Comparison
Ada vs Decagon
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
Ada
Ada documents setup through its dashboard and a website or mobile chat integration, with connected knowledge and configured workflows.Vendor-reported
- Source
- Key concepts (Ada docs)
- Checked
- History
- First published
- Correct this
- Request a correction with a public source. Claim ID
ada-deployment
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
Actions in backend systems
Ada
API tools, formerly called Actions, retrieve or send data through configured endpoints. Playbooks and Processes organise those calls into workflows.Vendor-reported
- Source
- API tools (Ada docs)
- Checked
- History
- First published
- Correct this
- Request a correction with a public source. Claim ID
ada-actions
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
Human handoff
Ada
Configured live transfers or follow-up tickets, with off-hours and error paths. Up to five active handoff configurations are documented.Vendor-reported
- Source
- Handoff management (Ada docs)
- Checked
- History
- First published
- Correct this
- Request a correction with a public source. Claim ID
ada-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
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
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.
| Attribute | Ada | Decagon |
|---|---|---|
| Review basis | Source-based review | Source-based review |
| Deployment model | Ada documents setup through its dashboard and a website or mobile chat integration, with connected knowledge and configured workflows.Vendor-reported
| 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
|
| Channels | Chat, voice, email and social messaging are documented. Voice and social connections use supported external platforms; confirm the intended channel integration.Vendor-reported
| 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
|
| Languages | 60 languages are documented for messaging and email; voice supports a subset. English remains the fallback language.Vendor-reported
| 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
|
| Help desk and CRM integrations | The integrations directory includes Zendesk, Salesforce, ServiceNow, Freshworks, Genesys and Help Scout. Check each entry for knowledge, messaging, email or voice support.Vendor-reported
| The integration page names Salesforce, Intercom and Zendesk for tickets and customer data, and Amazon Connect and RingCentral for telephony.Vendor-reported
|
| Knowledge sources | Knowledge can come from help centres, websites, articles created in Ada and custom sources through the Knowledge API.Vendor-reported
| Decagon documents knowledge synchronization from Confluence, Contentful and Kustomer.Vendor-reported
|
| Actions in backend systems | API tools, formerly called Actions, retrieve or send data through configured endpoints. Playbooks and Processes organise those calls into workflows.Vendor-reported
| APIs, custom tools and MCP connections provide access to data and actions. The integration must expose the operation the workflow requires.Vendor-reported
|
| Human handoff | Configured live transfers or follow-up tickets, with off-hours and error paths. Up to five active handoff configurations are documented.Vendor-reported
| Documented options include chat escalation, email routing and transfer of voice calls to a human agent.Vendor-reported
|
| Target customer size | Ada presents an enterprise-focused sales process with a tailored demonstration and implementation plan. This positioning does not establish a minimum viable company size.Vendor-reported
| 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
|
| Vendor-reported performance claims | Ada reports that Dott’s automated resolution increased from 32% to 77% after adopting Ada and connecting backend automations. This is one customer’s vendor-published result, not a platform-wide average or a comparable benchmark.Vendor-reported
| 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
|
| 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, not a test: explain a duplicate charge using the customer’s payment records. Ada documents billing inquiries; verify identity checks, access to the payment system and the route for a disputed charge. Answering a question and reversing a payment are separate operations. 1 cited claim for billing on AdaAda lists billing and payment questions among its email workflows, using information retrieved from connected business systems.Vendor-reported
| 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
|
| 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, not a test: retrieve shipment status for a customer’s order and give the carrier’s tracking link. Validate customer ownership, missing orders and stale tracking data. A lookup does not demonstrate that lost parcels are resolved. 1 cited claim for orders on AdaAda documents API-driven order-status lookups, so live order answers depend on connecting the order system.Vendor-reported
| 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
|
| 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, not a test: check whether an unopened item is inside the return window, then request a label from the order system. Confirm the label was created before saying the return is arranged, and route policy exceptions to a person. 1 cited claim for returns on AdaAda describes returns workflows that check order eligibility, offer permitted options and create a return label through connected systems.Vendor-reported
| 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
|
| 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, not a test: answer whether a product works with a specific phone model from the compatibility guide. Check that the reply uses the correct product version and asks for missing details instead of inventing compatibility. 1 cited claim for product questions on AdaAda uses imported knowledge to answer questions; its documentation explains that relevant passages are retrieved from that content.Vendor-reported
| 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
|
| 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, not a test: update the signed-in customer’s contact details through an authorised account API. Verify that another customer’s records cannot be changed and that failed updates are not reported as complete. 1 cited claim for account issues on AdaAda documents account updates through external APIs and sign-in tokens for sensitive actions.Vendor-reported
| 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
|
| 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, not a test: a customer says repeated delivery problems remain unresolved. Configure a route to the complaints team with the case details. Routing is documented; the reviewed sources do not measure successful complaint resolution or de-escalation. 1 cited claim for complaints on AdaAda documents routing to human support based on conversation context and configured handoff descriptions.Vendor-reported
| 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
|
| 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, not a test: a customer requests a person after an unsuccessful answer. Verify that the receiving team gets the conversation and that, outside working hours, the customer receives a clear follow-up path. 1 cited claim for human handoff on AdaAda documents live transfers, follow-up tickets, off-hours paths and error fallbacks across its handoff setup.Vendor-reported
| 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
|
| 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 Illustrative buying scenario: a small shop needs only shipping FAQs and occasional order lookups. Ask Ada to demonstrate that limited scope and the work needed to maintain it. Demo-led procurement does not establish that every small business is a poor fit. No supporting source is recorded here. Validate it with the vendor; absence of evidence does not establish a missing capability. | 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. |
| 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 Illustrative buying scenario: a growing retailer wants email and chat support connected to an existing help desk. Evaluate the exact connectors, workflow ownership and conversation volume. Employee count alone does not establish suitability. No supporting source is recorded here. Validate it with the vendor; absence of evidence does not establish a missing capability. | 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. |
| 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: a multi-brand support team needs shared knowledge with brand-specific policies and handoff routes. Request a demonstration of those boundaries. Enterprise positioning is documented; successful performance for that configuration is not established here. 1 cited claim for enterprise on AdaAda’s demo page explicitly targets enterprise customer-experience teams and proposes a tailored demonstration and implementation plan.Vendor-reported
| 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
|
| Industry evidenceRetail and e-commerce | Vendor-documented Ada's own retail and ecommerce page is the only source placing the product here. It describes returns workflows against connected commerce systems; no independent report of a retail deployment was found. 1 cited claim for retail and e-commerce on AdaAda describes returns workflows that check order eligibility, offer permitted options and create a return label through connected systems.Vendor-reported
| 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
|
| 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 Chat, voice, email and social messaging are documented. Voice and social connections use supported external platforms; confirm the intended channel integration. 1 cited claim for web and in-app chat on AdaChat, voice, email and social messaging are documented. Voice and social connections use supported external platforms; confirm the intended channel integration.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 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 Chat, voice, email and social messaging are documented. Voice and social connections use supported external platforms; confirm the intended channel integration. 1 cited claim for email on AdaChat, voice, email and social messaging are documented. Voice and social connections use supported external platforms; confirm the intended channel integration.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
| |
| Voice and phone | Vendor-documented Chat, voice, email and social messaging are documented. Voice and social connections use supported external platforms; confirm the intended channel integration. 1 cited claim for voice and phone on AdaChat, voice, email and social messaging are documented. Voice and social connections use supported external platforms; confirm the intended channel integration.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 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
|
| SMS | Not established No supporting source is recorded here. Validate it with the vendor; absence of evidence does not establish a missing capability. | 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
|
| 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. | |
| Social messaging | Vendor-documented Chat, voice, email and social messaging are documented. Voice and social connections use supported external platforms; confirm the intended channel integration. 1 cited claim for social messaging on AdaChat, voice, email and social messaging are documented. Voice and social connections use supported external platforms; confirm the intended channel integration.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 The integrations directory includes Zendesk, Salesforce, ServiceNow, Freshworks, Genesys and Help Scout. Check each entry for knowledge, messaging, email or voice support. 1 cited claim for zendesk on AdaThe integrations directory includes Zendesk, Salesforce, ServiceNow, Freshworks, Genesys and Help Scout. Check each entry for knowledge, messaging, email or voice support.Vendor-reported
| 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
|
| Salesforce | Vendor-documented The integrations directory includes Zendesk, Salesforce, ServiceNow, Freshworks, Genesys and Help Scout. Check each entry for knowledge, messaging, email or voice support. 1 cited claim for salesforce on AdaThe integrations directory includes Zendesk, Salesforce, ServiceNow, Freshworks, Genesys and Help Scout. Check each entry for knowledge, messaging, email or voice support.Vendor-reported
| 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
|
| ServiceNow | Vendor-documented The integrations directory includes Zendesk, Salesforce, ServiceNow, Freshworks, Genesys and Help Scout. Check each entry for knowledge, messaging, email or voice support. 1 cited claim for servicenow on AdaThe integrations directory includes Zendesk, Salesforce, ServiceNow, Freshworks, Genesys and Help Scout. Check each entry for knowledge, messaging, email or voice support.Vendor-reported
| 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 The integrations directory includes Zendesk, Salesforce, ServiceNow, Freshworks, Genesys and Help Scout. Check each entry for knowledge, messaging, email or voice support. 1 cited claim for freshdesk on AdaThe integrations directory includes Zendesk, Salesforce, ServiceNow, Freshworks, Genesys and Help Scout. Check each entry for knowledge, messaging, email or voice support.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 | 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 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
|
| HubSpot | 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. |
| 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 | Vendor-documented The integrations directory includes Zendesk, Salesforce, ServiceNow, Freshworks, Genesys and Help Scout. Check each entry for knowledge, messaging, email or voice support. 1 cited claim for help scout on AdaThe integrations directory includes Zendesk, Salesforce, ServiceNow, Freshworks, Genesys and Help Scout. Check each entry for knowledge, messaging, email or voice support.Vendor-reported
| 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
Ada: 9 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 · Social messagingNot established→Vendor-documented
- Help desk · ZendeskNot established→Vendor-documented
- Help desk · SalesforceNot established→Vendor-documented
- Help desk · ServiceNowNot established→Vendor-documented
- Help desk · FreshdeskNot established→Vendor-documented
- and 1 more
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
· Catalog
Launch: 22 AI customer service agents and 532 claims, every one sourced and dated
Ada: Added to the catalog with 24 claims and 9 rows with evidence.
Decagon: Added to the catalog with 26 claims and 9 rows with evidence.
Recorded before launch
Notes the profile carried when it went live, from research before launch.
Ada: Added editorial product positioning with its scope, rationale, and vendor source. Source
Ada: Rechecked current documentation; replaced merchant-review extrapolations and unsupported fit verdict inputs with scoped capabilities, named vendor examples and clearly labelled illustrative scenarios. Source
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.