Build a Yes/No Troubleshooting Decision Tree for a Recurring Product Issue
You get a step-by-step yes/no troubleshooting tree ordered from fastest, most likely checks to slowest, with ready-to-send customer messages and a clear escalation point.
Prompt
Act as a senior support operations lead who writes troubleshooting guides for frontline agents.
Your job: build a yes/no troubleshooting decision tree for one recurring product issue my team handles.
Before writing anything, ask me these questions in one message, then wait for my answers:
1. What is the issue, in the customer's words, and which product or plan does it affect?
2. What are the known causes, and roughly how often is each one the culprit?
3. What can frontline agents check or fix themselves, and what needs another team?
4. What must an escalation ticket include?
Rules:
- Order checks by speed and likelihood: quick checks for common causes first, slow or rare checks last.
- Every step is one question answerable only Yes or No, and each answer points to a fix ID or the next step number.
- Give each step a time estimate in minutes.
- Each fix includes 1-2 sentences an agent can send the customer word for word.
- Mark the single escalation point with the word ESCALATE. No step may require access agents don't have.
Output format:
1. Issue summary (2 lines)
2. Decision tree: numbered steps, each with Check, Time, If Yes, If No
3. Escalation block: trigger, receiving team, required info
4. Fix table with columns: Fix ID, Cause, Agent action, Customer message
End with one line listing your assumptions and any likely causes I didn't mention.Example output
Tips and common edits
Why this works
- Ordering checks by speed and likelihood means most tickets resolve in the first few steps instead of after a long script.
- Strict yes/no branches with step numbers make the tree easy to follow and easy to turn into a macro or flowchart.
- A single marked ESCALATE point with required info stops premature escalations and incomplete Tier 2 tickets.
Use when one issue keeps flooding your queue and agents handle it inconsistently. Have the known causes and your escalation rules ready. Works in ChatGPT, Claude or Gemini.
Common edits
- Ask for the tree as Mermaid flowchart code to paste into your knowledge base.
- Add a column for the help center article link each fix should reference.
Prompt details
- By
- Prompts-GPT editors
- Published
Did this prompt work?
Keep exploring
More like this
Turn Pasted Customer Questions into a Clear FAQ Page with Short Answers
You get a ready-to-publish FAQ page with duplicate questions merged, answers under 60 words drawn only from your facts, and a list of gaps.
Audit a Help Center Article for Gaps, Jargon and Outdated Steps
Paste a help center article and get a pass/fail checklist scorecard plus a line-by-line fix list ranked by customer impact, without a full rewrite.
Turn Feature Notes into a Step-by-Step Help Center How-To Guide
Paste rough notes about a product feature and get a customer-ready how-to guide with one action per step, bold UI labels, expected results and a troubleshooting section.
Write Chatbot Intent Answers with Trigger Phrases and Human Handoff Rules
Get a set of chatbot intents for your top support questions, each with customer-style trigger phrases, a short bot answer, and an exact rule for handing off to a human.
Write Help Article Titles and Meta Descriptions in Your Customers' Words
Get help article titles that start with the customer's task verb and meta descriptions within search length limits, each with a character count and the customer phrase it matches.
Turn a Resolved Support Ticket Thread into a Help Center Article
Paste a solved ticket thread and get a ready-to-publish help article with customer details removed, verb-first fix steps, and symptoms written the way customers search.