How to build a help center that actually reduces support tickets

A help center is not a place to dump documentation. It is a product feature whose job is simple: answer a customer's question faster than they could get an answer by writing to you. When it works, ticket volume drops and the tickets that remain are the interesting ones.

This guide walks through how to plan, write and launch one in an afternoon, and how to keep it useful afterwards.

1. Start from your tickets, not from your product

The most common mistake is to write articles that mirror your product's menu: one article per screen, one per setting. Customers do not think in screens. They think in tasks and problems: "How do I cancel?", "Why didn't my invoice arrive?", "Can I change my e-mail?"

Export the last two or three months of support conversations and tag them by question. You will usually find that 15–25 questions cover the majority of your volume. Those are your first articles.

Copy the exact words customers use into a spreadsheet. They become your article titles and the words people will type into your search box.

2. Organise in a handful of categories

Five to eight categories are enough for most SaaS products and online stores:

• Getting started — sign-up, first steps, inviting the team
• Account & billing — plans, invoices, payment methods, cancellation
• Using the product — the main tasks, one article per task
• Integrations — one article per integration
• Troubleshooting — error messages and "it doesn't work" questions

Each category should have a one-line description; it helps both readers and search engines understand what lives there.

3. Write articles that answer one question each

A good help article has a title that is the question, a first sentence that is the answer, and then the steps. Keep it short, use numbered steps for procedures, and add a screenshot only where the interface is ambiguous.

We wrote a whole guide on this: Writing help articles people actually finish.

4. Make search the front door

Most visitors never browse categories — they search. Your help center needs search that:

• returns results as they type, not after a page load;
• tolerates partial words ("refu" should find "refund");
• shows the matching sentence, not just a title.

kbshelf builds a search index every time you publish and runs it in the visitor's browser, so results appear in milliseconds without a search server.

5. Put help where the questions happen

A help center on its own domain is great for Google and for links in e-mails. But the moment a customer gets stuck is inside your app. An in-app widget that opens search and articles in a panel catches those moments before they become tickets.

6. Use your own domain

help.yourcompany.com builds trust, keeps the SEO value of your articles on your brand, and survives a change of tools. On kbshelf, it is one CNAME record; the HTTPS certificate is issued automatically.

7. Measure two things — and act on them

You do not need dashboards full of charts. Two signals tell you almost everything:

1. "Was this helpful?" votes per article. Articles with many 👎 need a rewrite: usually the answer is buried or a step is missing.
2. Searches that returned nothing. Each one is a question you have not answered yet — often in the customer's own words. That list is your writing backlog.

Review both every two weeks. Thirty minutes of rewriting based on this data does more than a week of writing new articles nobody asked for.

8. Make it readable by AI assistants

More and more customers ask ChatGPT, Claude or Perplexity before they search your site. Publishing an llms.txt file and a plain Markdown version of each article makes your answers easy for those assistants to find and quote correctly.

A realistic launch plan

Day	What to do
Day 1	Tag recent tickets, pick the top 20 questions, create categories
Day 2–3	Write the 20 articles (or import your existing help center)
Day 4	Add your logo and colour, connect your domain, publish
Day 5	Add the widget to your app and link the help center from your e-mails
Every 2 weeks	Rewrite the least helpful articles, answer the top missed searches

If you already have a help center elsewhere, you can import it by pasting its URL and skip most of days 1–3.