Comparison
Kore.ai 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
Kore.ai
Kore.ai documents two deployment models for its agent platform: browser-based cloud SaaS requiring no installation, and a self-hosted on-premises option for compliance-driven organisations.Vendor-reported
- Source
- Kore.ai Agent Platform documentation
- Checked
- History
- First published
- Correct this
- Request a correction with a public source. Claim ID
kore-ai-cmp-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
Kore.ai
Kore.ai's AI for Service page states its agents handle tasks such as scheduling, inventory and routine inquiries, and can summarise and transfer conversations to live agents.Vendor-reported
- Source
- AI for Service - Kore.ai
- Checked
- History
- First published
- Correct this
- Request a correction with a public source. Claim ID
kore-ai-cmp-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
Kore.ai
Kore.ai documents escalation to a human agent that forwards session variables and conversation history plus routing metadata, delivered as SIP headers on voice channels and through the provider's API on digital channels, with the exact format depending on the receiving platform.Vendor-reported
- Source
- Escalation to human agent - Kore.ai Agent Platform documentation
- Checked
- History
- First published
- Correct this
- Request a correction with a public source. Claim ID
kore-ai-cmp-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 analysts and trade press.States rest on 1 independent source across analysts and trade press. 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 | Kore.ai | Sierra |
|---|---|---|
| Review basis | Source-based review | Source-based review |
| Deployment model | Kore.ai documents two deployment models for its agent platform: browser-based cloud SaaS requiring no installation, and a self-hosted on-premises option for compliance-driven organisations.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 | Kore.ai's channel documentation lists digital channels (Slack, LINE, Microsoft Teams, WhatsApp, Messenger, Twilio SMS, Telegram, Zendesk, Instagram, Genesys, Genesys Open Messaging, Email), voice channels (Realtime LLM Voice, Pipeline Voice, VXML IVR, Genesys Audio Connector, AudioCodes), SDK channels (Web SDK, API, Mobile SDK), webhooks, and the AG-UI and Agent-to-Agent protocols.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 | Unknown | 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 | Kore.ai documents pre-built connectors for Salesforce, ServiceNow, Zendesk, SharePoint, Confluence, Jira, Google Drive, Box and Amazon S3, with the Zendesk connector indexing tickets, ticket comments and Help Center articles under Zendesk's own visibility settings.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 | Kore.ai documents an ingestion pipeline of extraction, chunking (fixed-size, semantic or sliding-window), enrichment, embedding and storage, with hybrid semantic and keyword search, re-ranking and permission filtering applied before chunks reach the agent.Vendor-reported
| The SDK documents ingestion of company FAQs, policies and documentation into its knowledge engine.Vendor-reported
|
| Actions in backend systems | Kore.ai's AI for Service page states its agents handle tasks such as scheduling, inventory and routine inquiries, and can summarise and transfer conversations to live agents.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 | Kore.ai documents escalation to a human agent that forwards session variables and conversation history plus routing metadata, delivered as SIP headers on voice channels and through the provider's API on digital channels, with the exact format depending on the receiving platform.Vendor-reported
| The SDK documents routing to a team member with an automatic conversation summary.Vendor-reported
|
| Target customer size | CX Today reported Kore.ai as targeting large regulated enterprises in banking, healthcare and retail, with prebuilt applications intended for rapid deployment in those sectors.Independent report
| 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 | Kore.ai's AI for Service page reports unnamed customer outcomes including 95% AI agent accuracy with 75% automated interactions and $97M annual cost reduction at a retail bank, 94% of contacts handled by AI agents with a 74% reduction in escalations and 65% self-service completion at a financial services firm, and a 25% reduction in average handle time at an e-commerce company.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. | Not established No supporting source is recorded here. Validate it with the vendor; absence of evidence does not establish a missing capability. | 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. | Not established No supporting source is recorded here. Validate it with the vendor; absence of evidence does not establish a missing capability. | 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. | Not established No supporting source is recorded here. Validate it with the vendor; absence of evidence does not establish a missing capability. | 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 No independent, non-vendor evidence of answer quality on product questions was found during this check, so this area is evidenced by vendor documentation only. 1 cited claim for product questions on Kore.aiKore.ai documents knowledge ingestion from file uploads (PDF, DOCX, TXT, CSV, MD, XLSX, JSON, HTML, up to 100 MB per file), web crawling of up to 1,000 pages per batch, and enterprise connectors, retrieved at query time by hybrid semantic-plus-keyword search with re-ranking.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. | Not established No supporting source is recorded here. Validate it with the vendor; absence of evidence does not establish a missing capability. | 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. | Not established No supporting source is recorded here. Validate it with the vendor; absence of evidence does not establish a missing capability. | 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 The same CX Today piece flags context preservation across agent handoffs as the thing buyers should verify; Kore.ai's own documentation lists missing conversation_history and incomplete on_human_complete handlers as implementation failure points. 2 cited claims for human handoff on Kore.aiKore.ai documents escalation to a human agent that passes session variables and conversation history via a context_for_human block, converting routing metadata to SIP headers on voice channels and forwarding it through the provider's API on digital channels.Vendor-reported
CX Today reported that Kore.ai's agent platform supports orchestration patterns including handoff and escalation across channels, and quoted the design position that handing off to a human is part of the journey rather than a failure state.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 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 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. | External report Kore.ai documents its agent platform as available both as browser-based cloud SaaS and as a self-hosted on-premises deployment aimed at compliance-driven organisations, with multi-tenancy and horizontal scalability. 2 cited claims for enterprise on Kore.aiKore.ai documents its agent platform as available both as browser-based cloud SaaS and as a self-hosted on-premises deployment aimed at compliance-driven organisations, with multi-tenancy and horizontal scalability.Vendor-reported
CX Today reported that Kore.ai's customer base sits in regulated industries such as banking, healthcare and retail, and that in regulated environments the vendor blends probabilistic AI with deterministic rules rather than operating fully autonomously.Independent report
| 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 | External report Retail appears in CX Today's account of the customer base, and the vendor reports a handle-time reduction at an unnamed ecommerce company. 3 cited claims for retail and e-commerce on Kore.aiKore.ai's AI for Service page reports unnamed customer outcomes including 95% AI agent accuracy with 75% automated interactions and $97M annual cost reduction at a retail bank, 94% of contacts handled by AI agents with a 74% reduction in escalations and 65% self-service completion at a financial services firm, and a 25% reduction in average handle time at an e-commerce company.Vendor-reported
CX Today reported that Kore.ai's customer base sits in regulated industries such as banking, healthcare and retail, and that in regulated environments the vendor blends probabilistic AI with deterministic rules rather than operating fully autonomously.Independent report
CX Today reported Kore.ai as targeting large regulated enterprises in banking, healthcare and retail, with prebuilt applications intended for rapid deployment in those sectors.Independent report
| 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 | External report CX Today places Kore.ai's customer base in banking; the vendor reports unnamed outcomes at a retail bank and a financial services firm. The independent source describes who buys the platform, not how well it resolves a banking conversation. 3 cited claims for financial services on Kore.aiKore.ai's AI for Service page reports unnamed customer outcomes including 95% AI agent accuracy with 75% automated interactions and $97M annual cost reduction at a retail bank, 94% of contacts handled by AI agents with a 74% reduction in escalations and 65% self-service completion at a financial services firm, and a 25% reduction in average handle time at an e-commerce company.Vendor-reported
CX Today reported that Kore.ai's customer base sits in regulated industries such as banking, healthcare and retail, and that in regulated environments the vendor blends probabilistic AI with deterministic rules rather than operating fully autonomously.Independent report
CX Today reported Kore.ai as targeting large regulated enterprises in banking, healthcare and retail, with prebuilt applications intended for rapid deployment in those sectors.Independent report
| 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 | External report CX Today names healthcare among the regulated sectors Kore.ai targets and sells into. No healthcare deployment outcome is reported, and the same coverage notes the vendor constrains autonomy in regulated settings. 2 cited claims for healthcare on Kore.aiCX Today reported that Kore.ai's customer base sits in regulated industries such as banking, healthcare and retail, and that in regulated environments the vendor blends probabilistic AI with deterministic rules rather than operating fully autonomously.Independent report
CX Today reported Kore.ai as targeting large regulated enterprises in banking, healthcare and retail, with prebuilt applications intended for rapid deployment in those sectors.Independent report
| 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 Kore.ai's channel documentation lists digital channels (Slack, LINE, Microsoft Teams, WhatsApp, Messenger, Twilio SMS, Telegram, Zendesk, Instagram, Genesys, Genesys Open Messaging, Email), voice channels (Realtime LLM Voice, Pipeline Voice, VXML IVR, Genesys Audio Connector, AudioCodes), SDK channels (Web SDK, API, Mobile SDK), webhooks, and the AG-UI and Agent-to-Agent protocols. 1 cited claim for web and in-app chat on Kore.aiKore.ai's channel documentation lists digital channels (Slack, LINE, Microsoft Teams, WhatsApp, Messenger, Twilio SMS, Telegram, Zendesk, Instagram, Genesys, Genesys Open Messaging, Email), voice channels (Realtime LLM Voice, Pipeline Voice, VXML IVR, Genesys Audio Connector, AudioCodes), SDK channels (Web SDK, API, Mobile SDK), webhooks, and the AG-UI and Agent-to-Agent protocols.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 Kore.ai's channel documentation lists digital channels (Slack, LINE, Microsoft Teams, WhatsApp, Messenger, Twilio SMS, Telegram, Zendesk, Instagram, Genesys, Genesys Open Messaging, Email), voice channels (Realtime LLM Voice, Pipeline Voice, VXML IVR, Genesys Audio Connector, AudioCodes), SDK channels (Web SDK, API, Mobile SDK), webhooks, and the AG-UI and Agent-to-Agent protocols. 1 cited claim for email on Kore.aiKore.ai's channel documentation lists digital channels (Slack, LINE, Microsoft Teams, WhatsApp, Messenger, Twilio SMS, Telegram, Zendesk, Instagram, Genesys, Genesys Open Messaging, Email), voice channels (Realtime LLM Voice, Pipeline Voice, VXML IVR, Genesys Audio Connector, AudioCodes), SDK channels (Web SDK, API, Mobile SDK), webhooks, and the AG-UI and Agent-to-Agent protocols.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 Kore.ai's channel documentation lists digital channels (Slack, LINE, Microsoft Teams, WhatsApp, Messenger, Twilio SMS, Telegram, Zendesk, Instagram, Genesys, Genesys Open Messaging, Email), voice channels (Realtime LLM Voice, Pipeline Voice, VXML IVR, Genesys Audio Connector, AudioCodes), SDK channels (Web SDK, API, Mobile SDK), webhooks, and the AG-UI and Agent-to-Agent protocols. 1 cited claim for voice and phone on Kore.aiKore.ai's channel documentation lists digital channels (Slack, LINE, Microsoft Teams, WhatsApp, Messenger, Twilio SMS, Telegram, Zendesk, Instagram, Genesys, Genesys Open Messaging, Email), voice channels (Realtime LLM Voice, Pipeline Voice, VXML IVR, Genesys Audio Connector, AudioCodes), SDK channels (Web SDK, API, Mobile SDK), webhooks, and the AG-UI and Agent-to-Agent protocols.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 Kore.ai's channel documentation lists digital channels (Slack, LINE, Microsoft Teams, WhatsApp, Messenger, Twilio SMS, Telegram, Zendesk, Instagram, Genesys, Genesys Open Messaging, Email), voice channels (Realtime LLM Voice, Pipeline Voice, VXML IVR, Genesys Audio Connector, AudioCodes), SDK channels (Web SDK, API, Mobile SDK), webhooks, and the AG-UI and Agent-to-Agent protocols. 1 cited claim for sms on Kore.aiKore.ai's channel documentation lists digital channels (Slack, LINE, Microsoft Teams, WhatsApp, Messenger, Twilio SMS, Telegram, Zendesk, Instagram, Genesys, Genesys Open Messaging, Email), voice channels (Realtime LLM Voice, Pipeline Voice, VXML IVR, Genesys Audio Connector, AudioCodes), SDK channels (Web SDK, API, Mobile SDK), webhooks, and the AG-UI and Agent-to-Agent protocols.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
|
| Vendor-documented Kore.ai's channel documentation lists digital channels (Slack, LINE, Microsoft Teams, WhatsApp, Messenger, Twilio SMS, Telegram, Zendesk, Instagram, Genesys, Genesys Open Messaging, Email), voice channels (Realtime LLM Voice, Pipeline Voice, VXML IVR, Genesys Audio Connector, AudioCodes), SDK channels (Web SDK, API, Mobile SDK), webhooks, and the AG-UI and Agent-to-Agent protocols. 1 cited claim for whatsapp on Kore.aiKore.ai's channel documentation lists digital channels (Slack, LINE, Microsoft Teams, WhatsApp, Messenger, Twilio SMS, Telegram, Zendesk, Instagram, Genesys, Genesys Open Messaging, Email), voice channels (Realtime LLM Voice, Pipeline Voice, VXML IVR, Genesys Audio Connector, AudioCodes), SDK channels (Web SDK, API, Mobile SDK), webhooks, and the AG-UI and Agent-to-Agent protocols.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 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 | Vendor-documented Kore.ai's channel documentation lists digital channels (Slack, LINE, Microsoft Teams, WhatsApp, Messenger, Twilio SMS, Telegram, Zendesk, Instagram, Genesys, Genesys Open Messaging, Email), voice channels (Realtime LLM Voice, Pipeline Voice, VXML IVR, Genesys Audio Connector, AudioCodes), SDK channels (Web SDK, API, Mobile SDK), webhooks, and the AG-UI and Agent-to-Agent protocols. 1 cited claim for social messaging on Kore.aiKore.ai's channel documentation lists digital channels (Slack, LINE, Microsoft Teams, WhatsApp, Messenger, Twilio SMS, Telegram, Zendesk, Instagram, Genesys, Genesys Open Messaging, Email), voice channels (Realtime LLM Voice, Pipeline Voice, VXML IVR, Genesys Audio Connector, AudioCodes), SDK channels (Web SDK, API, Mobile SDK), webhooks, and the AG-UI and Agent-to-Agent protocols.Vendor-reported
| Not established No supporting source is recorded here. Validate it with the vendor; absence of evidence does not establish a missing capability. |
| Help desks | ||
| Zendesk | Vendor-documented Kore.ai documents pre-built connectors for Salesforce, ServiceNow, Zendesk, SharePoint, Confluence, Jira, Google Drive, Box and Amazon S3, with the Zendesk connector indexing tickets, ticket comments and Help Center articles under Zendesk's own visibility settings. 1 cited claim for zendesk on Kore.aiKore.ai documents pre-built connectors for Salesforce, ServiceNow, Zendesk, SharePoint, Confluence, Jira, Google Drive, Box and Amazon S3, with the Zendesk connector indexing tickets, ticket comments and Help Center articles under Zendesk's own visibility settings.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 Kore.ai documents pre-built connectors for Salesforce, ServiceNow, Zendesk, SharePoint, Confluence, Jira, Google Drive, Box and Amazon S3, with the Zendesk connector indexing tickets, ticket comments and Help Center articles under Zendesk's own visibility settings. 1 cited claim for salesforce on Kore.aiKore.ai documents pre-built connectors for Salesforce, ServiceNow, Zendesk, SharePoint, Confluence, Jira, Google Drive, Box and Amazon S3, with the Zendesk connector indexing tickets, ticket comments and Help Center articles under Zendesk's own visibility settings.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 | Vendor-documented Kore.ai documents pre-built connectors for Salesforce, ServiceNow, Zendesk, SharePoint, Confluence, Jira, Google Drive, Box and Amazon S3, with the Zendesk connector indexing tickets, ticket comments and Help Center articles under Zendesk's own visibility settings. 1 cited claim for servicenow on Kore.aiKore.ai documents pre-built connectors for Salesforce, ServiceNow, Zendesk, SharePoint, Confluence, Jira, Google Drive, Box and Amazon S3, with the Zendesk connector indexing tickets, ticket comments and Help Center articles under Zendesk's own visibility settings.Vendor-reported
| Not established No supporting source is recorded here. Validate it with the vendor; absence of evidence does not establish a missing capability. |
| Freshdesk | 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 | 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. |
| 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
Kore.ai: 9 evidence states moved
- Channel · Web and in-app chatNot established→Vendor-documented
- Channel · EmailNot established→Vendor-documented
- Channel · Voice and phoneNot established→Vendor-documented
- Channel · SMSNot established→Vendor-documented
- Channel · WhatsAppNot established→Vendor-documented
- Channel · Social messagingNot established→Vendor-documented
- Help desk · ZendeskNot established→Vendor-documented
- Help desk · SalesforceNot established→Vendor-documented
- and 1 more
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
Kore.ai: Added to the catalog with 22 claims and 6 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.
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.