Access
Try itExperimental
See what an agent can do with Decagon before you ever sign up. Pick a story: recorded sessions replay real probe-harness transcripts; commands tagged live-capable can re-run against the real endpoint from our edge, right now (▶ run live — the exact same request, live and recorded lines always labeled); sandboxed self-drive sessions are designed and gated (docs/TRY-IT.md).
$curl -si https://docs.decagon.ai/ | head -12 # finding: technical docs are login-gatedrecorded session — replayed, not liveVerified integrations
No integration evidence found in our corpus for this product yet — that means none was found, never that it doesn’t integrate.
By theme — the product's score on each story themeBy theme
Agent actions — stories about agent actions in this arenaAgent actionsevidence →
Stories about agent actions in this arena
Agenticness — how well agents can access and operate the productAgenticnessevidence →
How well agents can access and operate the product
Automation depth — how much of the product can run unattendedAutomation depthevidence →
How much of the product can run unattended
Channels languages — stories about channels languages in this arenaChannels languagesevidence →
Stories about channels languages in this arena
Escalation handoff — stories about escalation handoff in this arenaEscalation handoffevidence →
Stories about escalation handoff in this arena
Guardrails safety — stories about guardrails safety in this arenaGuardrails safetyevidence →
Stories about guardrails safety in this arena
Insights analytics — stories about insights analytics in this arenaInsights analyticsevidence →
Stories about insights analytics in this arena
Integrations platform — stories about integrations platform in this arenaIntegrations platformevidence →
Stories about integrations platform in this arena
Knowledge grounding — stories about knowledge grounding in this arenaKnowledge groundingevidence →
Stories about knowledge grounding in this arena
Openness — open source, data portability, and self-hosting storiesOpennessevidence →
Open source, data portability, and self-hosting stories
Pricing economics — stories about pricing economics in this arenaPricing economicsevidence →
Stories about pricing economics in this arena
Privacy posture — data-handling and privacy storiesPrivacy postureevidence →
Data-handling and privacy stories
Resolution quality — stories about resolution quality in this arenaResolution qualityevidence →
Stories about resolution quality in this arena
Testing qa — stories about testing qa in this arenaTesting qaevidence →
Stories about testing qa in this arena
Story verdicts — every judged story with its evidenceStory verdicts
Follow the green: where the map greys out is where Decagon stops today. ✓ full · ~ partial · ! disputed · — none · n/a not applicable.
Agent actions — stories about agent actions in this arenaAgent actions
Stories about agent actions in this arena
Agenticness — how well agents can access and operate the productAgenticness
How well agents can access and operate the product
API surface
Drive the product through a documented public API
—0/10
Subscribe to events via webhooks
—0/10
Build against official SDKs
—0/10
Issue scoped/least-privilege API credentials for an agent
~4/10
unlocks → Headless / CI
Connect an agent via an official MCP server
—0/10
Download a machine-readable API spec (OpenAPI or equivalent)
—0/10
Rely on versioned APIs with a documented deprecation policy
—0/10
Test against a sandbox environment without touching production data
~5/10
unlocks → Headless / CI
Explore an interactive API reference with runnable examples
—0/10
Docs for agents
Point an agent at llms.txt or agent-oriented docs
~6/10
Agentic features
Delegate tasks to a built-in AI assistant inside the product
~5/10
Operate the product with natural-language commands
~6/10
Plug MCP servers into this product so it can use their tools
~3/10
Get AI-generated insights and suggestions from my data inside the product
✓8/10
Set up automations that run autonomously in the background
~6/10
Automation depth — how much of the product can run unattendedAutomation depth
How much of the product can run unattended
Channels languages — stories about channels languages in this arenaChannels languages
Stories about channels languages in this arena
One agent covers chat, email, and in-app, plus the channels my customers actually use — Slack, WhatsApp, social
~5/10
The agent supports customers in many languages, even where my knowledge base exists only in English
~4/10
The agent handles phone calls — speech in, speech out — with the same knowledge and actions as chat
~6/10
Escalation handoff — stories about escalation handoff in this arenaEscalation handoff
Stories about escalation handoff in this arena
Guardrails safety — stories about guardrails safety in this arenaGuardrails safety
Stories about guardrails safety in this arena
Guardrails stop the agent from inventing policies, prices, or promises — off-knowledge questions get a safe decline, not a guess
~4/10
Launch in a supervised mode where the agent drafts replies for human approval before anything reaches a customer
—–
I mark topics as human-only — legal threats, cancellations, security — and the agent never freelances on them
~5/10
Insights analytics — stories about insights analytics in this arenaInsights analytics
Stories about insights analytics in this arena
Integrations platform — stories about integrations platform in this arenaIntegrations platform
Stories about integrations platform in this arena
Knowledge grounding — stories about knowledge grounding in this arenaKnowledge grounding
Stories about knowledge grounding in this arena
Knowledge stays current automatically — the agent re-syncs sources on a schedule or on change, not via manual re-uploads
—0/10
The platform surfaces knowledge gaps and conflicting content that cause the agent to miss or fumble questions
✓7/10
Every answer is grounded in my own content and shows which article or source it drew from
—0/10
The agent ingests my help center, docs, past tickets, and internal wikis as knowledge sources without manual re-authoring
~4/10
Openness — open source, data portability, and self-hosting storiesOpenness
Open source, data portability, and self-hosting stories
Pricing economics — stories about pricing economics in this arenaPricing economics
Stories about pricing economics in this arena
Privacy posture — data-handling and privacy storiesPrivacy posture
Data-handling and privacy stories
Resolution quality — stories about resolution quality in this arenaResolution quality
Stories about resolution quality in this arena
Answers use the customer's live data — plan, order status, account history — not just generic help articles
~6/10
The agent asks clarifying questions and works through multi-step troubleshooting instead of dumping one canned answer
~5/10
The agent fully resolves a meaningful share of conversations end-to-end — measured as resolutions, not mere deflections or bounces
~4/10
I control the agent's tone and brand voice, and it stays consistent across topics and languages
~7/10
Testing qa — stories about testing qa in this arenaTesting qa
Stories about testing qa in this arena
Sorted by importance (agentic first) (high → low) · 53/53 stories · click a row’s chevron for the rationale and evidence
Delegate tasks to a built-in AI assistant inside the product G Agentic features | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 3 | partial | 5/10 | Cclaimed | |
Plug MCP servers into this product so it can use their tools G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 3 | partial | 3/10 | Cclaimed | |
Connect an agent via an official MCP server G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 3 | none | 0/10 | ||
Drive the product through a documented public API G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 3 | none | 0/10 | ||
Get AI-generated insights and suggestions from my data inside the product G Agentic features | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | full | 8/10 | Cclaimed | |
Operate the product with natural-language commands G Agentic features | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | partial | 6/10 | Cclaimed | |
Point an agent at llms.txt or agent-oriented docs G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | partial | 6/10 | Tprobed | |
Set up automations that run autonomously in the background G Agentic features | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | partial | 6/10 | Cclaimed | |
Issue scoped/least-privilege API credentials for an agent G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | partial | 4/10 | Cclaimed | |
Build against official SDKs G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | 0/10 | ||
Download a machine-readable API spec (OpenAPI or equivalent) G Api quality | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | 0/10 | ||
Explore an interactive API reference with runnable examples G Api quality | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | 0/10 | ||
Rely on versioned APIs with a documented deprecation policy G Api quality | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | 0/10 | ||
Run the product headlessly / in CI for automation G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | 0/10 | ||
Subscribe to events via webhooks G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | 0/10 | ||
Use an official CLI G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | n/a | untested | none yet | |
Test against a sandbox environment without touching production data G Api quality | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 1 | partial | 5/10 | Cclaimed | |
The agent takes real actions through my APIs — refunds, order changes, subscription updates — with scoped auth per action C Actions | developer | Agent actions — stories about agent actions in this arenaAgent actions | 3 | partial | 6/10 | Cclaimed | |
Dashboards show resolution rate, CSAT, handoff rate, and cost per resolution — the numbers I report to my exec team C Analytics | support leader | Insights analytics — stories about insights analytics in this arenaInsights analytics | 3 | partial | 5/10 | Cclaimed | |
Define rules that trigger actions automatically on events G | ai-native user | Automation depth — how much of the product can run unattendedAutomation depth | 3 | partial | 5/10 | Cclaimed | |
Guardrails stop the agent from inventing policies, prices, or promises — off-knowledge questions get a safe decline, not a guess C Hallucination | ai-native user | Guardrails safety — stories about guardrails safety in this arenaGuardrails safety | 3 | partial | 4/10 | Cclaimed | |
The agent fully resolves a meaningful share of conversations end-to-end — measured as resolutions, not mere deflections or bounces C Resolution | support leader | Resolution quality — stories about resolution quality in this arenaResolution quality | 3 | partial | 4/10 | Cclaimed | |
The agent ingests my help center, docs, past tickets, and internal wikis as knowledge sources without manual re-authoring C Ingestion | support ops lead | Knowledge grounding — stories about knowledge grounding in this arenaKnowledge grounding | 3 | partial | 4/10 | Cclaimed | |
The agent runs inside my existing helpdesk — Zendesk, Salesforce, Intercom — or standalone, syncing tickets and context both ways C Helpdesk | developer | Integrations platform — stories about integrations platform in this arenaIntegrations platform | 3 | partial | 4/10 | Cclaimed | |
Every answer is grounded in my own content and shows which article or source it drew from C Grounding | ai-native user | Knowledge grounding — stories about knowledge grounding in this arenaKnowledge grounding | 3 | none | 0/10 | ||
Export all of my data in open formats and leave G | ai-native user | Openness — open source, data portability, and self-hosting storiesOpenness | 3 | none | 0/10 | ||
Prevent my data from being used to train AI models G | ai-native user | Privacy posture — data-handling and privacy storiesPrivacy posture | 3 | none | untested | none yet | |
Self-host the core product G | ai-native user | Openness — open source, data portability, and self-hosting storiesOpenness | 3 | n/a | untested | none yet | |
When the agent escalates, the human gets the full conversation, a summary, and collected details — the customer never repeats themselves C Handoff | support leader | Escalation handoff — stories about escalation handoff in this arenaEscalation handoff | 3 | none | untested | none yet | |
I test the agent against historical tickets or simulated conversations before it faces real customers C Simulation | support ops lead | Testing qa — stories about testing qa in this arenaTesting qa | 2 | full | 8/10 | Cclaimed | |
I encode standard operating procedures the agent follows step-by-step for known issue types, with deterministic branching C Procedures | support ops lead | Agent actions — stories about agent actions in this arenaAgent actions | 2 | full | 7/10 | Cclaimed | |
Answers use the customer's live data — plan, order status, account history — not just generic help articles C Personalization | support leader | Resolution quality — stories about resolution quality in this arenaResolution quality | 2 | partial | 6/10 | Cclaimed | |
The agent handles phone calls — speech in, speech out — with the same knowledge and actions as chat C Voice | support leader | Channels languages — stories about channels languages in this arenaChannels languages | 2 | partial | 6/10 | Cclaimed | |
I mark topics as human-only — legal threats, cancellations, security — and the agent never freelances on them C Topic controls | support ops lead | Guardrails safety — stories about guardrails safety in this arenaGuardrails safety | 2 | partial | 5/10 | Cclaimed | |
One agent covers chat, email, and in-app, plus the channels my customers actually use — Slack, WhatsApp, social C Channels | support leader | Channels languages — stories about channels languages in this arenaChannels languages | 2 | partial | 5/10 | Cclaimed | |
The agent asks clarifying questions and works through multi-step troubleshooting instead of dumping one canned answer C Reasoning | support leader | Resolution quality — stories about resolution quality in this arenaResolution quality | 2 | partial | 5/10 | Cclaimed | |
I configure when the agent must hand off — by topic, sentiment, customer tier, or explicit request — and it reliably obeys C Rules | support ops lead | Escalation handoff — stories about escalation handoff in this arenaEscalation handoff | 2 | partial | 4/10 | Cclaimed | |
The agent supports customers in many languages, even where my knowledge base exists only in English C Languages | support leader | Channels languages — stories about channels languages in this arenaChannels languages | 2 | partial | 4/10 | Cclaimed | |
Control data retention and deletion G | ai-native user | Privacy posture — data-handling and privacy storiesPrivacy posture | 2 | partial | 3/10 | Cclaimed | |
Do everything through the API that I can do in the UI G | ai-native user | Openness — open source, data portability, and self-hosting storiesOpenness | 2 | none | 0/10 | ||
Knowledge stays current automatically — the agent re-syncs sources on a schedule or on change, not via manual re-uploads C Freshness | support ops lead | Knowledge grounding — stories about knowledge grounding in this arenaKnowledge grounding | 2 | none | 0/10 | ||
Choose where my data is stored (region/residency) G | ai-native user | Privacy posture — data-handling and privacy storiesPrivacy posture | 2 | none | untested | none yet | |
Launch in a supervised mode where the agent drafts replies for human approval before anything reaches a customer C Supervision | support ops lead | Guardrails safety — stories about guardrails safety in this arenaGuardrails safety | 2 | none | untested | none yet | |
Opt out of telemetry and usage tracking G | ai-native user | Privacy posture — data-handling and privacy storiesPrivacy posture | 2 | none | untested | none yet | |
Perform bulk operations across many items at once G | ai-native user | Automation depth — how much of the product can run unattendedAutomation depth | 2 | none | untested | none yet | |
Pricing is outcome-based and published — I pay per resolution with caps and controls, not an opaque enterprise quote G Pricing | support leader | Pricing economics — stories about pricing economics in this arenaPricing economics | 2 | none | untested | none yet | |
Read the product's source under an open license G | ai-native user | Openness — open source, data portability, and self-hosting storiesOpenness | 2 | n/a | untested | none yet | |
Schedule recurring jobs or workflows G | ai-native user | Automation depth — how much of the product can run unattendedAutomation depth | 2 | none | untested | none yet | |
AI conversations get ongoing QA — scored samples, flagged failures, and a review loop that feeds fixes back into the agent C Qa | support ops lead | Testing qa — stories about testing qa in this arenaTesting qa | 1 | full | 8/10 | Cclaimed | |
I control the agent's tone and brand voice, and it stays consistent across topics and languages C Voice | support leader | Resolution quality — stories about resolution quality in this arenaResolution quality | 1 | partial | 7/10 | Cclaimed | |
The platform clusters conversations by topic and surfaces emerging product issues before they spike ticket volume C Insights | support leader | Insights analytics — stories about insights analytics in this arenaInsights analytics | 1 | partial | 7/10 | Cclaimed | |
The platform surfaces knowledge gaps and conflicting content that cause the agent to miss or fumble questions C Gaps | support ops lead | Knowledge grounding — stories about knowledge grounding in this arenaKnowledge grounding | 1 | full | 7/10 | Cclaimed | |
Version, review, and roll back my automations G | ai-native user | Automation depth — how much of the product can run unattendedAutomation depth | 1 | partial | 4/10 | Cclaimed |
Opportunities — the stories that would move this product's scores, from its own judged verdictsOpportunitiestop 8 of 45 stories with headroom
What would move Decagon’s scores — derived from its own judged verdicts, biggest headroom first. Each line quotes what the judge found missing; shipping it (or evidencing it publicly) is the fix.
Agenticness — how well agents can access and operate the productConnect an agent via an official MCP server
nonemoves agent-readyimpact 45
Decagon's MCP blog post (decagon-docs-3) discusses using MCP to curate/scope tool access for its own agents (i.e., Decagon as an MCP client consuming external tools), not exposing an official MCP server that lets an external AI agent connect into Decagon.
Agenticness — how well agents can access and operate the productDrive the product through a documented public API
nonemoves agent-readyimpact 45
No evidence of a documented public API; the openapi probe returned 404s across all candidate paths and no docs reference an API reference, SDK, or programmatic endpoint.
Agenticness — how well agents can access and operate the productPlug MCP servers into this product so it can use their tools
partialq3/10moves agent-readyimpact 31.5
Missing: technical setup docs for adding an MCP server, list of supported MCP servers/tools, hands-on or independent verification that agents actually invoke MCP tools.
Escalation handoff — stories about escalation handoff in this arenaWhen the agent escalates, the human gets the full conversation, a summary, and collected details — the customer never repeats themselves
nonemoves PA Scoreimpact 30
The evidence pack contains no mention of escalation-to-human handoff, conversation summaries handed to agents, or collected-details transfer preventing repetition.
Knowledge grounding — stories about knowledge grounding in this arenaEvery answer is grounded in my own content and shows which article or source it drew from
nonemoves PA Scoreimpact 30
Missing: any documentation of inline citations, source attribution UI, or 'view source' feature in chat/voice/email responses.
Openness — open source, data portability, and self-hosting storiesExport all of my data in open formats and leave
nonemoves PA Scoreimpact 30
Decagon's evidence pack contains no documented data-export feature, open-format export tooling, or account-deletion/portability workflow; the only tangential mention ("data portability and control" in decagon-docs-28) is vague marketing language about maintaining conversation context, not a concrete export/exit mechanism, and the probe shows no public API/OpenAPI spec that could support programmatic data extraction.
Privacy posture — data-handling and privacy storiesPrevent my data from being used to train AI models
nonemoves PA Scoreimpact 30
No evidence in the pack addresses data usage for AI model training or an opt-out/no-training policy; the security page covers JWT tokens and SSO but not training data practices.
Agenticness — how well agents can access and operate the productRun the product headlessly / in CI for automation
nonemoves agent-readyimpact 30
Missing: any CLI/SDK for headless execution, CI-pipeline integration docs, or public API reference enabling automation.
Showing the top 8 of 45 — every none/partial verdict in the story verdicts table is headroom.
Think a verdict is wrong? Every verdicts-table row has a Flag link — see the methodology.
Coverage map — which docs area, API section, or community source covers which judged storiesCoverage map7 surfaces · 30 covered stories
Where the cited evidence behind each covered verdict came from — the same citations the verdicts table shows, no extra judging.
Product docs26 stories
- The agent takes real actions through my APIs — refunds, order changes, subscription updates — with scoped auth per action
- I encode standard operating procedures the agent follows step-by-step for known issue types, with deterministic branching
- Get AI-generated insights and suggestions from my data inside the product
- Set up automations that run autonomously in the background
- Delegate tasks to a built-in AI assistant inside the product
- Operate the product with natural-language commands
- Test against a sandbox environment without touching production data
- Define rules that trigger actions automatically on events
- Version, review, and roll back my automations
- One agent covers chat, email, and in-app, plus the channels my customers actually use — Slack, WhatsApp, social
- The agent supports customers in many languages, even where my knowledge base exists only in English
- The agent handles phone calls — speech in, speech out — with the same knowledge and actions as chat
- I configure when the agent must hand off — by topic, sentiment, customer tier, or explicit request — and it reliably obeys
- Guardrails stop the agent from inventing policies, prices, or promises — off-knowledge questions get a safe decline, not a guess
- I mark topics as human-only — legal threats, cancellations, security — and the agent never freelances on them
- Dashboards show resolution rate, CSAT, handoff rate, and cost per resolution — the numbers I report to my exec team
- The platform clusters conversations by topic and surfaces emerging product issues before they spike ticket volume
- The agent runs inside my existing helpdesk — Zendesk, Salesforce, Intercom — or standalone, syncing tickets and context both ways
- The platform surfaces knowledge gaps and conflicting content that cause the agent to miss or fumble questions
- The agent ingests my help center, docs, past tickets, and internal wikis as knowledge sources without manual re-authoring
- Answers use the customer's live data — plan, order status, account history — not just generic help articles
- The agent asks clarifying questions and works through multi-step troubleshooting instead of dumping one canned answer
- The agent fully resolves a meaningful share of conversations end-to-end — measured as resolutions, not mere deflections or bounces
- I control the agent's tone and brand voice, and it stays consistent across topics and languages
- AI conversations get ongoing QA — scored samples, flagged failures, and a review loop that feeds fixes back into the agent
- I test the agent against historical tickets or simulated conversations before it faces real customers
Proactive agents docs7 stories
- Set up automations that run autonomously in the background
- Define rules that trigger actions automatically on events
- One agent covers chat, email, and in-app, plus the channels my customers actually use — Slack, WhatsApp, social
- The agent handles phone calls — speech in, speech out — with the same knowledge and actions as chat
- The agent runs inside my existing helpdesk — Zendesk, Salesforce, Intercom — or standalone, syncing tickets and context both ways
- Control data retention and deletion
- The agent asks clarifying questions and works through multi-step troubleshooting instead of dumping one canned answer
Blog docs6 stories
- The agent takes real actions through my APIs — refunds, order changes, subscription updates — with scoped auth per action
- Plug MCP servers into this product so it can use their tools
- The agent runs inside my existing helpdesk — Zendesk, Salesforce, Intercom — or standalone, syncing tickets and context both ways
- Answers use the customer's live data — plan, order status, account history — not just generic help articles
- The agent asks clarifying questions and works through multi-step troubleshooting instead of dumping one canned answer
- The agent fully resolves a meaningful share of conversations end-to-end — measured as resolutions, not mere deflections or bounces
Security docs5 stories
- The agent takes real actions through my APIs — refunds, order changes, subscription updates — with scoped auth per action
- Issue scoped/least-privilege API credentials for an agent
- The agent runs inside my existing helpdesk — Zendesk, Salesforce, Intercom — or standalone, syncing tickets and context both ways
- Control data retention and deletion
- Answers use the customer's live data — plan, order status, account history — not just generic help articles
Probe proofs — replayable recordings from the probe harnessProbe proofs
Replayable recordings from our probe harness — see the Prove-It protocol to submit one.
$curl -si https://docs.decagon.ai/ | head -12 # finding: technical docs are login-gatedreproduced$ curl -si https://docs.decagon.ai/ | head -12 # finding: technical docs are login-gated HTTP/2 307 cache-control: public, max-age=0, must-revalidate content-type: text/plain date: Thu, 10 Sep 2026 18:40:32 GMT location: /login?redirect=%2F server: Vercel strict-transport-security: max-age=63072000 x-frame-options: DENY x-vercel-id: sfo1::nxz48-1789065632478-27ce6bc4497d Redirecting...
$curl -s https://decagon.ai/sitemap.xml | grep -o 'https://decagon.ai/product/[^<]*' | sort | head -12reproduced$ curl -s https://decagon.ai/sitemap.xml | grep -o 'https://decagon.ai/product/[^<]*' | sort | head -12 https://decagon.ai/product/aop https://decagon.ai/product/chat https://decagon.ai/product/duet https://decagon.ai/product/email https://decagon.ai/product/experiments https://decagon.ai/product/insights-and-reporting https://decagon.ai/product/integrations https://decagon.ai/product/overview https://decagon.ai/product/suggestions https://decagon.ai/product/testing-qa https://decagon.ai/product/voice https://decagon.ai/product/watchtower
$curl -s https://decagon.ai/llms.txt | head -8reproduced$ curl -s https://decagon.ai/llms.txt | head -8 # Decagon Decagon is an enterprise-grade AI platform revolutionizing customer support through the use of advanced conversational AI agents. It stands out from other platforms by offering a comprehensive AI agent engine, which acts as a data flywheel, enabling intelligent, context-aware, and seamless customer interactions across various channels like chat, SMS, email, and voice. Decagon's platform emphasizes accuracy, empathy, and continuous learning, allowing AI agents to improve with each interaction and provide dynamic, personalized answers. It also offers comprehensive features like routing, insights, QA, transparency, and more. Unlike traditional chatbots, Decagon's AI agents can take real-time actions, such as creating tickets and updating knowledge bases, to effectively resolve customer issues. Security and scalability are also core strengths, making it a preferred choice for world-class companies seeking to enhance their customer experience while maintaining high standards of data privacy. ## Resources
Claims vs evidence — vendor claims reconciled against independent verdictsClaims vs evidence
0 of 13 testable claims verified · 0 contradicted → integrity 0/100
18 distinct capability claims found in Decagon’s own claimed-docs/GitHub materials, reconciled against our judge’s independent verdicts.
0
Verified
13
Unverified
0
Contradicted
17
Undersold
Unverified (16)
“Technical teams retain full visibility and control over guardrails, integrations, and versioning of the agent”
“Agents use short-lived, scoped JWT tokens for real-time system access, discarded after each session”
Issue scoped/least-privilege API credentials for an agentpartialproof ↗
“Browser Actions let the agent log in, navigate, and complete tasks inside any system via computer use”
The agent takes real actions through my APIs — refunds, order changes, subscription updates — with scoped auth per actionpartialproof ↗
“Non-technical teams can define and adjust agent behavior in natural language, similar to writing human-agent SOPs”
I encode standard operating procedures the agent follows step-by-step for known issue types, with deterministic branchingfullproof ↗
“Past customer interactions are analyzed to auto-generate Agent Operating Procedures based on real customer needs”
I encode standard operating procedures the agent follows step-by-step for known issue types, with deterministic branchingfullproof ↗
“Watchtower lets you define flagging criteria in natural language (e.g. frustration, policy violations) and applies it contextually”
AI conversations get ongoing QA — scored samples, flagged failures, and a review loop that feeds fixes back into the agentfullproof ↗
“Ask open-ended natural-language questions like 'why are customers requesting refunds?' to instantly analyze conversations”
The platform clusters conversations by topic and surfaces emerging product issues before they spike ticket volumepartialproof ↗
“Automatically detects knowledge gaps and drafts help-center content based on how top human agents resolved similar issues”
The platform surfaces knowledge gaps and conflicting content that cause the agent to miss or fumble questionsfullproof ↗
“Duet can auto-generate tests covering diverse conversation paths to verify accuracy, policy adherence, and brand tone”
I test the agent against historical tickets or simulated conversations before it faces real customersfullproof ↗
“Chat agent works across web, mobile, and messaging platforms with on-brand styling”
One agent covers chat, email, and in-app, plus the channels my customers actually use — Slack, WhatsApp, socialpartialproof ↗
“Voice AI agents handle natural, multilingual phone conversations customized to brand voice”
The agent handles phone calls — speech in, speech out — with the same knowledge and actions as chatpartialproof ↗
“Voice AI agents handle natural, multilingual phone conversations customized to brand voice”
The agent supports customers in many languages, even where my knowledge base exists only in Englishpartialproof ↗
“Email agent understands context, stays on brand, and manages complex multi-message customer threads”
One agent covers chat, email, and in-app, plus the channels my customers actually use — Slack, WhatsApp, socialpartialproof ↗
“Customizable visual heatmaps make it easy to spot spikes or dips in key support metrics”
Dashboards show resolution rate, CSAT, handoff rate, and cost per resolution — the numbers I report to my exec teampartialproof ↗
“Agent carries conversation history across sessions and proactively recommends actions based on customer signals”
Answers use the customer's live data — plan, order status, account history — not just generic help articlespartialproof ↗
“Can initiate proactive, on-brand outbound calls timed to key moments in the customer journey”
The agent handles phone calls — speech in, speech out — with the same knowledge and actions as chatpartialproof ↗
Undersold (17)
Point an agent at llms.txt or agent-oriented docspartialproof ↗
Plug MCP servers into this product so it can use their toolspartialproof ↗
Get AI-generated insights and suggestions from my data inside the productfullproof ↗
Set up automations that run autonomously in the backgroundpartialproof ↗
Delegate tasks to a built-in AI assistant inside the productpartialproof ↗
Operate the product with natural-language commandspartialproof ↗
Test against a sandbox environment without touching production datapartialproof ↗
Define rules that trigger actions automatically on eventspartialproof ↗
I configure when the agent must hand off — by topic, sentiment, customer tier, or explicit request — and it reliably obeyspartialproof ↗
Guardrails stop the agent from inventing policies, prices, or promises — off-knowledge questions get a safe decline, not a guesspartialproof ↗
I mark topics as human-only — legal threats, cancellations, security — and the agent never freelances on thempartialproof ↗
The agent runs inside my existing helpdesk — Zendesk, Salesforce, Intercom — or standalone, syncing tickets and context both wayspartialproof ↗
The agent ingests my help center, docs, past tickets, and internal wikis as knowledge sources without manual re-authoringpartialproof ↗
The agent asks clarifying questions and works through multi-step troubleshooting instead of dumping one canned answerpartialproof ↗
The agent fully resolves a meaningful share of conversations end-to-end — measured as resolutions, not mere deflections or bouncespartialproof ↗
I control the agent's tone and brand voice, and it stays consistent across topics and languagespartialproof ↗
Claims outside our story set (3)
Real capability claims found in Decagon’s own materials, but no story in this arena’s taxonomy covers them yet — that’s feedback on the taxonomy, not a mark against the product.
“A purpose-built infrastructure layer curates, scopes, and evaluates how the agent's tools are actually used”
source ↗“Run controlled experiments by defining a variable and traffic split, measured against a control group in production”
source ↗“Integrates with identity providers like Okta and Microsoft Entra for secure, passwordless access across systems”
source ↗
Business model
Enterprise-only custom quotes; usage-based per-conversation or per-resolution pricing. No public price list (third parties report roughly $0.99/conversation and ~$50K annual minimums).
pricing ↗Score trend
How this product’s scores have moved as evidence and verdicts are re-derived — a point per change, not per day.
Try Experimental
Run it in the microterminal →Recorded agent sessions — and a live MCP handshake where the vendor ships one.
Flag
⚑ Flag a verdictThink a verdict is wrong? Opens a prefilled GitHub issue — or use the ⚑ next to any verdict above.
For agents
Agent surface uptime llms.txt up (tracking since Sep 11 '26)