Ticket deflection
Ticket deflection is the practice of resolving user questions through self-service resources, such as documentation or an AI assistant, before they become support tickets.
In a documentation context, deflection happens when a user finds the answer in the docs, a search result, or a docs chatbot instead of writing to support. The question still gets asked; it just gets answered without a human agent.
AI chatbots on docs sites deflect tickets by answering in context. A user stuck on an API error asks the widget, gets a grounded answer with a source link, and never opens a ticket. This only works when answers are accurate, which is why grounding and source citations matter more than conversation volume.
Deflection is measured with deflection rate: the share of questions resolved by self-service. Tracking it requires knowing both how many questions the assistant resolved and how many of those users still ended up in the support queue.
Frequently asked questions
Is ticket deflection the same as deflection rate?
No. Ticket deflection is the practice; deflection rate is the metric that measures it, expressed as the percentage of questions resolved without a support ticket.
Do docs chatbots actually deflect tickets?
Yes, when they are grounded in the documentation and cite their sources. A chatbot that guesses creates more tickets than it deflects, because users escalate after getting wrong answers.