A little care goes a long way
Write the answer you wish you could send every time
A practical starting point for a useful help center: one real question, one clear answer, and a next step.
A help center does not have to be large to be useful. Start with a question your team has answered more than once this week.
Use the customer’s words in the title
“Where can I find my invoice?” is easier to recognize than “Billing document retrieval.” A clear title helps someone decide whether they are in the right place before reading the whole article.
Put the answer before the background
Give the shortest complete answer first. Then add steps, examples, or exceptions. If the reader has to scroll past your product philosophy to find a button name, move the button name up.
Show the next step
A useful article lets the reader do something:
- Find the relevant page or setting.
- Make a change or understand a decision.
- Know how to ask for help if it does not work.
Link to another article only when it helps finish that task. A small set of connected answers is more useful than a long collection with no clear path.
Review as a visitor
Keep unfinished articles in draft. Before publishing, check that any screenshots and instructions match your current product. After publishing, open the public page and try the instructions yourself.
In FlexHello, drafts stay in your workspace and published articles appear in the public help center. Start with your first collection.