Ticket deflection rate measures how effectively self-service resources—such as knowledge bases, chatbots, or in-app guidance—prevent customers from submitting a support ticket. A higher rate generally signals that help content is relevant and easy to find, reducing cost per contact and freeing agents for complex issues.
Formula: (Tickets deflected ÷ (Tickets deflected + Tickets submitted)) × 100
For example, if a chatbot resolves 400 sessions and 600 tickets are still submitted, the deflection rate is 40%.
Key things to track alongside this metric:
- Self-service page exit rates (did customers leave satisfied?)
- Post-deflection CSAT (customer satisfaction) to confirm quality wasn't sacrificed
- Deflection by channel or topic to find content gaps
Deflection rate can be misleading if poorly designed bots simply block ticket submission without solving the problem, so always pair it with satisfaction signals.