RescueEscalationHuman review required

Escalation First Response

Draft a calm, specific first reply to an angry customer that buys you time without over-promising.

The first response to an escalation is not where you fix the problem. It is where you decide whether the customer believes you will. Honesty about what you do not know buys more trust than false confidence ever does.

The template

Copy it, swap the {{marked}} variables for your account, and run it.

prompt.txt

A customer has escalated and is upset. Draft a first response email from me
(their CSM). The goal is to de-escalate and set a concrete next step, NOT to
resolve the issue in this email or to promise things I cannot control.

What happened: {{incident}}
What the customer said (their words / tone): {{customer_message}}
What I actually know right now: {{known_facts}}
What I do NOT yet know: {{unknowns}}
What I can honestly commit to today: {{safe_commitment}}
My relationship with them: {{relationship}}

Rules:
- Acknowledge the specific impact, not a generic "sorry for any inconvenience."
- Never promise a fix or a timeline I did not give you in "safe commitment."
- No corporate throat-clearing. Get to the point in the first two sentences.
- End with one concrete next step and a time.

Variables

{{incident}}: What happenede.g. a failed export blocked their month-end close for 6 hours yesterday
{{customer_message}}: Customer's message / tonee.g. "This is the third time. I'm starting to wonder if this platform can be trusted with our reporting."
{{known_facts}}: What you know right nowe.g. engineering confirmed a queue backlog; the export ran successfully at 11pm
{{unknowns}}: What you don't yet knowe.g. root cause; whether it can recur; whether other customers were hit
{{safe_commitment}}: What you can honestly commit toe.g. a root-cause summary by Thursday EOD and a call with me + an engineer
{{relationship}}: Your relationshipe.g. 2-year customer, generally happy, this is their first real escalation

Worked example

A CSM opens their inbox to a furious email: a reporting export failed during the customer's month-end close, for the third time. Engineering has a partial picture but no root cause yet. The CSM needs to respond within the hour without promising a fix they cannot guarantee.

filled-prompt.txt

What happened: a failed export blocked their month-end close for 6 hours yesterday
What the customer said: "This is the third time. I'm starting to wonder if this platform can be trusted with our reporting."
What I know right now: engineering confirmed a queue backlog; the export ran successfully at 11pm
What I do NOT yet know: root cause; whether it can recur; whether other customers were hit
What I can commit to today: a root-cause summary by Thursday EOD and a call with me + an engineer
Relationship: 2-year customer, generally happy, this is their first real escalation

Good output vs bad output

GOODAcknowledges the exact impact and the trust hit, separates known from unknown honestly, and commits only to what was in "safe commitment."

Subject: Your month-end export, what I know and what happens next

Priya,

A failed export blocking your close for six hours, on the third occurrence, is
not acceptable, and I understand why your confidence is shaken. I am not going
to hand you a reassurance I cannot back up yet.

Here is exactly where things stand: engineering confirmed a queue backlog
caused yesterday's failure, and the export did complete at 11pm. What I do not
yet know is the root cause or whether it can recur, and I will not guess.

What I can commit to today: a written root-cause summary by Thursday end of
day, and a call with me and one of our engineers so you can ask them directly.
I will send three time options within the hour.

I own this until it is closed.

Ryan

BADLooks fine at a glance. Here is why it fails.

Hi Priya,

Thank you so much for reaching out and for your patience! We sincerely
apologize for any inconvenience this may have caused. Your satisfaction is our
top priority and we take this very seriously.

Good news: our team has already resolved the issue and everything should be
working smoothly now. We're confident this won't happen again. Please don't
hesitate to reach out if you have any other questions!

Warm regards,
Ryan

Wrong register"Thank you for your patience" and "any inconvenience" to a customer who just questioned whether you can be trusted reads as tone-deaf and inflames it.
Over-promising"We're confident this won't happen again", the CSM does not know the root cause, so this is a promise they cannot keep and will be quoted back to them.
Unverified claim"Already resolved" overstates a single successful 11pm run into a fix; the root cause is still unknown.
No next step"Reach out if you have questions" pushes the work back onto the angry customer instead of committing to the Thursday summary and call.

Guardrails

When NOT to use this

Do not use for a legal, security, or data-breach escalation. Those go straight to your incident and legal process; a CSM email can create liability.
Not for a customer threatening to churn over commercials; that is a save play, not a de-escalation email.

Responsible use

The model does not know your real commitments. If "safe commitment" is wrong, the email is wrong. You own every promise in it.
Never let the model invent a root cause or a timeline to sound reassuring. Empty confidence is how escalations become churn.

A human must review the output before it reaches the customer.

Model + settings

Model: Claude Sonnet is plenty; Opus if the account is large and the wording is delicate.
Temperature: 0.5 (moderate, you want a human, warm tone, not a template)
Settings: Give it your real "safe commitment" every time. This is the field that keeps the model from over-promising.
Always read it out loud before sending. If any sentence commits you to something you did not authorize, cut it.

Back to all prompts