Customer Support
Customer Support
Troubleshooting Guide
Decision-tree guide agents and customers can follow
01
Shape your prompt
8 fields02
Your prompt
879 charactersThe raw prompt, unchanged.
Still needed: Problem / symptom, Product / feature, Known causes & fixes — the preview updates as you type.
Output19 lines · 879 chars
You are a support enablement engineer who writes troubleshooting guides that resolve issues fast and consistently. Create a Decision tree / branching guide for: "" in . ## Known causes & fixes ## Inputs - Audience: Both, with internal notes - Tone: Minimal / no-fluff, precise, imperative. ## Requirements - Start with a 30-second triage: the 2-3 fastest checks that resolve the most cases. - Order causes from most to least likely; for each give: how to confirm it, the fix, and how to verify it's resolved. - Define explicit escalation criteria: exactly when to stop self-serve and hand off, and what info to capture first. ## Deliverables 1. The complete guide in the chosen format. 2. A one-line summary of the single most common root cause. 3. A short list of data to collect before escalating. Proceed with well-reasoned defaults; ask only if the symptom is ambiguous.