How to build a knowledge base that cuts support tickets

We earn a commission if you buy through some links on this page, at no extra cost to you. It never affects the order. How we make money.

If you build a knowledge base well, customers find answers on their own, your team answers fewer repeat questions, and AI support bots have accurate material to draw on. Built badly, it becomes a collection of outdated articles nobody reads. This guide shows how to build a knowledge base from your real support tickets, write articles people can follow, organise them so they are easy to find, and keep them up to date.

What a knowledge base is

A knowledge base, also called a help centre or FAQ site, is a searchable library of articles that answer customer questions: how to do something, how to fix a problem, and what your policies are. It can be external, for customers, or internal, for staff, with procedures and answers to complex cases. Many businesses have both.

Most help desk software includes a knowledge base, so articles can be linked from tickets, suggested in chat and used by AI bots. Standalone tools and website pages work too, but connected knowledge bases make it easier to measure which articles reduce tickets.

Why it is worth the effort

• Fewer repeat tickets: many customers would rather find an answer themselves than wait for a reply.
• Faster answers: agents link to articles instead of writing long explanations.
• Consistent information: everyone gives the same answer.
• Better AI: support bots answer from your articles, so accurate articles mean accurate bot answers.
• Sales and SEO: public help articles answer pre-sale questions and can bring search traffic.
• Easier onboarding: new staff learn from the same material.

Step 1: find topics in your tickets

The best list of topics is your support inbox. Export or review the last two or three months of tickets and group them by question. Count how often each comes up. The top twenty questions will usually cover a large share of your volume.

Also look at sales questions, chat transcripts, WhatsApp messages and searches on your website. Ask agents which explanations they type most often. Do not start by writing about every feature; start with what customers actually ask. Tagging tickets by category, as described in customer support metrics, makes this easier over time.

Step 2: choose a structure

Organise articles into a few clear categories that match how customers think, not how your company is organised. Common categories:

• Getting started
• Account and billing
• Orders, delivery and returns (for stores)
• Using specific features
• Troubleshooting
• Policies: privacy, terms, refunds

Keep the structure shallow: categories and articles, perhaps with one level of sections. Deep folders hide content. Search is how most people will navigate, so structure is a fallback, not the main route.

Step 3: write articles people can follow

Good help articles are short, specific and practical. Guidelines:

• One question per article. "How to change your delivery address", not "Account settings".
• Use the customer's words in the title, the way they ask the question.
• Answer first. Put the answer or the first step in the opening lines.
• Number the steps for tasks, one action per step.
• Use exact labels from your product or website, in bold.
• Add screenshots only where they help, and update them when the screen changes.
• Link to related articles for the next likely question.
• Keep sentences short and avoid jargon.

A simple article template

Use a consistent template so articles feel familiar:

1. Title: the question or task, in plain words.
2. Summary: one or two sentences with the answer or what the article covers.
3. Before you start: anything needed, such as permissions or information.
4. Steps: numbered, with exact labels.
5. What happens next: what the customer should see, and how long it takes.
6. If it does not work: common problems and fixes.
7. Related articles and how to contact support.

Policies follow a simpler pattern: the rule, who it applies to, any exceptions, and what to do.

Step 4: make it easy to find

Customers should reach the knowledge base from everywhere they look for help:

• A "Help" link in your website header and footer.
• Article suggestions in your contact form and chat widget before customers submit a ticket.
• Links in order confirmations, onboarding emails and invoices.
• Contextual links inside your product next to features.

Make sure search works well. Add synonyms customers use, and check the search report for queries that return nothing. Public articles can also appear in search engines, so give them clear titles and descriptions; our guide to SEO for small businesses covers the basics.

Step 5: connect it to your help desk and AI

Once articles exist, use them in daily support. Agents should link to articles in replies and flag any that are wrong or missing. Help desks can suggest relevant articles automatically while an agent writes.

AI bots and reply assistants in help desks generate answers from your knowledge base. That makes accuracy critical: if an article is outdated, the bot will confidently give the outdated answer. Before turning on a bot, review your top articles, remove contradictions, and decide which topics the bot should always hand to a person, such as refunds or complaints. See what help desk software is for the AI features available.

Internal knowledge base for your team

An internal knowledge base holds what staff need but customers should not see: how to process a refund, how to handle an angry customer, escalation contacts, workarounds for known bugs, and policies on exceptions. It helps new hires get up to speed and keeps answers consistent when experienced staff are away.

