Pro free for 30 days.No card.Start free →

Customer FAQ and knowledge base: how to write one that cuts support questions

How to build a customer FAQ and knowledge base without special software: find the questions customers actually ask, write short plain-language answers, organize them so people can find them, check what works, and keep articles current.

By WorkBOS Content Desk7 min read
Wooden signpost with direction signs pointing to help and answers (Photo by geralt on Pixabay)
Photo: geralt / Pixabay

Customers would often rather find an answer themselves than wait for a reply. At the same time, every question you answer by hand costs your small team time that could go to selling, delivering or fixing things. A well-built customer FAQ and knowledge base sits between the two: it answers the common questions once, in a place customers can find at any hour, and it frees you to handle the cases that truly need a person.

This guide walks you through building one without special software or a writing team. You will learn how to find out what customers really ask, how to write answers that are short and clear, how to organize them, how to tell whether they work, and how to keep them from going stale. It is written for owners and small teams, and the advice applies whether you publish on your website, in a portal or in a shared drive.

FAQ or knowledge base: what is the difference?

The two terms overlap, and small businesses usually need both in simple form.

  • An FAQ is a short list of the questions people ask most, with brief answers. It suits businesses with a limited range of products or services.
  • A knowledge base is a larger library of help articles, how-to steps and policies, grouped by topic and searchable. It suits businesses where customers need step-by-step guidance.

Start small and grow

Begin with an FAQ of ten to fifteen answers. As the list grows, group it by topic, and turn the longer answers into full articles. You do not need to publish a hundred pages on day one.

Check whether an FAQ is the right tool first

The US government's Digital.gov plain-language guidance makes a point worth remembering: FAQs often frustrate readers, so first ask whether clear main content would do the job. In its section on special cases in plain-language writing, it says an FAQ should supplement a page that explains the basics, not replace it or walk through a whole process. For a business, that means your pricing page should explain pricing, and the FAQ should handle the leftover questions.

Step 1: Find out what people really ask

Do not guess. The same Digital.gov guidance warns against assuming what kinds of questions people will have, and recommends using the questions customers actually ask in calls and emails.

Where to look

  • Your support inbox and chat history, for repeated subjects.
  • Notes from sales calls: what do prospects ask before they buy?
  • Reviews and social comments, which often contain the same worry in different words.
  • Your team: ask each person for the three questions they answer most often.

Count and rank

Put the questions in a simple list, merge duplicates, and count how often each appears. The questions at the top are your first articles. Aim to answer the top ten before you write anything else.

Step 2: Write answers people can use

An FAQ answer is not a marketing page. It should help a worried or busy person get on with their day.

Use the customer's wording

Write the question the way a customer would say it: "How do I change my delivery address?" rather than "Address amendment procedure." If you can, use the exact phrase from real emails. Digital.gov also advises plain language, with no insider jargon or unexplained abbreviations.

Answer first, then explain

Put the answer in the first sentence, then add detail only if needed. A good pattern is:

  1. A one-sentence direct answer.
  2. Numbered steps, if there is a process.
  3. One example or screenshot, if it helps.
  4. A line about what to do if it does not work, such as a contact link.

Keep each answer unique

The Digital.gov guidance says each answer should add unique content. Repeating the same point in several places makes pages go stale, because when something changes you have to remember every spot. Write it once and link to it from elsewhere.

Keep the list short enough to scan

A long, flat list overwhelms readers, who may give up before finding their answer. Group questions under clear headings such as Ordering, Payments, Delivery and Returns, Account, so people can jump to the right section.

Step 3: Organize so people can find things

Writing a good answer is only half the job. If customers cannot find it, it might as well not exist.

A simple structure

| Level | Example | |---|---| | Topic (5-8 of them) | Billing | | Article | How do I get a copy of my invoice? | | Related articles | Update my billing details; Payment methods |

Make search work

If your site or tool has a search box, test it with ten real customer phrases. Help Scout's guidance on improving help content suggests checking what customers search for and whether those searches return results; frequent searches with no matching article show a content gap, and retitling articles with the short phrases customers actually type can help.

Put a link to the relevant answer in your order confirmation, onboarding email, invoice footer or checkout page. The best place for an answer is in front of the customer at the moment they would otherwise write to you.

Step 4: Tell whether it is working

Publishing is not the finish line. Check three things each month.

  • Ticket data. Help Scout notes that when answers are hard to find, customers contact support next. If tickets keep arriving on a topic that already has an article, the article is not working. If tickets arrive on a topic with no article, you have found a gap.
  • Searches with no results. These are a free list of the articles you should write next.
  • Feedback. Add a simple "Did this answer your question?" prompt at the end of each article and read the "no" responses.

A short checklist for each article

  • Does the title match how customers phrase it?
  • Is the answer in the first sentence?
  • Are the steps correct today?
  • Does it link to a next step or a person?
  • Is a date or owner recorded for the next review?

Step 5: Keep it up to date

Nothing damages trust like a help article describing a button that no longer exists.

Give each article an owner and a review date

Put the owner's name and a review date in your internal tracking sheet. Review quarterly, or whenever a price, policy or process changes. If you change a product or policy, updating the matching article should be part of the same job, not an afterthought.

Retire what you no longer need

Remove or merge articles that nobody reads and nobody asks about. A smaller, accurate library beats a large, partly wrong one.

Common mistakes

  • Writing from the inside out. Using your internal names and process rather than the customer's words.
  • Making the FAQ do the work of the main page. Basics belong on the page itself.
  • Long, unsorted lists. Customers give up before finding the answer.
  • Duplicated answers. They drift out of sync.
  • Publish and forget. Out-of-date answers create new complaints.
  • No path to a person. Always give a way to reach you when the article does not help.

Where WorkBOS fits

If your team already works in WorkBOS, its drives and office suite can hold your internal answer library, where staff keep the approved wording for common questions so everyone replies the same way. A public-facing FAQ can live on your own website or be shared with clients through the branded client portal, and forms can capture the questions that are not yet answered. Roles and permissions let you decide who may edit published answers, and the audit log records changes. See the docs for how each piece works and pricing for plans. Related reading: our guide to handling angry customers and building a help desk workflow.

Frequently asked questions

Q: How many questions should an FAQ have? A: Start with the ten to fifteen most common, then add as new patterns appear. Keep the list short enough to scan, and group by topic once it grows.

Q: Where should I publish my knowledge base? A: Anywhere customers already look: a section of your website, your client portal, or linked from emails and invoices. Visibility matters more than the tool.

Q: How often should I update it? A: Review every article at least quarterly, and update the matching article immediately whenever a price, policy or process changes.

Q: Should I write for search engines or for customers? A: Write for customers first, using their own words in titles and headings. That also tends to match what they type into search.

Q: Can AI help write articles? A: It can draft them from your real ticket history, but a person who knows the facts must review every answer before it is published.

Sources are linked in the text above: Digital.gov, Help Scout.

Run it all from one place

Projects, clients, finance, people and AI employees in one system. Start free, no card needed.

Start free →