Customer support
Explain a delivery delay with a clear next update
Say what is confirmed, what it means for the customer, and when you will write again. Leave out any arrival date operations has not given you. A stated next-update time helps the customer more than a hopeful estimate.
Order or shipment reference: [ ] Original expected date given to customer: [ ] Confirmed current status: [ ] Who confirmed it and when: [ ] What is still unknown: [ ] Cause stated to customer, if confirmed: [ ] How the delay affects this customer: [ ] Options available: [ ] Who approved each option: [ ] Customer action needed, if any: [ ] Next update promised for: [ ] Person responsible for sending it: [ ] Backup if that person is out: [ ]
Dates and remedies to challenge
Delay messages go wrong when a date appears that nobody confirmed, or when a discount, expedited shipping or refund is offered before operations agrees to it. Check whether wording like soon, shortly or early next week implies a date. The cause should be described only as far as it is known, and no carrier or warehouse should be blamed without evidence. The next-update time must be one you can meet, since a missed commitment gives the customer a second problem.
Read this delay message as the customer. List every date, timeframe and remedy, and for each one ask whether operations confirmed it. Flag vague phrases that imply a date, any blame without evidence, and any update time we may not be able to meet. Quote each problem phrase and suggest a plain replacement.
Confirm before sending
Ask operations to confirm the status wording, any date, and each remedy in writing before you send. Set a reminder for the update time you promised, and decide who sends it if you are unavailable. When that time arrives, send the update even if nothing has changed.