As of 13 August 2026, AI can only partly write a help centre article for your business.

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 30 minutes until you can act on the result.

   How to actually do it

   1. Open the current product documentation, customer terms, price list, support contact details and a sample of recent support answers for the topic.
   2. Remove obsolete, confidential or customer-specific information, then paste the remaining approved material into the prompt under the source material heading.
   3. Replace the bracketed task, audience and business-context sections with the exact customer problem the article must solve.
   4. Run the prompt and save the article draft and its fact-check table in your help-centre working document.
   5. Compare every instruction, feature, price, deadline, eligibility condition and contact detail against the current product and business sources, and correct or delete anything unsupported.
   6. Ask a support or product colleague to test the steps using a realistic customer question and record any missing exception or confusing instruction.
   7. Publish the approved article in your help-centre system, then link it from the relevant support replies and check that the escalation route still works.

   Prompt

   Write a help centre article for a UK business using only the source material below. The article is for customers who need to [complete a task or solve a problem].
   
   Business and product context:
   [PASTE PRODUCT, SERVICE AND AUDIENCE DETAILS]
   
   Approved source material:
   [PASTE CURRENT INTERNAL DOCUMENTATION, TERMS, PRICE LISTS, PRODUCT INSTRUCTIONS OR SUPPORT ANSWERS]
   
   Article requirements:
   - Use plain British English and a calm, practical tone.
   - Start with a short summary explaining who the article is for and what it helps them do.
   - Use a clear title, descriptive headings and numbered steps where the customer must act in sequence.
   - Include prerequisites, limits, exceptions, likely error messages and what to do if the steps do not work, but include them only when supported by the source material.
   - Do not invent features, prices, deadlines, guarantees, legal rights or contact details.
   - Do not make assumptions about the reader's account, device or circumstances.
   - If the source material is incomplete or contradictory, stop and list the exact questions a member of our team must answer before publication.
   - End with a short escalation section stating when the customer should contact support and what information they should provide.
   - After the article, provide a fact-check table with columns for claim, supporting source and unresolved question.
   
   Return the draft article first, followed by the fact-check table. Source material follows:
   [PASTE MATERIAL HERE]

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