Transparent Refund Delay Responder
Draft professional, transparent emails for delayed refunds without over-promising timelines.
Customise & copy
Add the context you have. The prompt updates as you work.
The name of the customer inquiring about the refund.
The purchase or order reference number.
Current status or reason for the delay to explain to the customer.
Live prompt
3 fieldsDraft an email reply to Jane Doe regarding their delayed refund for transaction ORD-98765. The delay is due to the following reason: Our payment processor is currently experiencing a technical backlog affecting batch refund settlements.. Requirements: - Acknowledge the delay clearly and directly. - Maintain a calm, professional, and empathetic tone without fluff or corporate buzzwords. - Explain the situation transparently. - Do NOT promise a specific arrival date or timeframe for the refund. - Keep it concise and ready to send with no placeholder brackets remaining.
Proof before you use it
A real example
Tested on gemini-3.1-flash-lite on 2026-09-02
{
"delay_reason": "Our payment processor is experiencing an unexpected system-wide backlog for all outgoing electronic transfers.",
"customer_name": "Marcus Vance",
"transaction_reference": "TXN-33492"
}A small ritual that works
How to use it
- 01Enter the customer's name and the transaction reference number.
- 02Paste the specific reason for the delay into the prompt.
- 03Review the generated email for tone and accuracy.
- 04Send directly to the customer without adding fluff or false promises.
Why it works
The prompt establishes clear constraints by requiring transparent communication of the delay without promising an unrealistic arrival timeframe, while maintaining a calm and empathetic tone.
Where it fails
INSUFFICIENT_EVIDENCE
Customisation tips
Modify the delay_reason variable to reflect specific operational updates when migrating payment gateways or encountering processor-side technical backlogs.
Watch-outs
- Ensure that support agents do not inadvertently add a specific refund timeline in the blank fields, as the prompt explicitly forbids promising an arrival date.
- Verify that all placeholder brackets are completely removed prior to sending.
Works in
Was this useful?
Submit your variation
If your version helps, it may be published with your name and a link back to you.
Want to make AI useful across your team? Explore Atul's training.