- Deflection Rate
- A metric showing how often customers are redirected from assisted support to self-service, automation, or lower-cost channels.
Why CX and AI teams search for this
Automation teams search for deflection rate when measuring self-service ROI, while CX leaders use it to check whether automation creates hidden effort.
Deflection Rate measures how often customer contacts are redirected away from assisted support toward self-service, AI agents, knowledge base articles, community content, or automated workflows.
Deflection can be valuable when customers get faster answers. It can be harmful when it blocks customers from the help they need.
Deflection vs Containment: Deflection focuses on reducing assisted support demand. Containment focuses on whether the customer stayed within the automated or self-service channel. Resolution determines whether the issue was actually solved.
Why It Matters: Deflection rate is often used to justify automation ROI, but it should be paired with CSAT, CES, sentiment, repeat contact, and escalation metrics to make sure cost savings are not coming at the expense of customer experience.
Examples
- A help center article prevents a customer from creating a billing support ticket.
- A chatbot routes customers to a return workflow instead of opening a live chat.
- A high deflection rate is investigated because repeat contacts increased the next day.
FAQs
What is a good deflection rate?
A good deflection rate depends on channel, issue type, and customer segment. It should be judged alongside resolution, sentiment, repeat contact, and customer effort.
Can deflection hurt customer experience?
Yes. Deflection hurts CX when customers are blocked from human help, routed to irrelevant content, or forced to repeat themselves later.