What is ticket deflection?
Questions answered before they become tickets - how deflection works, how to measure it, and how not to fake it.
Ticket deflection. Ticket deflection is when a customer resolves a question through self-service - a help center article, an AI answer, an FAQ - instead of opening a support ticket. Ticket deflection is usually expressed as a rate: the share of would-be tickets that self-service resolved without a human conversation.
How it works
Deflection happens at the moments a question is about to become a ticket. A customer searches the help center and finds the article; a widget suggests relevant articles as they type into the contact form, and they stop typing; an AI assistant answers from the knowledge base and asks whether that resolved it. In each case the raw material is the same: published answers, surfaced at the right instant, with a working path to a human when the answer isn’t enough.
The honest complication is that deflection is inherently hard to observe. A ticket that was never created leaves no record, and an article page view is not evidence of a resolved question - the reader may have left more confused. Real measurement needs positive signals: a “yes, this answered it” vote, or a customer who saw a suggestion and abandoned the contact form.
Why it matters
A deflected ticket is the cheapest resolution there is - instant for the customer, free of queue time, and it costs the team nothing at the moment of need. Deflection is how a small team survives growth without hiring in step with volume: every article that absorbs a recurring question keeps absorbing it indefinitely.
The word has a dark side worth naming. Deflection achieved by hiding the contact button, burying the email address, or looping customers through an unhelpful bot is not deflection - it is abandonment with better branding, and it converts tickets into churn. The test is simple: deflection should be an offer the customer happily accepts, never an obstacle they fail to get past.
How to measure it
Deflection rate formula. Deflection rate = self-service resolutions ÷ (self-service resolutions + tickets created) × 100 - where a self-service resolution requires positive evidence, such as a “this answered my question” vote, not just a page view. Counting raw article views as resolutions inflates the rate beyond meaning.
Watch two companion signals. Ticket volume per customer (not absolute volume) tells you whether self-service is genuinely absorbing demand as you grow. And the questions that still become tickets are your writing backlog: each repeated ticket topic without a matching article is a deflection opportunity someone has already specified for you, complete with the customer’s own wording to borrow for the title.