How Do I Write Help Center Articles That Actually Help?
Write help center articles that reduce support tickets. Start with the answer, use the customer's words, include every step, and keep it updated.
TL;DR
Write help articles that work by following four rules: start with the answer (no intros), use the customer's exact words in the title, include every step (screenshots help), and update when the product changes. Articles that follow these rules get found, get read, and prevent support tickets.
Start with the answer, not the background
The first sentence of every help article should answer the question. Not "In this article, we'll explore..." Not "Before we begin, let's understand..." Just the answer.
Bad: "Managing your subscription is an important part of your account. In this article, we'll walk through the various options available to you."
Good: "To cancel your subscription, go to Settings > Billing > Cancel Plan. Your access continues until the end of your billing period."
Customers land on your article after searching for a specific thing. Respect their time — answer first, then provide details for those who need them.
Use the customer's words, not yours
Your article title should match how customers phrase the question. Look at your support inbox — how do customers actually ask this?
They don't search for "Subscription Lifecycle Management." They search for "how to cancel" or "where are my invoices."
Internal term → Customer term: - "Workspace provisioning" → "How to create a workspace" - "Authentication configuration" → "How to set up login" - "Data retention policy" → "What happens when I cancel" - "Deployment pipeline" → "How to publish my changes"
The title determines whether the article shows up in search. Match the customer's vocabulary.
Include every step
The most common failure mode for help articles: they skip steps that seem obvious to you but aren't obvious to the customer.
If your article says "Go to Settings," which settings? The gear icon in the sidebar? The account dropdown? The team settings page? Be specific: "Click the gear icon in the bottom-left corner of the sidebar, then click 'Billing.'"
Add screenshots for any step that involves navigating to a specific place. A screenshot eliminates ambiguity in a way that text can't.
The completeness test: Could someone who has never seen your product before follow these steps successfully? If not, you've skipped something.
Keep articles updated
An outdated article is worse than no article. It erodes trust. A customer who follows outdated instructions fails, then emails you — and now they're frustrated instead of neutral.
Update triggers: - UI changed → update screenshots immediately - Feature renamed → update title and body - New option added → add it to the relevant article - Feature removed → remove the article or redirect it
Set a monthly reminder to review your 10 highest-traffic articles. Check that screenshots match the current UI and that all steps still work.
Kairoo tracks which articles get negative feedback ratings — a signal that something might be outdated. Use this to prioritize updates.
See what your first 5 articles should be or learn about content gap detection. Start free.
Frequently asked questions
How long should a help article be?
As long as needed to fully answer the question, but no longer. Simple questions: 100-300 words. Multi-step guides: 300-800 words. Complex troubleshooting: up to 1,200 words. If it's longer, split it.
Should I use AI to write help articles?
AI is great for first drafts — it generates structure and covers obvious points. But always edit for accuracy, add screenshots, and verify that steps work. AI doesn't know your product's current UI.