A delayed delivery needs a customer update, not another internal alert

Key Takeaways

When a delivery runs late, the customer should hear it from you first, with a new ETA and a reason, before they call to ask.
An internal alert is not an update. It tells the logistics inbox something is wrong; someone still has to get the new ETA from the carrier, write the message and send it.
A useful delay update has 4 parts: what's late, the new ETA, the reason and what happens next.
Wilson, by Cartage, is an AI logistics agent that gets the new ETA and reason from the carrier, then tells the team and anyone else the company has set to be notified, including the consignee by email or SMS.
Decisions stay internal. The customer needs the ETA; the team needs the options, such as rebooking or expediting.

Why do delay alerts stay inside the company?

Delay alerts stay inside the company because an alert is a notification, not an action: it reaches the logistics inbox, and someone still has to confirm the new ETA with the carrier, write the update and send it to the customer. When the coordinator is busy, that chain stops at the alert. The customer ends up as the last to know.

This affects manufacturers and distributors that ship to customers who plan around delivery dates: a production line waiting on components, a distributor's branch waiting to fill orders, a retailer with a receiving appointment. For them a late load without notice costs more than a late load with notice, because they can't re-plan labor or tell their own customers. Early warning is still uncommon: in a BCI Global survey of 240 supply chain leaders (March 2025), only 35% reported end-to-end visibility.

One late load, hour by hour

Take one LTL load at a distributor, for example:

Wednesday 11:05 a.m. The tracking feed shows the load missed a terminal scan. An alert lands in the shared logistics inbox.
11:40 a.m. The coordinator, on a call about another load, hasn't opened it. Customer service doesn't have access to that inbox.
1:20 p.m. The coordinator emails the carrier asking for an ETA. The carrier's customer service says it will check with the terminal.
3:10 p.m. No reply. The coordinator calls; the load was held at a terminal for a trailer issue and will deliver Thursday morning instead of Wednesday afternoon.
4:05 p.m. The customer's receiving manager calls customer service asking where the 6 pallets are. Customer service doesn't know. They message the coordinator.
4:30 p.m. The customer finally hears "Thursday morning," five hours after the first alert and after their receiving crew waited all afternoon.

Every piece of information existed by 3:10 p.m. The gap was the update, not the tracking.

What should a delay update to the customer include?

A delay update should say what’s late, the new ETA, the reason and what happens next. Leave any one out and the customer will call to ask for it.

Part	Example	Why it matters
What’s late	Order 4512, 6 pallets, PO 88213	The customer matches it to their own order without a call
New ETA	Thursday, 10 a.m. to noon	They can move labor and receiving appointments
Reason	Held at the carrier’s terminal	They can judge whether it will slip again
What happens next	We’ll confirm on pickup from the terminal and on delivery	They know when to expect the next message

Use the customer’s own reference numbers, not only the carrier’s PRO number (the tracking number an LTL carrier assigns). Give an ETA window rather than “delayed” or “soon.” Keep the reason short and factual; the customer doesn’t need the carrier’s internal explanation.

When the new ETA is still unknown, send an update anyway: say the load is delayed, that you’re getting a new ETA from the carrier and when you’ll update next. Silence costs more trust than an incomplete answer. For setting these rules by customer, see late freight needs an update rule, not another reminder.

When should the customer get the update, and what mistakes delay it?

Send the update as soon as the new ETA is confirmed, before the customer has to ask, and send another whenever the ETA changes again. Timing matters more than polish.

The sequence is simple. A load misses a checkpoint or the carrier reports a delay; someone gets the new ETA and reason from the carrier; the customer gets the 4-part update; and they hear again on any further change and at delivery. Who gets notified, and how, should be set per customer in advance, so nobody decides it at 4 p.m. on a busy day.

Common mistakes

Routing alerts to a shared inbox nobody owns. The alert exists, but no one acts on it until the customer calls.
Waiting for a perfect ETA. Hours pass while the coordinator chases the carrier, and the customer's receiving crew waits.
Updating customer service but not the customer. Customer service now knows, but they still have to write and send the message.
Sending one update and stopping. If the ETA slips again, the first update becomes wrong information.
Sharing internal decisions with the customer. A message that debates rebooking options or blames the carrier creates more questions than it answers.

How does Wilson, by Cartage, update customers on delays?

