What is deflection rate?

Deflection rate is the share of would-be support tickets that never reached a person because the customer found an answer first, from a help article, a search result or an AI agent. The formula is tickets avoided divided by tickets expected without self-service, and the denominator is the problem: nobody counts the tickets that were not created. Every deflection figure is an estimate built on a baseline.

It matters because deflection is the number most vendors lead with and the one least likely to mean what you think. The honest version compares ticket volume before and after launch, adjusted for traffic, or counts conversations where the visitor confirmed the answer helped and did not open a ticket within some window. The loose version, common on chatbot dashboards, counts any chat that never reached a person as deflected, which is containment under another name and includes every visitor who gave up.

Where it runs out: "deflected" sounds like "resolved" and is not. A visitor who read a wrong answer and left is deflected. A visitor who got a right answer and emailed anyway is not. Benchmarks by industry range widely partly because each source counted differently. Use deflection as a volume estimate for sizing and cost, report resolution rate under a strict definition for quality, and never let a vendor's deflection figure stand in for either without its formula beside it.