Deflection rate measures the percentage of customer inquiries that are redirected away from human agents — typically to self-service resources, FAQ pages, or automated responses. It's one of the most commonly cited metrics in customer service automation, and one of the most misleading.

Deflection rate = (Inquiries handled without a human agent / Total inquiries) x 100

The problem with deflection rate as a success metric is that it measures activity, not outcomes. A customer who is shown a help article and gives up is counted as "deflected" — even though their issue is unresolved and their experience was negative. A customer who is routed through a chatbot loop and eventually abandons the conversation is "deflected." A customer who calls in after being deflected creates a new interaction that may also be deflected.

This is why leading CX organizations are shifting from deflection to resolution as their primary automation metric. The question isn't "did we keep the customer away from a human?" but "did we actually solve their problem?"

• The distinction has real business consequences. High deflection rates often mask:

• Hidden demand: Customers who need help but can't get it, leading to churn

• Channel shifting: Customers deflected from chat who call in (or vice versa), inflating total contact volume

• Repeat contacts: Customers who come back because their issue wasn't actually resolved

AI vendors who lead with deflection rate as their primary metric are often optimizing for the wrong thing. The more meaningful metrics are resolution rate (was the issue solved?) and customer effort score (how hard did the customer have to work?).

Related terms: resolution rate, self-service rate, customer effort score, cost per resolution