Deflection Rate
Deflection rate is the percentage of potential support tickets that are prevented before they reach a human agent. It measures how many customers find the answer they need through a help center, knowledge base, or automated system, without creating a ticket. A higher deflection rate means fewer tickets in the queue and more customers getting instant answers.
Formula: (Tickets prevented / Total potential tickets) × 100
How is deflection rate calculated?
Most teams measure it one of three ways, depending on the data available:
| Method | Calculation |
|---|---|
| Direct | (Help center visits with no ticket created / Total visits) × 100 |
| Inverse | 100% − ticket creation rate, where ticket creation rate = (tickets created / help center visits) × 100 |
| Ticket-based | (Baseline tickets − current tickets / Baseline tickets) × 100 |
The direct method is the most common because it ties the metric straight to help center behavior.
Why does deflection rate matter?
A high deflection rate means customers get answers instantly, at any hour, without waiting for an agent. For the business, each prevented ticket frees your team for the complex issues that genuinely need a human. It is one of the clearest signals that your self-service resources are working. For benchmarks, calculation nuances, and strategies to move the number, read the complete guide to deflection rate.
Related terms
- CX glossary: browse all customer experience terms.
- Self-service rate: customers who resolve issues on their own.
- Containment rate: issues fully resolved inside an automated system.
Frequently asked questions
What is a good deflection rate?
It varies by industry and maturity. Mature self-service programs reach 50 to 70 percent, meaning half or more of potential tickets are resolved before they reach an agent. The trend matters more than the absolute number: a rising rate means your knowledge base is improving.
How is deflection rate different from self-service rate?
Deflection rate measures tickets prevented. Self-service rate measures issues customers resolve on their own. They overlap, but deflection focuses on what never arrives in the queue, while self-service focuses on the customer succeeding independently.
How do you calculate deflection rate?
Divide tickets prevented by total potential tickets, then multiply by 100. In practice, teams measure it as knowledge base visits that did not create a ticket, or as 100 percent minus the ticket creation rate.
See it work
Helpfeel is built to move this number. We set up and tune the knowledge base so your customers find answers before they need to contact support. See how the done-for-you model works.