Companies build a help centre by documenting the product feature by feature, publishing it, and observing that ticket volume does not fall. The reason is that the documentation is organised the way the product is built, and users arrive with a problem described in their own words. A section titled Account Settings does not answer why can't I log in, and a user who fails to find an answer in ninety seconds contacts support and never returns to the help centre.
So write from the queue. Export the last few hundred tickets, group them by what the customer was actually trying to do, and count. You will find that a modest number of distinct problems account for most of the volume — commonly a dozen or two. Those are your first articles, written with the customer's phrasing in the title, and getting them right removes more tickets than a hundred pages of feature documentation.
Make each article answer one question and lead with the answer. Users are not reading for interest; they are stuck. The first sentence should be the resolution, followed by the steps, followed by what to do if that did not work. Long preambles explaining the concept before the fix are the most common reason people abandon an article that contained what they needed.
Put the help centre where the problem occurs rather than behind a link in the footer. Contextual help on the screen where people get stuck — a short explanation next to the confusing field, a link to the specific article from the specific error message — deflects far more tickets than a searchable site does, because it requires no search. The error messages themselves are worth auditing for this: an error that says what to do next is a support ticket prevented.
Then measure it, which almost nobody does. Which articles are viewed, which are viewed and then followed by a support ticket anyway, and what people search for and find nothing. That last list is the most valuable thing the help centre produces: a prioritised set of gaps written by your users. A help centre with no analytics is a publishing exercise rather than a support channel.
Finally, give support the ability to fix it. The person answering the ticket knows the answer was missing and knows how they explained it, and if adding or correcting an article requires a request to marketing, it will not happen. Support writing and editing directly, with light review, produces a help centre that improves weekly. It also produces one written in the language customers use, which is the property that makes it findable.
