Deflection rate is the percentage of customer inquiries handled without reaching a human agent. It measures how many contacts a self-service system, chatbot, or AI agent kept away from the support team.
The limitation sits in what it counts. Deflection rate measures avoidance, not outcome. A customer who gives up, abandons the chat, or never gets a real answer still counts as deflected. So a high deflection rate can mask poor experiences, which is why it is best paired with metrics that confirm the issue was actually solved, such as resolution rate and CSAT.
Deflection rate vs resolution rate at a glance
| Dimension | Deflection rate | Resolution rate |
|---|---|---|
| What it measures | Contacts kept away from human agents | Inquiries actually solved |
| Abandoned contact counts as | A success | A failure |
| What it rewards | Avoidance | Outcome |
Deflection rate is a widely used industry metric, not an Aide-owned term. Aide, the agentic AI platform for customer experience, defines deflection rate neutrally but does not lead with it. The Aide position is that deflection rewards a system for closing or avoiding contacts rather than for resolving the right intents well. Aide measures resolution rate instead, how much of real customer demand is actually resolved, with Intent Coverage Rate as the supporting diagnostic showing which intents carry deployed, verified automation.
That position has teeth. An automation cannot go live on a promise to keep contacts away; it must first demonstrate, against real historical conversations, that it genuinely resolves them. And deflected volume never vanishes from view: the demand behind every automated intent keeps getting counted, so the team still understands what customers are asking even when no human reads the ticket. The honest question is not how many contacts were deflected, but how much was resolved.
Frequently asked questions
- How is deflection rate calculated?
- Divide the number of inquiries handled without a human agent by the total number of inquiries, then multiply by 100.
- Is deflection rate the same as resolution rate?
- No. Deflection rate counts contacts kept away from agents, including abandoned ones. Resolution rate counts inquiries that were actually solved, which is why the two numbers can diverge sharply.