What is ticket deflection?
Ticket deflection is when a customer resolves a question on their own, through self-service help or an automated assistant, instead of opening a support ticket. The deflection rate is the share of would-be tickets resolved this way, and it is the main number used to judge whether self-service is working.
How deflection is measured
Self-service resolutions divided by self-service resolutions plus tickets gives the rate. Deciding what counts as a resolution is harder. A help center page view is not one, since a reader who then opens a ticket anyway was not deflected. A better signal is an explicit confirmation from the user, or the absence of a ticket in the hours after they asked, and the cleanest cross-check is tickets per active user before and after the change. Assistants that log every question and its outcome make the first two signals available, which help center analytics never were.
Deflection also needs a baseline. Pulling the last ninety days of tickets and tagging them by category shows which ones are candidates. How-do-I questions, setup, configuration, and where-is-X questions typically make up the bulk of the volume and are the ones self-service can absorb. Our guide to how to deflect support tickets walks through that audit.
Why deflection rates plateau
Deflection driven by a knowledge base stalls because the articles fall behind the product, so the answer a user finds describes last quarter's interface, and because even a correct article only explains. The user still has to leave the help center, find the screen, and do the steps, and a share of them give up and open a ticket at that point.
Chatbots that read from the same knowledge base inherit the first problem, since they answer faster but from the same stale source, and a chatbot without actions inherits the second one too.
How to get past the plateau
The help has to be inside the product, so the user does not have to translate an article back into the interface. It has to be current, which in practice means it cannot depend on someone updating articles after every release. And for task questions it has to be able to perform the task. A user who asks how to change the billing email and has it changed for them has no reason to open a ticket.
Deflection should be read alongside resolution accuracy and escalation quality. A high deflection rate built on wrong answers costs more in churn than the tickets it saved, and a handoff that arrives at the support desk with the conversation attached is worth more than one that arrives cold.
How Frigade fits
Frigade deflects the how-to and where-is questions inside the product, answering primarily from its own knowledge of how the product works, with the customer's docs as a supplement, and taking the action when the question is a task. Questions it cannot answer with confidence hand off to the customer's support tool with the conversation attached, and every question and outcome is logged, which keeps the deflection number auditable rather than inferred from page views.
Common questions
- How is ticket deflection rate calculated?
- Divide the number of questions resolved by self-service by the total number of questions, meaning self-service resolutions plus tickets opened. Counting the numerator is the difficult part. Treating every help center page view as a deflection overstates it badly. A stricter definition counts a question as deflected only when the user confirmed the answer helped, or did not open a ticket within a window after asking. Comparing tickets per active user before and after a self-service change is the simplest cross-check.
- What is a good ticket deflection rate?
- Products relying on a static knowledge base and search usually plateau between 15 and 25 percent. In-product assistants that answer in context and can take actions reach 50 percent and higher, with setup and how-to categories going well above that. The categories that stay hard to deflect are bugs, billing disputes, and anything that requires a human decision.
- Knowledge baseA knowledge base is a searchable collection of articles, guides, and answers that explains how a product works, so users and support agents can find answers without asking someone. In SaaS it usually means a public help center plus an internal library that support agents and AI assistants draw on.
- Contextual helpContextual help is assistance that changes based on where the user is and what they are doing in the product, so the answer matches the screen in front of them. It ranges from a tooltip on a single field to an assistant that knows the user's current page and answers accordingly.
- Customer onboardingCustomer onboarding is the process of taking a new customer from the point of purchase to the point where they are getting the value they bought the product for. In B2B SaaS it covers implementation, account setup, training, and the first weeks of use, and it is judged by time to value and by whether the account is still active at renewal.
- In-app guidanceIn-app guidance is help delivered inside the product interface, where the user is working, instead of in a separate help center, email, or support ticket. It includes tooltips, walkthroughs, checklists, contextual hints, and in-product assistants that answer questions and complete tasks.