Free tool

Knowledge base article template

Describe one help-center topic, pick the article type, audience, and tone, and generate a properly structured article — title, intro, steps, related links, and a summary. Plus a library of ready-to-use article templates, one for every type. Free, no signup required.

Article type
Audience
Tone
Your prompt
Write a help-center (knowledge base) article on the topic below.

Write it as a how-to article: 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].
The reader is an everyday end user, not technical. Avoid jargon, spell out anything technical in plain words, and assume no prior setup knowledge.
Tone: plain and direct — short sentences, no filler, the wording a reader can follow on the first pass while something is broken.

Structure every article the same way:
1. A clear, specific H1 title written the way someone would search for this — match the task, not your feature name.
2. A short intro (two or three sentences): the problem this solves and who it's for.
3. Prerequisites, if any — what the reader needs before they start.
4. The body in the shape described above.
5. A short "Related articles" list of 2–4 adjacent topics, as [bracketed titles] for me to link.
6. A one-line summary at the end the reader could take away on its own.

Write only about what's in the topic below. Don't invent product names, settings, prices, or steps — where you need a specific detail I haven't given you, leave a [bracketed placeholder] for me to fill in. Keep it skimmable: short paragraphs, descriptive sub-headings, and one idea per step.

The topic this article explains:
[describe the help-center topic this article should explain here]
Generate in

Opens in your AI of choice, free and unlimited, no signup. Always read the article before you publish it, since AI can sound confident and still get a step or setting wrong.

Article templates

6 knowledge base article templates

A ready-made skeleton for each kind of help-center article. Copy one, fill in the [brackets], and paste it into your help center, or open it in ChatGPT to write it out for your product.

How to [do the task]

How-to
# How to [do the specific task]

