Zendesk
Zendesk AI Agents
Customer-service AI agents connected to Zendesk knowledge, ticketing, and configured business workflows.
- Facts last checked
- Page updated
- Sources
- Vendor siteMarkdown record
Product positioning
Explore the landscapeSupport operations · Broad platform
Editorial view of product scope. This is not a performance ranking.
We place the native Zendesk offering in support operations and broad platform because its AI agents sit alongside knowledge, ticketing, and human support. This is a scope assessment, not a performance ranking.Editorial assessment
- Source
- Zendesk AI Agents product overview
- Checked
- History
- First published
- Correct this
- Request a correction with a public source. Claim ID
zendesk-ai-agents-positioning
What this review establishes
Source-based review
This review examines published product documentation and attributed reports. Workflow examples explain what to check in your setup. We have not operated this agent or measured its resolution rate; reported results remain attributed to their publisher.
Workflows, examples, and evidence
Evidence labels follow the published rubric. Each row explains what a source actually supports, the conditions that matter, and a scenario to validate. Illustrative scenarios are evaluation prompts, not completed tests.
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.
| Area | Evidence status | Evidence |
|---|---|---|
| Billing 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. | 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. Zendesk'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
|
| Orders 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: 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. Zendesk 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
|
| Returns 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: 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. Zendesk 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
|
| Product 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. | 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. Zendesk 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
|
| Account 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: 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. Zendesk'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
|
| Complaints 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: 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. Zendesk 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
|
| Human handoff Illustrative scenario Please connect me to a person who can approve this exception. What to verify: Transfer to an available team with the conversation and relevant records. Outside working hours, explain the actual follow-up path rather than promise immediate contact. | External report | Illustrative 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. Zendesk 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
|
| Small 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. | 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. Zendesk includes AI-agent access in Support and Suite plans; advanced features and add-ons depend on the selected package.Vendor-reported
|
| Mid-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. | 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. Zendesk describes Suite as a multi-channel service package with ticketing, messaging, help-centre content, and AI agents.Vendor-reported
|
| Enterprise 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 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. Zendesk 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
|
Industries the sources place it in
An industry row says where Zendesk AI Agents has been documented or reported working, not how well it worked there. Most rows are unknown for most agents, because the public record is thin. How industry evidence is counted.
| Industry | Evidence status | Evidence |
|---|---|---|
| Retail and e-commerce | 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.Vendor-reported
|
| Financial services | 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.Vendor-reported
|
| Telecommunications | 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.Vendor-reported
|
| Travel and hospitality | 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.Vendor-reported
|
| Healthcare | 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.Vendor-reported
|
| Public sector and education | 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.Vendor-reported
|
| Logistics and delivery | Not established | No reviewed source places Zendesk AI Agents in this industry. That is a gap in the public record, not evidence that the product is unsuitable. |
Channels the sources document
A channel row says the cited sources document Zendesk AI Agents answering customers there, not how well it does. A channel nobody documents is not established, which is not the same as unsupported. How channels and help desks are recorded.
| Channel | Evidence status | Evidence |
|---|---|---|
| Web and in-app chat | External report | Zendesk 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
|
| Caveat documented | Zendesk 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 | Zendesk 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 | Not established | No reviewed source documents Zendesk AI Agents answering customers on this channel. That is a gap in the public record, not evidence that it cannot. |
| 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.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 | Caveat documented | Zendesk 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 the sources document
A help-desk row says the cited sources document Zendesk AI Agents connecting to it: running inside it, handing conversations to it, or reading from it. The claim says which. How channels and help desks are recorded.
| Help desk | Evidence status | Evidence |
|---|---|---|
| Zendesk | 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.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 | Not established | No reviewed source documents Zendesk AI Agents connecting to this help desk. That is a gap in the public record, not evidence that it cannot. |
| ServiceNow | Not established | No reviewed source documents Zendesk AI Agents connecting to this help desk. That is a gap in the public record, not evidence that it cannot. |
| Freshdesk | Not established | No reviewed source documents Zendesk AI Agents connecting to this help desk. That is a gap in the public record, not evidence that it cannot. |
| Intercom | Not established | No reviewed source documents Zendesk AI Agents connecting to this help desk. That is a gap in the public record, not evidence that it cannot. |
| HubSpot | Not established | No reviewed source documents Zendesk AI Agents connecting to this help desk. That is a gap in the public record, not evidence that it cannot. |
| Kustomer | Not established | No reviewed source documents Zendesk AI Agents connecting to this help desk. That is a gap in the public record, not evidence that it cannot. |
| Gorgias | Not established | No reviewed source documents Zendesk AI Agents connecting to this help desk. That is a gap in the public record, not evidence that it cannot. |
| Gladly | Not established | No reviewed source documents Zendesk AI Agents connecting to this help desk. That is a gap in the public record, not evidence that it cannot. |
| Help Scout | Not established | No reviewed source documents Zendesk AI Agents connecting to this help desk. That is a gap in the public record, not evidence that it cannot. |
| Front | Not established | No reviewed source documents Zendesk AI Agents connecting to this help desk. That is a gap in the public record, not evidence that it cannot. |
| Microsoft Dynamics 365 | Not established | No reviewed source documents Zendesk AI Agents connecting to this help desk. That is a gap in the public record, not evidence that it cannot. |
Documented capabilities
AI agents can use multiple Zendesk help centres and connected external sources. The documentation distinguishes authenticated access to restricted articles from public-only access for unauthenticated customers.Vendor-reported
- Source
- Connecting knowledge sources to power generative replies in AI agents (Zendesk help)
- Checked
- History
- First published
- Correct this
- Request a correction with a public source. Claim ID
zendesk-knowledge-access
In a Zendesk-published case study, Babbel describes connecting backend APIs so customers can check and manage subscriptions. This is a named implementation example, published by the vendor rather than independently tested by this portal.Vendor-reported
- Source
- Zendesk AI speaks Babbel's language (vendor-published customer story)
- Checked
- History
- First published
- Correct this
- Request a correction with a public source. Claim ID
zendesk-subscription-example
Zendesk documents ticket-routing rules based on intent, sentiment, priority, and agent group. For example, negative-sentiment tickets can be assigned to a specialist team when those rules are configured.Vendor-reported
- Source
- Routing automatically triaged tickets using omnichannel routing (Zendesk help)
- Checked
- History
- First published
- Correct this
- Request a correction with a public source. Claim ID
zendesk-human-routing
G2 lists Zendesk for Customer Service, the support suite in which the AI agents are one capability, at 4.3 out of 5 across 7052 reviews. This aggregate covers self-selected reviewers of the whole suite; it is not a rating of the AI agents.Independent report
- Source
- Zendesk for Customer Service reviews on G2
- Checked
- History
- First published
- Correct this
- Request a correction with a public source. Claim ID
zendesk-ai-agents-g2-aggregate
A small-business co-founder and CTO reviewing Zendesk for Customer Service on G2 called it "Easy to setup and leverage advanced features like the AI agent to quickly resolve customers issues". The same reviewer disliked that provisioning new agents "is tied to a contract that isn't self service".Independent report
- Source
- Zendesk for Customer Service reviews on G2
- Published
- Checked
- History
- First published
- Correct this
- Request a correction with a public source. Claim ID
zendesk-ai-agents-g2-fit-small-2
A mid-market support coordinator reviewing Zendesk for Customer Service on G2 described the AI pricing as "particularly compelling: if they do not deliver a resolution, they do not charge." This is one reviewer's view of the per-resolution model.Independent report
- Source
- Zendesk for Customer Service reviews on G2
- Published
- Checked
- History
- First published
- Correct this
- Request a correction with a public source. Claim ID
zendesk-ai-agents-g2-outcome-pricing
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.Vendor-reported
- Source
- How can I add the AI agent to WhatsApp or another social messaging channel? (Zendesk help)
- Checked
- History
- First published
- Correct this
- Request a correction with a public source. Claim ID
zendesk-ai-agents-doc-whatsapp-social
Zendesk announced general availability of voice AI agents on 1 September 2026, after an early access programme that began in February 2026. Zendesk says transferred calls carry the conversation history and context into the ticket. They are not available with Talk Partner Edition, and Zendesk Contact Center support is planned for a later release.Vendor-reported
- Source
- Announcing the general availability of voice AI agents (Zendesk help)
- Published
- Checked
- History
- First published
- Correct this
- Request a correction with a public source. Claim ID
zendesk-ai-agents-doc-voice-ga
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.Vendor-reported
- Source
- NOBULL scales CX with Zendesk AI (vendor-published customer story)
- Published
- Checked
- History
- First published
- Correct this
- Request a correction with a public source. Claim ID
zendesk-ai-agents-doc-retail-nobull
In a Zendesk-published story, stationery retailer Papier says its AI agent integrates with its delivery platform, Sorted, to fetch tracking numbers and shipping statuses, and collects order IDs and photos of faulty items before a human takes over.Vendor-reported
- Source
- How an AI agent paved the way for Papier’s US expansion (vendor-published customer story)
- Published
- Checked
- History
- First published
- Correct this
- Request a correction with a public source. Claim ID
zendesk-ai-agents-doc-retail-papier
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.Vendor-reported
- Source
- Best Egg uses Zendesk AI to automate 80% of chat inquiries (vendor-published customer story)
- Published
- Checked
- History
- First published
- Correct this
- Request a correction with a public source. Claim ID
zendesk-ai-agents-doc-finserv-bestegg
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.Vendor-reported
- Source
- Phonero achieves 59% automation with Zendesk AI agents (vendor-published customer story)
- Published
- Checked
- History
- First published
- Correct this
- Request a correction with a public source. Claim ID
zendesk-ai-agents-doc-telecom-phonero
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.Vendor-reported
- Source
- Serko scales global travel support with Zendesk AI (vendor-published customer story)
- Published
- Checked
- History
- First published
- Correct this
- Request a correction with a public source. Claim ID
zendesk-ai-agents-doc-travel-serko
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.Vendor-reported
- Source
- Zendesk for government (vendor industry page)
- Checked
- History
- First published
- Correct this
- Request a correction with a public source. Claim ID
zendesk-ai-agents-doc-government-page
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
- Source
- How to use ZenDesk AI Agents | Supercharge Customer Service with AI in 2026 (YouTube, Stewart Gauld)
- Published
- Checked
- History
- First published
- Correct this
- Request a correction with a public source. Claim ID
zendesk-ai-agents-yt-messaging-setup
In a Zendesk-published customer interview, Keyvan Sadigh of Lucid Software says the team manually built AI agents across use cases and improved pilot accuracy from 50–60% to above 90% after a few weeks of effort and optimization. He does not define the accuracy metric or provide an evaluation sample, so this is a customer-reported pilot result rather than an independently verified resolution rate.Vendor-reported
- Source
- Lucid Software drives AI-powered support transformation with Zendesk | Zendesk customer story (YouTube, Zendesk)
- Published
- Checked
- History
- First published
- Correct this
- Request a correction with a public source. Claim ID
zendesk-ai-agents-yt-lucid-pilot-optimization
In a Zendesk-published customer interview, Luca Giaccardi of Qantas Loyalty reports a 30–35% initial automated-resolution target, 60% within the first two weeks and peaks of 85%; general-knowledge inquiries occasionally reached the high 90s. He conditions these results on providing the information, clear intent and ongoing case review; they are not a general Zendesk benchmark.Vendor-reported
- Source
- Qantas Loyalty soars past automation goals with Zendesk AI Agents | Zendesk customer story (YouTube, Zendesk)
- Published
- Checked
- History
- First published
- Correct this
- Request a correction with a public source. Claim ID
zendesk-ai-agents-yt-qantas-automated-resolutions
Limitations and implementation conditions
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
- Source
- Paul30 and Fiona11: response length and repeated troubleshooting (Zendesk Community)
- Published
- Checked
- History
- First published
- Correct this
- Request a correction with a public source. Claim ID
zendesk-email-response-caveat
Kārlis Stenders reported a 128-character reason-for-contact field during an Advanced AI Agent messaging migration and described a custom workaround. His follow-up corrected a setting that could submit tickets before contact details were collected. This is a configuration-specific report.Independent report
- Source
- Kārlis Stenders: Advanced AI Agent escalation form (Zendesk Community)
- Published
- Checked
- History
- First published
- Correct this
- Request a correction with a public source. Claim ID
zendesk-handoff-form-caveat
The April 2026 multilingual voice announcement describes an early access programme, with 10 languages available and additional languages planned. Confirm current voice access and the required language; general multilingual marketing does not establish voice parity.Vendor-reported
- Source
- Multilingual support for voice AI agents: April 2026 EAP announcement (Zendesk help)
- Published
- Checked
- History
- First published
- Correct this
- Request a correction with a public source. Claim ID
zendesk-voice-availability-caveat
Zendesk says external knowledge is normally refreshed every 24 hours, while help-centre searches use current content. A recently changed external policy may therefore be absent until the next sync.Vendor-reported
- Source
- Connecting knowledge sources to power generative replies in AI agents (Zendesk help)
- Checked
- History
- First published
- Correct this
- Request a correction with a public source. Claim ID
zendesk-external-knowledge-freshness
A mid-market administrator reviewing Zendesk for Customer Service on G2 wrote that "The help files in the academy section are a bit outdated for the AI Agents part."Independent report
- Source
- Zendesk for Customer Service reviews on G2
- Published
- Checked
- History
- First published
- Correct this
- Request a correction with a public source. Claim ID
zendesk-ai-agents-g2-fit-mid-market-1
An enterprise software engineer reviewing Zendesk for Customer Service on G2 asked for "more flexible pricing options, especially for smaller teams and POCs". The comment is about suite pricing, not the AI agents specifically.Independent report
- Source
- Zendesk for Customer Service reviews on G2
- Published
- Checked
- History
- First published
- Correct this
- Request a correction with a public source. Claim ID
zendesk-ai-agents-g2-fit-enterprise-3
A mid-market support coordinator reviewing Zendesk for Customer Service on G2 wrote that "implementing both the customer-facing AI agents and the agent-assist capabilities requires time and effort", including building prompts and fine-tuning, while judging the investment worthwhile.Independent report
- Source
- Zendesk for Customer Service reviews on G2
- Published
- Checked
- History
- First published
- Correct this
- Request a correction with a public source. Claim ID
zendesk-ai-agents-g2-setup-effort
A mid-market reviewer of Zendesk for Customer Service on G2 named "training for your AI agent" as a dislike: as flows change, "these should match what's on your knowledge base".Independent report
- Source
- Zendesk for Customer Service reviews on G2
- Published
- Checked
- History
- First published
- Correct this
- Request a correction with a public source. Claim ID
zendesk-ai-agents-g2-agent-training
A small-business engineer reviewing Zendesk for Customer Service on G2 said the AI could improve by "having more conversational, context-aware, and seamless handovers from the AI to the human agent". It is a request for improvement, not a measured failure.Independent report
- Source
- Zendesk for Customer Service reviews on G2
- Published
- Checked
- History
- First published
- Correct this
- Request a correction with a public source. Claim ID
zendesk-ai-agents-g2-handover
A small healthcare-business reviewer of Zendesk for Customer Service on G2 (0.5 stars) found it complicated to configure and wrote: "There's too much push to use AI when not all businesses and use cases benefit from that."Independent report
- Source
- Zendesk for Customer Service reviews on G2
- Published
- Checked
- History
- First published
- Correct this
- Request a correction with a public source. Claim ID
zendesk-ai-agents-g2-ai-push
A Trustpilot reviewer of Zendesk who set up its AI Agents objected to automated-resolution billing, writing: "They count abandoned chats as automated resolutions that you have to pay for." This is one customer's account of how resolutions were counted.Independent report
- Source
- Naila Khan: Trustpilot review of Zendesk
- Published
- Checked
- History
- First published
- Correct this
- Request a correction with a public source. Claim ID
zendesk-ai-agents-tp-ar-billing
A Trustpilot reviewer of Zendesk (3 stars) called the combination of licence, AI and resolution costs too much: "Only providing fifteen resolution credits per license per month is nothing." They added that per-resolution pricing "still does not remove my agents from having to get involved".Independent report
- Source
- Bobby: Trustpilot review of Zendesk
- Published
- Checked
- History
- First published
- Correct this
- Request a correction with a public source. Claim ID
zendesk-ai-agents-tp-resolution-credits
A German Trustpilot reviewer of Zendesk, paying a mid five-figure sum a year, described the chatbot as dated ("Der Chatbot wirkt wie aus einer anderen Zeit") and said everything has to be built laboriously with workflows and rigid decision trees ("starre Entscheidungsbäume"), which they found impractical for changing delivery times and product ranges.Independent report
- Source
- Lukas: Trustpilot review of Zendesk
- Published
- Checked
- History
- First published
- Correct this
- Request a correction with a public source. Claim ID
zendesk-ai-agents-tp-decision-trees
A Dutch Trustpilot review on Zendesk's page says the chatbot on retailer Mellerbrand's site would only communicate in Spanish ("met deze bot is alleen in het Spaans te communiceren"), briefly switching to English or Dutch before reverting. It is one deployment and may reflect its language configuration.Independent report
- Source
- Charles Zoeterwoude: Trustpilot review of Zendesk
- Published
- Checked
- History
- First published
- Correct this
- Request a correction with a public source. Claim ID
zendesk-ai-agents-tp-language
An enterprise reviewer of Zendesk for Customer Service on G2 reported that "Intelligent triage occasionally misreads sentiment on sarcastic messages", once flagging an annoyed customer as calm, and that agents still double-check tone-sensitive tickets manually. Intelligent triage is a ticket-classification feature of the Copilot add-on, separate from the AI agents; it matters here because Zendesk's sentiment-based complaint routing relies on it.Independent report
- Source
- Zendesk for Customer Service reviews on G2
- Published
- Checked
- History
- First published
- Correct this
- Request a correction with a public source. Claim ID
zendesk-ai-agents-g2-triage-sarcasm
Zendesk's migration guide says new AI agents are single-channel: one agent cannot serve both messaging and email, so a team covering both needs two agents. Essential AI agents, which were omnichannel, are being removed in December 2026.Vendor-reported
- Source
- Migrating to the new AI agents experience (Zendesk help)
- Checked
- History
- First published
- Correct this
- Request a correction with a public source. Claim ID
zendesk-ai-agents-doc-single-channel
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
- Source
- About AI agents with agentic AI (Zendesk help)
- Checked
- History
- First published
- Correct this
- Request a correction with a public source. Claim ID
zendesk-ai-agents-doc-email-formatting
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
- Source
- Why doesn’t the AI agent’s automatic translation detect the end user’s locale on social channels? (Zendesk help)
- Checked
- History
- First published
- Correct this
- Request a correction with a public source. Claim ID
zendesk-ai-agents-doc-social-translation
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
- Source
- Voice AI agent pronunciation issues (Zendesk help)
- Checked
- History
- First published
- Correct this
- Request a correction with a public source. Claim ID
zendesk-ai-agents-doc-voice-pronunciation
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.Vendor-reported
- Source
- About voice AI agents (Zendesk help)
- Checked
- History
- First published
- Correct this
- Request a correction with a public source. Claim ID
zendesk-ai-agents-doc-voice-emergency
Zendesk's pricing page includes 5 automated resolutions per agent a month on Support Team and Suite Team and 10 on Suite Professional; additional resolutions cost $1.50 each committed or $2.00 pay-as-you-go. AI-agent cost therefore rises with automated volume beyond the allowance.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-ai-agents-doc-ar-pricing
Zendesk documents that, until an AI agent ticket is escalated to a human agent (when it becomes a regular ticket), ticket triggers and automations (except the automatic close four days after solving), SLAs and omnichannel routing do not work on it; messaging triggers do.Vendor-reported
- Source
- Understanding AI agent tickets for AI agent–only conversations (Zendesk help)
- Checked
- History
- First published
- Correct this
- Request a correction with a public source. Claim ID
zendesk-ai-agents-doc-ai-agent-tickets
Zendesk Community member Christtttya reported in September 2026 that when an AI agent replies and then escalates, the First Reply SLA may already be satisfied, so the ticket "may remain in the human agent's queue without an effective SLA constraint". They asked for an SLA reset on escalation.Independent report
- Source
- Christtttya: SLA after AI agent escalation (Zendesk Community)
- Published
- Checked
- History
- First published
- Correct this
- Request a correction with a public source. Claim ID
zendesk-ai-agents-forum-sla-after-escalation
Zendesk Community member Anne-Flore reported that the ai_agent_automated_resolution tag stays on tickets that were reopened and finally answered by human agents, so "tickets are considered resolved by AI even though the final response is provided by a human agent". A reply agreed the tag "is applied too early and never removed".Independent report
- Source
- Anne-Flore: automated-resolution tag on reopened tickets (Zendesk Community)
- Published
- Checked
- History
- First published
- Correct this
- Request a correction with a public source. Claim ID
zendesk-ai-agents-forum-ar-tag
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
- Source
- Daniel: routing WhatsApp template replies in Advanced AI (Zendesk Community)
- Published
- Checked
- History
- First published
- Correct this
- Request a correction with a public source. Claim ID
zendesk-ai-agents-forum-whatsapp-templates
Basic product information
Zendesk AI Agents use connected knowledge and configured conversation flows to handle customer requests. This profile covers the native Zendesk offering; Forethought-based deployments on other service platforms require a separate scope check. Available channels and action capabilities depend on the purchased package and configuration.
- Deployment model
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
- Channels
Zendesk advertises web, mobile, social, email, and voice. Check channel-specific documentation and availability for the selected agent.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-channels
- Languages
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
- Source
- Zendesk AI Agents product overview
- Checked
- History
- First published
- Correct this
- Request a correction with a public source. Claim ID
zendesk-cmp-languages
- Help desk and CRM integrations
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
- Source
- Zendesk AI Agents product overview
- Checked
- History
- First published
- Correct this
- Request a correction with a public source. Claim ID
zendesk-cmp-helpdesks
- Knowledge sources
Zendesk help centres and external content brought in through crawlers or knowledge connectors. External content reflects its most recent sync.Vendor-reported
- Source
- Connecting knowledge sources to power generative replies in AI agents (Zendesk help)
- Checked
- History
- First published
- Correct this
- Request a correction with a public source. Claim ID
zendesk-cmp-knowledge
- Actions in backend systems
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
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
- Target customer size
Support and Suite plans span different service needs, with enterprise options available. Company size is not a tested suitability criterion.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-targetsize
- Vendor-reported performance claims
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
- Source
- Zendesk AI speaks Babbel's language (vendor-published customer story)
- Checked
- History
- First published
- Correct this
- Request a correction with a public source. Claim ID
zendesk-cmp-vendormetrics
Compare Zendesk AI Agents with
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
2 claims added
· Evidence, Re-check
Zendesk AI Agents: channel limits, industry stories and new customer reports
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
· Structure
Channels and help desks become evidence rows, and records gain bylines
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
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.
Added editorial product positioning with its scope, rationale, and vendor source. Source
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
Spotted an error?
Send a correction with a link to a public source. We reply within 14 days and record every accepted change in the changelog. See what counts as a correction.
Request a correction