Mike HeapMike is an experienced Product Manager who focuses on all the “non-development” areas of My AskAI, from finance and customer success to product design, copywriting, testing and more.
Table of Contents
- Containment rate, in more depth
- How is containment rate measured?
- What's a "good" containment rate?
- Common misconceptions about containment rate
- Misconception 1: containment rate is the same as resolution rate
- Misconception 2: a higher containment rate is always better
- Misconception 3: an abandoned conversation doesn't count as contained
- What containment rate is NOT, and how does it relate to other metrics?
- How does My AskAI handle containment rate?
- FAQs
Created time
Jun 2, 2026 02:37 PM
Title length (<60)
Author
Ecomm?
Image
Publish date
Jun 5, 2026
Slug
what-is-containment-rate
Featured
Type
Article
Ready to Publish
Ready to Publish
Containment rate is the percentage of customer conversations an AI agent or IVR handles without escalating to a human, whether or not the customer's issue was actually solved.
The word doing the damage in that definition is "handled". Containment only tells you a conversation stayed in the automated channel and never reached a person. It says nothing about whether the customer's problem got solved, or whether they walked away happy.
That's what separates it from the two metrics it gets confused with. Resolution rate measures whether the issue was actually solved; deflection rate measures whether a contact was prevented from ever opening (we cover the full three-way distinction further down). Containment sits in the middle, and it's the weakest signal of the three.
If you're on this page, a vendor has probably quoted you an "80% containment rate" and you want to know whether that number means anything. The short version: not on its own.
Containment rate, in more depth
TL;DR: Containment measures where a ticket stayed (in the automated channel) rather than whether it got solved. It started life as an IVR metric, and a high number can still hide a trapped customer.
Decagon's glossary defines it cleanly: chatbot containment rate is "a measure of how many customer interactions are fully handled by a chatbot or AI agent without needing to pass the conversation to a human representative". Most vendor definitions agree on that shape. Where they go quiet is on what "fully handled" quietly includes.
Fun fact: the term didn't start with chatbots. As Calabrio explains, containment is a contact-center metric: it originally measured the share of phone calls completed inside the IVR without routing to a live agent. It got carried over to chat wholesale, and it brought its blind spot with it: a call that ends in the IVR is "contained" whether the caller got their answer or just gave up and hung up.
Moveo puts the problem in one line we'd happily steal: "Every resolution contains. But not every containment resolves." A solved ticket is always contained, but a contained ticket isn't always solved. That gap is the whole story of this metric.
How is containment rate measured?
TL;DR: Containment rate = conversations handled without a human ÷ total conversations × 100. The fight is over what counts as "handled", and every vendor draws that line differently.
The formula is simple. The argument, in our experience, is all about the numerator.
Containment rate = (conversations handled without a human) ÷ (total conversations) × 100%
Decagon's worked example: if a chatbot handled 800 out of 1,000 conversations without passing them to a live agent, the containment rate is 80%. Moveo uses the same maths. Nothing we'd argue with there.
The trouble, from what we see across rollouts, is what counts as "handled without a human". Under most definitions it silently includes customers who abandoned the chat, customers who got a deflecting reply and gave up, and customers who accepted a wrong answer and left. Calabrio lists four failure modes that all read as success on a containment dashboard: abandonment without resolution, customers escalating elsewhere after "completing" a task, the bot misinterpreting the request, and false positives that send irrelevant answers.
And vendors count it differently, which is why two "80% contained" numbers rarely mean the same thing. Here's how the definitions diverge:
Vendor | What counts as "contained / handled without a human" | The catch |
My AskAI | Conversation not escalated to a human. We report it as AI resolution rate, not containment, and make escalation deliberately easy. | We don't claim to know an issue was solved without the customer confirming it. |
Fin (Intercom) | An end-to-end answer, or a configured Procedure that ends in a handoff, can count. | A configured handoff can count toward the number; see the Fin pricing page. |
Zendesk (Autoresolve) | A ticket that stays closed for a 72-hour quiet period. | Silence isn't the same as solved; see Zendesk's outcome-based pricing post. |
Gorgias (Automate) | Counts when the customer didn't reply. | Non-reply includes customers who gave up; see the Gorgias pricing page. |
Decagon | An internal "AI resolved" tag; the criteria aren't public. | You can't audit a numerator you can't see. |
IVR / contact-center (Teneo, Calabrio) | A call completed inside the IVR without an agent. | Abandoned calls read as "contained" too. |
What's a "good" containment rate?
TL;DR: 70-80% is the number vendors quote, but it's meaningless without a CSAT figure beside it. Read the band against your queue and your satisfaction score, never on its own.
The number vendors throw around is 70-80%, but a containment rate without a CSAT figure next to it tells you almost nothing. We'll give you the bands, then the caveat that matters more than the bands.
The two best-sourced benchmark sets (Moveo's and Calabrio's) broadly agree on the shape:
Tier | Containment range | What it usually means |
World-class | 80-90% | Mature deployment in a transactional vertical (ecommerce, fintech), APIs connected. Gartner's forward target is up to 80% by 2029. |
Solid / mature | 65-75% | Knowledge base optimized, common questions covered. |
Average | 40-65% | Partial coverage; a meaningful tail still escalates. |
Basic / rule-based | 20-40% | Rule-based bots with thin knowledge. |
Two things distort those bands. The first is your queue.
A transactional ecommerce inbox (where-is-my-order, returns, sizing) contains high; a regulated or high-judgment queue (fintech, healthcare, complex technical support) should contain lower, because more of those tickets ought to reach a person. A high containment rate in a high-judgment queue is a red flag rather than a trophy.
The second is satisfaction. Moveo puts it plainly: when containment climbs while CSAT drops, the AI is deflecting people rather than solving their problems. The fix is to never read containment without CSAT and recontact rate beside it.
We've seen that pairing run in both directions across our own rollouts. Sofar Sounds, running support on Zendesk through us, reports a 26% AI resolution rate alongside 85% AI CSAT: deliberately low containment by design, because their triage-first setup routes most of the inbox to humans with AI-prepared context.
Compare that with TravelJoy at 80% resolution and 86% CSAT, or Zinc at 68% and 97% CSAT. A "low" number with high satisfaction is a deliberate design choice, and that's invisible if you only watch containment.
It isn't just us saying the headline is gameable. The first page of Google for this term is full of CX practitioners (on LinkedIn, on YouTube, in r/CustomerSuccess) arguing that chasing containment optimizes for the wrong thing.
Common misconceptions about containment rate
TL;DR: The three big myths are that containment equals resolution, that higher is always better, and that an abandoned chat doesn't count as contained. All three are wrong.
Three myths cause most of the trouble, and they all stem from treating "contained" as if it meant "done".
Misconception 1: containment rate is the same as resolution rate
It isn't. Contained means no human was reached; resolved means the issue was solved.
We think the honest test is how easy your AI makes it to reach a person. Get that right and the number self-corrects, because anything the AI can't handle goes to a human instead. The trouble starts when teams make a person hard to reach: the number looks great and quietly stops being true.
Misconception 2: a higher containment rate is always better
Not without CSAT, and not in queues where a fast handoff is the right answer. Chasing containment pushes a team to suppress escalation, which is exactly the wrong instinct when escalation is the correct outcome. We'd rather see a lower number we trust than a high one propped up by a hard-to-find "talk to a human" button.
Misconception 3: an abandoned conversation doesn't count as contained
Under several definitions, it does. Gorgias counts a conversation when the customer didn't reply; IVR counts a call completed in-channel; Moveo's own example describes a customer who didn't understand the AI's answer and simply gave up, which still counts as contained. The give-up case is the single most misleading thing the metric hides.
What containment rate is NOT, and how does it relate to other metrics?
TL;DR: Deflection fires before a ticket opens, containment fires in-channel, and resolution measures the actual outcome. Of the three, resolution is the one worth reporting.
Containment is one of four metrics that get used interchangeably and measure different things. Here's the quick decode:
Term | What it measures | Difference from containment |
Deflection rate | A contact prevented from ever reaching a human (often pre-ticket, funnel-top). | Fires before a ticket opens; containment fires in-channel. |
AI resolution rate | Whether the issue was actually solved end-to-end. | Measures the outcome, not the channel the ticket stayed in. |
Autonomous resolution | The AI solved it start-to-finish, no human, issue confirmed. | The honest version of "contained and solved". |
Automation rate | The share of work the AI touched. | Touching a ticket isn't containing it, and containing it isn't resolving it. |
If you want the full three-way breakdown of containment vs deflection vs resolution, with the formulas, the unobservable denominators, and which one to report on, that's its own piece. The one-line version: of the three, resolution is the one worth reporting, because it's the only one that implies the customer's issue actually got solved.
How does My AskAI handle containment rate?
TL;DR: We don't optimize for containment. We report AI resolution rate paired with CSAT, keep escalation easy so the number stays honest, and charge per ticket so we've no reason to inflate it.
We don't optimize for containment, and we don't lead with it. Our dashboard reports AI resolution rate, and pairs it with AI CSAT scored across 100% of conversations rather than the usual 2-10% sample.
Our resolution number is deliberately conservative. We count a conversation as resolved when it wasn't escalated to a human, and we make escalation genuinely easy, so the customer can reach a person whenever they want, and the AI hands off when it can't answer, detects frustration, or hits a topic set for escalation. We don't pretend to know an issue was solved without the customer confirming it; we'd rather under-claim than inflate a number by making the human hard to find.
That honesty is helped by how we charge. We're usage-based (per ticket rather than per resolution), so the bill stays flat as the AI gets better, and we've got no incentive to dress a containment number up as resolution. When a vendor quotes you a containment or "resolution" rate, the useful question is always the same: what counts in your numerator, and how easy is it for my customer to reach a person?
You can see the honest version of this in the numbers. Sofar Sounds runs at 26% resolution with 85% CSAT because they chose to escalate most of the inbox; TravelJoy climbed from 24% on Zendesk's own AI to 80% with us; RecruitCRM went from roughly 35% to 68%. None of those teams would learn anything useful from a containment figure on its own.
FAQs
What is a containment rate?
Containment rate is the percentage of customer conversations an AI agent or IVR handles without escalating to a human. Crucially, it counts a conversation as contained whether or not the customer's issue was actually solved, so we treat it as a channel metric rather than an outcome metric.
What is containment rate in AI?
In AI customer service, containment rate is the share of chats or tickets an AI agent closes without handing off to a person. It's the chatbot version of the old IVR call-containment metric, and it carries the same blind spot: an abandoned or unresolved conversation still counts as contained.
What is call containment rate?
Call containment rate is the original, voice version of the metric: the percentage of phone calls resolved inside the IVR or voice bot without routing to a live agent. We'd point you to Teneo's glossary for what IVR containment measures and misses: chiefly that a caller who hangs up in frustration is "contained" too.
What is containment in customer service?
In customer service, "containment" means a contact was kept inside the self-service or automated channel and never escalated to a human agent. It's used for both chat and voice. It tells you where a ticket stayed rather than whether the customer got what they needed.
What is a good chatbot containment rate?
Mature chatbot deployments tend to land in the 65-75% range, and leaders in transactional verticals reach 80-90%. But the band is meaningless without CSAT next to it: we'd take a 60% containment rate with high satisfaction over an 85% one where customers are quietly giving up.
How do you calculate containment rate?
Containment rate = (conversations handled without a human) ÷ (total conversations) × 100. So 800 contained out of 1,000 conversations is an 80% containment rate. The maths is the easy part; the judgment call is what we'd legitimately count as "handled without a human".
What's the difference between containment rate and resolution rate?
Containment measures whether a human was reached; resolution measures whether the issue was solved. A ticket where the customer gave up is contained but unresolved. We report resolution rate rather than containment because it maps to what the customer actually wanted.
What's the difference between containment rate and deflection rate?
Deflection usually fires before a ticket opens (a help-center article answered the question, so no contact was created), while containment fires in-channel (a conversation started and stayed with the AI). Both measure the absence of a human rather than whether the problem was solved.
What is containment rate in a contact center?
In a contact center, we mostly see it refer to IVR or voice-bot containment: the share of calls handled by automation without an agent. Calabrio notes that adoption of the metric has climbed steadily, from around 36% of companies tracking it in 2018 to 67% by 2022.
What is IVR containment rate, and what's a good benchmark?
IVR containment rate is the percentage of inbound calls fully resolved in the IVR without a live agent. In our experience benchmarks vary widely by call type, since simple transactional menus contain far higher than complex support lines, so a single "good" number is misleading without the queue context.
Is a high containment rate always good?
No. A high rate can mean great self-service, or it can mean customers couldn't find the escalation path and gave up. In high-judgment queues (fintech, healthcare, complex technical support) a high containment rate is often a warning sign, because many of those tickets should reach a person.
Does an abandoned conversation count as contained?
Under most vendor definitions, yes, and that's the metric's biggest flaw. If a customer abandons the chat or simply stops replying, several platforms still count the conversation as contained. It's why we never read containment without recontact rate and CSAT alongside it.
Why do some experts say containment rate is the wrong metric?
Because, in our view, it rewards keeping customers away from humans rather than solving their problems. CX practitioners on LinkedIn and elsewhere argue that optimizing for containment incentivizes suppressing handoff, the opposite of good service when a person is what the customer needs.
Which metric should I track instead of containment rate?
Track AI resolution rate, paired with CSAT. Resolution tells you the issue was solved; CSAT catches the fast-but-frustrating case where it technically closed but the customer wasn't happy. Containment is fine as a secondary operational number, just not the one you report up the chain.
