Published August 16, 2026

Zendesk AI Agents, Realistically

The demo resolves everything. Your queue will not. Here is where automated resolution genuinely works and where it costs you more than it saves.

What the pieces are

Zendesk has consolidated a lot of naming over the years, so the terms overlap.

AI agents handle a conversation end to end, in chat or email, resolving the request without a human where they can.
Answer Bot was the earlier name for article suggestions, surfacing help centre content in response to a question.
Copilot works the other way round, helping the agent rather than replacing them: drafting replies, summarising long threads, suggesting next steps.

Copilot is the one that pays back fastest for most teams, because assisting an agent has a much lower failure cost than answering a customer alone.

Where automated resolution works

It works when the answer is stable, documented and identical every time.

Where is my order, given an order number.
How do I reset my password.
What are your opening hours, your returns window, your delivery times.
Which plan includes feature X.

It fails when the customer is angry, when the answer depends on account specifics the bot cannot see, or when the question is really three questions in a paragraph. In those cases a confident wrong answer costs you more than no answer at all, because now you have an upset customer and a correction to make.

Measuring deflection honestly

The number vendors quote is conversations handled. The number that matters is tickets that never reached an agent and did not come back.

Track the reopen rate and the follow-up contact rate on bot-resolved conversations. A bot with a 40% resolution rate and a 30% follow-up rate is not deflecting 40%, and the gap between those two figures is the honest measure.

Run the ticket deflection calculator against your real numbers rather than the ones in the pitch deck.

The duplicates AI creates

This is worth knowing before you turn anything on. When a bot conversation fails to resolve, customers often abandon it and email instead, or start again in a new session.

You now have two records of one problem, from one person, minutes apart, on two channels. That is a textbook duplicate, and adding an AI layer reliably increases the rate rather than reducing it.

Worth planning for rather than discovering: merge duplicates automatically and the bot can fail safely.

Frequently asked questions

Is Zendesk Answer Bot still a product?+

The capability lives on inside the AI agent and Copilot features. Article suggestions still work the same way, the branding moved.

What resolution rate should we expect?+

For well-documented repetitive questions, a meaningful share. For anything account-specific or emotional, much less. Measure resolution net of follow-up contacts.

Do AI agents increase duplicate tickets?+

Often, yes. Abandoned bot conversations get retried by email, so one problem produces two records. Merging catches them.

Let the bot fail safely

When an abandoned bot conversation turns into a second ticket, Ticket Merger merges it into the first instead of paying an agent to answer twice.

Start free trial

14-day free trial. No credit card required.