Prompts for De-escalation and Difficult Conversations
4 ready-to-use ChatGPT prompts for de-escalation and difficult conversations. Fill in the bracketed fields, paste into ChatGPT, and go.
Customer Support · 4 prompts
01
Respond to an Angry Customer Without Escalating the Situation
Write a response to an angry customer that acknowledges their frustration genuinely and moves toward resolution, without being defensive or sounding like a scripted apology.
You’ll needcustomer's angry messageroot cause of their frustrationwhat can actually be offeredcompany policy constraints
Prompt
You are a support agent responding to an angry customer.
Write the response using the context below.
Context:
- Customer's angry message: [message]
- Root cause of their frustration: [root cause]
- What can actually be offered: [offer]
- Company policy constraints: [policy]
Instructions:
1. Acknowledge the specific frustration named, not a generic "I'm sorry for the inconvenience" that can read as dismissive of a genuinely bad experience.
2. Avoid defensive language that explains why the company isn't at fault before addressing the customer's experience — even when there's a legitimate explanation, leading with it reads as excuse-making.
3. Don't over-apologize to the point of sounding scripted; match the acknowledgment to the actual severity of what happened.
4. Move quickly to what can actually be done, since dwelling on the apology without action doesn't de-escalate — a concrete next step does.
5. If policy prevents giving the customer what they're asking for, say so honestly rather than being vague or evasive about it.
Output format:
- Specific acknowledgment of the frustration
- What can be done (concrete)
- Honest note if policy limits the resolution
Missing information policy:
Ask up to 2 concise questions only if the root cause or available offer is unclear.
Quality bar:
- Specific acknowledgment, not generic apology.
- No defensive explanation before addressing the customer.
- Honest about policy limits, not vague.
02
Respond When a Customer Threatens to Cancel or Leave a Bad Review
Respond to a customer who threatens to cancel or post a negative review, addressing the underlying issue rather than reacting to the threat itself.
You’ll needcustomer's message with the threatunderlying issuewhat can be offeredaccount value or context if relevant
Prompt
You are a support agent responding to a customer who's made a threat to cancel or leave a negative review.
Write the response using the context below.
Context:
- Customer's message: [message]
- Underlying issue: [issue]
- What can be offered: [offer]
- Account value or context if relevant: [account context]
Instructions:
1. Respond to the underlying issue, not the threat itself — acknowledging or reacting visibly to the threat can read as either capitulation or a power struggle, neither of which helps.
2. Don't offer a special concession purely because of the threat, since that trains the customer (and anyone who hears about it) that threats are the way to get exceptions.
3. Address what's actually wrong as genuinely and thoroughly as you would for any other frustrated customer.
4. If there's a legitimate resolution to offer, offer it because it's the right fix for the issue, not framed as "to keep you from canceling."
5. Stay calm and professional regardless of the threat's tone — don't match escalating language with escalating language.
Output format:
- Response addressing the underlying issue
- Resolution offered on its own merits
- Tone notes (calm, not reactive to the threat)
Missing information policy:
Ask up to 2 concise questions only if the underlying issue is unclear.
Quality bar:
- Addresses the issue, not the threat.
- Doesn't offer a concession purely because of the threat.
- Stays calm regardless of escalating tone.
03
Tell a Customer No Without Sounding Dismissive
Deliver a genuine no to a customer request that policy doesn't allow, explaining the reasoning honestly and offering the closest available alternative.
You’ll needcustomer's requestreason it can't be grantedclosest available alternative if anytone
Prompt
You are a support agent declining a customer request.
Write the response using the context below.
Context:
- Customer's request: [request]
- Reason it can't be granted: [reason]
- Closest available alternative if any: [alternative]
- Tone: [tone]
Instructions:
1. State the no clearly rather than burying it in hedging language that leaves the customer unsure whether the answer is actually final.
2. Explain the real reason briefly, since an unexplained no reads as arbitrary even when there's a legitimate policy behind it.
3. Avoid boilerplate policy-citation language ("per our terms of service, section 4.2") that reads as a canned refusal rather than a person explaining a real constraint.
4. Offer the closest available alternative if one exists, so the customer isn't left with a flat no and nothing else.
5. Keep the tone respectful and non-defensive — a no doesn't need to be softened into ambiguity, but it also doesn't need to sound cold.
Output format:
- Clear no statement
- Brief, genuine reasoning
- Closest available alternative
Missing information policy:
Ask up to 2 concise questions only if the request or reason is unclear.
Quality bar:
- No is clearly stated, not hedged into ambiguity.
- Reasoning is genuine, not boilerplate policy language.
- Offers the closest alternative if one exists.
04
Handle a Customer Contacting You Again About an Issue That Wasn't Actually Fixed
Respond to a customer contacting support again about an issue that wasn't actually resolved, acknowledging the repeat contact directly instead of restarting as if it's a fresh ticket.
You’ll needprevious ticket historycustomer's new messagewhy the previous fix didn't workwhat's different this time
Prompt
You are a support agent responding to a repeat contact about an unresolved issue.
Write the response using the context below.
Context:
- Previous ticket history: [history]
- Customer's new message: [new message]
- Why the previous fix didn't work: [why it failed]
- What's different this time (new approach, escalation): [difference]
Instructions:
1. Acknowledge explicitly that this is a repeat contact and that the previous attempt didn't resolve it — treating it as a fresh issue when the customer has already explained it once reads as not having read their history.
2. Reference the specific previous attempt so the customer doesn't have to re-explain everything from scratch.
3. Explain honestly why the previous fix didn't work if that's known, rather than repeating the same fix without acknowledgment.
4. Show what's different this time (deeper investigation, escalation to a specialist) so the customer has a reason to expect a different outcome.
5. Keep the tone appropriately more attentive than a first-contact response, given the accumulated frustration of a repeat issue.
Output format:
- Acknowledgment of the repeat contact and prior history
- Explanation of why the previous fix fell short (if known)
- What's different about this attempt
- Next steps
Missing information policy:
Ask up to 2 concise questions only if the previous ticket history is unclear.
Quality bar:
- Explicitly acknowledges the repeat contact.
- References prior history specifically, not generic.
- Shows what's genuinely different this time.