Build a troubleshooting decision tree for agents
Use to turn a messy diagnostic process into a clean branching guide agents can follow under pressure.
You design internal troubleshooting guides for {{company}}.
The problem area: {{problem_area}}. Known causes and fixes: {{known_causes}}. Tools agents can use: {{agent_tools}}.
Build a decision tree where:
- Each node is a yes/no question or a quick check an agent can perform.
- Each branch leads to either the next check or a resolution step.
- Dead ends route to escalation with a note on what to capture first.
Format as an indented outline. Keep questions concrete and answerable in seconds. Include the single most common fix at the top as a fast path.Click the copy button in the top right of the block to grab the full prompt.
Replace each placeholder below with your own values before you run the prompt.
- {{company}}
- {{problem_area}}
- {{known_causes}}
- {{agent_tools}}
Related prompts
You are a senior customer support agent for {{company}}. Write a first reply to this message from an upset customer. Customer message: """ {{customer_message}} """ Requirements: -...
Write a support reply about a delayed order for {{company}}. Details: - Order number: {{order_number}} - Original delivery estimate: {{original_eta}} - New realistic estimate: {{ne...
Write a support reply confirming an approved refund for {{company}}. Details: - Customer name: {{customer_name}} - Amount: {{refund_amount}} - Payment method refunded to: {{payment...
Write a support reply that politely declines a refund for {{company}}. Context: - What the customer asked for: {{request}} - Policy that applies: {{policy}} - Why it does not quali...
Write a churn-save email for {{company}} aimed at a customer who is canceling. Context: - Plan they are on: {{plan}} - Stated cancel reason: {{cancel_reason}} - Best save offer you...
You are setting up canned response macros for {{company}}'s help desk. Create {{count}} reusable macros covering these common topics: {{topics}} For each macro provide: - A short i...
0 Comments
Loading discussion...