# What is Ticket Deflection?

Also called case deflection, deflection rate.

Ticket deflection is the resolution of a support request through self-service or automated response so that it never enters a human agent's queue. Deflection rate is the share of contacts handled this way. The metric is widely reported and easy to inflate, because an abandoned request and a resolved one can look identical in the data.

Counting is the central difficulty. If a customer opens a help article and does not file a ticket, that is recorded as deflection. It may equally mean they gave up, found the answer elsewhere, or churned. Measurement approaches that avoid this include asking whether the answer helped, and tracking whether the same person returns with a related question shortly afterward.

Genuine deflection concentrates in a small number of question types. In most support operations a short list of repeated questions accounts for a large share of volume: order status, password resets, billing dates, basic configuration. These are answerable from a record lookup and have little ambiguity, which is what makes them suitable for automated resolution.

Deflection is a poor goal in isolation. Optimizing for it alone rewards making human contact difficult, which suppresses tickets without resolving anything and reliably shows up later in retention data. The usual corrective is to pair deflection with a satisfaction measure and a repeat contact measure, so that suppression and resolution can be told apart.

The cases that should not be deflected are reasonably consistent across published guidance: anything involving a complaint, a cancellation, a payment dispute, a safety concern, or a distressed customer. These carry relationship consequences and require accountability that a self-service path cannot provide, and routing them straight to a person is the better outcome.

## Key points

- Requests resolved without reaching a human queue
- Abandonment and resolution look alike in raw counts
- Concentrates in a few high volume, low ambiguity questions
- Must be paired with satisfaction and repeat contact metrics
- Complaints, disputes, and cancellations should not be deflected

## In practice

A subscription service finds that where is my order and how do I change my delivery date account for over half of inbound contacts, both answerable from the order record. An agent answers them directly in chat and follows up with a one question check on whether the answer helped. Contacts mentioning cancellation, a charge dispute, or a damaged item route immediately to a person.

## Related terms

- [AI in Customer Support](/en/glossary/ai-in-customer-support)
- [First Contact Resolution](/en/glossary/first-contact-resolution)
- [Escalation Path](/en/glossary/escalation-path)
- [Coverage](/en/glossary/coverage)
- [Exception Handling](/en/glossary/exception-handling)

[Back to the AI Glossary](/en/glossary)