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.
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.