How to write a knowledge base article
A generated draft gets you most of the way. The rest is knowing what a knowledge base article actually is, the format and types they come in, what a finished one looks like, and how a clean article becomes the answer your AI agent gives.
What is a knowledge base article?
A knowledge base article is a single help-center page that answers one question or explains one task — how to do something, how to fix an error, what a feature is, or how to get started. One article, one job. Together they form a knowledge base your customers can search instead of emailing you.
The distinction that matters is against internal documentation. Documentation describes a system for people who already work on it. A knowledge base article answers a question for someone who is stuck right now, does not know your vocabulary, and wants to stop reading as soon as the problem is solved. That difference changes the title (written the way a customer would search, not the way your team names things), the length (as short as the answer allows), and the structure (predictable, so readers can skim to the part they need).
A useful test: if someone landed on the article from a search engine with no other context, would it solve their problem on its own? If it only makes sense after reading three other pages, it is documentation, not a knowledge base article.
Knowledge base article types
Most help centers only need six article types. What changes between them is the shape the reader needs — steps, causes, a definition — not the tone or the formatting. Pick the type first and the structure follows. The builder above writes to whichever one you choose.
- How-to
- a single clear goal, the prerequisites needed before starting, then numbered steps in the exact order the reader performs them. Each step is one action that starts with a verb. Note where a screenshot would go with [screenshot: what it shows].
- Troubleshooting
- name the symptom the way a user would describe it, then list the likely causes from most to least common, each with the fix as numbered steps. Start with the quickest check. End with what to do if none of the fixes work.
- Getting started
- what the reader will be able to do by the end, what they need first, then the setup as numbered steps from zero to a first success. Keep it to the shortest path that works; link deeper topics rather than covering everything.
- Concept explainer
- a plain one-sentence definition first, then why it matters and when it applies, then how it works in sections. Use a concrete example. No numbered steps unless the concept genuinely is a sequence.
- FAQ-style
- a short intro, then the real questions a reader has about this topic as sub-headings, each with a direct answer that leads with yes, no, or the key fact. Order the questions from most to least common.
- Release note
- a one-line summary of what changed and who it affects, then what's new, why it matters to the reader, and any action they need to take. Keep it short and skimmable; link the full how-to rather than repeating it.
Knowledge base article format
The best help centers feel predictable: every article is built the same way, so readers always know where to look. These are the parts the templates here put in place, in the order a reader meets them.
Write the title the way a customer would type it — "How to reset your password," not "Password management." The title is how they find it.
Two or three sentences: what this solves and who it's for. Let the reader confirm they're in the right place before they commit.
What the reader needs before they start — a plan, a permission, a setting. Naming it up front saves a failed attempt halfway down.
Numbered steps for a how-to, symptom-cause-fix for troubleshooting, a plain definition for a concept. The type decides the shape.
Two to four links to adjacent topics. They keep readers moving and stop one article from trying to cover everything.
The single takeaway, on its own at the end. It's what a skimmer reads, and what an AI agent often quotes.
Knowledge base article examples
The templates in the tool above are skeletons you fill in. These two sample knowledge base articles are the same structure written out in full — a how-to and a troubleshooting article — so you can see what “done” looks like before you write your own.
How-to
Example article
How to add a teammate to your shared inbox
Invite a colleague so they can read and reply to conversations in a shared inbox. You need to be an admin to do this.
Before you start
You need admin access, and a free seat on your plan. Billing shows how many seats are left.
Steps
- Open Settings and select Team.
- Click Invite teammate.
- Enter their work email address and choose a role — Agent can reply, Admin can also change settings.
- Pick which inboxes they should see. You can change this later.
- Click Send invite. They will get an email with a link that expires in seven days.
If it doesn't work
If the invite never arrives, it is almost always a spam filter. Ask them to check junk mail, then resend from Settings → Team → Pending.
Related
Changing a teammate's role · Removing a teammate · How seats are billed
Troubleshooting
Example article
Replies aren't reaching customers: how to fix it
You send a reply and it looks sent in your inbox, but the customer says they never received it. These are the causes, most common first.
1. Your domain isn't verified
Unverified sending domains get filtered before they reach the inbox. Open Settings → Domains and check for a green Verified badge. If it is missing, re-add the DNS records shown there and allow up to an hour.
2. The reply went to the wrong address
Check the To field on the sent message. If the customer wrote in from an alias, replies go to the alias unless you change it.
3. The customer's provider is filtering you
Ask them to check spam and add your address to their contacts. If a whole domain is affected, contact us and we will check the sending reputation.
If none of these work
Send us the conversation link and the time you replied. Message headers are kept for 30 days, and they show exactly where the message stopped.
Notice what both examples do: the title is phrased the way a customer would search for it, the intro confirms they are in the right place in one line, and the body stops the moment the problem is solved. Neither tries to cover a second topic — that would be a second article, linked from this one.
Vague vs. usable — the same step
Same instruction, two very different steps. The first sounds helpful and leaves the reader guessing. The second tells them exactly what to do and what they'll see.
The step
“Turning on notifications”
Too vague
“Head to your settings and make sure notifications are enabled so you don't miss anything important.”
A step worth following
Go to Settings → Notifications, switch "Email alerts" to On, and click Save. You'll see a green "Saved" badge and get a confirmation email within a minute.
How to write one that deflects tickets
An article only deflects a ticket if a customer can find it, understand it, and finish the task. These are the habits that get you there, whatever the article is about.
Use the words customers use, not your internal feature names. The closest match to the question is the one that gets found.
Each article answers a single question. If it's covering three tasks, split it into three that link to each other.
Put the fix or the key fact in the first line. A reader in trouble shouldn't have to read three paragraphs to reach it.
Mark where a screenshot goes. A picture of the right screen removes the doubt that sends someone to support anyway.
Link the related article or the way to reach a human. An article with no exit just generates the next question.
AI sounds confident even when it's wrong about your steps or settings. You're the editor on every article, not the rubber stamp.
From article to AI answer
A well-structured article isn't just for people. It's the source an AI agent reads to answer your customers. A clear title, one job per article, the answer up front, and a clean summary are exactly what makes an article easy for an agent to quote correctly — the same habits that help a person help a machine. Turn your drafts into help center articles customers can search, and let an AI agent answer the repeat questions from them for you.
A doc template vs a real help center
A template in Notion, Word, or a Google Doc is a fine place to draft an article. But a folder of docs can't be searched by your customers, can't answer inside the chat widget, and goes stale the moment a step changes.
| Capability | Doc template | Selvo Help Center |
|---|---|---|
| Writing the article | ||
| Gives you a proven article structure | ||
| Stays accurate as your product changes | Edit each doc by hand | Edit once, live everywhere |
| Built for help-center articles, not generic docs | A blank page with headings | Purpose-built articles |
| How customers find answers | ||
| Customers search across every article | ||
| Each article has its own shareable page | ||
| Answers customers right inside the chat widget | ||
| An AI agent answers from your articles 24/7 | ||
| Upkeep & cost | ||
| One place to update when something changes | ||
| Shows you which articles deflect tickets | ||
| Price | Free | Included with Selvo |
