Containment rate is the share of customer conversations an automated system, such as an AI agent or chatbot, handles from start to finish without escalating to a human. If 100 conversations reach the bot and 70 end without a handoff, the containment rate is 70%. It is used as a headline efficiency metric because every contained conversation is one a human did not have to staff. The number is easy to game in one direction, though: it counts conversations that did not reach a human, not conversations that were actually resolved, so a customer who abandons the chat in frustration is counted exactly the same as one whose problem was solved.
In short
- Containment rate is the percentage of conversations an AI agent or bot completes without handing off to a human.
- It measures deflection, not resolution. A customer who gives up, times out, or is dead-ended without an escalation path is still counted as contained.
- A high containment rate can therefore hide a bad customer experience, which is why it should never be read on its own.
- The honest version pairs containment with a resolution check: of the conversations that were contained, how many actually solved the customer’s problem?
- Answering that requires reading what the AI agent said, not just whether a human got involved, which is a quality-assurance question rather than an analytics one.
- Because Kaizo does not sell its own AI agents, it can score those conversations and separate true containment from abandonment without any incentive to flatter the bot’s number.
How containment rate is calculated
The formula is straightforward. Take the conversations that entered the automated channel over a period, count the ones that ended without being escalated to a human, and divide.
Containment rate = conversations resolved without human escalation / total conversations handled by the automation.
So if 1,000 conversations reach an AI agent in a week and 650 of them never touch a human, containment is 65%. The appeal is obvious: it maps almost directly onto cost, because a contained conversation carries no agent handling time. That is also why it tends to become the number a bot deployment is judged on, and why it deserves more scrutiny than it usually gets.
Why the number can mislead
The weakness is in the word “resolved” in that formula, because most containment measurements do not actually check for resolution. They check for the absence of a human. Those are not the same thing, and the gap between them is where the metric goes wrong.
A conversation counts as contained if the customer got what they needed and left satisfied. It also counts as contained if the customer could not find an escalation path and gave up, if they abandoned the chat halfway through, if they got a wrong answer and did not realize it, or if the bot answered a question they were not asking and they closed the window. Every one of those is a failure, and every one of them improves the containment rate.
This creates a perverse incentive. The fastest way to raise containment is to make escalation harder, and a bot that hides the path to a human will post a better number than one that offers help the moment it is stuck. The metric rewards exactly the behavior that most damages the customer relationship.
Containment rate vs resolution rate
The distinction that fixes most of the problem is the one between containment and resolution.
| Containment rate | Resolution rate | |
|---|---|---|
| What it counts | Conversations that ended without a human | Conversations where the customer’s issue was actually solved |
| A customer who gives up | Counted as a success | Counted as a failure |
| What it is a proxy for | Cost avoided | Job done |
| How to measure it | Read the routing log | Read the conversation |
How to use containment rate honestly
The metric is not useless. It is a legitimate efficiency signal as long as it is never read alone. The honest way to use it is to pair it with a resolution check: of the conversations you contained, how many actually resolved the customer’s problem, and how many were abandonments or wrong answers wearing a containment badge.
Answering that means looking at what the AI agent said and whether it was correct, complete, and appropriate, which is a quality-assurance question, not an analytics one. It is the same discipline you would apply to a human agent, applied to a bot: read the interaction, score it against a rubric, and trace the score back to the evidence. Our guide to measuring containment rate without fooling yourself walks through how to do that, and how to QA AI agents and chatbots covers the scoring method underneath it.
One structural note. A platform that sells its own AI agents has a reason to prefer the flattering version of this number, because containment is how those agents are sold. Kaizo does not sell AI agents. It scores the conversations they produce, which means it can report true containment against abandonment with nothing to protect.
Frequently asked questions
What is a good containment rate?
There is no single benchmark worth quoting, because containment rate on its own does not tell you whether customers were helped. A high number produced by hiding the escalation path is worse than a lower number where every contained conversation was genuinely resolved. Judge containment against a resolution check rather than against an industry average.
What is the difference between containment rate and deflection rate?
They are often used interchangeably. Both describe conversations kept away from a human agent. Deflection sometimes refers specifically to steering a customer to self-service before a conversation starts, while containment usually refers to a conversation the automation handles to completion. Both share the same blind spot: neither, by default, checks whether the customer’s problem was solved.
Does a high containment rate mean the AI agent is working well?
Not by itself. Containment counts the absence of a human, not the presence of a resolution, so a customer who abandons the chat is counted as contained. To know whether the AI agent is working, pair containment with a resolution check that reads the actual conversations and scores whether each one solved the issue.
How do you measure whether a contained conversation was actually resolved?
By scoring the conversation itself, not the routing outcome. That means evaluating what the AI agent said against a rubric: was the answer correct, complete, and appropriate, and did the customer’s issue end resolved rather than abandoned. It is the same quality-assurance approach used on human agents, applied to automated conversations.
Related terms
See what your containment rate is actually hiding
Bring the conversations your AI agent contained last month. We will score them against your own rubric and show you how many were genuinely resolved and how many were abandonments counted as successes. Because Kaizo does not sell its own AI agents, every score traces back to the evidence in the transcript, so you can trust the resolution number as much as the containment one.
