Skip to content
Supportman
Glossary
Efficiency

Deflection Rate

— Definition —

Deflection Rate measures the percentage of potential support contacts that were handled by self-service resources — help center articles, chatbots, or FAQs — before the customer submitted a ticket or opened a live conversation. High deflection rate reduces agent workload and improves response times for tickets that genuinely require human assistance. It is the top-line ROI metric for knowledge base and automation investments.

— Formula —

Deflection Rate = (Self-service sessions that did not result in a ticket ÷ Total self-service sessions) × 100

Deflection is hard to measure precisely — you can only observe customers who didn't submit a ticket, not confirm why they didn't. The common proxy: help center searches or article views versus tickets submitted. Track the ratio trend rather than treating any single number as absolute truth.

— Benchmark ranges —

B2B SaaS, mature knowledge base

Excellent50%+
Good30–50%
Developing15–30%
Early stageBelow 15%
— Calculator —

Calculate your deflection rate

Deflection rate42.0%
— Common mistakes —
  • 1Inflating deflection by tracking article views — page views do not equal resolved issues. Use search-to-ticket conversion rates instead.
  • 2Celebrating high deflection without checking CSAT — if customers can't find answers and give up without submitting a ticket, deflection looks high but customers are frustrated.
  • 3Not segmenting by issue type — password resets deflect at 90%+; billing disputes deflect at under 10%. Aggregate deflection hides both signals.
  • 4Measuring deflection without tracking deflection quality — verify that "deflected" sessions don't generate repeat contacts via a different channel.

Five minutes to live, no IT ticket required.