Back to Recipe Book
Business 🍳 Home Cook

Refund Request Response (Customer Service)

Two response templates for difficult refund requests β€” an empathetic retention save with a high-value alternative, and a firm-but-polished exit that closes cleanly without triggering a dispute or negative review.

Best for SaaS cancellations, digital product refund requests, service complaints
When to use When a customer asks for a refund and the outcome (save vs. exit) still matters to your brand
customer servicerefundsretentionbrand reputationsupport

How you handle a refund is the most memorable customer service interaction you’ll have. A cold, automated response creates reviews. A warm, clear one creates reputation. This recipe writes both versions β€” save attempt and clean exit β€” without defensive language or robotic boilerplate.

The Recipe

Act as an elite Customer Success Manager and brand reputation protector. I have received a difficult refund request from a customer who is unhappy or facing issues with our product/service. I need to handle this with deep empathy, protect our brand's public image, and β€” if possible β€” gently turn the interaction into a retention or feedback save.

The customer's situation and complaint: [INSERT CUSTOMER ISSUE & COMPLAINT]
Our refund policy rules: [e.g., strict 14-day window, no refunds on digital downloads, or full unconditional guarantee]

Please generate 2 distinct response templates based on our operational needs:
- Version 1 (The Elegant Save): A deeply empathetic, high-care message that acknowledges their frustration, provides an immediate fix or a high-value alternative asset (e.g., 1-on-1 support, account credit, custom tier modification), and politely asks if they would be open to trying the fix before finalizing the cancellation.
- Version 2 (The Firm but Polished Exit): A professional, respectful, and crystal-clear message that cleanly facilitates the refund (or holds the firm boundary if outside the policy limits) while keeping the communication incredibly polite to prevent negative reviews, forum drama, or payment disputes.

Ensure all versions completely eliminate defensive language, cold corporate jargon, or automated robotic boilerplate.

Version 1 vs. Version 2: when to use each

VersionUse whenGoal
The Elegant SaveCustomer seems fixable β€” frustrated but not hostileRetain with a high-value offer
The Firm Polished ExitOutside policy, hostile, or determined to leaveClose cleanly, prevent a dispute

The language that kills brand reputation

Avoid these in every response:

  • β€œPer our policy…” (cold, robotic)
  • β€œUnfortunately, we are unable to…” (passive, impersonal)
  • β€œI apologize for any inconvenience” (empty, automated-sounding)
  • β€œThis is outside our refund window” (statement of rejection, not resolution)

Replace with: acknowledgment of the specific frustration, ownership of the interaction, and a clear next step β€” whether that’s a fix or a clean exit.

πŸ” Leftover Remixes

🌢️ Spicy: β€œAfter both versions, write a 3-sentence internal note I can add to the customer record documenting what happened and what offer was made.”

🧊 Mild: β€œWrite only Version 2. The customer is outside the refund window and has been rude. Keep it under 100 words.”