Keep it in the help desk if it supports internal articles, or in a shared workspace tool. Our project management ranking includes tools such as Notion that many teams use for internal documentation; see Notion vs ClickUp.

Keeping articles up to date

Outdated articles cause more harm than missing ones, because customers trust them. Build maintenance into your routine:

• Give each article an owner and a review date.
• When the product, prices or policies change, update related articles before or at launch.
• Add a "Was this helpful?" button and read the negative feedback.
• Let agents flag problems from inside tickets.
• Review the most viewed articles every quarter.
• Archive articles for retired features.

Measuring whether it works

Useful signals:

• Article views and the most viewed articles.
• Helpful votes and comments.
• Searches with no results, which show missing content.
• Tickets on topics that have an article, which suggest the article is unclear or hard to find.
• Contact rate: tickets per customer, which should fall over time.
• Bot resolution rate, if you use AI.

Pick the article with the most views and the worst feedback and improve it first. Small fixes to popular articles have the biggest effect.

Writing for different languages

If your customers speak several languages, start with the language most of them use, then translate your top articles. AI translation is a good first draft, but have a fluent speaker review anything about money, legal terms or safety. Keep translations in step with the original by noting which version each was translated from. Many help desks support multilingual knowledge bases and show the right language automatically.

Using video and images

Short screen recordings can make complex tasks easier to follow, but they are harder to update and to search. Use them as a supplement to written steps, not a replacement. Keep videos under two minutes and focused on a single task. For images, crop to the relevant part of the screen, highlight the button or field, and add alt text for accessibility. If you make product videos with AI tools, see making videos with AI.

Tools for a knowledge base

Most help desks include a knowledge base, so start there. Compare their help centre features in the help desk ranking and Zendesk vs Freshdesk. Current entry prices: Zendesk From USD 19 per agent per month, annual, Freshdesk From USD 19 per agent per month, annual, Help Scout Free plan, then USD 25 per user per month, Zoho Desk Free plan, then INR 420 per agent per month, annual (India price) (≈ USD 4.35). Check which plan includes the knowledge base features you need, such as multiple languages, custom domains and internal articles.

A simple website section can also work for a very small business, especially if you only need a handful of articles; see how to start a business website.

A two-week plan to launch

1. Days 1 to 2: list the top twenty questions from your tickets.
2. Day 3: choose categories and an article template.
3. Days 4 to 9: write the twenty articles, a few each day, and have a colleague test the steps.
4. Day 10: add links in your website, contact form and emails.
5. Days 11 to 14: agents link to articles in replies and note gaps.

Then add a few articles each week, based on new tickets and search gaps.

Common mistakes

• Writing about features instead of answering real questions.
• Long articles covering many topics at once.
• Titles in company jargon that customers would never search for.
• No owner or review date, so articles go stale.
• Hiding the knowledge base so customers never find it.
• Turning on an AI bot before checking that articles are accurate.

Example articles for common business types

To get started faster, here are typical first articles by business type:

• Online store: delivery times and costs, tracking an order, returns and refunds, payment methods, changing or cancelling an order, sizing guides.
• Software or app: creating an account, resetting a password, inviting team members, changing plan, cancelling, connecting integrations, common error messages.
• Service business: booking and rescheduling, what to expect at an appointment, prices and payment, cancellation policy, preparing documents.
• Training or courses: accessing courses, certificates, payment plans, refunds, technical requirements.

Adjust to your own tickets, but these lists cover many of the questions small businesses receive. Reducing no-shows through clear booking information is covered in how to reduce appointment no-shows.

Writing style tips that make a difference

Small style choices make articles much easier to use:

• Write in the second person: "Select Settings", not "The user selects Settings".
• Start steps with a verb: "Open", "Select", "Enter".
• Say where to look before what to do: "In the top right corner, select your name".
• Avoid "simply" and "just"; if it were simple, customers would not need help.
• Use the same word for the same thing throughout, matching your product.
• Explain what the customer will see after each important step.
• Keep paragraphs to two or three sentences.

Read each article aloud before publishing. If you stumble, a customer will too.

Knowledge base and SEO

Public help articles can attract search traffic from people with the exact problems your product solves, including people who are not customers yet. Use clear titles that match search phrases, write a short description for each article, link related articles together, and make sure search engines can crawl the help centre. Avoid publishing thin, duplicate articles just to cover keywords; one complete article beats five near-identical ones. Our guide to keyword research explains how to find the phrases customers use.

Questions