Comparison
Decagon vs Zendesk AI Agents
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
Zendesk AI Agents
Vendor-hosted service within Zendesk Support and Suite. Feature access and advanced integrations vary by package.Vendor-reported
- Source
- Zendesk plans and AI agent availability
- Checked
- History
- First published
- Correct this
- Request a correction with a public source. Claim ID
zendesk-cmp-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
Zendesk AI Agents
Zendesk documents API calls for live order lookups, with a different implementation path for AI Agents Advanced. Confirm required write actions and permissions separately.Vendor-reported
- Source
- How can I link my AI agent with my customer orders? (Zendesk help)
- Checked
- History
- First published
- Correct this
- Request a correction with a public source. Claim ID
zendesk-cmp-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
Zendesk AI Agents
Escalates to human teams with context according to Zendesk. Confirm queue routing, contact details, and reply-channel behavior in the intended setup.Vendor-reported
- Source
- Zendesk AI Agents product overview
- Checked
- History
- First published
- Correct this
- Request a correction with a public source. Claim ID
zendesk-cmp-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
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 | Decagon | Zendesk AI Agents |
|---|---|---|
| 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 within Zendesk Support and Suite. Feature access and advanced integrations vary by package.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
| Zendesk advertises web, mobile, social, email, and voice. Check channel-specific documentation and availability for the selected agent.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
| Zendesk advertises support for 80 languages. Confirm the required channel separately; the voice announcement describes an early access rollout rather than identical availability everywhere.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
| Native Zendesk deployment is the scope of this profile. Zendesk also markets Forethought agents for other service platforms; confirm those connectors and capabilities separately.Vendor-reported
|
| Knowledge sources | Decagon documents knowledge synchronization from Confluence, Contentful and Kustomer.Vendor-reported
| Zendesk help centres and external content brought in through crawlers or knowledge connectors. External content reflects its most recent sync.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
| Zendesk documents API calls for live order lookups, with a different implementation path for AI Agents Advanced. Confirm required write actions and permissions separately.Vendor-reported
|
| Human handoff | Documented options include chat escalation, email routing and transfer of voice calls to a human agent.Vendor-reported
| Escalates to human teams with context according to Zendesk. Confirm queue routing, contact details, and reply-channel behavior in the intended setup.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
| Support and Suite plans span different service needs, with enterprise options available. Company size is not a tested suitability criterion.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
| Zendesk's Babbel story reports more than 50% AI automation. This is a vendor-published customer result, not our benchmark or an expected rate for another business.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 subscriber asks when renewal is due. Connect the authenticated account to the billing record and limit allowed changes. Babbel provides a concrete vendor-published example; a disputed charge would require different rules and human review. 1 cited claim for billing on Zendesk AI AgentsZendesk's Babbel case study describes subscription-status answers and self-service subscription management through Babbel's backend APIs. It does not establish general invoice, refund, or charge-dispute performance.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 whether an order has shipped. The workflow needs an authorised order lookup and a response for missing or stale tracking data. Integration work is a prerequisite, not evidence that Zendesk is a poor fit for orders. 1 cited claim for orders on Zendesk AI AgentsZendesk documents an order-status use case and a separate integration path using API calls to retrieve order data. Implementation differs for AI Agents Advanced.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 wants to return an item outside the normal window. Connect the order record, encode the policy, and route exceptions to the appropriate person. Confirm any refund action and duplicate-request handling in the chosen package. 1 cited claim for returns on Zendesk AI AgentsZendesk lists returns and refund requests as topics that can trigger a configured procedure, dialogue, or reply. Defining the topic alone does not implement a return or issue a refund.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 about a feature available only on one plan. Use current plan-specific content and verify that the answer includes the relevant restriction. The email reports in the limitations section are reasons to check response length and context handling, not proof that this entire use case fails. 1 cited claim for product questions on Zendesk AI AgentsZendesk documents generated answers from connected help centres and external knowledge sources, with article permissions applied to restricted content.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: a customer cannot sign in. A reset guide can be answered from documentation; changing an email address or unlocking an account needs identity checks and an authorised backend action. Evaluate those as separate tasks. 1 cited claim for account issues on Zendesk AI AgentsZendesk's industry guidance lists password resets and subscription updates as AI-agent use cases. It does not provide evidence that every identity or account-recovery flow is preconfigured.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 disputes a repeated failed delivery. Check that the complaint becomes a ticket for the correct team, with context and a clear next step. Confirm the required intelligent-triage entitlement and triggers rather than assuming the AI agent enables them automatically. 1 cited claim for complaints on Zendesk AI AgentsZendesk documents platform triggers that route negative-sentiment tickets to a selected group and set priority. This supports complaint routing; it does not demonstrate autonomous complaint resolution.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
| External report Illustrative scenario: a customer asks for a human after troubleshooting. Verify contact capture, transcript transfer, destination queue, and the ability to reply on the intended channel. The cited community workaround shows one implementation path, not a general handoff success rate. 2 cited claims for human handoff on Zendesk AI AgentsZendesk states that its AI agents can escalate to human teams with conversation context.Vendor-reported
Kārlis Stenders describes collecting an issue description conversationally so it appears in the transcript during an Advanced AI Agent messaging handoff. The same post reports form limitations and corrects a custom workaround; it does not quantify reliability.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 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 uses an existing Zendesk inbox for FAQs and human escalation. Assess setup ownership, expected usage, and required features. Plan availability is not proof that the package is affordable or appropriate for every small business. 1 cited claim for small businesses on Zendesk AI AgentsZendesk includes AI-agent access in Support and Suite plans; advanced features and add-ons depend on the selected package.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 support team needs one process across email and messaging. Confirm whether knowledge, routing, and actions behave consistently on both channels. Company size alone does not establish this operational fit. 1 cited claim for mid-market on Zendesk AI AgentsZendesk describes Suite as a multi-channel service package with ticketing, messaging, help-centre content, and AI agents.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 business units require separate permissions and approval paths. Confirm how those controls apply to the selected AI agent, connected systems, and data. Validate operational boundaries before expanding to sensitive workflows. 1 cited claim for enterprise on Zendesk AI AgentsZendesk lists enterprise options with approval workflows, sandbox access, and custom roles. These are package capabilities, not a guarantee that every AI workflow meets enterprise requirements.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
| Not established No supporting source is recorded here. Validate it with the vendor; absence of evidence does not establish a missing capability. |
| 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 Zendesk advertises web, mobile, social, email, and voice. Check channel-specific documentation and availability for the selected agent. 1 cited claim for web and in-app chat on Zendesk AI AgentsZendesk advertises web, mobile, social, email, and voice. Check channel-specific documentation and availability for the selected agent.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 Zendesk advertises web, mobile, social, email, and voice. Check channel-specific documentation and availability for the selected agent. 1 cited claim for email on Zendesk AI AgentsZendesk advertises web, mobile, social, email, and voice. Check channel-specific documentation and availability for the selected agent.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
| Vendor-documented Zendesk advertises web, mobile, social, email, and voice. Check channel-specific documentation and availability for the selected agent. 1 cited claim for voice and phone on Zendesk AI AgentsZendesk advertises web, mobile, social, email, and voice. Check channel-specific documentation and availability for the selected agent.Vendor-reported
|
| 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
| 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. | Not established No supporting source is recorded here. Validate it with the vendor; absence of evidence does not establish a missing capability. | |
| 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 Zendesk advertises web, mobile, social, email, and voice. Check channel-specific documentation and availability for the selected agent. 1 cited claim for social messaging on Zendesk AI AgentsZendesk advertises web, mobile, social, email, and voice. Check channel-specific documentation and availability for the selected agent.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 Native Zendesk deployment is the scope of this profile. Zendesk also markets Forethought agents for other service platforms; confirm those connectors and capabilities separately. 1 cited claim for zendesk on Zendesk AI AgentsNative Zendesk deployment is the scope of this profile. Zendesk also markets Forethought agents for other service platforms; confirm those connectors and capabilities separately.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
| 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 | 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. |
| 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
| Not established No supporting source is recorded here. Validate it with the vendor; absence of evidence does not establish a missing capability. |
| 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 | 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
Zendesk AI Agents: 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 · Social messagingNot established→Vendor-documented
- Help desk · ZendeskNot established→Vendor-documented
· 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.
Zendesk AI Agents: Added to the catalog with 28 claims and 10 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.
Zendesk AI Agents: Added editorial product positioning with its scope, rationale, and vendor source. Source
Zendesk AI Agents: Rechecked product documentation, a named customer example, and firsthand community reports. Removed launch coverage as independent success evidence, replaced blanket fit judgments with conditional scenarios, and distinguished setup prerequisites from failures. Source