---
title: "Containment is not resolution, and optimising the first destroys the second"
summary: "A support agent can post excellent containment numbers while making customers angrier. The metric that separates the two is uncomfortable and worth adopting."
canonical: https://cpaas.co/en/learn/ai-agents-and-the-containment-trap
kind: article
depth: applied
origin: original
published: 2026-08-19T16:26:18.899Z
updated: 2026-10-14T16:26:19.490Z
topics: ["AI", "Customer Experience", "Analytics"]
language: en
---
# Containment is not resolution, and optimising the first destroys the second

An AI agent goes live in support, and within a month the dashboard shows seven in ten conversations "handled without a human". Meanwhile phone volume has not fallen, complaints mention "the bot", and customers are writing in twice about the same order. Nothing is broken in the reporting; it is measuring the wrong thing. This piece explains the gap, the metric that closes it, and how to design an agent that is judged by whether it helped.

## Three words that are not synonyms

- **Deflection:** the contact never reached a queue.
- **Containment:** the interaction ended without escalation to a human.
- **Resolution:** the customer's problem was actually solved.

A system can score well on the first two while failing the third, and the failure is invisible in a dashboard that reports only those two.

> **Interactive figure — containment-resolution.** Set containment high and resolution low. The third bar is people who were counted as a success and came back.
> Available at https://cpaas.co/en/learn/ai-agents-and-the-containment-trap

## Why the gap is structural

Containment is measured at the end of an interaction. Resolution can only be measured afterwards: did they come back, did the underlying thing get fixed?

Anything measured at the end of an interaction can be improved by making the interaction harder to leave. A customer who gives up on the chat and phones instead is "contained" by every definition the dashboard uses, and has cost you two contacts instead of one. Nobody chose this metric; it accumulated, because "did this session reach a human?" is the easiest thing to instrument.

Generative AI agents add a second risk. They rarely get stuck; they answer. A confident wrong answer ends the conversation — counted as containment — and creates a problem that returns days later, often on a different channel.

Published figures for containment and resolution vary widely between sources, which itself shows the definitions are not stable. Treat any benchmark with caution; the durable point is that the gap exists and is often large.

## The metric to adopt

**Resolution rate: the share of conversations where the customer did not come back about the same issue, on any channel, within a defined window.**

- **The window.** Seven days suits most consumer support; thirty for anything tied to a delivery or billing cycle. State which you used; the number is meaningless without it.
- **Same issue, not same customer.** A customer returning about something new is a good sign. You need issue-level identity — usually a topic classifier over the conversation text, not a category someone picked.
- **Count channel switches.** A contained chat followed by a call about the same thing is a failure, and the most expensive kind. If your chat and voice systems cannot see each other, the metric will flatter you.

```diagram:checklist
# A resolution rate that means something
A stated window | Seven days for most consumer support; thirty for anything tied to delivery or billing
Same issue, not same customer | A customer back about something new is a good sign
Channel switches counted | A contained chat followed by a call about the same thing is the most expensive failure
```

## A worked example

A retailer's agent handles 10,000 conversations in a month.

```diagram:stats
88 | Deflection | Per cent that never reached a queue. Includes everyone who gave up.
71 | Containment | Per cent that ended without a human. Includes everyone who left unsatisfied.
43 | Resolution | Per cent where the problem was solved and the customer did not come back.
> Illustrative. Only the third number corresponds to something a customer would recognise as help.
```

Of the 7,100 contained conversations, 2,800 customers came back within seven days about the same issue — 1,900 by chat again, 900 by phone. So 4,300 conversations, 43% of the total, were truly resolved by the agent. The team then changed three things: escalation offered after two failed attempts, full transcript passed to the human, and an explicit "Did that solve it?" at the end. Containment fell to 64%; resolution rose to 52%; phone contacts about chat issues fell by a third.

```diagram:share
# The 7,100 "contained" conversations, seven days later
Truly resolved | 4,300 | Did not come back about the same issue
Came back by chat | 1,900 | Same issue, same channel
Came back by phone | 900 | Same issue, the most expensive way
```

## Designing for resolution

```diagram:flow
# Designing for resolution rather than containment
Offer the human early | An agent that surfaces escalation gets better resolution and, often, better satisfaction than one that resists it.
Carry the context over | The damaging pattern is not the bot that fails. It is the bot that fails and hands over blank, so the customer repeats everything.
Detect the loop | Two failed attempts at the same intent is a handover trigger, not a third attempt.
Close the issue explicitly | Ask. "Did that solve it?" is one turn and it converts a guess into a measurement.
Watch the return | Same issue, defined window, across every channel. This is the number that goes in the report.
> Every step here can lower containment and raise resolution. That trade has to be agreed before the numbers arrive.
```

Two more design rules:

- **Tell people it is an AI.** It is required in some places (see [AI Act Article 50](/en/learn/ai-act-article-50-for-messaging)) and it changes behaviour for the better: people ask clearer questions and escalate rather than argue.
- **Ground the answers.** Limit the agent to your own policies, order data and help content, and have it hand over rather than guess when those do not cover the question.

## Be honest about the goal

If the objective is cost reduction, say so and measure **cost per resolved issue**. That is a legitimate goal and it keeps the incentive attached to resolution. Cost per contained contact optimises a number that can rise while the business gets worse. The failure mode is claiming a service improvement while measuring a cost one: it works for two quarters, until someone compares the containment chart with complaint volume.

## What to ask a provider

- How do you define containment and resolution, and can I change the return window?
- Can you detect a customer returning on another channel — including voice — about the same issue?
- What exactly does the human see at handover: the full transcript, the customer's identity, the agent's reasoning?
- What does the agent do when your knowledge sources do not cover a question?

## Where to go next

Next in this track: [measuring a conversational programme](/en/learn/measuring-a-conversational-programme). For the disclosure rules that now apply to AI agents in the EU, read [AI Act Article 50 for messaging](/en/learn/ai-act-article-50-for-messaging); for the queue the agent hands over to, see [the support queue as a system](/en/learn/the-support-queue-as-a-system).

---

Published by the company behind five products in this category. Those products appear in this site's directory alongside competitors under the same published criteria and are labelled as its own. Editorial content does not recommend them.