[One or two sentences: what this article helps the reader do and when they'd need it.]

**Before you start**
- [Prerequisite — e.g. an account on the [plan] plan]
- [Prerequisite — e.g. admin access to [area]]

**Steps**
1. Go to [where] and [first action].
2. [Next action]. [screenshot: what the reader should see]
3. [Next action].
4. [Final action] to [confirm it worked].

**If it doesn't work**
[The one thing that most often goes wrong, and how to fix it.]

**Related articles**
- [Adjacent how-to]
- [The concept behind this]

*Summary: [the task] takes [N] steps — [the gist in one line].*

[Symptom]: how to fix it

Troubleshooting
# [Symptom, in the reader's words — e.g. "Emails aren't sending"]

[One or two sentences: what this article covers and who runs into it.]

**Quick checks first**
- [The fastest thing to check — e.g. is [setting] turned on?]
- [Second quick check]

**Cause 1 — [most common cause]**
1. [Step to confirm this is the cause.]
2. [Step to fix it.]

**Cause 2 — [next cause]**
1. [Step to confirm.]
2. [Step to fix.]

**Still not working?**
[What to gather and how to reach support — e.g. "Send us [details] at [link]".]

**Related articles**
- [The how-to for the working flow]
- [A related error]

*Summary: [symptom] is usually [most common cause] — [one-line fix].*

Getting started with [product / feature]

Getting started
# Getting started with [product or feature]

[One or two sentences: what the reader will be able to do by the end.]

**What you'll need**
- [Requirement]
- [Requirement]

**Set up in [N] steps**
1. [Create / connect / turn on the first thing].
2. [The next setup step].
3. [The step that produces a first visible result].

**You're set up — what next**
[The first useful thing to do now that setup is done, with a link.]

**Related articles**
- [The next feature to explore]
- [Common first-week questions]

*Summary: you can be up and running in about [time] — [the gist].*

What is [concept]?

Concept explainer
# What is [concept]?

[Concept] is [a plain one-sentence definition anyone could understand].

**Why it matters**
[Two or three sentences: what it lets the reader do, or the problem it solves.]

**When it applies**
[The situations where this concept comes up for the reader.]

**How it works**
[Explain in 2–3 short sections or a simple example. Keep it concrete — show one real case rather than every possibility.]

**Related articles**
- [The how-to that uses this concept]
- [A related concept]

*Summary: [concept] is [the one-line takeaway].*

[Topic]: frequently asked questions

FAQ-style
# [Topic]: frequently asked questions

[One sentence introducing the topic these questions cover.]

**[The most common question, in the reader's words]?**
[A direct answer that leads with yes, no, or the key fact, then one line of context.]

**[Next question]?**
[Direct answer.]

**[Next question]?**
[Direct answer.]

**[Next question]?**
[Direct answer.]

**Related articles**
- [The full how-to for this topic]
- [A related FAQ]

*Summary: [the single most important thing to know about this topic].*

[Feature] is now available

Release note
# [What changed — e.g. "You can now [do the new thing]"]

[One line: what's new and who it affects.]

**What's new**
[Two or three sentences on the change and what it lets the reader do.]

**Why it matters**
[The problem this solves or the time it saves.]

**What you need to do**
[Any action required — or "Nothing, it's on by default." Link the full how-to.]

**Related articles**
- [How to use [feature]]
- [What's changed previously]

*Summary: [feature] is live — [the one-line benefit].*
Guide

How to write a knowledge base article

A generated draft gets you most of the way. The rest is knowing the structure every good article shares, how to write one that actually deflects tickets, and how a clean article becomes the answer your AI agent gives.

Anatomy of a good help-center article

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.

A title that matches the search

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.

A short intro

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.

Prerequisites

What the reader needs before they start — a plan, a permission, a setting. Naming it up front saves a failed attempt halfway down.

The body, in the right shape

Numbered steps for a how-to, symptom-cause-fix for troubleshooting, a plain definition for a concept. The type decides the shape.

Related articles

Two to four links to adjacent topics. They keep readers moving and stop one article from trying to cover everything.

A one-line summary

The single takeaway, on its own at the end. It's what a skimmer reads, and what an AI agent often quotes.

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.

Title it like the search

Use the words customers use, not your internal feature names. The closest match to the question is the one that gets found.

One article, one job

Each article answers a single question. If it's covering three tasks, split it into three that link to each other.

Lead with the answer

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.

Show, don't just tell

Mark where a screenshot goes. A picture of the right screen removes the doubt that sends someone to support anyway.

End with a next step

Link the related article or the way to reach a human. An article with no exit just generates the next question.

Read it before you publish

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.

CapabilityDoc templateSelvo 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
Selvo Help Center

Give your articles a home that scales

A template drafts a static article, and you maintain it by hand. Selvo's help center turns each one into a searchable article customers find on their own, and an AI agent trained on those articles answers the repeat questions inside your chat widget 24/7, so your team handles the ones that need a human.

See how Selvo Help Center works

Questions about knowledge base articles

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. Good articles have a clear title that matches what people search, a short intro, steps or sections in a predictable structure, and links to related articles. Together they form a knowledge base your customers (and an AI agent) can search instead of emailing support.
How do I structure a knowledge base article?
Use the same skeleton every time so readers always know where to look: a clear, specific H1 title written the way someone would search for it; a two-or-three-sentence intro naming the problem and who it's for; prerequisites if there are any; the body in the shape the article needs (numbered steps for a how-to, symptom-cause-fix for troubleshooting, a plain definition for a concept); a short list of related articles; and a one-line summary. The builder and templates here put that structure in place for you.
How long should a knowledge base article be?
As long as it takes to answer the one thing it's about, and no longer. Most good articles are short. A few hundred words and a handful of steps. If an article is trying to cover several tasks, that's usually a sign it should be split into separate articles that link to each other. One article, one job: that keeps each page easy to scan and easy for search (and an AI agent) to match to a specific question.
How many articles do I need to launch a help center?
Fewer than you think. Start with the questions your team already answers most. Usually 10 to 20 articles cover the bulk of incoming tickets. Look at your inbox or canned replies for the repeats, write those first, and add articles as new questions come up. A focused help center that answers the top questions well beats a sprawling one full of pages nobody reads.
How does a help center reduce support tickets?
Every clear article is a question your team doesn't have to answer by hand. Customers who can find the answer themselves don't open a ticket, and the articles double as the source an AI agent answers from inside your chat widget — so the repeat questions get handled 24/7 without reaching a person. The better structured and more searchable your articles are, the more tickets they deflect. Selvo's help center and AI agent do this inside the inbox your team already uses.
Is this knowledge base template tool free?
Yes, completely free. No signup, no email, no paywall. Describe a topic and open a structured article prompt pre-filled in ChatGPT, Claude, Perplexity, or Google AI, copy it into any tool, or grab one of the ready-to-use article skeletons. Usage is unlimited.

Something we didn't cover? Email a founder — answer in your inbox the same day.

We built the support tool we wished existed.

Help center, chat widget, AI agent, and shared inbox. The whole support stack on one bill. Free for fourteen days, no credit card.