What Is Ticket Deflection?
Ticket deflection measures how often customers find answers without contacting support — reducing volume while improving self-service capability.
Key Takeaways
- Ticket deflection is the proportion of potential contacts resolved without an agent.
- Deflection reduces support costs without degrading customer experience.
- Chatbots, knowledge bases, and in-product help are the main deflection mechanisms.
- Deflection quality matters — deflecting customers who still have unresolved problems damages satisfaction.
What ticket deflection means
Ticket deflection occurs when a customer who would otherwise have contacted support finds the answer they need through a self-service channel — a knowledge base article, an FAQ, an in-app tooltip, or a chatbot — without ever opening a ticket. The deflection rate is the percentage of total potential support contacts (self-service interactions + actual tickets) that were resolved without agent involvement. A 40% deflection rate means that for every 100 customers who sought help, 40 resolved their issue without speaking to an agent.
Why deflection matters commercially
Support is a cost centre, and agent time is the primary cost. Deflecting tickets reduces the volume landing on agents without reducing the number of customers getting help. At scale, the economics are significant: if your average cost per ticket is £8 and you deflect 500 tickets per month, that is £4,000 saved per month — or roughly the cost of a part-time support agent. Deflection also improves the experience for customers who prefer not to wait for agent responses.
Measuring deflection rate
Deflection can be measured in several ways. For chatbots: track the percentage of chat sessions that end without escalating to a human agent. For knowledge bases: track the number of article views versus the number of tickets opened by the same users within 24 hours. For in-product help: measure whether users who engage with help content submit fewer tickets than those who do not. No single method is perfect, but combining two or three data sources gives a reliable directional picture.
Deflection without frustration
Poor deflection — pointing customers at irrelevant articles, chatbot loops that never resolve the issue, or FAQs that are months out of date — is worse than no deflection. It wastes the customer's time and often generates an angrier ticket than if they had contacted support directly. Measure deflection quality alongside deflection rate: track post-deflection CSAT and the rate at which 'deflected' users still open a ticket within 24 hours. High secondary contact rates after deflection attempts signal that your self-service content needs significant improvement.