Comparison
Ada vs Kore.ai
Compare documented workflows and implementation requirements using attributed public sources. Facts last checked , the earlier of the two records. Machine-readable record.
Start with your setup
These are documented product differences and requirements. A feature list or a single customer report does not establish which agent will perform better for your team.
Deployment model
Ada
Ada documents setup through its dashboard and a website or mobile chat integration, with connected knowledge and configured workflows.Vendor-reported
- Source
- Key concepts (Ada docs)
- Checked
- History
- First published
- Correct this
- Request a correction with a public source. Claim ID
ada-deployment
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
Actions in backend systems
Ada
API tools, formerly called Actions, retrieve or send data through configured endpoints. Playbooks and Processes organise those calls into workflows.Vendor-reported
- Source
- API tools (Ada docs)
- Checked
- History
- First published
- Correct this
- Request a correction with a public source. Claim ID
ada-actions
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
Human handoff
Ada
Configured live transfers or follow-up tickets, with off-hours and error paths. Up to five active handoff configurations are documented.Vendor-reported
- Source
- Handoff management (Ada docs)
- Checked
- History
- First published
- Correct this
- Request a correction with a public source. Claim ID
ada-handoff
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
Side by side
Product attributes first, then what the sources establish for each customer workflow, then the industries they place each agent in. Open any claim to see its source, the date it was checked, and how to request a correction. Two agents are rarely documented to the same depth, so read a difference between the two columns as a difference in the public record before reading it as a difference in the products.
What this agent was judged by
No independent source has been found for any fit area, so every state here rests on vendor material or nothing.States rest on 0 independent sources. This is not the same yardstick for every agent, and that asymmetry is a known limitation.
What this agent was judged by
The independent evidence behind these states comes mainly from 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.
| Attribute | Ada | Kore.ai |
|---|---|---|
| Review basis | Source-based review | Source-based review |
| Deployment model | Ada documents setup through its dashboard and a website or mobile chat integration, with connected knowledge and configured workflows.Vendor-reported
| 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
|
| Channels | Chat, voice, email and social messaging are documented. Voice and social connections use supported external platforms; confirm the intended channel integration.Vendor-reported
| 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
|
| Languages | 60 languages are documented for messaging and email; voice supports a subset. English remains the fallback language.Vendor-reported
| Unknown |
| Help desk and CRM integrations | The integrations directory includes Zendesk, Salesforce, ServiceNow, Freshworks, Genesys and Help Scout. Check each entry for knowledge, messaging, email or voice support.Vendor-reported
| 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
|
| Knowledge sources | Knowledge can come from help centres, websites, articles created in Ada and custom sources through the Knowledge API.Vendor-reported
| 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
|
| Actions in backend systems | API tools, formerly called Actions, retrieve or send data through configured endpoints. Playbooks and Processes organise those calls into workflows.Vendor-reported
| 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
|
| Human handoff | Configured live transfers or follow-up tickets, with off-hours and error paths. Up to five active handoff configurations are documented.Vendor-reported
| 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
|
| Target customer size | Ada presents an enterprise-focused sales process with a tailored demonstration and implementation plan. This positioning does not establish a minimum viable company size.Vendor-reported
| 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-reported performance claims | Ada reports that Dott’s automated resolution increased from 32% to 77% after adopting Ada and connecting backend automations. This is one customer’s vendor-published result, not a platform-wide average or a comparable benchmark.Vendor-reported
| 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
|
| Workflow evidenceBilling Illustrative scenario I was charged twice for the same order. Can you refund the extra payment? What to verify: Verify identity, inspect payment records, apply the refund policy, and confirm the payment-system result. If no authorized refund action is connected, hand off with the evidence. | Vendor-documented Illustrative scenario, not a test: explain a duplicate charge using the customer’s payment records. Ada documents billing inquiries; verify identity checks, access to the payment system and the route for a disputed charge. Answering a question and reversing a payment are separate operations. 1 cited claim for billing on AdaAda lists billing and payment questions among its email workflows, using information retrieved from connected business systems.Vendor-reported
| Not established No supporting source is recorded here. Validate it with the vendor; absence of evidence does not establish a missing capability. |
| Workflow evidenceOrders Illustrative scenario My order has not arrived. Where is it? What to verify: Retrieve the correct order and current carrier status. Distinguish a real tracking update from an estimate; do not invent a delivery date. | Vendor-documented Illustrative scenario, not a test: retrieve shipment status for a customer’s order and give the carrier’s tracking link. Validate customer ownership, missing orders and stale tracking data. A lookup does not demonstrate that lost parcels are resolved. 1 cited claim for orders on AdaAda documents API-driven order-status lookups, so live order answers depend on connecting the order system.Vendor-reported
| Not established No supporting source is recorded here. Validate it with the vendor; absence of evidence does not establish a missing capability. |
| Workflow evidenceReturns Illustrative scenario I bought this 12 days ago and opened the box. Can I return it? What to verify: Check the actual return window, product exclusions, and order record. A policy answer and an executed return are different capabilities. | Vendor-documented Illustrative scenario, not a test: check whether an unopened item is inside the return window, then request a label from the order system. Confirm the label was created before saying the return is arranged, and route policy exceptions to a person. 1 cited claim for returns on AdaAda describes returns workflows that check order eligibility, offer permitted options and create a return label through connected systems.Vendor-reported
| Not established No supporting source is recorded here. Validate it with the vendor; absence of evidence does not establish a missing capability. |
| Workflow evidenceProduct questions Illustrative scenario Does this adapter work with my exact laptop model? What to verify: Use a current, approved compatibility source. Ask for the model when missing and distinguish documented compatibility from an assumption. | Vendor-documented Illustrative scenario, not a test: answer whether a product works with a specific phone model from the compatibility guide. Check that the reply uses the correct product version and asks for missing details instead of inventing compatibility. 1 cited claim for product questions on AdaAda uses imported knowledge to answer questions; its documentation explains that relevant passages are retrieved from that content.Vendor-reported
| Vendor-documented 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
|
| Workflow evidenceAccount issues Illustrative scenario I lost access to my email. Change the address on my account. What to verify: Follow the approved identity-recovery process before accessing or changing account data. Escalate when identity cannot be verified. | Vendor-documented Illustrative scenario, not a test: update the signed-in customer’s contact details through an authorised account API. Verify that another customer’s records cannot be changed and that failed updates are not reported as complete. 1 cited claim for account issues on AdaAda documents account updates through external APIs and sign-in tokens for sensitive actions.Vendor-reported
| Not established No supporting source is recorded here. Validate it with the vendor; absence of evidence does not establish a missing capability. |
| Workflow evidenceComplaints Illustrative scenario I have contacted you three times and the problem is still unresolved. What to verify: Recognize the repeat complaint, retain relevant history, and route it to the right team. Do not promise compensation outside the policy. | Vendor-documented Illustrative scenario, not a test: a customer says repeated delivery problems remain unresolved. Configure a route to the complaints team with the case details. Routing is documented; the reviewed sources do not measure successful complaint resolution or de-escalation. 1 cited claim for complaints on AdaAda documents routing to human support based on conversation context and configured handoff descriptions.Vendor-reported
| Not established No supporting source is recorded here. Validate it with the vendor; absence of evidence does not establish a missing capability. |
| Workflow evidenceHuman handoff Illustrative scenario Please connect me to a person who can approve this exception. What to verify: Transfer to an available team with the conversation and relevant records. Outside working hours, explain the actual follow-up path rather than promise immediate contact. | Vendor-documented Illustrative scenario, not a test: a customer requests a person after an unsuccessful answer. Verify that the receiving team gets the conversation and that, outside working hours, the customer receives a clear follow-up path. 1 cited claim for human handoff on AdaAda documents live transfers, follow-up tickets, off-hours paths and error fallbacks across its handoff setup.Vendor-reported
| External report 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
|
| Workflow evidenceSmall businesses Illustrative scenario A two-person support team wants to launch without a dedicated engineer. What to verify: Validate setup effort, existing help-desk support, required integrations, and ongoing maintenance. A small customer's story alone does not establish suitability for every small business. | Not established Illustrative buying scenario: a small shop needs only shipping FAQs and occasional order lookups. Ask Ada to demonstrate that limited scope and the work needed to maintain it. Demo-led procurement does not establish that every small business is a poor fit. No supporting source is recorded here. Validate it with the vendor; absence of evidence does not establish a missing capability. | Not established No supporting source is recorded here. Validate it with the vendor; absence of evidence does not establish a missing capability. |
| Workflow evidenceMid-market Illustrative scenario A growing support team needs separate queues and connected order and account systems. What to verify: Validate routing, permissions, integration ownership, and handling of each team's policies in the intended configuration. | Not established Illustrative buying scenario: a growing retailer wants email and chat support connected to an existing help desk. Evaluate the exact connectors, workflow ownership and conversation volume. Employee count alone does not establish suitability. No supporting source is recorded here. Validate it with the vendor; absence of evidence does not establish a missing capability. | Not established No supporting source is recorded here. Validate it with the vendor; absence of evidence does not establish a missing capability. |
| Workflow evidenceEnterprise Illustrative scenario A multi-brand support organization needs controlled access across regional teams. What to verify: Validate data boundaries, audit records, escalation ownership, and the specific deployment requirements. A vendor's enterprise positioning is not proof of these controls. | Vendor-documented Illustrative buying scenario: a multi-brand support team needs shared knowledge with brand-specific policies and handoff routes. Request a demonstration of those boundaries. Enterprise positioning is documented; successful performance for that configuration is not established here. 1 cited claim for enterprise on AdaAda’s demo page explicitly targets enterprise customer-experience teams and proposes a tailored demonstration and implementation plan.Vendor-reported
| 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
|
| Industry evidenceRetail and e-commerce | Vendor-documented Ada's own retail and ecommerce page is the only source placing the product here. It describes returns workflows against connected commerce systems; no independent report of a retail deployment was found. 1 cited claim for retail and e-commerce on AdaAda describes returns workflows that check order eligibility, offer permitted options and create a return label through connected systems.Vendor-reported
| 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
|
| 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. | 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
|
| 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. | 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
|
| Industry evidencePublic sector and education | Not established No supporting source is recorded here. Validate it with the vendor; absence of evidence does not establish a missing capability. | Not established No supporting source is recorded here. Validate it with the vendor; absence of evidence does not establish a missing capability. |
| Industry evidenceLogistics and delivery | Not established No supporting source is recorded here. Validate it with the vendor; absence of evidence does not establish a missing capability. | Not established No supporting source is recorded here. Validate it with the vendor; absence of evidence does not establish a missing capability. |
| Channels | ||
| Web and in-app chat | Vendor-documented Chat, voice, email and social messaging are documented. Voice and social connections use supported external platforms; confirm the intended channel integration. 1 cited claim for web and in-app chat on AdaChat, voice, email and social messaging are documented. Voice and social connections use supported external platforms; confirm the intended channel integration.Vendor-reported
| Vendor-documented 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 Chat, voice, email and social messaging are documented. Voice and social connections use supported external platforms; confirm the intended channel integration. 1 cited claim for email on AdaChat, voice, email and social messaging are documented. Voice and social connections use supported external platforms; confirm the intended channel integration.Vendor-reported
| Vendor-documented 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
| |
| Voice and phone | Vendor-documented Chat, voice, email and social messaging are documented. Voice and social connections use supported external platforms; confirm the intended channel integration. 1 cited claim for voice and phone on AdaChat, voice, email and social messaging are documented. Voice and social connections use supported external platforms; confirm the intended channel integration.Vendor-reported
| Vendor-documented 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
|
| SMS | Not established No supporting source is recorded here. Validate it with the vendor; absence of evidence does not establish a missing capability. | Vendor-documented 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
|
| Not established No supporting source is recorded here. Validate it with the vendor; absence of evidence does not establish a missing capability. | 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
| |
| Social messaging | Vendor-documented Chat, voice, email and social messaging are documented. Voice and social connections use supported external platforms; confirm the intended channel integration. 1 cited claim for social messaging on AdaChat, voice, email and social messaging are documented. Voice and social connections use supported external platforms; confirm the intended channel integration.Vendor-reported
| 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
|
| Help desks | ||
| Zendesk | Vendor-documented The integrations directory includes Zendesk, Salesforce, ServiceNow, Freshworks, Genesys and Help Scout. Check each entry for knowledge, messaging, email or voice support. 1 cited claim for zendesk on AdaThe integrations directory includes Zendesk, Salesforce, ServiceNow, Freshworks, Genesys and Help Scout. Check each entry for knowledge, messaging, email or voice support.Vendor-reported
| Vendor-documented 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
|
| Salesforce | Vendor-documented The integrations directory includes Zendesk, Salesforce, ServiceNow, Freshworks, Genesys and Help Scout. Check each entry for knowledge, messaging, email or voice support. 1 cited claim for salesforce on AdaThe integrations directory includes Zendesk, Salesforce, ServiceNow, Freshworks, Genesys and Help Scout. Check each entry for knowledge, messaging, email or voice support.Vendor-reported
| Vendor-documented 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
|
| ServiceNow | Vendor-documented The integrations directory includes Zendesk, Salesforce, ServiceNow, Freshworks, Genesys and Help Scout. Check each entry for knowledge, messaging, email or voice support. 1 cited claim for servicenow on AdaThe integrations directory includes Zendesk, Salesforce, ServiceNow, Freshworks, Genesys and Help Scout. Check each entry for knowledge, messaging, email or voice support.Vendor-reported
| 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
|
| Freshdesk | Vendor-documented The integrations directory includes Zendesk, Salesforce, ServiceNow, Freshworks, Genesys and Help Scout. Check each entry for knowledge, messaging, email or voice support. 1 cited claim for freshdesk on AdaThe integrations directory includes Zendesk, Salesforce, ServiceNow, Freshworks, Genesys and Help Scout. Check each entry for knowledge, messaging, email or voice support.Vendor-reported
| Not established No supporting source is recorded here. Validate it with the vendor; absence of evidence does not establish a missing capability. |
| Intercom | Not established No supporting source is recorded here. Validate it with the vendor; absence of evidence does not establish a missing capability. | 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 | Vendor-documented The integrations directory includes Zendesk, Salesforce, ServiceNow, Freshworks, Genesys and Help Scout. Check each entry for knowledge, messaging, email or voice support. 1 cited claim for help scout on AdaThe integrations directory includes Zendesk, Salesforce, ServiceNow, Freshworks, Genesys and Help Scout. Check each entry for knowledge, messaging, email or voice support.Vendor-reported
| Not established No supporting source is recorded here. Validate it with the vendor; absence of evidence does not establish a missing capability. |
| Front | Not established No supporting source is recorded here. Validate it with the vendor; absence of evidence does not establish a missing capability. | Not established No supporting source is recorded here. Validate it with the vendor; absence of evidence does not establish a missing capability. |
| Microsoft Dynamics 365 | Not established No supporting source is recorded here. Validate it with the vendor; absence of evidence does not establish a missing capability. | Not established No supporting source is recorded here. Validate it with the vendor; absence of evidence does not establish a missing capability. |
Change history
Open the changelogEvery change to this record is in the public changelog, with what it changed and why.
· Structure
Channels and help desks become evidence rows, and records gain bylines
Ada: 9 evidence states moved
- Channel · Web and in-app chatNot established→Vendor-documented
- Channel · EmailNot established→Vendor-documented
- Channel · Voice and phoneNot established→Vendor-documented
- Channel · Social messagingNot established→Vendor-documented
- Help desk · ZendeskNot established→Vendor-documented
- Help desk · SalesforceNot established→Vendor-documented
- Help desk · ServiceNowNot established→Vendor-documented
- Help desk · FreshdeskNot established→Vendor-documented
- and 1 more
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
· Catalog
Launch: 22 AI customer service agents and 532 claims, every one sourced and dated
Ada: Added to the catalog with 24 claims and 9 rows with evidence.
Kore.ai: Added to the catalog with 22 claims and 6 rows with evidence.
Recorded before launch
Notes the profile carried when it went live, from research before launch.
Ada: Added editorial product positioning with its scope, rationale, and vendor source. Source
Ada: Rechecked current documentation; replaced merchant-review extrapolations and unsupported fit verdict inputs with scoped capabilities, named vendor examples and clearly labelled illustrative scenarios. Source