Zendesk bot containment rate report

Last updated: April 27, 2026

Zendesk bot containment rate report

As more support teams add bots, one number shows up quickly in dashboards: bot containment rate.

That metric can be useful, but it is easy to misuse. A high containment rate sounds like success because more conversations stayed with the bot. But if those conversations never actually solved the customer’s problem, containment becomes a vanity number instead of an operations metric.

This guide explains how to report on bot containment rate in Zendesk, what the metric can and cannot tell you, and how to combine it with the rest of your support metrics dashboard.

What bot containment rate actually measures

Bot containment rate is the percentage of conversations the bot handled without handing them off to a human.

The basic formula is:

Bot-only conversations / total bot-started conversations

That tells you whether the automation kept the conversation. It does not tell you whether the customer got a real resolution.

That is why containment should always be paired with:

  • bot resolution rate
  • CSAT or bot satisfaction where available
  • escalation volume and quality
  • downstream ticket creation or follow-up rate

For the glossary definition, see bot containment rate.

Why support teams should track it

Containment rate matters because it helps answer questions such as:

  • Is the bot absorbing simple demand, or are most conversations still escalating?
  • Which intents are safe for automation and which still need humans?
  • Did a knowledge-base or workflow change improve the automation experience?
  • Is the bot reducing agent workload, or just adding another step before handoff?

For small teams, this metric is especially useful because the value of automation is usually not “having AI.” It is reducing repetitive work without making the customer journey worse.

How to build the report in Zendesk

1. Start with bot-started conversations

Use the Zendesk analytics surface that includes AI or bot interactions. If you have the prebuilt AI dashboard, start there. Otherwise use the ticket or messaging data that identifies:

  • conversations started with bot involvement
  • conversations handed to a human
  • conversations completed without handoff

The exact fields depend on your Zendesk plan and AI setup, so the first step is confirming what marks bot-handled traffic in your environment.

2. Create the containment rate view

Trend by week:

  • total bot-started conversations
  • bot-only conversations
  • containment rate

Weekly trends are easier to interpret than daily spikes, especially when automation volume is still growing.

3. Break it down by intent and channel

Your best cuts are usually:

  • intent or topic
  • channel
  • language
  • team or business line

This prevents the classic mistake of trusting one overall rate. Bots may perform well on password resets and poorly on billing or account-specific questions.

4. Add the paired metrics

Your containment report should sit beside:

  • bot resolution rate
  • escalation rate
  • CSAT or satisfaction score
  • human first response time after escalation

That turns one number into an actual operations view.

The most useful patterns to watch

High containment, high resolution

This is the good version of automation. The bot handled the conversation, and the customer issue was actually resolved.

High containment, low resolution

This is the danger case. Customers are staying with the bot, but the outcome is weak. Common reasons:

  • the bot gives generic answers that do not solve the issue
  • customers drop off without escalation
  • the automation hides a bad experience rather than reducing work

Low containment, strong human outcomes

This usually means the bot is acting more like triage than resolution. That is not necessarily bad if it routes well and shortens the path to the right human team.

Falling containment after a content change

This often means the bot lost confidence or intent coverage. Review the exact topics where handoff increased.

How to interpret containment by use case

FAQ-style requests

High containment is usually realistic for:

  • order status
  • password reset
  • shipping policy
  • account lookup

These topics have narrow answer paths, so containment can legitimately be high.

Complex support issues

Lower containment is normal for:

  • bugs
  • billing disputes
  • integrations
  • account changes involving multiple systems

If your team expects high containment here, the metric will pressure the bot to keep conversations it should escalate.

Messaging vs email

Messaging often creates different containment behavior than email because customers expect faster back-and-forth. Review channel performance separately instead of using one blended number.

Common mistakes

  • Treating containment as proof of value. It only proves the conversation stayed with the bot.
  • Ignoring silent failure. Customers who give up without rating the experience can make containment look healthier than it is.
  • Optimizing for fewer handoffs at all costs. A delayed escalation is often worse than a quick handoff.
  • Reviewing the overall rate only. Topic-level breakdowns are what make the metric actionable.
  • Forgetting the human side. If escalated conversations have terrible handoff quality, the bot may still be increasing work even with decent containment.

What to do when containment looks wrong

When containment drops:

  1. Review which intents or article paths changed.
  2. Check whether bot confidence thresholds became too conservative.
  3. Compare with escalation quality and human reply time after handoff.
  4. Look for one channel or one language driving the decline.

When containment is high but customers still struggle:

  1. Compare containment with bot resolution rate.
  2. Review satisfaction or abandonment trends.
  3. Audit transcripts for repetitive, circular bot behavior.
  4. Expand escalation triggers for topics where the bot is keeping work it should release.

Where this fits in your dashboard

Bot containment rate works best next to:

That combination shows:

  • whether automation absorbed work
  • whether escalations stayed fast
  • whether customer experience stayed intact

FAQ

What is a good bot containment rate? There is no universal target. The right rate depends on topic mix. Compare by intent first, not across the whole support operation.

Can containment rate be higher than resolution rate? Yes, and it often is. That is exactly why you should not treat containment as a success metric by itself.

Should I try to maximize containment? No. The goal is appropriate containment, not maximum containment. Good automation knows when to hand off.

What is the fastest way to improve containment responsibly? Improve the highest-volume low-complexity intents first, and make sure escalation remains easy for everything else.

See where your bot helps and where it hides work - start free