Ticket Deflection
Also known as: Case Deflection, Issue Deflection, Support Deflection
Ticket Deflection refers to strategies and mechanisms that prevent support tickets from being created by resolving customer issues through alternative means — typically self-service, automation, or proactive support.
Why Ticket Deflection Matters
Effective deflection:
- Reduces costs — Each deflected ticket saves money
- Improves customer experience — Instant answers beat waiting for agents
- Scales efficiently — Handle more customers without adding staff
- Focuses agents — Let humans handle complex issues that need expertise
How to Measure Deflection
Deflection Rate = (Issues Resolved Without Ticket / Total Issues) × 100
Measuring deflection is challenging. Look for:
- Pre-ticket interceptions — Users who viewed help content before abandoning ticket form
- Bot resolutions — Chatbot conversations that didn’t escalate
- Successful self-service — Knowledge base articles rated helpful
- Reduced ticket volume — Decline in tickets for documented topics
Deflection Methods
Knowledge Base Deflection
Intercept users searching for help with relevant articles before they create tickets.
In-Context Help
Provide help content embedded in the product where issues occur.
Chatbots and Automation
Use AI or rule-based bots to answer common questions instantly.
Proactive Communication
Alert customers about known issues before they contact support.
Community Forums
Enable customers to help each other with common problems.
Effective Deflection Strategies
Before Contact
- Robust, searchable knowledge base
- In-app help and tooltips
- Proactive status updates for known issues
- Onboarding that prevents common problems
During Contact Attempt
- Smart search suggestions on ticket form
- Bot engagement before human routing
- Recommended articles based on issue description
- Community answers for similar questions
Process Optimization
- Fix bugs that generate tickets
- Improve UX to prevent confusion
- Clearer product documentation
- Better onboarding and training
Deflection vs. Obstruction
Important distinction:
Good deflection: Quickly solves the customer’s problem without agent involvement
Bad obstruction: Makes it hard to reach support, frustrating customers
Always ensure customers can reach humans when self-service doesn’t work.
Deflection Analysis with TicketBoard
TicketBoard helps identify deflection opportunities by analyzing:
- Most common ticket topics and tags
- Recurring issues across customers
- Patterns in ticket creation
- Trends that indicate emerging issues