Wilson, by Cartage, tracks each load with the best source available, gets the new ETA and reason from the carrier when a load runs late, and tells the team and anyone else the company has set to be notified. Traditional logistics software gives teams information. Wilson executes the work required to move shipments forward.

Step	Trigger	What Wilson does	When a person steps in
1. Track	Load is in transit	Uses the carrier’s API, GPS or ELD data, or the carrier’s website by PRO number; emails or calls the carrier when none exist	Not required
2. Get the ETA	Load is running late	Contacts the carrier for the new ETA and the reason	Not required
3. Notify the team	New ETA confirmed	Tells the team in Slack or Microsoft Teams	Not required
4. Notify the customer	New ETA confirmed	Notifies the consignee by email or SMS and the shipper by email, as configured	If customer notifications are set to need approval
5. Escalate	The delay needs a decision	Escalates to the team with the history and options	Deciding rebooking, expediting or other next steps

Each company chooses who’s notified and how. The team, the carrier and the shipper can get booked, picked up, running late, delivered and POD filed updates; the consignee gets the same set except booked. Customers can also follow their shipments on a tracking link with the company’s branding. See branded shipment tracking for customers.

Approval rules apply to notifications like any other action. Wilson starts with assisted execution, and a company can require approval on customer notifications while it reviews the first messages, then loosen that as trust builds. When a delay needs a decision, such as a rebooking above a cost threshold, Wilson escalates instead of acting. Every message and change is recorded in the shipment’s change history.

Wilson isn’t a visibility platform. A visibility platform shows where a load is; Wilson acts on what it finds by contacting the carrier, updating the people who need to know and initiating rebooking when needed. For the category, see what an AI logistics agent is.

What should stay internal, and what should a demo show?

Keep decisions, carrier performance and cost impact internal, and send the customer only the ETA, the reason and what happens next. The customer needs to re-plan; the team needs to decide.

Rebooking, expediting or splitting a shipment are internal choices until one is made. Carrier performance belongs in the carrier scorecard; Wilson scores carriers on service and cost from the shipments it runs. Cost impact, such as an added accessorial (an extra charge beyond the linehaul rate, like redelivery or detention), belongs with the people who approve spend. For who owns the recovery plan, see delay alert to recovery plan owner.

What to ask a vendor to show in a demo

Mark a load as running late and show how the new ETA and reason are obtained from the carrier.
Show the actual customer message the consignee receives, by email and by SMS.
Change who’s notified for one customer and show the next update follow the new setting.
Show a second ETA change and the follow-up update it triggers.
Show the escalation when the delay needs a rebooking decision.

FAQs

How should I tell a customer about a delayed delivery? As soon as the new ETA is known, tell them what's late, the new ETA, the reason and what happens next. Wilson, by Cartage, gets that ETA and reason from the carrier and notifies the people the company has set, including the consignee.
Why aren't delay alerts enough? Alerts tell the team something is wrong. Someone still has to confirm the ETA with the carrier and send the customer an update.
What if I don't have a new ETA yet? Tell the customer the load is delayed, that you're getting a new ETA and when they'll hear next.
How does Wilson get the new ETA? From the best source available: the carrier's API, GPS or ELD data or the carrier's website by PRO number. When none exist, it emails or calls the carrier.
Which updates does the consignee get from Wilson? Picked up, running late, delivered and POD filed, by email or SMS. Each company chooses who's notified and how.
Can customers track their own shipments? Yes. Customers can follow their shipments on a tracking link with the company's branding.
Can I review customer messages before they go out? Yes. A company can set customer notifications to need approval.
How is Wilson priced? There's no subscription fee. Pricing is a percentage of the carrier payments that run through Wilson, and that fee covers the full lifecycle from create to pay.

Conclusion

An alert that only reaches the logistics inbox doesn't help the customer waiting at the dock. A delay needs a new ETA, a reason and an update sent before the customer asks, plus another if the ETA changes again. The information usually exists hours before the customer hears it; the gap is the work of getting it and sending it.

Wilson, by Cartage, gets the new ETA and reason from the carrier and notifies the team and customers the way the company configures, while decisions stay with the team. Bring one late load from last week and watch Wilson send the update to your customer in a demo at cartage.ai.

Sources

BCI Global, "No visibility, no resilient supply chain," March 2025: https://www.bciglobal.com/bci-global-report-no-visibility-no-resilient-supply-chain
Cartage, Wilson product FAQ, October 2026: https://cartage.ai