Self-service that deflects for the right reason
Write from contact reasons, not from the product
Export the last few thousand conversations and group them by what the customer wanted. That list, ordered by volume, is your table of contents. It will look nothing like your feature list, and that is the point.
Start with the ten reasons that generate the most contacts. Ten genuinely good articles deflect more than a hundred thin ones, and they are maintainable by a real team.
Answer in the first two lines
Someone reading a help article is mid-problem and slightly annoyed. Put the answer at the top, then the caveats, then the background. Anything that reads like an introduction is a reason to leave and open a chat instead.
Write the way an agent would speak. If a macro already answers this question well, the article is largely written — the two should not disagree, and keeping them in one voice stops them from drifting.
- Lead with the answer, then conditions, then context.
- One question per article; split anything with two answers.
- Say what the customer should do next, explicitly.
- Include the failure case — what to do when the steps do not work.
Put the article where the question is asked
A help centre that only exists at a /help URL is a library nobody visits. The article about delivery windows belongs in the delivery confirmation email and beside the checkout, not three clicks into a knowledge base.
Surfacing suggestions inside the contact form is the highest-value placement, because it reaches people at the moment they have decided to write to you. Measure that placement separately — it behaves nothing like organic help-centre traffic.
Keep it current or take it down
An out-of-date article is worse than a missing one: it produces confident wrong actions and a second, angrier contact. Give every article an owner and a review date, and treat a policy change as incomplete until the affected articles are updated.
Review the search terms that returned nothing. They are the cheapest content brief you will ever get — customers telling you, in their own words, what they expected to find.
Measure deflection honestly
Page views are not deflection. The number worth tracking is whether contacts about a topic fall after its article is published and promoted, with volume for that contact reason as the baseline.
Watch for the opposite effect too. If an article gets heavy traffic and contacts about it stay flat, the article is being read and failing — usually because it explains a process rather than solving the problem behind it.