Build a knowledge base that deflects tickets, not one that decorates the website

Build a knowledge base that deflects tickets, not one that decorates the website

A knowledge base is the highest-leverage thing in a service hub and the most neglected. Done well, it answers the repetitive questions before they ever become tickets, which means your team spends its hours on the problems that actually need a human. Done as an afterthought, it is a graveyard of stale articles nobody reads and a search that returns nothing useful.

Build the knowledge base from your real ticket data, not from what you imagine customers ask. Pull the questions that come in most often, and write an article for each, in that order. The fastest way to find your first twenty articles is to read your last few hundred tickets and count. This is not a content project to brainstorm, it is a pattern you already have sitting in your queue.

Configure the loop between tickets and articles so the knowledge base improves itself. When an agent answers a recurring question, the answer should become or update an article, and the ticket tool should make that one click, not a separate task someone never gets to. Tag tickets that had no article so the gaps are visible, and review that list on a cadence. A knowledge base that does not grow from live tickets goes stale within a quarter.

Put the knowledge base where the customer already is. Surface relevant articles inside the support widget and at the point a customer is about to open a ticket, so the answer reaches them before they wait for a human. Deflection is not about hiding from customers, it is about giving the fast self-serve path to the people who want it while keeping the human path open for those who need it.

Measure deflection honestly. Track which articles are read, which resolve the question, and which tickets got opened anyway, and prune or rewrite the articles that do not earn their place. An unmeasured knowledge base is just a content pile; a measured one is a lever you can pull on.

INTERVIEW EWOUD: How many tickets has a well-built knowledge base deflected for a client, and what is the one article that surprised you with how much volume it absorbed?