Deflection rate
Deflection rate is the percentage of customer issues resolved without human agent involvement. The most-quoted metric in AI-for-support sales.
Deflection rate is the percentage form of ticket deflection: (tickets closed without human) / (total incoming tickets). It is the metric every AI-for-support vendor leads with and the metric most likely to mislead a buyer if used in isolation.
Because the metric depends on what counts as the denominator, definitions vary: some teams include only contacts that reached a help center or bot, others include all inbound demand. Comparing rates across vendors or periods is only meaningful if the definition is held constant. A high deflection rate paired with rising repeat contacts or falling satisfaction usually means issues are being pushed away rather than resolved.
In context
The arithmetic is simple; the interpretation is not. A 60% deflection rate can mean "60% of customers got the right answer fast" or "60% of customers gave up and went to Twitter." The dashboard treats them identically.
Published benchmarks: Zendesk enterprise median 41.2%, top quartile 58.7%, with a 30-40 percentage-point gap between vendor marketing claims and field reality. Intercom Fin: ~41% average, 65% peak. ServiceNow Virtual Agent: 45-60% range cited, with 80-94% in best-case deployments.
The honest reading: deflection rate is a useful diagnostic when paired with AHT, FRT, CSAT, and recoverability. As a standalone contracted metric, it incentivizes the wrong behavior, close the ticket without resolving the issue.
How Auralis uses Deflection rate
Auralis publishes up to 75% deflection in repetitive categories. The contract includes the outcome metrics that determine whether that deflection moves the business or carries hidden cost.