Key takeaways
- Build the help center from your inbox, not from your org chart. The first 20 to 30 articles should answer the questions customers already ask most.
- Organise by what customers are trying to do (order, pay, fix, change, cancel), name articles the way customers phrase questions, and make search the main way in.
- Put help where the question happens. Link articles from the chat widget, the contact form, order emails and the product itself, not only from a footer link.
- Measure searches with no results, articles that lead to a contact anyway, and the questions still arriving in the inbox. Those three lists are your writing plan.
- Help Scout is our top pick for most small and mid-size teams because its Docs are easy to write and organise and connect directly to the inbox and chat widget your team already uses.
Most help centers are built in a burst of good intentions. Someone writes 40 articles over two weeks, organises them into categories that mirror the company's departments, and links the whole thing from the footer. A year later half the articles are out of date, the search returns nothing useful, and the inbox is as busy as ever.
A help center that works looks different. It answers the questions customers really ask, in the words they use, and it shows up where they get stuck, not three clicks away. It's also never finished: it grows every week from what the inbox teaches you.
This guide covers how to plan, write, place and maintain that kind of help center. Summer is a good time to do it, because the content you build now is what you, your customers and any AI agent will lean on when volumes rise later in the year.
Why most help centers don't get used
The symptoms are easy to spot:
- Organised around the company. Categories like "Logistics", "Finance" and "Platform" mean nothing to a customer looking for "Where's my order?"
- Titles nobody searches for. "Reverse logistics policy" instead of "How do I return something?"
- Weak search. Customers type two words, get no results and open a chat.
- Hidden. The only link is in the footer, so customers who are already annoyed never see it.
- Stale. One wrong article teaches customers not to trust the rest.
The fix is less about the tool and more about how you plan and maintain the content.
Step 1: Start from your inbox
Export your last 300 to 500 conversations from email and chat and tag each one with the customer's goal: track an order, return something, change an account, fix a problem, understand pricing, cancel. Count them. The top 20 to 30 questions are your launch list.
For each one, note the exact words customers use. "Cancel my order", "stop my order" and "I ordered by mistake" are the same article, and all three phrases belong in it.
Step 2: Organise by what customers are trying to do
Group articles by task, not by department.
| Instead of | Use |
|---|---|
| Logistics | Orders and delivery |
| Finance | Payments and invoices |
| Platform | Your account |
| Product specifications | Using [product] |
| Legal | Returns, refunds and warranty |
Keep it shallow: a handful of categories, each with a few sections at most. Customers should never need more than two clicks to reach an article, and most will come in through search anyway.
Step 3: Write articles people can scan
Every article answers one question and follows the same pattern:
- A title phrased as the question or task: "How do I change my delivery address?"
- The answer in the first two sentences. Not background, not a welcome.
- Steps as a numbered list, one action per step, with the names of buttons exactly as they appear on screen.
- Conditions and exceptions in plain words: "You can change the address until the order ships."
- What to do if it didn't work, with a link to contact you.
Write as your best agent would explain it, not as a policy document. Short paragraphs, real examples, and screenshots only where they genuinely help (and never as the only place the information appears).
If an article needs a paragraph of introduction before the answer, it's answering the wrong question.
Step 4: Make search the front door
Most visitors search first. Help them find the right article from a two-word query:
- Put customer phrases in titles and the first lines, including synonyms ("cancel", "stop", "undo").
- Check the search with your top 30 questions. If the right article isn't in the top three results, rename or rewrite it.
- Review searches with no results every week and write the missing article.
- Merge near-duplicates. Two similar articles split the search results and confuse readers.
Step 5: Put help where the question happens
A help center link in the footer reaches almost nobody. Bring articles to the moment of need:
| Where the customer is | What to show |
|---|---|
| Chat widget | Suggested articles, or an AI agent that answers from them |
| Contact form | Articles matching what they type before they send |
| Order confirmation and shipping emails | Links to delivery, changes and returns articles |
| Checkout and pricing pages | Short answers on payment, delivery and plans |
| Inside your product or account area | Contextual links next to the feature |
| Saved replies | A link to the full article at the end of the answer |
Step 6: Measure what's missing
Three reports tell you almost everything:
- Searches with no results: your missing articles.
- Articles followed by a contact: articles that don't answer the question, or answer it badly.
- Top contact reasons in the inbox: questions the help center isn't reaching.
Thumbs up or down at the end of each article helps too, especially with an optional "What was missing?" box.
Step 7: Keep it alive
- Give every article an owner and a review date, starting with policies, prices and delivery times.
- Make help content part of every change. A new returns window or feature isn't done until the article is.
- Write one or two new articles a week from what the inbox and searches tell you.
- Archive ruthlessly. Old promotions, retired products and outdated screenshots do more harm than good.
Common mistakes
- Launching with everything. A huge help center that's half wrong is worse than a small one that's right.
- Copying legal text. Terms belong on their own page. Help articles explain them.
- Only linking from the footer. Put help in the widget, the emails and the product.
- Forgetting AI readers. If you use an AI agent, it reads the same articles. Our guide on writing help content your AI agent can use covers the extra rules.
The best tools for building a help center
We looked at how easy each tool is to write in and keep organised, how good the search is, how well it connects to chat and the inbox, and how pricing suits a small team.
Help Scout's Docs is a clean, easy knowledge base that sits next to its shared inbox and Beacon, the widget that suggests articles before a customer writes in. The free plan includes one Docs site, and paid plans add more sites for separate brands or products. It suits teams that want a good-looking help center without a documentation project.
Why we like it
- Simple editor and tidy, searchable help center
- Beacon suggests articles inside the contact and chat widget
- Free plan includes a Docs site
Watch out for
- Limited for very large or heavily structured documentation
- The AI answers add-on is billed per resolution
Zendesk's help center handles hundreds of articles across brands and many languages, with roles, approvals and a community option. It suits support organisations with several people maintaining content and customers in many markets.
Why we like it
- Strong publishing workflow and permissions
- Multilingual and multi-brand at scale
Watch out for
- Priced per agent, with more advanced features on higher plans
- More setup and maintenance than a small team needs
Document360 is a dedicated knowledge base platform with versioning, categories several levels deep, workspaces and built-in AI search. It fits software companies with large, technical documentation and a dedicated owner.
Why we like it
- Deep structure, versioning and review workflows
- AI search and writing assistance included
Watch out for
- Quote-based pricing, no public price list
- Heavier than a small support team needs
Many small companies publish a public help center straight from Notion pages. It's fast to start and easy for anyone to edit, but search, analytics and the link to your support inbox are basic compared with real knowledge base tools.
Why we like it
- Free to start and very easy to edit
- Good for a first version with a handful of articles
Watch out for
- Limited help center search and analytics
- No built-in article suggestions in a support widget
Tidio isn't a knowledge base tool, but it makes the one you build work harder. Lyro, its AI agent, learns from your help center and website and answers customers in the chat widget in many languages, handing over to your team when it isn't sure. If your customers would rather ask than search, pair Tidio with any help center above. On the Premium plan, Tidio's services team also keeps Lyro's knowledge up to date for you.
Why we like it
- Answers chat questions straight from your help content
- Works with the help center you already have
- Live chat, AI agent and inbox in one tool
- Free plan includes a small allowance of AI conversations
Watch out for
- Not a place to write and publish help articles
- AI conversations are billed by volume as traffic grows
A three-week plan
- Week 1: export conversations, tag the goals, list the top 30 questions with the customer's own words.
- Week 2: set up a handful of task-based categories and write the 30 articles using the pattern above.
- Week 3: connect the help center to your chat widget, contact form and order emails, test search with real questions, and set up a weekly 30-minute review.
If most of your customers would rather ask than read, connect the help center to an AI agent so the same answers reach them in chat. Tidio's Lyro learns from your help center and website, and our guide on how to automate customer support explains how to roll it out.
Frequently asked questions
How many articles should a help center have at launch?
Fewer than you think. Twenty to thirty articles that answer your most common questions well beat two hundred thin ones. Start with what your inbox shows people ask, then add articles every week based on searches with no results and new questions.
How do I know if my help center is working?
Watch three things. Searches that return nothing show missing articles. Articles followed by a contact request show articles that don't answer the question. And if the same questions still dominate your inbox, customers aren't finding the help center at all.
Should the help center be public or behind a login?
Make general help public so customers and search engines can find it. Keep account-specific or sensitive instructions behind a login. Most small businesses only need a public help center.
Can a chatbot replace a help center?
Not really. An AI agent answers from written content, so the help center is what makes the chatbot accurate. The two work best together. Customers who like to read find the article, and customers who prefer to ask get the same answer in chat.