Writing help articles that cut repeat customer questions
Kazee team · · 6 min read
Every support team in Kenya has a handful of questions it answers again and again. How do I change my delivery address? Can I get a copy of my invoice? What time does the Nakuru branch close? None of them is hard. Together they fill the day, and the customer with a difficult problem waits behind them.
A good help article gives the answer once, in a place people can find. Some customers will then help themselves, and your agents can send a link instead of typing the same reply again. It will not end repeat questions, but it can make them fewer and quicker to answer. This guide covers which questions to write up, how to write an article people can follow, where to put it, and how to keep it correct.
Start with the questions you really get
Do not begin with a list of what you think customers should know. Begin with what they ask.
- Collect a recent sample. Take the last month of emails, chats and call notes, and the messages your team answers on their phones. Fifty to a hundred is enough.
- Give each one a short label. "Delivery address", "invoice copy", "opening hours". Keep the labels few.
- Count them. Sort the labels from most to least common.
- Ask your agents. "Which question would you be happiest never to answer again?"
- Pick five to ten. Write those first.
Keep a note of the words customers used. If they ask about a "receipt" and your article says "proof of purchase", they may not recognise it as their answer. The Knowledge-Centered Service practices, a published method for support teams, make the same point: capturing the requester's words and phrases makes an article easier for the next person to find. Google's guide for site owners also advises you to think about the words a user might search for.
Some questions need a fix, not an article
Not every repeat question should become an article.
- The question points to a fault. If people keep asking what a line on your invoice means, change the invoice.
- The answer is personal. "Where is my order?" depends on the order. An article can explain how delivery works, but a person or a system still has to answer for that customer.
- The answer needs a decision. A refund or an exception needs someone with authority. Explain the rules and how to ask, then let your team decide.
What a good article looks like
People skim. GOV.UK's guidance for its writers says they often skim and do not read every sentence. Eyetracking research from Nielsen Norman Group found the same scanning habit on desktop and on mobile, and advises starting headings with the words that carry the most information. So build each article around that habit.
- One question per article. A second question gets a second article and a link.
- A title in the customer's words. "I forgot my password" beats "Credential recovery".
- The answer first. Put background last, if you need it at all.
- Numbered steps. One action in each step.
- What they should see. "You will get an SMS with a code." This tells people they are on the right track.
- What to do if it fails. Name the next step and who to contact.
- Short sentences and plain words. GOV.UK suggests splitting sentences over 25 words and using short words where they will do.
Here is the difference in practice. This version is correct, but hard to use:
"In the event that a user is unable to access their account, a password reset may be initiated via the login page, subject to verification."
This one answers the same question:
"I forgot my password. You can set a new one from the sign-in page."
- Open the sign-in page and choose Forgot password.
- Enter your phone number. We will send you a code by SMS.
- Enter the code, then choose a new password.
- No code after a few minutes? Check the number you entered, then contact us and say which number you used.
Write the steps from your own product, and follow them yourself before you publish.
Write for the people reading
- Think of the phone. Many customers will open your article on a phone, perhaps on mobile data. Keep it short, and use a picture only where words are not enough.
- Use their language. If many customers write to you in Swahili, offer your top articles in Swahili, and ask a fluent speaker to check them.
- Protect people's details. Never show a real customer's name or number in an example or a screenshot.
Where to put your articles
The simplest home is your own website. Ten questions can sit on one FAQ page. As the list grows, give each article its own page, so an agent can send a link to the exact answer.
Then put the links where the question starts: on the contact page, in the order confirmation, on the invoice and in your automatic email reply. Make it easy to reach a person from every article. An article should be a quicker way to an answer, not a wall in front of your team.
Keep a separate set of notes for agents. Escalation steps, approval limits and known faults help your team, but they do not belong on a public page.
Keep them correct
A wrong article does more harm than no article, because people trust it and then contact you annoyed.
- Give each article an owner. That person keeps it correct.
- Show a "last checked" date, so agents and customers can judge it.
- Update articles when things change. Add "check the help articles" to the list for any change to a process, form or delivery area.
- Let agents fix what they find. Knowledge-Centered Service calls this reuse is review: the people using an article improve it as they go.
- Remove what is out of date. Check the whole set a few times a year.
How to tell whether it is working
Repeat your count a month or two after publishing. Use the same labels and the same size of sample. If "invoice copy" was a large share of your sample and is now smaller, the article is probably helping. Use shares, not totals, because a busy month raises every total.
Ask your agents too. They can say whether customers still ask, and whether sending a link saves them time. Page views show that an article was opened, not that it answered the question, so do not rely on them alone.
Where Kazee fits
Kazee Desk helps with part of this job, and it is worth being clear about which part. Email, SMS and live chat arrive as tickets in one queue, so you have one place to look for repeat questions. Macros and rules can add tags, and canned responses drop a saved answer into a reply. Your team can also write knowledge base articles in categories, as drafts or published.
That knowledge base is for your own agents today. Desk has no public help centre, and its website widget is for live chat only, so the customer-facing articles in this guide would need to live on your own website.
Whichever tool you use, the method is the same: count the real questions, write the answers plainly, and give every article an owner. If you would like to see how Kazee Desk could support your agents, book a demo and we will show you around.
Sources
- Consortium for Service Innovation, KCS v6 Practices Guide, Technique 1.2: Capture the Requestor’s Context
- Consortium for Service Innovation, KCS v6 Practices Guide, Technique 4.1: Reuse is Review
- Google Search Central, SEO Starter Guide: expecting readers’ search terms
- GOV.UK Content and publishing guidance, Use a clear structure: how people read online
- GOV.UK Content and publishing guidance, Use clear language: sentence length and plain words
- Nielsen Norman Group, F-Shaped Pattern of Reading on the Web (Kara Pernice, 12 November 2017; last reviewed 19 August 2026)