Comparison
Agentforce 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
Agentforce
Service Agents are configured in Salesforce and connected to customer channels, with a default service template or specialised templates. Confirm the required editions for the chosen agent type.Vendor-reported
- Source
- Agentforce Service Agent (Salesforce Help)
- Checked
- History
- First published
- Correct this
- Request a correction with a public source. Claim ID
agentforce-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
Agentforce
Actions can use Salesforce workflows, code and external APIs. A refund is a configured sequence with eligibility checks and payment confirmation, not a universal action available on every installation.Vendor-reported
- Source
- Agentic integration patterns (Salesforce Architects)
- Checked
- History
- First published
- Correct this
- Request a correction with a public source. Claim ID
agentforce-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
Agentforce
Omni-Channel Flow routes complex or sensitive requests from the Service Agent to service representatives or another configured destination.Vendor-reported
- Source
- Agentforce Service Agent (Salesforce Help)
- Checked
- History
- First published
- Correct this
- Request a correction with a public source. Claim ID
agentforce-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 | Agentforce | Kore.ai |
|---|---|---|
| Review basis | Source-based review | Source-based review |
| Deployment model | Service Agents are configured in Salesforce and connected to customer channels, with a default service template or specialised templates. Confirm the required editions for the chosen agent type.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 | Salesforce describes messaging, web, mobile and voice service experiences. Channel availability and setup should be checked for the specific Service Agent offering.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 | The current supported-language table includes English, French, German, Japanese, Polish and others, with some additional languages marked beta. Voice support differs; use the table for the chosen channel.Vendor-reported
| Unknown |
| Help desk and CRM integrations | The reviewed deployment uses Salesforce service records and routing. External business systems can be connected through configured agent actions; this does not establish a turnkey connector for every other help desk.Editorial assessment
| 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 | Agentforce Data Library indexes knowledge articles, uploaded files or web sources. It requires Data 360 setup; the library must be assigned to the agent.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 | Actions can use Salesforce workflows, code and external APIs. A refund is a configured sequence with eligibility checks and payment confirmation, not a universal action available on every installation.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 | Omni-Channel Flow routes complex or sensitive requests from the Service Agent to service representatives or another configured destination.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 | Salesforce markets Agentforce for enterprise-scale support. Our editorial assessment is that existing Salesforce data, administrator capacity and integration needs are more useful selection criteria than employee count.Editorial assessment
| 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 | Salesforce’s customer story reports about 76% of queries resolved without a human on its own Help site. This vendor-operated deployment is not a controlled comparison, and its resolution definition and workload should not be assumed equivalent to other vendors’ figures.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 disputed charge from an authenticated customer’s billing records. Confirm the licensed service offering, billing connection and approval path. The employee-facing Communications example cannot establish that the general Service Agent can resolve this independently. 1 cited claim for billing on AgentforceSalesforce describes billing-detail and dispute actions for Agentforce for Communications. That page labels its prebuilt subagent employee-facing and includes an availability disclaimer; it does not establish an included customer-facing Service Agent billing flow.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: look up a shipment by order number and return its status. Prove customer verification and order access first; separately test cancellations, missing parcels and stale tracking. The partner demonstration listed above covers lookup, not all order support. 1 cited claim for orders on AgentforceSalesforce’s Service training gives order lookup and cancellation as configurable workflow examples, with a lost-package request routed to a person.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: request a refund within the return window. The payment connection must return confirmation before the case is closed, and retrying a request must not issue a second refund. Confirm which actions your team must implement. 1 cited claim for returns on AgentforceSalesforce’s architecture guide illustrates a refund chain: retrieve order details, check eligibility, call the payment gateway and update the case after confirmation. It is an implementation pattern, not a measured deployment result.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: explain a warranty’s coverage from the approved article. Verify that the answer matches the customer’s model and region and asks for clarification when those details are missing. A knowledge source does not guarantee a correct answer. 1 cited claim for product questions on AgentforceSalesforce documents a knowledge-answering action for questions such as return policies and warranty information.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: help a locked-out customer recover access. Verify identity using the intended authentication flow before exposing account data or initiating a reset. Demonstrate the actual identity-provider integration, not just a helpful-sounding reply. 1 cited claim for account issues on AgentforceSalesforce’s Service training includes customer-detail retrieval and password-reset examples, with verification instructions and additional configuration for private 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 objects to repeated unresolved charges. Route the case to a person with context and a clear next step. This source documents escalation, not reliable emotion detection or successful resolution of complaints. 1 cited claim for complaints on AgentforceSalesforce documents escalation of complex or sensitive Service Agent requests through Omni-Channel Flow.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 asks to speak to a person. Confirm the destination queue is staffed, the conversation reaches it and the customer receives an off-hours path when nobody is available. 1 cited claim for human handoff on AgentforceService Agents use configured Omni-Channel Flow routing to transfer support requests to service representatives or other destinations.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 team already using Salesforce wants to answer common support questions. Assess the required setup, data access and ongoing ownership. Neither team size nor an analyst’s view of implementation skills establishes that the product will fail for this team. 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 company with Salesforce support records wants order lookup connected to a separate fulfilment system. Evaluate integration effort and administrator capacity. This is a configuration and operating-model decision, not a verdict based on headcount. 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 global support organisation needs customer-specific access across multiple business systems. Request evidence for permissions, routing and language coverage in that configuration. Enterprise positioning alone does not establish successful deployment. 1 cited claim for enterprise on AgentforceSalesforce positions Agentforce for enterprise-scale support and documents building agents with its platform tools and integrations.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 | Not established No supporting source is recorded here. Validate it with the vendor; absence of evidence does not establish a missing capability. | 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 Salesforce describes messaging, web, mobile and voice service experiences. Channel availability and setup should be checked for the specific Service Agent offering. 1 cited claim for web and in-app chat on AgentforceSalesforce describes messaging, web, mobile and voice service experiences. Channel availability and setup should be checked for the specific Service Agent offering.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
|
| 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 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 Salesforce describes messaging, web, mobile and voice service experiences. Channel availability and setup should be checked for the specific Service Agent offering. 1 cited claim for voice and phone on AgentforceSalesforce describes messaging, web, mobile and voice service experiences. Channel availability and setup should be checked for the specific Service Agent offering.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 | 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 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 | 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 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 Service Agents are configured in Salesforce and connected to customer channels, with a default service template or specialised templates. Confirm the required editions for the chosen agent type. 1 cited claim for salesforce on AgentforceService Agents are configured in Salesforce and connected to customer channels, with a default service template or specialised templates. Confirm the required editions for the chosen agent type.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 | 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 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 | 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
Agentforce: 3 evidence states moved
- Channel · Web and in-app chatNot established→Vendor-documented
- Channel · Voice and phoneNot established→Vendor-documented
- Help desk · SalesforceNot established→Vendor-documented
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
Agentforce: Added to the catalog with 24 claims and 8 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.
Agentforce: Added editorial product positioning with its scope, rationale, and vendor source. Source
Agentforce: Rechecked product-specific documentation; removed promotional and unrelated reports from fit evidence, corrected outdated language coverage, and added scoped workflow examples and implementation conditions. Source