What is deflection rate in customer support?
Deflection rate is the proportion of customer questions resolved by self-service or automation without reaching a human agent.
If a thousand people ask something in a month and seven hundred get what they needed without a person, deflection is seventy percent. It is the headline number for whether support automation is doing anything, and it is the number most often reported wrong.
Why it matters
The common error is treating every conversation that did not become a ticket as a deflection. Someone who asked a question, got a useless answer and closed the tab did not have their question deflected — they had it abandoned, and the business now has an unhappy customer and a metric that improved. An honest deflection rate counts only conversations where the question was actually answered, which means measuring it needs some signal of resolution: an explicit thumbs-up, a click on the cited page, or at minimum the absence of an immediate rephrasing of the same question.
Examples
- A visitor asks about delivery times, gets the answer, and leaves satisfied — a deflection.
- A visitor asks the same question three different ways and then emails support — not a deflection, however the tooling counts it.
- A visitor gets a refusal and a link to the contact form — honest, and correctly counted as a handoff.
Not the same as
Containment rate
Containment counts conversations that stayed inside the automated channel, whether or not they were resolved. Deflection should count only the resolved ones.
Related
term
What is containment rate?
Containment measures where a conversation ended up, not how it went. A conversation is contained if it never reached an agent — including one where the customer gave up. This makes it easy to report and easy to game: removing the handoff button raises containment immediately.
term
What is a handoff in customer support?
Every automated support system needs a way out, and the quality of that exit matters as much as the answers. A good handoff carries the transcript, so the customer is not asked to repeat what they already typed — which is the single most common complaint about support automation, and one that is entirely avoidable.
term
What is a knowledge gap in customer support?
Every refusal is a record of something customers want to know and the website does not say. Collected over a month, those refusals become a ranked list of what is missing, ordered by how many people asked — which is a content brief nobody had to guess at.
tool
Deflection rate calculator
Most deflection numbers are inflated by counting abandoned conversations as successes. This one keeps them separate, so you see both the honest rate and what a looser count would have claimed.
tool
Chatbot ROI calculator
Estimates the support cost an AI chatbot would remove, based on your ticket volume, handling time and loaded hourly cost — plus payback period against a monthly subscription.
use case
Ticket deflection you can actually verify
Deflection is usually counted as tickets that did not get filed. That number cannot tell a customer who found their answer from one who gave up. What separates them is whether the question was answered and whether the visitor could check the source.
RubyRep is this, applied to your website.
Give it your URL and it reads your pages, then answers your customers from them.
Train My RubyRep