Comparison
Genesys Cloud CX vs Zendesk AI Agents
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
Genesys Cloud CX
Genesys Virtual Agent runs inside Genesys Cloud: it is enabled in voice or digital bot flows built in Architect, and Genesys states it can be used in new or existing bot flows. Usage is metered through AI Experience tokens.Vendor-reported
- Source
- About Genesys Virtual Agent - Genesys Cloud Resource Center
- Checked
- History
- First published
- Correct this
- Request a correction with a public source. Claim ID
genesys-cloud-cx-doc-deployment
Zendesk AI Agents
Vendor-hosted service within Zendesk Support and Suite. Feature access and advanced integrations vary by package.Vendor-reported
- Source
- Zendesk plans and AI agent availability
- Checked
- History
- First published
- Correct this
- Request a correction with a public source. Claim ID
zendesk-cmp-deployment
Actions in backend systems
Genesys Cloud CX
Genesys states its Cloud Agentic Virtual Agent can execute multi-step workflows using approved tools and guardrails against back-office systems, covering verification, updates and troubleshooting.Vendor-reported
- Source
- Virtual Agents - Genesys
- Checked
- History
- First published
- Correct this
- Request a correction with a public source. Claim ID
genesys-cmp-actions
Zendesk AI Agents
Zendesk documents API calls for live order lookups, with a different implementation path for AI Agents Advanced. Confirm required write actions and permissions separately.Vendor-reported
- Source
- How can I link my AI agent with my customer orders? (Zendesk help)
- Checked
- History
- First published
- Correct this
- Request a correction with a public source. Claim ID
zendesk-cmp-actions
Human handoff
Genesys Cloud CX
Genesys states its virtual agent provides seamless, contextual handoffs with full context when a human agent steps in.Vendor-reported
- Source
- Virtual Agents - Genesys
- Checked
- History
- First published
- Correct this
- Request a correction with a public source. Claim ID
genesys-cmp-handoff
Zendesk AI Agents
Escalates to human teams with context according to Zendesk. Confirm queue routing, contact details, and reply-channel behavior in the intended setup.Vendor-reported
- Source
- Zendesk AI Agents product overview
- Checked
- History
- First published
- Correct this
- Request a correction with a public source. Claim ID
zendesk-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
The independent evidence behind these states comes mainly from analysts and trade press.States rest on 2 independent sources across analysts and trade press, other 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 practitioner forums and buyer reviews.States rest on 3 independent sources across practitioner forums and buyer reviews, end-user review sites. This is not the same yardstick for every agent, and that asymmetry is a known limitation.
| Attribute | Genesys Cloud CX | Zendesk AI Agents |
|---|---|---|
| Review basis | Source-based review | Source-based review |
| Deployment model | Genesys Virtual Agent runs inside Genesys Cloud: it is enabled in voice or digital bot flows built in Architect, and Genesys states it can be used in new or existing bot flows. Usage is metered through AI Experience tokens.Vendor-reported
| Vendor-hosted service within Zendesk Support and Suite. Feature access and advanced integrations vary by package.Vendor-reported
|
| Channels | Genesys documents that bots built in Architect can be integrated into call, chat and message flows, and markets AI agents across voice, text, web, social and WhatsApp.Vendor-reported
| Zendesk advertises web, mobile, social, email, and voice. Check channel-specific documentation and availability for the selected agent.Vendor-reported
|
| Languages | Genesys lists approximately 40 supported languages for voice bot flows and digital bot flows, with some entries flagged as partial NLU support.Vendor-reported
| Zendesk advertises support for 80 languages. Confirm the required channel separately; the voice announcement describes an early access rollout rather than identical availability everywhere.Vendor-reported
|
| Help desk and CRM integrations | Genesys documents data actions integrations for Salesforce, Zendesk and Microsoft Dynamics 365, as well as Google, AWS Lambda and JSON web services, whose data can drive decisions inside Architect interaction flows. Check each integration for the actions it supports.Vendor-reported
| Native Zendesk deployment is the scope of this profile. Zendesk also markets Forethought agents for other service platforms; confirm those connectors and capabilities separately.Vendor-reported
|
| Knowledge sources | Bot flows can be grounded in a Genesys knowledge base through Genesys Virtual Agent, and Genesys states its agentic virtual agent operates on approved enterprise knowledge, workflows and systems.Vendor-reported
| Zendesk help centres and external content brought in through crawlers or knowledge connectors. External content reflects its most recent sync.Vendor-reported
|
| Actions in backend systems | Genesys states its Cloud Agentic Virtual Agent can execute multi-step workflows using approved tools and guardrails against back-office systems, covering verification, updates and troubleshooting.Vendor-reported
| Zendesk documents API calls for live order lookups, with a different implementation path for AI Agents Advanced. Confirm required write actions and permissions separately.Vendor-reported
|
| Human handoff | Genesys states its virtual agent provides seamless, contextual handoffs with full context when a human agent steps in.Vendor-reported
| Escalates to human teams with context according to Zendesk. Confirm queue routing, contact details, and reply-channel behavior in the intended setup.Vendor-reported
|
| Target customer size | Vendr's buyer data shows Genesys contracts spanning small deployments of 25 to 100 users at $75,000 to $150,000 annually up to 500-plus-user deployments exceeding $1 million annually.Independent report
| Support and Suite plans span different service needs, with enterprise options available. Company size is not a tested suitability criterion.Vendor-reported
|
| Vendor-reported performance claims | Genesys publishes a customer account stating that Coca-Cola Bottlers' Sales and Services voicebots correctly matched from a list of 30 different intents in over 80% of cases and saved nearly $5,000 with $20,000 expected by year end.Vendor-reported
| Zendesk's Babbel story reports more than 50% AI automation. This is a vendor-published customer result, not our benchmark or an expected rate for another business.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 Announced scenario, not a documented production deployment; it depends on the ServiceNow integration. 1 cited claim for billing on Genesys Cloud CXGenesys's September 2025 announcement of its expanded ServiceNow partnership describes a scenario in which the Genesys Cloud Virtual Agent authenticates a customer calling about a sudden spike in their bill and collaborates with the ServiceNow AI Agent Fabric "for bill retrieval, charge explanations and promotion checks"; availability of the Agent2Agent orchestration capabilities was expected to begin between November 2025 and January 2026.Vendor-reported
| Caveat documented Illustrative scenario: a subscriber asks when renewal is due. Connect the authenticated account to the billing record and limit allowed changes. Babbel provides a concrete vendor-published example; a disputed charge would require different rules and human review. 2 cited claims for billing on Zendesk AI AgentsZendesk's Babbel case study describes subscription-status answers and self-service subscription management through Babbel's backend APIs. It does not establish general invoice, refund, or charge-dispute performance.Vendor-reported
A Trustpilot reviewer of Zendesk (a company-level listing), writing as a customer of BlueAir, described three days with what they called Zendesk's AI over a subscription problem: it "kept repeating itself offering solutions that didn't work earlier" before passing them to a person, who cited a known problem with BlueAir's own system. The reviewer attributes the bot to Zendesk; it is one deployment's report, not a failure rate.Independent report
|
| 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 scenario: a shopper asks whether an order has shipped. The workflow needs an authorised order lookup and a response for missing or stale tracking data. Integration work is a prerequisite, not evidence that Zendesk is a poor fit for orders. 1 cited claim for orders on Zendesk AI AgentsZendesk documents an order-status use case and a separate integration path using API calls to retrieve order data. Implementation differs for AI Agents Advanced.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 scenario: a customer wants to return an item outside the normal window. Connect the order record, encode the policy, and route exceptions to the appropriate person. Confirm any refund action and duplicate-request handling in the chosen package. 1 cited claim for returns on Zendesk AI AgentsZendesk lists returns and refund requests as topics that can trigger a configured procedure, dialogue, or reply. Defining the topic alone does not implement a return or issue a refund.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 Vendor documentation only; no third-party evidence of knowledge-grounded answer quality was found. 1 cited claim for product questions on Genesys Cloud CXGenesys documents knowledge base integration for bot flows via Genesys Virtual Agent, alongside intent, slot and utterance configuration for handling customer queries.Vendor-reported
| Caveat documented Illustrative scenario: a customer asks about a feature available only on one plan. Use current plan-specific content and verify that the answer includes the relevant restriction. The email reports in the limitations section are reasons to check response length and context handling, not proof that this entire use case fails. 3 cited claims for product questions on Zendesk AI AgentsZendesk documents generated answers from connected help centres and external knowledge sources, with article permissions applied to restricted content.Vendor-reported
A small-business VP of Engineering reviewing Zendesk for Customer Service on G2 praised "the support chatbot that can be trained on customer's data to provide basic answers" and said the team uses "the chatbox to answer basic questions". The review does not cover complex or plan-specific questions.Independent report
Zendesk lists as a current limitation that generative procedures do not support search rules for knowledge sources, so an agentic AI agent cannot be told to use only specific sources for certain users inside a procedure; search rules still work in dialogues.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 Documents account lookup through configured data actions; account changes such as password resets were not found documented for the virtual agent. 1 cited claim for account issues on Genesys Cloud CXGenesys documents that AI Guides for its Virtual Agent can call data actions, so that during a conversation the agent can retrieve a contact's details from a CRM "such as name, address, contact numbers, account number, or account status".Vendor-reported
| Vendor-documented Illustrative scenario: a customer cannot sign in. A reset guide can be answered from documentation; changing an email address or unlocking an account needs identity checks and an authorised backend action. Evaluate those as separate tasks. 1 cited claim for account issues on Zendesk AI AgentsZendesk's industry guidance lists password resets and subscription updates as AI-agent use cases. It does not provide evidence that every identity or account-recovery flow is preconfigured.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 scenario: a customer disputes a repeated failed delivery. Check that the complaint becomes a ticket for the correct team, with context and a clear next step. Confirm the required intelligent-triage entitlement and triggers rather than assuming the AI agent enables them automatically. 1 cited claim for complaints on Zendesk AI AgentsZendesk documents platform triggers that route negative-sentiment tickets to a selected group and set priority. This supports complaint routing; it does not demonstrate autonomous complaint resolution.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 Marketing-page claim; the specific fields or transcript passed to the human agent are not documented on the sources reviewed. Genesys's About Virtual Agent article now documents automatic bot-conversation summaries and wrap-up codes for transfers to human agents (genesys-cloud-cx-doc-handoff-summary). The YouTube demonstration is a single test-lab build with a scripted transfer after the bot finished, not a customer-requested escalation in a production deployment. 2 cited claims for human handoff on Genesys Cloud CXGenesys states its Agentic Virtual Agent provides seamless, contextual handoffs with full context when humans step in.Vendor-reported
In a YouTube tutorial recorded in his own test lab, Seth On Call added a transfer-to-queue step after his Genesys bot flow in an inbound message flow and showed a web-messaging conversation reaching a live agent once the bot had collected the customer's details: "Thanks for chatting with us. And then I should be actually getting routed into the queue. Okay, there we go. So, we'll answer this." He then answered as the agent, with the chat conversation shown in the agent view.Independent report
| External report Illustrative scenario: a customer asks for a human after troubleshooting. Verify contact capture, transcript transfer, destination queue, and the ability to reply on the intended channel. The cited community workaround shows one implementation path, not a general handoff success rate. 2 cited claims for human handoff on Zendesk AI AgentsZendesk states that its AI agents can escalate to human teams with conversation context.Vendor-reported
Kārlis Stenders describes collecting an issue description conversationally so it appears in the transcript during an Advanced AI Agent messaging handoff. The same post reports form limitations and corrects a custom workaround; it does not quantify reliability.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. | Caveat documented The cost floor applies to the Genesys Cloud CX contract as a whole, which is the entry point for using its virtual agents. 1 cited claim for small businesses on Genesys Cloud CXVendr reports that small Genesys deployments of 25 to 100 users typically cost $75,000 to $150,000 annually, with AI and bot modules priced separately on top.Independent report
| Vendor-documented Illustrative scenario: a small team uses an existing Zendesk inbox for FAQs and human escalation. Assess setup ownership, expected usage, and required features. Plan availability is not proof that the package is affordable or appropriate for every small business. 1 cited claim for small businesses on Zendesk AI AgentsZendesk includes AI-agent access in Support and Suite plans; advanced features and add-ons depend on the selected package.Vendor-reported
|
| 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. | Vendor-documented Illustrative scenario: a growing support team needs one process across email and messaging. Confirm whether knowledge, routing, and actions behave consistently on both channels. Company size alone does not establish this operational fit. 1 cited claim for mid-market on Zendesk AI AgentsZendesk describes Suite as a multi-channel service package with ticketing, messaging, help-centre content, and AI agents.Vendor-reported
|
| 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 The Vendr data evidences enterprise-scale adoption of the Genesys Cloud CX platform, not of the AI agent capability specifically. 2 cited claims for enterprise on Genesys Cloud CXGenesys promotes deploying AI agents across voice, text, web, social and WhatsApp with a single workbench to build, test and govern them, and cites 2 million Genesys Cloud users and 29 billion real-time conversations annually.Vendor-reported
Vendr reports Genesys deployments of 500 or more users exceeding $1 million annually and mid-sized deployments of 100 to 300 users at $150,000 to $400,000 annually.Independent report
| Vendor-documented Illustrative scenario: several business units require separate permissions and approval paths. Confirm how those controls apply to the selected AI agent, connected systems, and data. Validate operational boundaries before expanding to sensitive workflows. 1 cited claim for enterprise on Zendesk AI AgentsZendesk lists enterprise options with approval workflows, sandbox access, and custom roles. These are package capabilities, not a guarantee that every AI workflow meets enterprise requirements.Vendor-reported
|
| Industry evidenceRetail and e-commerce | Vendor-documented Genesys's virtual-agent page quotes Best Buy Canada's Director of Geek Squad Remote Services: "Virtual agents are allowing our agents to focus on the work they enjoy most: solving technical issues and providing higher-value support." 1 cited claim for retail and e-commerce on Genesys Cloud CXGenesys's virtual-agent page quotes Best Buy Canada's Director of Geek Squad Remote Services: "Virtual agents are allowing our agents to focus on the work they enjoy most: solving technical issues and providing higher-value support."Vendor-reported
| Vendor-documented In a Zendesk-published story, athletic footwear brand NOBULL reports that Zendesk AI agents deflect nearly 50 percent of chat inquiries and 30 percent of overall contacts. These are vendor-published customer figures, not results this portal tested. 1 cited claim for retail and e-commerce on Zendesk AI AgentsIn a Zendesk-published story, athletic footwear brand NOBULL reports that Zendesk AI agents deflect nearly 50 percent of chat inquiries and 30 percent of overall contacts. These are vendor-published customer figures, not results this portal tested.Vendor-reported
|
| Industry evidenceFinancial services | External report Genesys publishes a customer story in which Dutch mortgage-services provider Stater says the Genesys Cloud bots it runs for six clients "resolve around 60% of end customer requests first time, without ever touching a human agent". 2 cited claims for financial services on Genesys Cloud CXGenesys publishes a customer story in which Dutch mortgage-services provider Stater says the Genesys Cloud bots it runs for six clients "resolve around 60% of end customer requests first time, without ever touching a human agent".Vendor-reported
A G2 reviewer of the Genesys Cloud CX suite writes that Agent Copilot has "been a game changer for our credit union and our agents", and that Genesys is solving "the problem of agent knowledge gaps through the use of copilot".Independent report
| Vendor-documented In a Zendesk-published story, lender Best Egg reports chat automation of roughly 80 percent and email automation rising from about 1 to about 20 percent with AI-generated responses and no backend integrations, and says knowing its AI agent can only use approved content "has helped tremendously". Authentication and end-to-end request processing are described as plans, not current use. 1 cited claim for financial services on Zendesk AI AgentsIn a Zendesk-published story, lender Best Egg reports chat automation of roughly 80 percent and email automation rising from about 1 to about 20 percent with AI-generated responses and no backend integrations, and says knowing its AI agent can only use approved content "has helped tremendously". Authentication and end-to-end request processing are described as plans, not current use.Vendor-reported
|
| Industry evidenceTelecommunications | Not established No supporting source is recorded here. Validate it with the vendor; absence of evidence does not establish a missing capability. | Vendor-documented In a Zendesk-published story, Norwegian telecom provider Phonero reports a 59 percent automation rate on about 50,000 chats a year and 30 percent on about 24,000 emails, using Zendesk AI agents in its help centres. 1 cited claim for telecommunications on Zendesk AI AgentsIn a Zendesk-published story, Norwegian telecom provider Phonero reports a 59 percent automation rate on about 50,000 chats a year and 30 percent on about 24,000 emails, using Zendesk AI agents in its help centres.Vendor-reported
|
| 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. | Vendor-documented In a Zendesk-published story, business-travel platform Serko says it launched Zendesk AI Agents in September 2025 on one product line with about 20 use cases, routing exceptions such as tickets with attachments to humans, and reports 33 percent of resolutions fully automated in the first month. 1 cited claim for travel and hospitality on Zendesk AI AgentsIn a Zendesk-published story, business-travel platform Serko says it launched Zendesk AI Agents in September 2025 on one product line with about 20 use cases, routing exceptions such as tickets with attachments to humans, and reports 33 percent of resolutions fully automated in the first month.Vendor-reported
|
| Industry evidenceHealthcare | External report A G2 reviewer of the Genesys Cloud CX suite names "Agentic use cases for healthcare" as the problem the suite is solving for them. 1 cited claim for healthcare on Genesys Cloud CXA G2 reviewer of the Genesys Cloud CX suite names "Agentic use cases for healthcare" as the problem the suite is solving for them.Independent report
| Caveat documented Zendesk states that voice AI agents are not intended to evaluate or classify emergency calls, to dispatch or prioritise emergency first response, or for emergency healthcare patient triage. 1 cited claim for healthcare on Zendesk AI AgentsZendesk states that voice AI agents are not intended to evaluate or classify emergency calls, to dispatch or prioritise emergency first response, or for emergency healthcare patient triage.Vendor-reported
|
| 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. | Vendor-documented Zendesk's government industry page markets AI agents for questions such as permit statuses, benefit eligibility and appointment scheduling. It is a marketing page; the public-sector customer stories it links do not describe an AI-agent deployment. 1 cited claim for public sector and education on Zendesk AI AgentsZendesk's government industry page markets AI agents for questions such as permit statuses, benefit eligibility and appointment scheduling. It is a marketing page; the public-sector customer stories it links do not describe an AI-agent deployment.Vendor-reported
|
| 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 | External report Genesys documents that bots built in Architect can be integrated into call, chat and message flows, and markets AI agents across voice, text, web, social and WhatsApp. 2 cited claims for web and in-app chat on Genesys Cloud CXGenesys documents that bots built in Architect can be integrated into call, chat and message flows, and markets AI agents across voice, text, web, social and WhatsApp.Vendor-reported
In the same YouTube tutorial, Seth On Call reused the bot flow in an inbound message flow and showed it working in a website messenger, offering yes/no buttons and collecting the shopper ID and coupon code before the flow's scripted reply "so we applied your coupon code. Thanks for chatting with us."Independent report
| External report Zendesk advertises web, mobile, social, email, and voice. Check channel-specific documentation and availability for the selected agent. 3 cited claims for web and in-app chat on Zendesk AI AgentsZendesk advertises web, mobile, social, email, and voice. Check channel-specific documentation and availability for the selected agent.Vendor-reported
In an independent YouTube tutorial, Stewart Gauld creates an AI agent for messaging from a new trial account, publishes it ("And just like that, your AI agent is live.") and embeds it in a web chat widget. The video shows setup, not resolution quality or a handoff.Independent report
Kārlis Stenders describes collecting an issue description conversationally so it appears in the transcript during an Advanced AI Agent messaging handoff. The same post reports form limitations and corrects a custom workaround; it does not quantify reliability.Independent report
|
| Vendor-documented Genesys's supported-languages article describes Genesys Digital Bot Flows as a tool to "build bots within Architect and then integrate them into chat, email, and message flows". 1 cited claim for email on Genesys Cloud CXGenesys's supported-languages article describes Genesys Digital Bot Flows as a tool to "build bots within Architect and then integrate them into chat, email, and message flows".Vendor-reported
| Caveat documented Zendesk advertises web, mobile, social, email, and voice. Check channel-specific documentation and availability for the selected agent. 3 cited claims for email on Zendesk AI AgentsZendesk advertises web, mobile, social, email, and voice. Check channel-specific documentation and availability for the selected agent.Vendor-reported
Zendesk lists limited control of email formatting as a current limitation of agentic AI agents on email: control over greetings and the structure of outgoing emails is limited, with enhancements planned.Vendor-reported
In September 2026, community members Paul30 and Fiona11 reported overly long email answers; Paul30 also described repeated troubleshooting suggestions despite information about completed steps. These are reports about their setups, not a measured failure rate across Zendesk deployments.Independent report
| |
| Voice and phone | Caveat documented Genesys documents that bots built in Architect can be integrated into call, chat and message flows, and markets AI agents across voice, text, web, social and WhatsApp. 3 cited claims for voice and phone on Genesys Cloud CXGenesys documents that bots built in Architect can be integrated into call, chat and message flows, and markets AI agents across voice, text, web, social and WhatsApp.Vendor-reported
In a YouTube tutorial recorded in his own test lab, Seth On Call built a Genesys bot flow with intents, slots and a knowledge base, added it to an inbound call flow and showed it recognising the caller's intent and collecting a shopper ID and coupon code by voice, after which the call flow played his scripted confirmation: "We have applied the coupon to your account. Thanks for calling in."Independent report
Replying on Genesys's community forum to reports that voice bots treat background sounds as caller utterances, Genesys's Principal Product Manager for Virtual Agent wrote that the speech models "do handle background noise, its just not by the same type of microphone sensitivity, so clearly there are still a few gaps".Vendor-reported
| Caveat documented Zendesk advertises web, mobile, social, email, and voice. Check channel-specific documentation and availability for the selected agent. 2 cited claims for voice and phone on Zendesk AI AgentsZendesk advertises web, mobile, social, email, and voice. Check channel-specific documentation and availability for the selected agent.Vendor-reported
Zendesk documents a rare known limitation of voice AI agents: the agent can occasionally produce muffled, distorted or otherwise unusual-sounding speech, which Zendesk cannot resolve during a live call. Its recommended mitigation is choosing a default voice, such as Marin or Cedar, instead of a language-specific voice before deployment.Vendor-reported
|
| SMS | Vendor-documented Genesys's SMS messaging page states that it is possible to automate SMS customer service interactions and that this "leverages AI through virtual agents for managing interactions with customers". 1 cited claim for sms on Genesys Cloud CXGenesys's SMS messaging page states that it is possible to automate SMS customer service interactions and that this "leverages AI through virtual agents for managing interactions with customers".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 Genesys documents that bots built in Architect can be integrated into call, chat and message flows, and markets AI agents across voice, text, web, social and WhatsApp. 1 cited claim for whatsapp on Genesys Cloud CXGenesys documents that bots built in Architect can be integrated into call, chat and message flows, and markets AI agents across voice, text, web, social and WhatsApp.Vendor-reported
| Caveat documented Zendesk documents adding an AI agent to WhatsApp or other social messaging channels from the agent's Brand and channels settings. It requires Zendesk messaging and a WhatsApp channel already connected to the account. 3 cited claims for whatsapp on Zendesk AI AgentsZendesk documents adding an AI agent to WhatsApp or other social messaging channels from the agent's Brand and channels settings. It requires Zendesk messaging and a WhatsApp channel already connected to the account.Vendor-reported
Zendesk says social messaging channels such as WhatsApp and Facebook Messenger do not pass the user's locale, so automatic translation of AI agent messages is not available there; the agent instead translates from the language of the customer's first message, if that language is enabled.Vendor-reported
Zendesk Community member Daniel reported in June 2026 that when customers tap Yes or No on outbound WhatsApp templates, "the AI Agent fails to identify which Use Case it should trigger", leading to incorrect routing or a generic fallback; a reply suggested distinct button payloads as a workaround.Independent report
| |
| Social messaging | Vendor-documented Genesys documents that bots built in Architect can be integrated into call, chat and message flows, and markets AI agents across voice, text, web, social and WhatsApp. 1 cited claim for social messaging on Genesys Cloud CXGenesys documents that bots built in Architect can be integrated into call, chat and message flows, and markets AI agents across voice, text, web, social and WhatsApp.Vendor-reported
| Caveat documented Zendesk advertises web, mobile, social, email, and voice. Check channel-specific documentation and availability for the selected agent. 2 cited claims for social messaging on Zendesk AI AgentsZendesk advertises web, mobile, social, email, and voice. Check channel-specific documentation and availability for the selected agent.Vendor-reported
Zendesk says social messaging channels such as WhatsApp and Facebook Messenger do not pass the user's locale, so automatic translation of AI agent messages is not available there; the agent instead translates from the language of the customer's first message, if that language is enabled.Vendor-reported
|
| Help desks | ||
| Zendesk | Vendor-documented Genesys documents data actions integrations for Salesforce, Zendesk and Microsoft Dynamics 365, as well as Google, AWS Lambda and JSON web services, whose data can drive decisions inside Architect interaction flows. Check each integration for the actions it supports. 1 cited claim for zendesk on Genesys Cloud CXGenesys documents data actions integrations for Salesforce, Zendesk and Microsoft Dynamics 365, as well as Google, AWS Lambda and JSON web services, whose data can drive decisions inside Architect interaction flows. Check each integration for the actions it supports.Vendor-reported
| External report Native Zendesk deployment is the scope of this profile. Zendesk also markets Forethought agents for other service platforms; confirm those connectors and capabilities separately. 3 cited claims for zendesk on Zendesk AI AgentsNative Zendesk deployment is the scope of this profile. Zendesk also markets Forethought agents for other service platforms; confirm those connectors and capabilities separately.Vendor-reported
Kārlis Stenders describes collecting an issue description conversationally so it appears in the transcript during an Advanced AI Agent messaging handoff. The same post reports form limitations and corrects a custom workaround; it does not quantify reliability.Independent report
In an independent YouTube tutorial, Stewart Gauld creates an AI agent for messaging from a new trial account, publishes it ("And just like that, your AI agent is live.") and embeds it in a web chat widget. The video shows setup, not resolution quality or a handoff.Independent report
|
| Salesforce | Vendor-documented Genesys documents data actions integrations for Salesforce, Zendesk and Microsoft Dynamics 365, as well as Google, AWS Lambda and JSON web services, whose data can drive decisions inside Architect interaction flows. Check each integration for the actions it supports. 1 cited claim for salesforce on Genesys Cloud CXGenesys documents data actions integrations for Salesforce, Zendesk and Microsoft Dynamics 365, as well as Google, AWS Lambda and JSON web services, whose data can drive decisions inside Architect interaction flows. Check each integration for the actions it supports.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 Announced integration (Genesys Cloud Virtual Agent collaborating with ServiceNow's AI agents); availability was expected to begin November 2025 to January 2026 and was not separately confirmed. 1 cited claim for servicenow on Genesys Cloud CXGenesys's September 2025 announcement of its expanded ServiceNow partnership describes a scenario in which the Genesys Cloud Virtual Agent authenticates a customer calling about a sudden spike in their bill and collaborates with the ServiceNow AI Agent Fabric "for bill retrieval, charge explanations and promotion checks"; availability of the Agent2Agent orchestration capabilities was expected to begin between November 2025 and January 2026.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 | Vendor-documented Genesys documents data actions integrations for Salesforce, Zendesk and Microsoft Dynamics 365, as well as Google, AWS Lambda and JSON web services, whose data can drive decisions inside Architect interaction flows. Check each integration for the actions it supports. 1 cited claim for microsoft dynamics 365 on Genesys Cloud CXGenesys documents data actions integrations for Salesforce, Zendesk and Microsoft Dynamics 365, as well as Google, AWS Lambda and JSON web services, whose data can drive decisions inside Architect interaction flows. Check each integration for the actions it supports.Vendor-reported
| 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.
· Evidence
Customer stories from YouTube for eleven agents
Zendesk AI Agents: 2 claims added
· Evidence, Re-check
Zendesk AI Agents: channel limits, industry stories and new customer reports
Zendesk AI Agents: 36 claims added · 28 claims re-checked · 14 evidence states moved
- BillingVendor-documented→Caveat documented
- Product questionsVendor-documented→Caveat documented
- Industry · Retail and e-commerceNot established→Vendor-documented
- Industry · Financial servicesNot established→Vendor-documented
- Industry · TelecommunicationsNot established→Vendor-documented
- Industry · Travel and hospitalityNot established→Vendor-documented
- Industry · HealthcareNot established→Caveat documented
- Industry · Public sector and educationNot established→Vendor-documented
- and 6 more
· Evidence, Re-check
Genesys Cloud CX: token rates, channels, help desks and first user reports
Genesys Cloud CX: 29 claims added · 5 claims edited · 13 claims re-checked · 14 evidence states moved
- BillingNot established→Vendor-documented
- Account issuesNot established→Vendor-documented
- Human handoffVendor-documented→External report
- Industry · Retail and e-commerceNot established→Vendor-documented
- Industry · Financial servicesNot established→External report
- Industry · HealthcareNot established→External report
- Channel · Web and in-app chatVendor-documented→External report
- Channel · EmailNot established→Vendor-documented
- and 6 more
· Structure
Channels and help desks become evidence rows, and records gain bylines
Genesys Cloud CX: 4 evidence states moved
- Channel · Web and in-app chatNot established→Vendor-documented
- Channel · Voice and phoneNot established→Vendor-documented
- Channel · WhatsAppNot established→Vendor-documented
- Channel · Social messagingNot established→Vendor-documented
Zendesk AI Agents: 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 · Social messagingNot established→Vendor-documented
- Help desk · ZendeskNot established→Vendor-documented
· Catalog
Launch: 22 AI customer service agents and 532 claims, every one sourced and dated
Genesys Cloud CX: Added to the catalog with 21 claims and 4 rows with evidence.
Zendesk AI Agents: Added to the catalog with 28 claims and 10 rows with evidence.
Recorded before launch
Notes the profile carried when it went live, from research before launch.
Zendesk AI Agents: Added editorial product positioning with its scope, rationale, and vendor source. Source
Zendesk AI Agents: Rechecked product documentation, a named customer example, and firsthand community reports. Removed launch coverage as independent success evidence, replaced blanket fit judgments with conditional scenarios, and distinguished setup prerequisites from failures. Source