Comparison
Decagon vs Sierra
Compare documented workflows and implementation requirements using attributed public sources. Facts last checked , the earlier of the two records. Machine-readable record.
Start with your setup
These are documented product differences and requirements. A feature list or a single customer report does not establish which agent will perform better for your team.
Deployment model
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
Sierra
Sierra documents configuration through Agent Studio and custom integrations for proprietary systems. Deployment work includes defining journeys and connecting the systems those journeys use.Vendor-reported
- Source
- Agent Studio (Sierra)
- Checked
- History
- First published
- Correct this
- Request a correction with a public source. Claim ID
sierra-deployment
Actions in backend systems
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
Sierra
The SDK lists subscription updates and warranty submissions as examples of actions through connected systems. Required permissions and workflow configuration depend on the implementation.Vendor-reported
- Source
- Agent SDK (Sierra)
- Checked
- History
- First published
- Correct this
- Request a correction with a public source. Claim ID
sierra-actions
Human handoff
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
Sierra
The SDK documents routing to a team member with an automatic conversation summary.Vendor-reported
- Source
- Agent SDK (Sierra)
- Checked
- History
- First published
- Correct this
- Request a correction with a public source. Claim ID
sierra-handoff
Side by side
Product attributes first, then what the sources establish for each customer workflow, then the industries they place each agent in. Open any claim to see its source, the date it was checked, and how to request a correction. Two agents are rarely documented to the same depth, so read a difference between the two columns as a difference in the public record before reading it as a difference in the products.
What this agent was judged by
The independent evidence behind these states comes mainly from practitioner forums and buyer reviews.States rest on 1 independent source across practitioner forums and buyer reviews. This is not the same yardstick for every agent, and that asymmetry is a known limitation.
What this agent was judged by
No independent source has been found for any fit area, so every state here rests on vendor material or nothing.States rest on 0 independent sources. This is not the same yardstick for every agent, and that asymmetry is a known limitation.
| Attribute | Decagon | Sierra |
|---|---|---|
| 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
| Sierra documents configuration through Agent Studio and custom integrations for proprietary systems. Deployment work includes defining journeys and connecting the systems those journeys use.Vendor-reported
|
| Channels | 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
| Vendor-listed channels include phone, website and app chat, WhatsApp, Apple Business Chat, SMS and email. Live Assist supports staff, and Sierra also documents publishing selected agent journeys to ChatGPT.Vendor-reported
|
| Languages | 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
| The current Channels page describes voice models tuned for 60+ locales. A locale is not the same as a language; verify the exact language, accent and channel required for your deployment.Vendor-reported
|
| Help desk and CRM integrations | The integration page names Salesforce, Intercom and Zendesk for tickets and customer data, and Amazon Connect and RingCentral for telephony.Vendor-reported
| Agent Studio lists 40+ prebuilt integrations for knowledge, systems of record and contact centers, but this page does not identify the help-desk connectors. Confirm your help desk and required handoff behavior with Sierra.Vendor-reported
|
| Knowledge sources | Decagon documents knowledge synchronization from Confluence, Contentful and Kustomer.Vendor-reported
| The SDK documents ingestion of company FAQs, policies and documentation into its knowledge engine.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
| The SDK lists subscription updates and warranty submissions as examples of actions through connected systems. Required permissions and workflow configuration depend on the implementation.Vendor-reported
|
| Human handoff | Documented options include chat escalation, email routing and transfer of voice calls to a human agent.Vendor-reported
| The SDK documents routing to a team member with an automatic conversation summary.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
| Sierra’s public customer examples include AOL, Minted and Ramp. These show deployments in established businesses; they do not define a minimum viable team size.Vendor-reported
|
| Vendor-reported performance claims | 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
| Sierra reports 90% case resolution at Ramp. This is a vendor-published customer result with no common benchmark population supplied here; it should not be compared directly with another vendor’s deflection or resolution figure.Vendor-reported
|
| Workflow evidenceBilling Illustrative scenario I was charged twice for the same order. Can you refund the extra payment? What to verify: Verify identity, inspect payment records, apply the refund policy, and confirm the payment-system result. If no authorized refund action is connected, hand off with the evidence. | Vendor-documented Illustrative 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 evaluation: ask why a subscription charge increased, then request a card update. Verify identity checks, the source of the billing explanation and the permitted update path. 1 cited claim for billing on SierraSierra’s AOL case study describes explanations of outstanding balances, billing history and payment-method updates. The example is AOL’s configured agent, not a guarantee that every Sierra deployment includes billing access.Vendor-reported
|
| Workflow evidenceOrders Illustrative scenario My order has not arrived. Where is it? What to verify: Retrieve the correct order and current carrier status. Distinguish a real tracking update from an estimate; do not invent a delivery date. | Vendor-documented Illustrative 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 evaluation: use a split shipment with one delayed item. Require the agent to distinguish production status from carrier status and avoid promising a delivery date that the connected system does not provide. 1 cited claim for orders on SierraSierra’s Minted case study describes order updates across design approval, printing and shipping, plus priority-shipping changes for delayed orders. This supports an order-management use case in that deployment.Vendor-reported
|
| Workflow evidenceReturns Illustrative scenario I bought this 12 days ago and opened the box. Can I return it? What to verify: Check the actual return window, product exclusions, and order record. A policy answer and an executed return are different capabilities. | Vendor-documented Illustrative 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 evaluation: request an exchange for an item outside the normal return window. Check the configured exception policy, approval requirement and final state in the order system. 1 cited claim for returns on SierraSierra’s retail page lists refund requests and exchanges among supported workflows. It does not specify a universal return-policy configuration or prove that a particular refund reaches the payment processor.Vendor-reported
|
| Workflow evidenceProduct questions Illustrative scenario Does this adapter work with my exact laptop model? What to verify: Use a current, approved compatibility source. Ask for the model when missing and distinguish documented compatibility from an assumption. | Vendor-documented Illustrative 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 evaluation: ask whether an accessory works with an older product model. Supply an approved compatibility source and check that missing information leads to clarification rather than an invented answer. 1 cited claim for product questions on SierraSierra describes grounding answers in company knowledge, policies and brand guidance. That provides a route to product answers based on supplied content; it does not establish accuracy for a buyer’s catalog.Vendor-reported
|
| Workflow evidenceAccount issues Illustrative scenario I lost access to my email. Change the address on my account. What to verify: Follow the approved identity-recovery process before accessing or changing account data. Escalate when identity cannot be verified. | Vendor-documented Illustrative 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 evaluation: an authenticated cardholder requests a replacement card and address change. Check permissions, address confirmation and the resulting card state before considering the journey complete. 1 cited claim for account issues on SierraSierra’s Ramp case study describes card locking and replacement, address validation and transaction explanations. These are account actions in Ramp’s configured implementation; password recovery and other account workflows require their own evidence.Vendor-reported
|
| Workflow evidenceComplaints Illustrative scenario I have contacted you three times and the problem is still unresolved. What to verify: Recognize the repeat complaint, retain relevant history, and route it to the right team. Do not promise compensation outside the policy. | Vendor-documented Illustrative 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 evaluation: a customer repeats a cancellation request after rejecting a retention offer. Check that the configured flow respects the refusal and provides the agreed cancellation or human-escalation path. 1 cited claim for complaints on SierraSierra says its agents can recognize frustration and adapt their responses. This is a vendor claim about conversational behavior, not a measured result for complaint resolution or customer satisfaction.Vendor-reported
|
| Workflow evidenceHuman handoff Illustrative scenario Please connect me to a person who can approve this exception. What to verify: Transfer to an available team with the conversation and relevant records. Outside working hours, explain the actual follow-up path rather than promise immediate contact. | External report Illustrative evaluation: request a human after an unsuccessful troubleshooting step. Check queue routing, transcript transfer, repeated questions and the offline fallback. 2 cited claims for human handoff on DecagonDecagon documents live-chat escalation, email handoff and voice transfer to human agents.Vendor-reported
Krishan Y.’s August 12, 2026 review says their team can step in when human attention is needed. This corroborates takeover in one self-reported deployment, without measuring routing accuracy or waiting time.Independent report
| Vendor-documented Illustrative evaluation: request a person during a failed account update. Check queue routing, transcript and summary delivery, plus what the customer sees when the team is offline. 1 cited claim for human handoff on SierraSierra’s SDK page documents routing an escalated conversation to a team member with a generated summary. It does not establish how quickly a human answers in a particular contact center.Vendor-reported
|
| Workflow evidenceSmall businesses Illustrative scenario A two-person support team wants to launch without a dedicated engineer. What to verify: Validate setup effort, existing help-desk support, required integrations, and ongoing maintenance. A small customer's story alone does not establish suitability for every small business. | 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. | Not established Business size alone does not establish suitability. Illustrative buying scenario: a small team needs one FAQ channel; ask for the implementation work and ongoing maintenance required for that scope before deciding whether the platform is proportionate. No supporting source is recorded here. Validate it with the vendor; absence of evidence does not establish a missing capability. |
| Workflow evidenceMid-market Illustrative scenario A growing support team needs separate queues and connected order and account systems. What to verify: Validate routing, permissions, integration ownership, and handling of each team's policies in the intended configuration. | 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. | Not established The reviewed sources do not establish a universal mid-market fit. Illustrative buying scenario: a growing retailer needs order support across two brands; evaluate connector coverage, ownership of policy updates and support capacity for that deployment. No supporting source is recorded here. Validate it with the vendor; absence of evidence does not establish a missing capability. |
| Workflow evidenceEnterprise Illustrative scenario A multi-brand support organization needs controlled access across regional teams. What to verify: Validate data boundaries, audit records, escalation ownership, and the specific deployment requirements. A vendor's enterprise positioning is not proof of these controls. | Vendor-documented Illustrative 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 buying scenario: multiple business units need separate permissions and policies. Request a demonstration using those boundaries and review the operational and security requirements of the proposed deployment. 1 cited claim for enterprise on SierraSierra publishes customer stories for AOL, Minted and Ramp, including connected service workflows. These are vendor-published deployment examples, not proof that every enterprise requirement is met.Vendor-reported
|
| Industry evidenceRetail and e-commerce | 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
| Vendor-documented Sierra's retail and consumer goods page lists refunds and exchanges among supported workflows. Vendor documentation only; no retail deployment is independently reported. 1 cited claim for retail and e-commerce on SierraSierra’s retail page lists refund requests and exchanges among supported workflows. It does not specify a universal return-policy configuration or prove that a particular refund reaches the payment processor.Vendor-reported
|
| Industry evidenceFinancial services | Not established No supporting source is recorded here. Validate it with the vendor; absence of evidence does not establish a missing capability. | Not established No supporting source is recorded here. Validate it with the vendor; absence of evidence does not establish a missing capability. |
| Industry evidenceTelecommunications | Not established No supporting source is recorded here. Validate it with the vendor; absence of evidence does not establish a missing capability. | Not established No supporting source is recorded here. Validate it with the vendor; absence of evidence does not establish a missing capability. |
| Industry evidenceTravel and hospitality | Not established No supporting source is recorded here. Validate it with the vendor; absence of evidence does not establish a missing capability. | Not established No supporting source is recorded here. Validate it with the vendor; absence of evidence does not establish a missing capability. |
| Industry evidenceHealthcare | Not established No supporting source is recorded here. Validate it with the vendor; absence of evidence does not establish a missing capability. | Not established No supporting source is recorded here. Validate it with the vendor; absence of evidence does not establish a missing capability. |
| Industry evidencePublic sector and education | Not established No supporting source is recorded here. Validate it with the vendor; absence of evidence does not establish a missing capability. | Not established No supporting source is recorded here. Validate it with the vendor; absence of evidence does not establish a missing capability. |
| Industry evidenceLogistics and delivery | Not established No supporting source is recorded here. Validate it with the vendor; absence of evidence does not establish a missing capability. | Not established No supporting source is recorded here. Validate it with the vendor; absence of evidence does not establish a missing capability. |
| Channels | ||
| Web and in-app chat | Vendor-documented 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 Vendor-listed channels include phone, website and app chat, WhatsApp, Apple Business Chat, SMS and email. Live Assist supports staff, and Sierra also documents publishing selected agent journeys to ChatGPT. 1 cited claim for web and in-app chat on SierraVendor-listed channels include phone, website and app chat, WhatsApp, Apple Business Chat, SMS and email. Live Assist supports staff, and Sierra also documents publishing selected agent journeys to ChatGPT.Vendor-reported
|
| Vendor-documented 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 Vendor-listed channels include phone, website and app chat, WhatsApp, Apple Business Chat, SMS and email. Live Assist supports staff, and Sierra also documents publishing selected agent journeys to ChatGPT. 1 cited claim for email on SierraVendor-listed channels include phone, website and app chat, WhatsApp, Apple Business Chat, SMS and email. Live Assist supports staff, and Sierra also documents publishing selected agent journeys to ChatGPT.Vendor-reported
| |
| Voice and phone | 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 Vendor-listed channels include phone, website and app chat, WhatsApp, Apple Business Chat, SMS and email. Live Assist supports staff, and Sierra also documents publishing selected agent journeys to ChatGPT. 1 cited claim for voice and phone on SierraVendor-listed channels include phone, website and app chat, WhatsApp, Apple Business Chat, SMS and email. Live Assist supports staff, and Sierra also documents publishing selected agent journeys to ChatGPT.Vendor-reported
|
| SMS | Vendor-documented Decagon’s homepage lists chat, email and voice. SMS appears in its Curology customer story; confirm whether that channel is available for your proposed deployment. 1 cited claim for sms on DecagonDecagon’s homepage lists chat, email and voice. SMS appears in its Curology customer story; confirm whether that channel is available for your proposed deployment.Vendor-reported
| Vendor-documented Vendor-listed channels include phone, website and app chat, WhatsApp, Apple Business Chat, SMS and email. Live Assist supports staff, and Sierra also documents publishing selected agent journeys to ChatGPT. 1 cited claim for sms on SierraVendor-listed channels include phone, website and app chat, WhatsApp, Apple Business Chat, SMS and email. Live Assist supports staff, and Sierra also documents publishing selected agent journeys to ChatGPT.Vendor-reported
|
| Not established No supporting source is recorded here. Validate it with the vendor; absence of evidence does not establish a missing capability. | Vendor-documented Vendor-listed channels include phone, website and app chat, WhatsApp, Apple Business Chat, SMS and email. Live Assist supports staff, and Sierra also documents publishing selected agent journeys to ChatGPT. 1 cited claim for whatsapp on SierraVendor-listed channels include phone, website and app chat, WhatsApp, Apple Business Chat, SMS and email. Live Assist supports staff, and Sierra also documents publishing selected agent journeys to ChatGPT.Vendor-reported
| |
| Social messaging | 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 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
| Not established No supporting source is recorded here. Validate it with the vendor; absence of evidence does not establish a missing capability. |
| Salesforce | Vendor-documented 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
Sierra: 5 evidence states moved
- Channel · Web and in-app chatNot established→Vendor-documented
- Channel · EmailNot established→Vendor-documented
- Channel · Voice and phoneNot established→Vendor-documented
- Channel · SMSNot established→Vendor-documented
- Channel · WhatsAppNot established→Vendor-documented
· Catalog
Launch: 22 AI customer service agents and 532 claims, every one sourced and dated
Decagon: Added to the catalog with 26 claims and 9 rows with evidence.
Sierra: Added to the catalog with 23 claims and 9 rows with evidence.
Recorded before launch
Notes the profile carried when it went live, from research before launch.
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.
Sierra: Added editorial product positioning with its scope, rationale, and vendor source. Source
Sierra: Rechecked public sources; replaced broad fit verdict evidence with specific deployment examples and evaluation conditions. Removed unverified attribution, relayed marketing treated as independent confirmation, and business-size exclusions without evidence.