The one-time, factual note about chargebacks taking longer than a direct refund is useful information, not leverage: say it once and move on, since repeating it starts to sound like a threat. If the refund is genuinely stuck, fix it before you reply at all so the email describes something already done.
Support
De-escalate a customer threatening a credit card chargeback
A scenario prompt for talking a frustrated customer down from a chargeback by fixing the actual grievance, not by arguing the dispute.
Works with Claude / GPT2,600 uses★ 4.7
The prompt
support-chargeback-deescalation
A customer replies to a support thread that's been open for 5 days: "I've asked three times for a refund on my annual license and gotten nothing but 'we're looking into it.' I'm done waiting, I'm disputing this charge with my bank today." CONTEXT: [refund was actually approved internally 2 days ago but never sent, due to a queue backlog; no bad faith, just a process failure on our end] Write the reply, as the support lead who now owns this personally. Requirements: - Do not argue against the chargeback or explain why they should trust the process, since threatening a chargeback usually means they've stopped believing promises. Fix the underlying problem instead. - Take ownership of the delay in the first sentence, plainly, without blaming "the queue" or a different department by name. - State exactly what happens next with a real timeframe (for example, "refunded within the next hour, you'll get a confirmation email"), not "as soon as possible." - Note, once, that a chargeback can actually take longer to resolve than a direct refund and lock the account during the dispute, only as useful information, not as a threat or a reason to argue them out of filing one. - Keep it under 100 words and skip any line that sounds like a policy recitation. Replace the CONTEXT block with your actual situation, including whether the refund is real, before running this.