As of 13 August 2026, AI can turn your help articles into chatbot answers.

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 the current help centre, policy documents and customer-service escalation guidance, then remove superseded articles and duplicate versions.
   2. Paste the remaining articles into the prompt, including article titles and headings so the chatbot can identify its sources.
   3. Add your business name, product context, preferred tone and the exact route customers should use when a human must take over.
   4. Run the prompt in a chatbot interface and save the questions, answers, sources, escalation instructions and unresolved issues it produces.
   5. Compare every drafted answer with its cited article, checking prices, times, conditions, eligibility rules, contact details and promises against the current source.
   6. Test the set with real customer questions, including vague questions, exceptions and questions not covered by the articles, then rewrite any answer that should escalate.
   7. Import the approved answers or source articles into a purpose-built chatbot tool, configure its human hand-off, and test the live customer journey before publishing it.

   Prompt

   Turn the help articles below into a set of chatbot answers for a UK business.
   
   Use only the supplied material. Do not invent policies, prices, delivery times, guarantees, legal rights, contact details or product features. If the articles do not answer a question, say that the chatbot should explain that it cannot confirm the answer and offer the approved escalation route.
   
   Write:
   1. A list of likely customer questions, including different ways each question might be phrased.
   2. One concise answer for each question, using plain British English and a helpful, neutral tone.
   3. The source article or section used for each answer.
   4. An escalation instruction wherever the answer depends on account-specific information, a complaint, a refund exception, a safety issue, personal data, or a policy not stated in the articles.
   5. A short list of contradictions, missing information, outdated-looking details and questions that need a human decision before publication.
   
   Keep each answer focused on one customer intent. Do not merge separate policies into one answer. Do not claim that the chatbot has completed an action. Preserve any stated conditions and limits. Return the result in a table with these columns: customer question, chatbot answer, source, escalation needed, unresolved issue.
   
   Business context:
   [BUSINESS NAME AND WHAT IT PROVIDES]
   
   Approved tone and escalation wording:
   [PASTE TONE GUIDANCE AND THE ROUTE TO A HUMAN]
   
   Help articles:
   [PASTE THE CURRENT HELP ARTICLES HERE]

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