# Resolution vs. containment vs. deflection

> Deflection counts tickets never opened, containment counts AI conversations never handed to a human, resolution counts conversations the vendor's rule calls resolved. Only an audited resolution checks the issue stayed solved.

Published 2026-11-12 · Reviewed 2026-11-12. Canonical: https://attify.app/compare/resolution-vs-containment-vs-deflection

Deflection counts customers who used self-service and did not open a ticket; containment counts AI conversations that were not handed to a human; resolution counts conversations the vendor's rule says were resolved. Each is a step closer to the customer's problem being solved, and only an audited resolution checks that it stayed solved: no repeat contact within 7 days, no handoff, and a read confirmation.

| | Deflection | Containment | Resolution (vendor's rule) | Audited resolution |
|---|---|---|---|---|
| Counts | Self-service sessions with no ticket after | AI conversations with no transfer to a human | AI conversations the vendor's rule counts as resolved | Claimed resolutions that held |
| Typical rule | A ratio of sessions to tickets; Zendesk divides help center sessions by users who opened tickets ([Zendesk](https://support.zendesk.com/hc/en-us/articles/4408894139930-Getting-started-with-self-service-Part-6-Tracking-essential-self-service-metrics)) | No escalation | No escalation, plus a quiet period (72 hours or less where a vendor states one), an answer from content, or the vendor's own model ([definitions compared](https://attify.app/compare/support-ai-agent-outcome-definitions)) | No repeat contact in 7 days, no handoff of any kind, judge confirmation on a sample ([standard](https://attify.app/standards/support-resolution)) |
| Can count a customer who gave up | Yes | Yes | Yes, under a silence rule | Only if they never came back and the answer read as resolving the request |
| Can count a customer who came back the next day | Yes | Yes | Yes, in a new conversation or after the window closes | No |
| Who decides | The tool's analytics | The platform's escalation record | The vendor | Rules on the customer's records, and a judge validated against people |
| Glossary | [Deflection rate](https://attify.app/glossary/deflection-rate) | [Containment rate](https://attify.app/glossary/containment-rate) | [Resolution rate](https://attify.app/glossary/resolution-rate) | [Audited resolution](https://attify.app/glossary/audited-resolution) |

## How they nest

```
self-service sessions
 └─ deflected (no ticket opened)            ← deflection
AI conversations
 └─ not handed to a human                  ← containment
     └─ counted resolved by the vendor     ← resolution rate (claimed)
         └─ held: no repeat contact, no
            handoff, read as resolved      ← audited resolution
```

Deflection sits outside the conversation count: a deflected customer has no conversation to check, so Attify's standards do not measure it.

## Synthetic example

Of 1,000 AI conversations: 850 not handed to a human (containment 85.0%); the vendor counts 700 resolved (70.0%); 441 pass the 7-day, handoff and judge checks (audited 44.1%). Three different rates, each correct under its own rule.

## Questions

### Our bot shows 80% deflection but ticket volume hasn't dropped. Why?

Deflection counts customers who did not open a ticket after self-service, not customers whose problem was solved. Some came back another way, and some would never have opened a ticket. Look at repeat contacts and tickets per customer instead.

### Which one should I report to finance?

Audited resolutions, because they check that the outcome held; the other three do not. Show the vendor's resolution rate next to it, with the rule each used.

## Sources

- Zendesk: [Getting started with self-service, Part 6: Tracking essential self-service metrics](https://support.zendesk.com/hc/en-us/articles/4408894139930-Getting-started-with-self-service-Part-6-Tracking-essential-self-service-metrics), read 2026-11-08
- Attify: [Attify Audited Resolution Standard v0.11: Relation to established metrics](https://attify.app/standards/support-resolution#relation-to-established-metrics), read 2026-11-09
