Blog / Digital products /

When a product needs a self-serve help centre

Picture a support inbox where the same setup question lands every week. Someone types out the same answer, again. Then the product team asks the obvious thing: would a help centre make this stop?

Maybe. But only if people can find answers they trust, and only if somebody keeps those answers current.

A product needs a self-serve help centre when users ask the same questions again and again, those questions can be answered reliably without a conversation, and you can maintain the content. It shouldn’t become a dumping ground for internal notes, or a replacement for support when a person needs to look at the details.

Understand the demand

Review support requests and onboarding feedback. Group questions by task and stage: getting started, configuration, troubleshooting, billing, account access or advanced use. Look for repeated issues and points where people become stuck.

Ask support agents what they explain repeatedly and which cases require individual diagnosis. Some questions can be answered by a short article; others depend on account state, security checks or a customer’s specific setup. Do not try to automate a situation where a person needs to review the details.

Check the product itself too. If users keep asking how to do a basic task, the interface or onboarding probably needs work. I’d rather fix a confusing screen than write an article apologising for it, which is also why I lean towards self-serve products over support-heavy ones.

Choose a manageable scope

Start small. A getting-started guide, account recovery steps and clear fixes for the common errors will beat a giant encyclopaedia. Prioritise by customer impact, how often the question comes up and whether your team can verify the answer. If I had to pick one article to write first, it would be the setup guide.

Define what the help centre will not cover. Complex account decisions, security-sensitive requests or unusual technical failures may need a support route. Explain how to contact that team and what information is safe and useful to provide.

Make the content model simple. Each article needs a clear title, task, steps, prerequisites, expected result, last-reviewed date and owner. Use screenshots sparingly and update them when the interface changes.

Design for finding answers

Organise articles around what customers are trying to do, not around your org chart. Use labels people understand, link related steps together and make search cope with the words customers actually use. If the product has a technical term, include the customer’s phrase as well.

Keep the category tree shallow. People should reach common tasks fast, and search should appear once the library grows. Then test the navigation with someone who has never seen your internal structure.

Write procedural steps in order and state what success looks like. Include safe recovery actions and warn before steps that can delete data or change access. Avoid telling someone to disable protections or share credentials as a quick fix.

Connect help to the product

Place links near the point of need: settings, errors, onboarding and empty states. Keep links relevant so users do not have to search the entire library from a generic help button. If the product has several versions, identify which instructions apply.

Consider whether help content should be public, account-gated or available in the product. Public documentation can be useful for evaluation and search discovery, but private account details should never be exposed. Verify that access controls match the intended audience.

Ensure the help centre works with keyboard and assistive technology. Search fields need labels, headings need hierarchy and screenshots need appropriate alternatives. Do not rely on video alone for essential instructions.

Measure outcomes with care

Track whether people find articles and whether they finish the task, but treat analytics as partial evidence. A page view doesn’t prove an answer helped. Support volume can move for reasons that have nothing to do with the help centre, like a product change or a wave of new users.

Invite feedback with a simple prompt and a way to say what’s missing. Read the negative feedback and the searches that return nothing. Don’t force anyone to rate an article before they can carry on.

Count maintenance cost as well. An outdated article adds to the support burden and wears down trust, so give it an owner and a review trigger for when the interface, plan or policy changes.

Decide where self-service should stop

A help centre shouldn’t make customers cross a maze before they reach support. Put contact options next to content about account loss, billing disputes and security concerns, and anywhere the user can’t proceed. The article can collect useful details, but it must never ask anyone to post passwords, payment data or private account information.

Say which information support needs and why. A product version, error code or operating system helps. A full screen recording may expose personal data. Explain how to redact sensitive details, and give a secure route for sharing them if needed.

Also check that people use the content as intended. Searches that keep landing on an unrelated article point to an information architecture problem. A high exit rate alone doesn’t prove failure, because the person may have found the answer and left.

Plan for content ownership

A help centre needs an owner for accuracy, not just someone who can edit a page. That person reviews product changes, checks broken links and retires instructions that no longer apply. If several teams are involved, decide who approves technical, billing and policy content.

Set review triggers instead of relying on an annual date. A redesign, pricing change, security update or common incident may need an immediate revision. Show the last-reviewed date to maintainers, but don’t present it to customers as a guarantee that the answer is still current.

Archive old articles carefully. Redirect a page only when there’s a clear replacement, and keep material that existing users may still need.

So here’s my question for you: which kind of product change should automatically create a documentation review task?