Deflection rate
Deflection rate is the share of customers who used self-service (a help center, a bot, an AI agent) and did not go on to open a support ticket. It measures tickets avoided, not problems solved, and there is no single industry formula: each tool defines what counts as a deflection.
One documented version#
Zendesk's self-service score, also called the ticket deflection ratio, divides help center sessions by the number of users who opened tickets: a ratio of 4:1 means that for every four people who tried self-service, one submitted a request (Zendesk). It is a ratio of activity, not a count of solved issues.
What deflection cannot tell you#
- Whether the customer's problem was solved, or the customer gave up.
- Whether the customer came back on another channel later.
- Whether the customer would have opened a ticket at all.
Deflection, containment and resolution#
Deflection is about tickets that were never opened. Containment is about AI conversations that were not handed to a human. Resolution is about whether the issue was solved, and audited resolution about whether it stayed solved for 7 days with no handoff. See the side-by-side.
Attify's standards do not measure deflection: there is no conversation to check when a ticket was never opened.
Questions
Why is our deflection rate high but ticket volume flat?
- A deflection count cannot see customers who gave up on self-service and came back another way, or who never would have opened a ticket. Compare tickets per customer before and after, and repeat contacts after AI conversations.
Is deflection the same as resolution?
- No. Deflection says a ticket was not opened; resolution says the problem was solved. A deflected customer can still be stuck.