How to write help center articles
To write help center articles customers can use, start from the questions in your real tickets, answer one question per article, title it in the customer’s own words, and give numbered steps with a screenshot where the screen matters. Then review each article on a schedule and retire the ones that are out of date, so the help center stays something people trust.
- Pick topics from the tickets and chats you already get, not from a list of features.
- Write one question per article and title it the way a customer would type it.
- Put the answer first, then numbered steps and a screenshot where the screen matters.
- Test every article by following it yourself, or by asking someone new to try it.
- Review articles on a schedule and retire the ones that are wrong or unused.
Step by step
Pick topics from real tickets
Open your last month of tickets, chats and emails and tally the questions that come up more than once. Those are your first articles. Write the question as the customer wrote it, not as your team would label it. Start with the three or four questions that eat the most time, such as resetting a password, changing a delivery address or finding an invoice. Skip topics nobody has ever asked about. A short help center of useful articles beats a long one that covers every feature.
Write one question per article
An article should answer one question and stop. If an article covers refunds, exchanges and warranty claims, split it into three, and link them to each other. Short, single-purpose articles are easier to find, easier to keep correct and easier to link from a reply. Open with the answer in one or two sentences, so a reader who only needs the yes or no can leave after reading the first line.
Title it in the customer’s words
People search with their problem, not your product name for the feature. Use titles such as “How do I change my delivery address?” or “Why was I charged twice?” Check how customers phrase things in the ticket subjects and the search box on your site, and borrow that wording. Avoid internal terms, plan codes and jargon in the title. If two phrasings are common, put the second one in the first paragraph so search can match both.
Add numbered steps and screenshots
When the answer is a task, write numbered steps with one action each, starting with a verb: “Open Settings”, “Select Billing”, “Choose Download”. Name buttons exactly as they appear on screen. Add a screenshot only where the reader could get lost, and mark the spot to click. Say what the reader should see when it works. Put anything that can go wrong, such as an expired link, in a short line under the step where it happens.
Test the article before you publish
Follow your own steps on a fresh account or a different device, with nothing assumed. Better, hand the article to a new teammate and watch where they hesitate. Every pause points to a missing step or an unclear word. Check that the title matches the answer, that links work and that nothing shows another customer’s details in a screenshot. Then publish and add the article to the replies your team already sends.
Review and retire old articles
Give every article an owner and a review date. When a product, price or policy changes, update the matching articles the same week. Once a quarter, look at the articles that are never opened, the ones customers still write in about after reading, and any that contradict each other. Fix, merge or delete them. A retired article should redirect to the best current one, not leave a dead end.
What makes an article easy to find?
A findable article uses the words customers use, answers one question and links to its neighbours. Put the main phrase in the title and first sentence, and keep headings as questions. Add related articles at the bottom for readers who landed in the wrong place.
When is an article the wrong tool?
- Account-specific problems, such as a failed payment on one order, need a personal reply.
- Anything involving a complaint or an upset customer needs a person, not a link.
- One-off questions that will never be asked again are not worth an article.
- Advice on legal, tax or medical matters should come from a qualified advisor, not from a help article.
The help center is the source of truth your replies draw on. If you want the replies and the queue handled around it, our guide on clearing a support queue overnight covers that side, and this guide covers the articles themselves.
Help center article template
- Title: The question in the customer’s words, for example “How do I [do the thing]?”
- Short answer: One or two sentences that answer the question directly.
- Before you start: What the reader needs, such as a login, a role or a recent order.
- Steps: 1. [Verb and exact button name]. 2. [Verb and exact button name]. 3. [What they should see when it works].
- If it doesn’t work: The two most common problems and the fix for each.
- Related articles: Two or three links to the next questions people ask.
- Still stuck? How to reach a person, and what to include in the message.
- Owner and review date: Who keeps it correct, and when it is next checked.
Common mistakes to avoid
- Writing about features instead of the questions customers actually ask.
- Packing several questions into one long article that is hard to search and hard to update.
- Naming buttons and menus from memory, so the steps no longer match the screen.
- Using screenshots that show another customer’s details or that go stale after the next product update.
- Leaving outdated articles live, so customers follow steps that no longer work.
How the FrugalPod support pod works with your help center
FrugalPod’s support pod works from the help center you write. Triage tags and routes every ticket as it lands, which makes repeated questions easy to count. The Responder drafts answers from your help center in your tone, and when it has nothing to draw on, that gap tells you which article to write next. Nothing is sent until you approve it, every action is logged, and you can later choose to let routine replies go out on their own. See pricing for what it costs.
TriageTags, prioritises and routes every ticket as it lands, so you can see which questions repeat and deserve an article.
ResponderDrafts answers from your help center, which shows quickly where an article is missing or unclear.
Success watcherSpots usage drops and renewal risks early, which can point to a step worth explaining better.
Related
Common questions
Something missing? Write to admin@frugalpod.com and a person will reply.
How long should a help center article be?
As long as it takes to answer one question, and no longer. Many good articles are a short answer, five or six steps and a couple of related links. If an article needs several screens of scrolling, it probably covers more than one question and should be split into smaller articles.
How many articles do I need to start?
Start with the handful of questions that appear most in your tickets, perhaps ten articles, and add more as new questions repeat. A small set that is accurate and easy to find helps customers more than a large library that nobody has time to keep up to date.
Should every article have screenshots?
No. Use a screenshot only where the reader could get lost, such as finding a setting in a crowded screen. Simple questions are better answered in a sentence. Screenshots go stale when the product changes, so every one you add is something you must remember to update.
How often should I review help center articles?
Update an article as soon as the thing it describes changes, and run a wider check once a quarter. Look for articles nobody opens, ones customers still contact you about and ones that disagree with each other. Fix, merge or retire them, redirecting old links to a current article.