The only test that matters
A help article succeeds when a frustrated person, nine words into skimming it, finds their answer and leaves. It fails when it is complete, accurate, well-organized — and unread. Write for the skimmer, not the archivist.
Title with the customer's words
Customers search "refund" — not "billing adjustment policy." Pull titles from real transcripts and tickets: the exact phrasing people used when they asked. If your product renames a concept ("Workspaces") but customers say "accounts," the article title needs their word, with yours in the body.
Answer in the first sentence
Context, caveats, and background go AFTER the answer, not before it. Compare: "To reset your password, click Forgot Password on the sign-in page" versus three paragraphs on account security philosophy. The skimmer needs the verb and the button name immediately; the one reader in ten who needs the caveats will keep reading.
One task per article
"Managing your account" is a junk drawer; "Change your billing email" is an article. Small articles rank better in search, match one question each in your widget's suggestions, and — critically — make better AI training material: an assistant trained on single-task articles gives single-task answers instead of summaries of junk drawers.
Structure for skimming
- Numbered steps for anything procedural — never prose paragraphs describing clicks.
- Bold the UI names ("click Deployment") so eyes can jump from step to step.
- State the precondition first when there is one: "You need admin access for this."
- End with the next question. If readers of this article usually ask a follow-up, link it at the bottom.
Screenshots that age well
Screenshots go stale the day the UI changes, and stale screenshots are worse than none — they tell the reader the whole article might be wrong. Use them only where words genuinely fail, crop tightly to the control being discussed, and skip decorating every step with a full-window capture you will never maintain.
The monthly transcript audit
Once a month, read the chats and tickets about topics you have already documented. Each one is a verdict: the article was unfindable (fix the title), unclear (fix the first sentence), or incomplete (fix the body). This loop — real questions correcting written answers — is what separates a help center that deflects from a help center that exists. It is also exactly what improves an AI assistant trained on those articles: the bot is a mirror held up to your documentation.
Where this lives in MyLiveChat
The built-in knowledge base serves these articles three ways at once: as your public help center, as suggestions inside the chat widget, and as the AI assistant's approved training source. Write the answer once; it deflects in all three places.