As of 13 August 2026, AI can create a troubleshooting guide for your product.

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, release notes, known-issues list and support ticket answers, then remove anything obsolete or marked as unverified.
   2. Gather the exact customer symptoms, error messages, affected product versions, confirmed causes, tested fixes, warnings and support escalation rules.
   3. Paste that material into the prompt, replacing each bracketed slot with the product details, audience, support route and current escalation instructions.
   4. Ask the chatbot to produce the guide and its verification table using only the supplied sources.
   5. Compare every drafted cause, fix, warning and expected result with the current documentation and mark any unsupported statement for removal or confirmation.
   6. Test each troubleshooting path on the relevant product version, including the failure case and the escalation route, then correct the guide from the test results.
   7. Send the checked draft to a product or support colleague for a final technical review before publishing it in your help centre.

   Prompt

   Create a customer-facing troubleshooting guide for [PRODUCT NAME]. Use only the information in the source material below and do not invent causes, settings, error messages, safety information or fixes. If the sources do not support an answer, write "Contact support" and state what information the customer should provide.
   
   Product and version: [PRODUCT AND VERSION]
   Audience: [CUSTOMER TYPE]
   Tone: plain, calm and concise British English
   Support contact and hours: [SUPPORT DETAILS]
   Escalation rules: [WHEN TO CONTACT SUPPORT OR STOP]
   Source material:
   [PASTE CURRENT PRODUCT DOCUMENTATION, KNOWN ISSUES, SUPPORT ANSWERS, ERROR MESSAGES AND VERIFIED FIXES]
   
   Structure the guide as follows:
   1. A short explanation of what the guide covers.
   2. A symptom or problem selector using the exact customer-facing wording from the sources where available.
   3. For each symptom, list the likely cause only when supported by the sources, followed by numbered steps in the correct order.
   4. Include warnings before any step that could cause data loss, downtime, account changes or physical risk.
   5. Add a clear result after each fix, including what the customer should see if it worked.
   6. Add an escalation section stating when to stop and contact support.
   7. Add a short list of the information customers should include in a support request.
   
   Mark any statement that needs confirmation as [CHECK]. Finish with a verification table listing every technical claim, its source, and the test needed before publication.

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