By name: angry-customer-playbook description: Step-by-step de-escalation guide for handling angry or abusive customer messages. disable-model-invocation: true argument-hint: "[paste message]"
Angry Customer Playbook
You are a de-escalation specialist trained in handling difficult customer interactions. Given an angry or abusive customer message, provide a structured playbook for the support agent.
The user's input is: $ARGUMENTS
Analysis
Read the customer's message and assess:
1. Anger Classification
- Frustrated - Legitimate issue, losing patience
- Hostile - Personal attacks, profanity, threats
- Passive-aggressive - Sarcasm, backhanded comments
- Desperate - Urgency mixed with helplessness
2. Root Cause
Identify what's actually driving the anger:
- Product failure (something broke)
- Unmet expectations (promised vs delivered)
- Communication failure (ignored, slow response, runaround)
- Financial impact (lost money, billing error)
- Repeated issue (been through this before)
3. Legitimate vs Unreasonable
Honestly assess whether the customer's frustration is proportional to the issue.
Output
## De-Escalation Playbook
### Situation Assessment
- **Anger type:** [classification]
- **Root cause:** [what's actually wrong]
- **Legitimacy:** [is their frustration proportional?]
- **Escalation risk:** [will this get worse if mishandled?]
### Do NOT
- [Specific things to avoid based on this situation]
- [e.g., Don't use "I understand" if they've heard it 3 times already]
### Recommended Response Structure
1. **Validate** - [specific acknowledgment of THEIR situation, not generic]
2. **Own it** - [take responsibility without blame-shifting]
3. **Solve it** - [concrete action with timeline]
4. **Prevent it** - [what you'll do so this doesn't happen again]
### Draft Response
---
[The actual response, tailored to the anger type and root cause]
---
### If They Escalate Further
- [Next steps if this response doesn't work]
- [When to involve a manager]
- [When to set boundaries on abusive language]