Notify a customer of a shipping or fulfillment delay
Use when an order is delayed and you need to inform the customer before they get frustrated.
You are an ecommerce support agent writing a proactive delay notification.
Order details: {{order_details}}
Reason for delay (honest, customer-appropriate): {{delay_reason}}
New expected date: {{new_date}}
Compensation or gesture, if any: {{gesture}}
Write a reply that:
1. Leads with the new timeline so they get the key fact first.
2. Gives an honest, brief reason without over-explaining.
3. Offers any gesture proactively.
4. Provides tracking or a clear next checkpoint.
5. Makes it easy to reply if the new date does not work for them.
Tone: honest, considerate, not groveling. Under 120 words.Click the copy button in the top right of the block to grab the full prompt.
Replace each placeholder below with your own values before you run the prompt.
- {{order_details}}
- {{delay_reason}}
- {{new_date}}
- {{gesture}}
Related prompts
You are a senior customer support agent for {{company}}. Write a first reply to this message from an upset customer. Customer message: """ {{customer_message}} """ Requirements: -...
Write a support reply about a delayed order for {{company}}. Details: - Order number: {{order_number}} - Original delivery estimate: {{original_eta}} - New realistic estimate: {{ne...
Write a support reply confirming an approved refund for {{company}}. Details: - Customer name: {{customer_name}} - Amount: {{refund_amount}} - Payment method refunded to: {{payment...
Write a support reply that politely declines a refund for {{company}}. Context: - What the customer asked for: {{request}} - Policy that applies: {{policy}} - Why it does not quali...
Write a churn-save email for {{company}} aimed at a customer who is canceling. Context: - Plan they are on: {{plan}} - Stated cancel reason: {{cancel_reason}} - Best save offer you...
You are setting up canned response macros for {{company}}'s help desk. Create {{count}} reusable macros covering these common topics: {{topics}} For each macro provide: - A short i...
0 Comments
Loading discussion...