PlaybookPrompts

Re-anchor tone after a hostile customer message

Customer Support de-escalationtoneemail-replycustomer-anger

When a customer sends an aggressive or threatening message, your reply sets the emotional trajectory of the entire conversation. This prompt helps you draft a response that acknowledges frustration without matching it or caving unnecessarily.

Prompt
You are an experienced support specialist trained in de-escalation. A customer has sent a hostile message and I need to draft a reply that lowers the temperature without being dismissive or sycophantic.

Context:
- Customer message: {{CUSTOMER_MESSAGE}}
- Current status of their issue: {{ISSUE_STATUS}}
- What I can and cannot offer right now: {{OFFER_CONSTRAINTS}}

Follow these steps:
1. Identify the core grievance beneath the anger (separate the emotion from the request).
2. Draft an opening sentence that names the frustration specifically—do not use 'I understand your frustration' or 'I apologize for any inconvenience'.
3. Write 2-3 sentences that explain the current status in plain language, without deflecting blame onto other teams or systems.
4. State clearly what will happen next and by when. If no deadline is possible, say so and explain why.
5. Close with one sentence that leaves the door open for follow-up without sounding like a form letter.
6. Flag any part of the message that suggests an escalation risk (chargeback threat, legal language, public complaint threat) and suggest how to handle it separately.

Edge cases: If the message contains hate speech or personal threats, stop at step 1 and recommend escalating to a manager rather than responding directly. If the issue is already resolved, note that in step 3 and skip step 4.
Variables to fill in
  • {{CUSTOMER_MESSAGE}}
  • {{ISSUE_STATUS}}
  • {{OFFER_CONSTRAINTS}}

How to use this prompt

  1. Copy the prompt above (Copy button on the top-right).
  2. Replace each {{VAR}} with your own value. Variables: {{CUSTOMER_MESSAGE}}{{ISSUE_STATUS}}{{OFFER_CONSTRAINTS}}.
  3. Paste it into one of the recommended tools below.
  4. Iterate: tighten constraints in the prompt if the output is generic.

Why this prompt is structured this way

The prompt is split into explicit steps because LLMs do better when the path is named, not implied. Each variable forces specificity at the input layer — vague inputs get vague outputs.

Heads up: some of the links on this page are affiliate links — meaning we may earn a commission if you sign up after clicking, at no extra cost to you. We only recommend tools we'd put on our own stack. You can see our full affiliate disclosure here.

Pair this prompt with a tool

The PlaybookPrompts weekly

One short email per week. The five sharpest prompts we found, one tool worth your attention, one anti-pattern to avoid. Unsubscribe in one click.

Newsletter signup is not configured. Set PUBLIC_NEWSLETTER_USERNAME in the build env.