Write the answer once. Make it easy to use again.

Imagine answering “How do I change the delivery address?” four times in one afternoon. Each reply is slightly different. One mentions the dispatch deadline. The others forget it. Saving the answer could help, but saving an incomplete answer would spread the mistake.

A customer knowledge base is a collection of checked answers people can find and use themselves. Start with one repeated question that has a stable answer. Write the conditions, steps and fallback before creating a large library.

Choose a question with a clear finish

Read recent requests and group the same underlying problem together. “Where is my invoice?” may be one question even when people use different words. Choose a task the reader can finish, such as finding a document or requesting a change.

Do not start with a company history page because it is easy to write. A useful first article removes a piece of repeated work. Keep questions that need an individual decision on a human support route instead of pretending a generic answer covers every case.

Put the condition before the instruction

Say who the answer applies to

Explain any deadline, account requirement or limit at the start. An address-change article should not let someone read five steps before discovering the parcel has already left. Check the rule with the person responsible for the operation.

Show the result of each action

Name the control or contact route exactly as it appears. Explain what the reader should see after using it. Help Scout's article guidance recommends beginner-friendly steps and avoiding unstated assumptions; those are useful editing checks for a first help page.

This is a planning template. Replace it with your real policy and working controls before giving it to customers. A request being received does not mean the change has been accepted.

Use the customer's words in the title

Search for the words someone might type while stuck. “Change my address” is more useful than “Post-purchase fulfilment amendments”. Include a short answer near the beginning and keep important instructions in readable page text.

Google's AI-features guidance says the usual search foundations still apply. A clear article is worth writing for readers; special wording or a FAQ block does not guarantee a place in search or an AI answer.

Test the page without explaining it aloud

Ask a colleague who did not write it to follow the steps using a safe test record. Watch where they hesitate. Do not jump in to rescue a missing instruction, because that gap is exactly what a customer would meet.

Check the page on a phone, including links, screenshots and any scrolling table. If you add an image, use one that explains a step, remove private information and give it useful alternative text. A decorative picture cannot repair an unclear instruction.

Give the answer an owner after publication

A help page can become wrong when a policy or screen changes. Assign a review owner and connect updates to the relevant operating change. Archive or redirect obsolete guidance so two conflicting answers do not remain easy to find.

Use the response-template guide to share the article with a short answer in the message itself. Review repeat questions through the support-metrics routine, and keep a clear escalation route for cases the article cannot resolve. Self-service should be a helpful option, not a locked door.