Writing delivery status and running-late messages

A customer waiting on a delivery doesn't want a nice message. They want to know three things: is it coming, when, and what do they need to do. The worst messages are the ones that say nothing in a lot of words.

Delays happen for dull reasons. Roadworks, a late load-out, a dock that's backed up. A customer can cope with most of them if they hear early and plainly. What they don't forgive is silence, or a promise that then breaks.

Get the facts before you open the tool

The tool can only dress up what you give it. So collect these first, from the driver, the tracking system or your own job sheet:

• Which job, and its reference number.
• What has happened, in one plain sentence.
• The new estimated time, or a clear "we don't know yet".
• What you'll do next, and when you'll update them.
• Anything you need from the customer, such as a changed site contact.

Take the time estimate from the driver or tracker, never from the tool. If you don't know, say so. "We'll update you by the afternoon" is honest and useful. A made-up arrival time that turns out wrong is worse than no time.

What a good delay message says

Keep it short. A reader should get what they need from the first two lines on a phone screen.

• Lead with the news. "Your delivery will arrive later than planned."
• Give the new time, or say it isn't known.
• Say the reason in a few words. You don't need to over-explain.
• Say what happens next. When you'll next be in touch, and what they can do.
• Skip big apologies and excuses. One short "sorry for the delay" is enough.

Don't blame the driver, another customer or a named third party. And don't name a driver or give personal details about them in a message. Driver details are private data.

Prompting for the draft

Give the tool the facts as a short list, then ask for two or three lines in a calm, plain tone. Tell it, in so many words, not to add times, reasons or promises you didn't give it. It's also fair to ask for the same message in text length and email length.

When the draft comes back, look at what it added. Common extras are "don't worry", "we're doing everything we can" and "your goods are fine". The last one is a claim about the goods that nobody told the tool. Cut it unless you know it's true.

An AI tool can state false details as if they were fact¹. In a delay message that's usually a time, a reason or a reassurance.

Keep a record of what you sent

Delivery disputes often turn on who was told what, and when. Wikipedia's page on proof of delivery warns that a recipient company may deny getting a message about a delayed shipment, which can lead to legal complications². That's about business document exchange. The lesson fits a small office too.

So save the sent message with the job: the time, the channel and the wording. Don't rely on a chat tool's history. It isn't your record, and the history may be switched off or deleted.

When to ring instead

Some situations need a call, not a draft: a time-critical delivery that will miss its window, an upset customer, or a delay that involves damage or a safety matter. For those, speak to a person. Anything touching damage claims, insurance or legal rights is not something to hand to a chat tool. Ask your insurer or the relevant official body.

A short template to adapt

Fill in the brackets yourself, then ask the tool only to smooth the wording:

Hi [name], your delivery [reference] is running late because [reason]. We now expect it at [time, or "we'll confirm by [time]"]. [One line on what the customer needs to do, if anything.] We'll message you again by [time].

Once the real facts are in, the tool has little room to get them wrong. That's the point of the template.