You build a customer service knowledge base in four steps: gather the questions you already get, group them and keep the most repeated, write a clear answer for each, and keep them all in one tidy place with a review date. You don't need a special program: it can live in a document with search or a page on your website. What matters isn't the tool, it's that the answers are written down, the same for everyone, and up to date.
This is what you need before thinking about a chatbot. A good chatbot leans on a knowledge base; without one, it has nothing to draw from. But the knowledge base already saves you time even if you never build a bot.
What is a knowledge base and what's it for?
It's the place where what your company knows how to answer lives. The questions customers ask over and over —hours, lead times, how to return something, what a service includes— with their clear answer alongside, in one place and kept current. Nothing more.
It serves three things at once. So whoever's on the desk doesn't improvise or answer differently depending on the day. So a customer can find the answer themselves without having to write. And, if one day you build a chatbot, so that chatbot answers from your information and not from whatever it makes up. The same afternoon's work covers all three uses.
What do you need before you start?
Less than it seems:
- Two weeks of real questions. Not the ones you think you get: the ones that actually arrive. Note them as they come, in the customer's words.
- Someone who knows the answers. Usually whoever's been on the desk longest. Half an hour of their time beats any downloaded template.
- A place to keep them. A shared document, a spreadsheet or a page. As long as it has search and the whole team can see it, that's enough to start.
Notice "buy software" isn't on the list. That comes later, if at all, and only once you know what to keep inside.
How is it built, step by step?
Four steps, in order:
- Gather the questions you already get. Two weeks noting every query that comes in by phone, email or WhatsApp. Unfiltered: the real ones, exactly as the customer puts them.
- Group them and sort by frequency. Merge the ones that are the same question in different words. Put them most to least repeated. The top ten or fifteen are almost all the volume.
- Write one clear answer per question. Short, with concrete facts: lead times, prices, steps. The one you'd give on the phone, but written once and well thought out.
- Keep them in one place with a review date. All together, with search, reachable by the team. And a date to review them, because an answer with an old price lies on its own.
Start with fifteen questions, not a hundred. Fifteen good, up-to-date answers are worth more than a hundred half-written ones no one maintains.
How do you write a good answer?
The way you'd speak, not the way a lawyer would write. A useful answer gets to the point in the first line and then, if needed, adds the detail. Use the customer's words, not your internal ones: if they say "when will it arrive", don't title it "logistics delivery timeframes".
| Answer that gets in the way | Answer that helps | |
|---|---|---|
| Length | Three paragraphs of caveats | Two sentences with the concrete fact |
| Language | Internal company jargon | The words the customer uses |
| Specificity | "Shortly", "as soon as possible" | "Within 24-48 working hours" |
| When it doesn't apply | Silence or "it depends" | "If it's a holiday, the next working day" |
When is it NOT worth building?
Rarely, but there are cases:
- If every query is unique. If your customers never ask the same thing twice because each case is its own world, there are no frequent questions to gather. There the value is in the person, not the document.
- If you alone handle ten queries a month. At that volume, building and maintaining the base costs more than it saves. Keep four template answers and move on.
- If you won't maintain it. An abandoned knowledge base, with old data, is worse than none: it gives false information with an official air.
As soon as there's volume and repetition, it almost always pays off. The rest of the time, the key is one thing: don't build it if you won't look after it.
Frequently asked questions
What is a customer service knowledge base?
It's your customers' frequent questions with a clear, up-to-date answer for each, kept in one tidy place. It's used so your team answers the same way and well, for your website, and to feed a chatbot if you decide to build one.
Do I need a chatbot to have a knowledge base?
No, it's the other way round. First you build the knowledge base; the chatbot comes later and leans on it. Without written, organised answers, a chatbot has nothing to draw from. The knowledge base already saves you time even if you never add a bot.
How often should you update the knowledge base?
Whenever a fact changes (a price, a lead time, a policy) and with a full review every few months. An out-of-date answer is worse than none, because it gives false information with an official air. A visible review date helps.
How many questions should it have to start?
Start with the ten or fifteen you get most, not a hundred. Those few cover most queries. Fifteen good, up-to-date answers are worth more than a hundred half-written ones no one maintains.
First the written answer, then the machine
A knowledge base is gathering the questions you already get, writing a clear answer for each, and keeping them in a tidy, current place. You build it in an afternoon with the fifteen most frequent questions, and it serves your team, your website and a chatbot.
The order matters: the knowledge base comes before the chatbot, not after. And it only works if someone maintains it: an answer with an old fact does more harm than no answer.
Does your team answer the same thing twenty times a day?
We can look at what customers actually ask, organise the answers and put them somewhere useful, then decide whether a chatbot leans on them or isn't needed. We start from what you already know how to answer. Tell me how you handle support today.
See the chatbots service Let's talk about your case