As of 13 August 2026, AI can create a help centre from your business documents.

What to actually do

1. Hand it to a person

   The route this page recommends

   A person who owns the outcome does this end to end, worth it when the failure is dear.

2. Use a tool built for this

   Second choice

3. Do it yourself

   The distant third

   A chat interface, chat-fluent skill, and roughly 1 hour until you can act on the result.

   How to actually do it

   1. Open a working document or help-centre workspace and create a separate section for source documents, decisions, drafts and approval notes.
   2. Gather the current product guides, policies, process notes, pricing information, known limitations, support contact routes and any existing customer FAQs, keeping each file name and heading.
   3. Remove duplicate or superseded files, label the documents that are current, and add the business description, customer audience and preferred tone to the prompt.
   4. Paste the prompt and source material into an AI tool, then ask it to produce the information architecture, draft articles, FAQs, source map and unresolved-issues list in that order.
   5. Compare every drafted instruction, price, condition, link and contact route against the named source section, and mark unsupported or contradictory text for a colleague.
   6. Ask a product or support colleague to decide every item in the unresolved-issues list and to test the articles by following the steps as a customer would.
   7. Publish only the approved articles in the help-centre platform, assign an owner and review date to each article, and remove drafts that have no supporting source.

   Prompt

   Create a customer-facing help centre from the business documents below. First identify the products, tasks, policies, terms, prices, eligibility rules, limits, support routes and unresolved contradictions in the documents. Then propose a clear information architecture and draft the articles and FAQs in plain UK English.
   
   Use only information supported by the documents. Do not invent steps, features, guarantees, prices, deadlines, legal claims or contact details. If the documents do not answer a question, write "Not covered in the supplied documents" and list the information a colleague must provide. Preserve important conditions and exceptions. Keep each article focused on one customer task, use descriptive headings and numbered steps where appropriate, and include a short "Last checked" field without inventing a date. Add source references to the document name and section for every material claim.
   
   Return:
   1. A list of contradictions, missing information and content that needs a human decision.
   2. The proposed categories and article titles.
   3. The complete draft articles and FAQs.
   4. A source map showing which document and section supports each article.
   5. A publication checklist covering links, contact routes, prices, access permissions, accessibility and content ownership.
   
   Business context: [brief description of the business and customers]
   Preferred tone: [plain, formal, friendly or other]
   Existing help-centre structure or URL: [paste if available]
   Business documents:
   [Paste the documents here, keeping each document name and heading]

   Open it prefilled in ChatGPT or Claude, or copy it into Gemini, which takes no prefill link.