What is ticket deflection?
Ticket deflection is the share of customer questions that are handled through self-service or automation, such as a help center or chatbot, without reaching a human agent. Deflection rate shows how many contacts were kept away from the support team. It does not show whether the customer's problem was solved.
Also called: deflection rate, case deflection, self-service deflection
Why ticket deflection matters
Deflection rate is the classic cost metric for help centers and chatbots, and many AI vendors lead with it. It is also called case deflection or self-service deflection. Every contact that avoids a human queue saves agent time, which is why the number is popular in budgets and business cases.
The problem with deflection rate
A deflected conversation is closed, but it may still be unresolved. Three very different outcomes look identical on a deflection dashboard:
Good deflection: the customer got a correct answer and was satisfied.
Bad deflection: the customer gave up.
False-positive deflection: an AI agent gave a confident answer that was wrong.
Optimizing for deflection also rewards bots that avoid escalating or admitting uncertainty, and it can push brands to hide the route to a person. Customers who give up often come back through another channel, which shows up later as repeat contacts. For this reason, teams should track deflection alongside resolution rate, repeat contacts, CSAT and the quality of escalations.
How it's calculated
Deflection rate = inquiries handled by self-service or automation ÷ total incoming inquiries × 100
For example, if 4,000 of 10,000 inquiries in a month end in self-service, the deflection rate is 40%. Some tools count help center visitors in place of inquiries. Neither version records whether the issue was solved. Containment rate, which counts conversations that stayed inside the bot, has the same blind spot.
Example
SNIPES US reports two separate figures: a 65% chat deflection rate and a 55% resolution rate. Publishing both is useful because each answers a different question: how many conversations stayed away from agents, and how many were fully resolved.
Ticket deflection and DigitalGenius
DigitalGenius is designed to resolve tickets. Its AI agent completes the request in the brand's systems, such as a cancellation, refund or replacement, and hands the conversation to the team when a person is needed.
Related terms
Read more
FAQ
What's the difference between ticket deflection and ticket resolution?
Ticket deflection counts contacts that never reached a human agent. Ticket resolution counts contacts where the customer's issue was fixed. A conversation can be deflected and unresolved, for example when a customer abandons a chatbot and phones the contact center.
Is a high deflection rate good?
A high deflection rate is good only when the deflected customers got a correct answer. Check it against resolution rate, repeat contacts and CSAT. If deflection rises while repeat contacts or complaints also rise, customers are probably being blocked from getting help.
Is ticket deflection the same as containment?
They are closely related. Containment rate counts conversations that stayed inside an automated channel, such as a chatbot or phone menu, without transferring to a person. Deflection usually counts inquiries that never became an agent ticket. Neither measures whether the issue was solved.
· By Iain Moss