Purpose
Turn a tense or emotionally charged support situation into a calm, resolution-focused reply by leading with genuine acknowledgment before any explanation or fix. Solves the specialist's core problem: responses that are technically correct but emotionally tone-deaf, which escalate frustration instead of defusing it.
When to Use
Invoke this skill when the user asks to:
- Respond to an angry, frustrated, or upset customer message
- Deliver bad news — a denied refund, an unavailable feature, a policy limitation — without triggering escalation
- Rewrite a draft reply that sounds cold, defensive, robotic, or dismissive
- Apologize for an error, outage, delay, or billing mistake
- Handle a customer who feels ignored, blamed, or unheard
- Soften a "no" while still holding a firm boundary or policy
Inputs Required
Before starting, collect:
- Customer's message: The exact message or complaint, pasted in full so tone and specific grievances are visible
- Emotional state: Frustrated / angry / anxious / disappointed / feeling ignored (or best read from the message)
- What actually happened: The factual situation from the company's side
- The resolution: What can be offered — full fix, partial fix, workaround, or a firm "no"
- Boundaries/policy limits: Anything you cannot offer or promise
- Relationship context: New customer, long-time customer, prior complaints, or unknown
- Brand voice: Warm-casual / professional-warm / formal (defaults to professional-warm if not provided)
If emotional state isn't specified, infer it from the customer's message and state the read in the breakdown so the specialist can correct it.
Instructions
Step 1: Read the Emotion Before the Facts
Identify the primary emotion driving the message and the underlying need beneath it. Frustration usually masks one of these:
- Feeling unheard → needs acknowledgment
- Feeling wronged → needs validation that the problem is real
- Feeling powerless → needs a sense of control or a clear next step
- Feeling disrespected → needs to be treated as reasonable, not as a problem
Name the primary emotion and the underlying need. Everything downstream anchors to this.
Step 2: Open With an Active Listening Signal
The first 1–2 sentences must prove you read and understood — before any explanation. Use one of these openers, filled in with the customer's actual specifics:
- Reflect back: Restate their problem in your words ("You've been charged twice and no one has gotten back to you for three days — that's frustrating on both counts.")
- Name the feeling: Acknowledge the emotion explicitly ("I can hear how frustrating this has been.")
- Validate the legitimacy: Confirm the complaint is reasonable ("You're right to expect this to work the way it was described.")
Never open with a fact, a policy, or the word "unfortunately." Never open with "I understand your frustration, but" — the "but" erases the empathy.
Step 3: Take Appropriate Ownership
Match the ownership to the situation. Do not over-apologize or accept blame that isn't yours.
- Company error: Direct, specific apology ("We charged you twice — that's our mistake, and I'm sorry.")
- No one's fault / expectations gap: Acknowledge the impact without accepting false blame ("I'm sorry this didn't work the way you expected.")
- Customer error: Never blame — remove shame ("This is a really common mix-up — easy to fix.")
Avoid corporate non-apologies ("We're sorry you feel that way," "We apologize for any inconvenience"). Be specific about what you're sorry for.
Step 4: Bridge to the Resolution
Transition from emotion to action with a phrase that signals partnership, not defensiveness:
- "Here's what I can do right now:"
- "Let me get this sorted for you."
- "Here's how we'll make this right."
Then present the resolution:
- Full fix: State it plainly and set a timeline
- Partial fix / workaround: Lead with what you can do before what you can't
- A firm "no": Deliver the boundary with a reason and, whenever possible, an alternative ("I'm not able to refund past the 30-day window, but I can extend your plan by a month to make up for the lost time.")
Frame every limitation as protecting or serving the customer, never as protecting the company.
Step 5: Close With Control Returned to the Customer
End by handing them the next move and an easy path back:
- Offer a concrete next step or a direct line back to you
- Invite reply ("If that doesn't fully solve it, reply here and I'll keep working on it.")
- Sign off warmly and human, not automated
Step 6: Produce the De-escalation Breakdown
After the message, list the specific moves used so the specialist learns the pattern: emotion identified, opener type, ownership level, resolution framing, and boundary handling (if any).
Output Format
- Structure: Final customer-ready message first, then a labeled de-escalation breakdown
- Length: Message 80–150 words; breakdown 60–100 words
- Format: Message as clean prose ready to paste; breakdown as a short labeled list
- Sections: (1) Customer-Ready Message — (2) De-escalation Breakdown (Primary emotion / Opener type / Ownership level / Resolution framing / Boundary handling)
- Tone: Warm, calm, and specific — never scripted, never groveling. Matches the provided brand voice.
Quality Checklist
Before delivering output, verify:
- [ ] The message opens with an active listening signal — not a fact, policy, or "unfortunately"
- [ ] No "but" appears immediately after an empathy statement (use "and" or a new sentence)
- [ ] The apology (if any) is specific to what happened — no "sorry for any inconvenience"
- [ ] What can be offered is stated before what can't
- [ ] Any "no" includes a reason and, where possible, an alternative
- [ ] The message contains no bracket placeholders and is ready to send as-is
- [ ] The breakdown names the specific emotion and the moves used
Notes
- The single highest-impact move is Step 2: a real acknowledgment before any explanation prevents most escalations by itself.
- When rewriting an existing draft, keep any accurate facts but restructure so emotion is handled first, resolution second.
- Over-apologizing reads as weakness and invites more demands — one specific, sincere apology beats three vague ones.
- If the customer is abusive rather than upset, hold the empathy but add a calm boundary; flag to the specialist that escalation to a supervisor may be warranted.
How to use this skill
This file is a Claude Code skill in Anthropic's standard format — markdown with YAML frontmatter at the top.
Installing in Claude Code:
~/.claude/skills/<folder-name>/SKILL.md— auto-loads in every session anywhere on your machine (recommended for skills you'll use across multiple projects)<your-project>/.claude/skills/<folder-name>/SKILL.md— auto-loads only when working in that project (recommended for project-specific skills)
Restart Claude Code or open a new session to register.
Using in Claude.ai, ChatGPT, Gemini, or other AI tools:
- Drag this file into a new chat, or copy and paste its contents
- Send your task or request as your next message — the AI will apply the skill where it fits
For Claude Code skill details: https://docs.anthropic.com/en/docs/claude-code/skills