Does Having a Knowledge Base Actually Reduce Support Tickets

How Ticket Deflection Actually Works

Ticket deflection is the process of a customer finding an answer in your knowledge base instead of submitting a support ticket. It happens in two ways. First, proactive deflection: the customer visits your help center, searches for their question, and finds a satisfactory answer before deciding to contact support. Second, reactive deflection: the customer starts the contact process and is shown relevant knowledge base articles before they can submit their ticket, and the article resolves their question.

Both types require the same foundation: articles that answer real questions, written clearly enough that customers can act on the information without additional help.

What Determines the Size of the Reduction

Content Coverage

A knowledge base can only deflect tickets for topics it covers. If your top 30 questions account for 60 percent of tickets and you write articles for all 30, your maximum possible deflection is 60 percent of total volume. In practice, not every customer who could find the answer will find it, so actual deflection will be lower. Start with your highest-volume questions to maximize the impact of your first batch of articles.

Content Quality

An article that technically contains the answer but is confusing, incomplete, or uses unfamiliar language will not deflect tickets. The customer reads it, does not understand or trust the answer, and submits a ticket anyway. Quality means the answer is clear, complete, and written in the customer's language. See What Makes a Good Knowledge Base Article for writing standards.

Discoverability

Customers need to find the knowledge base before it can deflect their ticket. This means placing it prominently on your website, linking to it from contact pages, surfacing articles in chatbots, and including article links in auto-reply emails. The knowledge base should be the first thing a customer encounters when they look for help, not the last resort after they have already decided to contact support.

Search Quality

If your knowledge base search returns irrelevant results or no results for common queries, customers give up and submit tickets. Semantic search that understands natural language questions performs significantly better than basic keyword search for ticket deflection. See Knowledge Base Search Best Practices.

Realistic Expectations

Do not expect ticket volume to drop dramatically overnight. Ticket deflection builds gradually as you add content, improve articles based on feedback, and direct more traffic to the knowledge base. A typical timeline:

• Month 1: Launch with 20 to 30 articles covering top questions. Expect 5 to 10 percent deflection as customers discover the knowledge base.
• Month 3: Expanded content, improved search, better placement. Expect 15 to 25 percent deflection for covered topics.
• Month 6: Mature knowledge base with 50+ articles, tuned search, and established customer habits. Expect 25 to 40 percent deflection for covered topics.

What a Knowledge Base Cannot Deflect

Some tickets require human judgment, investigation, or action that a knowledge base article cannot provide. Account-specific issues, billing disputes, complex troubleshooting that requires access to the customer's data, and emotional situations where the customer needs empathy rather than information will always require human agents. A knowledge base frees your agents to spend more time on these complex cases by handling the simple, repetitive ones.

How to Measure Deflection

The clearest measure of ticket deflection is comparing ticket volume for specific topics before and after publishing knowledge base articles about those topics. If you received 200 tickets per month about password resets and now receive 120 after publishing a password reset article, the article is deflecting roughly 40 percent of those tickets. See How to Measure Knowledge Base Effectiveness for a full measurement framework.