# Containment Rate

Containment rate is the percentage of customer conversations that are fully resolved inside an automated system, such as a chatbot or interactive help center, without escalating to a human agent. It measures how well your automated channels answer and close customer issues on their own. A high containment rate means your automation is handling the routine work so your team can focus on the complex cases.

**Formula:** (Conversations resolved by automation / Total conversations in the automated channel) × 100

## How is containment rate calculated?

Most teams measure it by tracking conversations that enter an automated channel and comparing how many end without escalation:

| Metric                 | Definition                                                                                                              |
| ---------------------- | ----------------------------------------------------------------------------------------------------------------------- |
| Total conversations    | All customer interactions that start in the automated channel (chatbot, virtual assistant, or search-first help center) |
| Resolved conversations | Interactions that end without the customer requesting a human agent or opening a support ticket                         |
| Containment rate       | (Resolved / Total) × 100                                                                                                |

A contained conversation is one where the customer gets the answer they need and leaves satisfied. The system tracks whether the session ended naturally or whether the customer clicked "contact support" or asked to speak to someone.

## Why does containment rate matter?

A high containment rate means your automated systems are doing the work they were built for: answering routine questions instantly so your team has time for the conversations that need judgment, empathy, or deep product knowledge. It tells you whether your knowledge base and automation are good enough to close the loop without a human.

For benchmarks, strategies to improve this metric, and how containment fits into the full support efficiency picture, read the [complete guide to containment rate](/customer-support-metrics-and-kpis/containment-rate-complete-guide).

## Related terms

- [CX glossary](/glossary): browse all customer experience terms.
- [Deflection rate](/glossary/deflection-rate): tickets prevented before they reach an agent.
- [Self-service rate](/glossary/self-service-rate): customers who resolve issues on their own.

## Frequently asked questions

### What is a good containment rate?

It depends on the complexity of your product and the strength of your automated systems. Many teams reach 50 to 70 percent containment when their knowledge base and chatbot are well tuned. The goal is not to contain every conversation, but to resolve the routine ones so your team can focus on the complex cases.

### How is containment rate different from deflection rate?

Containment rate measures full resolution inside an automated system. Deflection rate measures tickets prevented before they reach a human. Deflection is broader: a customer who finds an answer and leaves may never have intended to contact you. Containment assumes the customer entered your system and the automation kept them there.

### How do you calculate containment rate?

Divide the number of conversations fully resolved by automation by the total number of conversations that entered the automated channel, then multiply by 100. A contained conversation is one that ends without escalation to a human agent.

## See it work

Helpfeel is built to move this number. We set up and tune the knowledge base so your automated channels resolve more on their own. [See how the done-for-you model works](/platform).