Write a Refund or Return Denial Email That Keeps the Customer
Get a clear, polite denial email that explains the policy reason in plain words, offers an approved alternative, and includes a short chat version and escalation-risk note.
You getSubject line, email reply and internal note
Prompt
You are a senior customer support lead who writes refund and return replies that hold the line on policy without losing the customer.
Your job: write a reply denying a refund or return request. Before writing, ask me these questions in one numbered message and wait for my answers:
1. What does the relevant policy say? Paste the exact wording if you have it.
2. What are the order details: product, order date, request date, price, and the customer's stated reason?
3. What can the team actually offer instead (store credit, exchange, repair, partial refund, discount)? List only what is approved.
4. Paste the customer's message or describe their tone.
Rules:
- State the decision within the first two sentences.
- Explain the reason in plain words, naming the specific policy point and the date or condition that applies.
- Offer at least one alternative from my approved list only; never promise anything I did not approve.
- No blame, use "unfortunately" at most once, and avoid "per our policy".
- Keep the email under 170 words and end with one clear next step for the customer.
Output format:
- Subject line
- Email reply
- Internal note: escalation risk (low, medium or high) and why, in one line
- Two-sentence version for chat or SMS
If any policy detail or approved alternative is missing, say so instead of guessing.Example output
Tips and common edits
Why this works
- Asking for the exact policy and approved alternatives first stops the model from inventing offers your team can't deliver.
- Putting the decision in the first two sentences avoids false hope and the angry follow-up it causes.
- The escalation-risk note and chat version give agents a ready plan for the next channel or reply.
Use when you must say no to a refund or return but want to keep the customer. Have the policy text, order dates, and your approved alternatives ready. Works in ChatGPT, Claude or Gemini.
Common edits
- Change the tone to match your brand voice, such as more casual for a DTC brand or more formal for B2B.
- Ask for three versions with different alternatives so you can pick the one that fits the customer best.
Prompt details
- By
- Prompts-GPT editors
- Published
Did this prompt work?
Keep exploring
More like this
Rewrite a Support Reply to Be Clearer, Shorter and Friendlier
Returns your support draft cut by at least 30 percent, with every fact and commitment kept and a table of risky promises plus safer wording.
Audit a Help Center Article for Gaps, Jargon and Outdated Steps
Paste a help center article and get a pass/fail checklist scorecard plus a line-by-line fix list ranked by customer impact, without a full rewrite.
Turn Feature Notes into a Step-by-Step Help Center How-To Guide
Paste rough notes about a product feature and get a customer-ready how-to guide with one action per step, bold UI labels, expected results and a troubleshooting section.
Write Chatbot Intent Answers with Trigger Phrases and Human Handoff Rules
Get a set of chatbot intents for your top support questions, each with customer-style trigger phrases, a short bot answer, and an exact rule for handing off to a human.
Write Help Article Titles and Meta Descriptions in Your Customers' Words
Get help article titles that start with the customer's task verb and meta descriptions within search length limits, each with a character count and the customer phrase it matches.
Build a Yes/No Troubleshooting Decision Tree for a Recurring Product Issue
You get a step-by-step yes/no troubleshooting tree ordered from fastest, most likely checks to slowest, with ready-to-send customer messages and a clear escalation point.