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

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

At a glanceDoorbell offline: yes/no checks in orderSix checks from fastest to slowest before escalating to Tier 2
  1. Light ring lit?0.5 minNo: fix power (F1)
  2. Wi-Fi changed in last 14 days?0.5 minYes: reconnect Wi-Fi (F2)
  3. Firmware 4.2 or later?1 minNo: push update (F3)
  4. 2.4 GHz network available?2 minNo: explain band requirement (F4)
  5. Back online after restart?4 minYes: temporary fault, close ticket (F5)
  6. Signal 2 bars or more?3 minYes: escalate; No: suggest extender (F6)

Example for: a 12-agent support team at Nestwell smart doorbells; customers report the doorbell shows "Offline" in the app.

1. Issue summary

The Nestwell app shows "Device offline" and live view will not load. This makes up about 18% of weekly tickets, mostly after a router change.

2. Decision tree

  1. Is the light ring on the doorbell lit? (Time: 0.5 min)

    • If Yes → Step 2
    • If No → Fix F1
  2. Did the customer change their router, Wi-Fi name or password in the last 14 days? (Time: 0.5 min)

    • If Yes → Fix F2
    • If No → Step 3
  3. Does Device Info in the app show firmware 4.2 or later? (Time: 1 min)

    • If Yes → Step 4
    • If No → Fix F3
  4. Is a 2.4 GHz Wi-Fi network available on the customer's router? (Time: 2 min)

    • If Yes → Step 5
    • If No → Fix F4
  5. After holding the doorbell button for 10 seconds to restart, is it back online within 3 minutes? (Time: 4 min)

    • If Yes → Fix F5
    • If No → Step 6
  6. Does the app's Wi-Fi signal reading show 2 bars or more at the door? (Time: 3 min)

    • If Yes → ESCALATE
    • If No → Fix F6

3. Escalation block

  • Trigger: Step 6 answered Yes (power, firmware, network band and signal all fine, still offline).
  • Receiving team: Tier 2 Device Engineering
  • Required info: device serial number, firmware version, router make and model, signal bars, steps 1-6 results, time of last online status.

4. Fix table

Fix IDCauseAgent actionCustomer message
F1No powerConfirm wiring or battery charge"Your doorbell isn't getting power. Please charge the battery for 2 hours or check the breaker, then tell me if the light comes on."
F2New Wi-Fi detailsGuide through Settings > Reconnect Wi-Fi"Since your Wi-Fi changed, the doorbell needs the new details. In the app, tap Settings, then Reconnect Wi-Fi."
F3Old firmwarePush update from admin panel"I've sent a free update to your doorbell. It will restart in about 5 minutes."
F45 GHz onlyExplain band requirement"Your doorbell needs a 2.4 GHz network. Most routers can turn this on in their settings; I can walk you through it."
F5Temporary faultClose ticket, note restart fix"Great, it's back online. If it drops again, a 10-second button hold usually fixes it."
F6Weak signalSuggest moving router or extender"The signal at your door is weak. A Wi-Fi extender within 5 metres of the door usually solves this."

Assumptions: agents can push firmware remotely and see signal bars. Also worth checking: ISP outages and accounts with an expired cloud plan.

Written by AI from this prompt. Your results will vary.

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 in Customer Support