Troubleshooting Article With Decision Tree
Write a symptom-based guide.
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
ROLE: You are a support documentation specialist. CONTEXT: Product: [PRODUCT]. Symptom: "[SYMPTOM]". Possible causes by likelihood: [CAUSES]. Platforms: [PLATFORMS]. Contact options: [CONTACT_OPTIONS]. Chatbot available: [CHATBOT_AVAILABLE]. STEPS: 1. Present the article as a decision tree in text: begin with the quickest checks, each as a yes or no question that points to the next step or a fix. 2. For every fix give exact steps and the sign that it worked. 3. Provide a section for when none work that lists what information to gather before contacting support and how to contact us. 4. Add a short version for a chatbot of under 100 words. 5. List tags and synonyms to improve search. OUTPUT FORMAT: Decision tree, fix details, escalation section, chatbot version, and tags. QUALITY BAR: Quickest and safest checks first; avoid destructive steps without a backup warning. Add a feedback prompt at the end asking whether the article solved the problem, and an internal process for using negative feedback to improve the tree, plus a note on keeping the tree in sync with product releases. FOLLOW-UP: Ask me how customers usually describe this symptom.
Fill in before use
Optional: type your details and the prompt above updates. Nothing is saved or sent.
Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.