Who owns the work between a delay alert and a recovery plan?

Key Takeaways

A delay alert says something is wrong; a recovery plan says what happens next. In many teams, the work between the two has no named owner, so it waits.
Five tasks sit in that gap: contact the carrier, get the new ETA and the reason, notify the team, notify the customer, and decide the recovery.
Four of the five are routine and can follow rules. Only the recovery decision needs judgment, and only when it changes cost, dates or a customer commitment beyond the rules.
Wilson, by Cartage, is an AI logistics agent that contacts the carrier, gets the new ETA and reason, notifies the team and customers as configured, and initiates rebooking from approved carriers when a pickup is missed.
Decisions that exceed the company's rules go to a person, and every step is recorded in the shipment's change history.

Why does the work after a delay alert go unowned?

The work after a delay alert goes unowned because alerts go to many people and none of them is assigned to act. Everyone sees the problem; each assumes someone else is calling the carrier. The fix is a default owner for every routine task and a named approver for the decision.

This affects manufacturers and distributors whose shipments feed production lines or customer orders, and whose alerts land in shared inboxes or chat channels. Visibility alone doesn't settle it: in a March 2025 survey of 240 supply chain leaders, BCI Global found only 35% reported end-to-end visibility. And even where an alert arrives on time, it doesn't call anyone.

One load, step by step

Wednesday 11:20 a.m. A tracking alert says an FTL load of resin bound for a customer's plant has stopped moving 300 miles out. It goes to a shared logistics inbox.
11:25 a.m. Three coordinators see it. One is on a call, one assumes the shipment owner has it, and one is booking loads for Thursday.
1:40 p.m. Customer service gets a call from the customer's receiving manager asking where the truck is. It has nothing to say.
1:55 p.m. A coordinator finally reaches the carrier dispatcher: the truck had a breakdown and needs four hours. The new ETA is after the plant's receiving cutoff.
2:30 p.m. The logistics manager has to decide between an after-hours delivery fee and a Thursday morning appointment, with the customer already frustrated.

The silence after the alert cost more than two hours.

What work sits between a delay alert and a recovery plan?

Five tasks: contact the carrier, get the new ETA and reason, notify the team, notify the customer, and decide the recovery. The first four are the same on almost every delay. The fifth depends on what the carrier says.

The order matters. Nobody can update the customer well without a new ETA, and nobody can decide the recovery without knowing why the load is late. Tracking sources help but don’t replace the conversation: a GPS ping shows a stopped truck, not whether the driver will be moving in 20 minutes or four hours.

The tasks also depend on where the load is. Before pickup, the most common problem is a missed pickup, meaning the carrier didn’t arrive in the confirmed window or cancelled, and recovery usually means rebooking another carrier. In transit, the load is already on a truck, so recovery means changing the delivery appointment, telling the receiver, or paying for a faster option. For why an alert alone isn’t enough, see a delay alert is not a resolution plan.

Who should own each task, and when does a manager step in?

Each routine task should have a default owner who acts without being asked; the recovery decision should go to a named person only when it exceeds the rules. Ownership written down beats ownership assumed.

Task	Default owner	Can follow rules?	When approval is needed
Contact the carrier	Whoever runs the shipment	Yes	Never
Get new ETA and reason	Whoever runs the shipment	Yes	Never
Notify the team	Whoever runs the shipment	Yes	Never
Notify the customer	Whoever runs the shipment, under notification rules	Yes, if configured	If the company requires sign-off on customer notifications
Rebook within the rules	Whoever runs the shipment	Yes	If above the cost threshold
Expedite, change delivery, or anything off-rule	Logistics lead or account owner	No	Always

The consequence of leaving this unwritten is the Wednesday above: three people aware, nobody acting. The consequence of sending every delay to the manager is the opposite problem: decisions wait in one person’s queue, including ones that never needed them. For who should hold the decision when a shipment goes wrong, see who approves the next move when a shipment goes wrong?

Common mistakes

Routing alerts to a shared inbox with no owner. Everyone sees it and the carrier still isn’t called.
Telling the customer before getting the reason. The first update is vague, so a second, contradictory one follows.
Escalating every delay to the manager. Routine rebookings wait behind real decisions.
Recording the outcome but not the steps. When the customer asks what happened, nobody can show when the carrier was called or what it said.

How does Wilson, by Cartage, own the work after a delay alert?

Wilson does the routine tasks on every delay, in order, and escalates the decisions that exceed the company’s rules. 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. Detect	Load running late, from carrier API, GPS or ELD data, the carrier’s website or a carrier message	Starts the carrier follow-up on the shipment	Not required
2. Contact	Delay detected	Contacts the carrier by email or phone, and calls if there’s no reply	Not required
3. ETA and reason	Carrier responds	Records the new ETA and the reason on the shipment	If the carrier can’t confirm
4. Notify	ETA confirmed	Tells the team in Slack or Microsoft Teams, and the shipper and consignee as configured	If the company put customer notifications under approval
5. Missed pickup	Carrier cancels or misses pickup	Contacts the carrier, notifies the team, notifies the customer if configured, initiates rebooking from approved carriers	If the rebooking needs approval
6. Escalate	Decision exceeds the rules	Escalates to the team with the shipment’s full record	Deciding the recovery

The team decides who’s notified, about what and how: the consignee, for example, gets picked up, running late, delivered and POD filed updates by email or SMS. The POD, or proof of delivery, is the signed record that the load arrived; Wilson requests it after delivery and escalates if it’s still missing past the set window.

The controls are set by the company. Wilson starts with assisted execution, and the company decides which actions wait for approval; rebooking runs automatically or after approval, depending on those rules. Wilson only rebooks with carriers the company has approved. Every message, call transcript, confirmation and change is recorded in the change history, so the account owner can show the customer exactly when the carrier was reached. Wilson monitors loads as part of running them, but it isn’t a visibility platform, and it doesn’t decide commercial trade-offs such as paying for an expedite; those stay with the team.

How do teams know the gap is closed?

The gap is closed when every delay has a recorded carrier contact, an ETA with a reason, the right notifications and, when needed, a decision with a name on it. An alert with nothing after it means the gap is still open.

Measure it on a few lanes: time from exception to notification, missed pickups and coordinator hours, compared with how those lanes ran before. Watch time from alert to first carrier contact in particular, since that’s where the Wednesday example lost most of its hours. For the full exception flow, see freight exception management, and for the category, what is an AI logistics agent?

What to ask a vendor to show in a demo

Trigger a delay on a live load. Show what happens in the first 15 minutes without anyone touching it.
Show a carrier that doesn’t answer. When does the follow-up switch to a phone call, and where is the transcript?
Show the customer update. Who receives it, through which channel, and what does it say about the reason?
Show a missed pickup. Walk through the rebooking and where approval comes in.
Show an escalation. What does the manager see, and what has already been done?

FAQs

Who should act on a shipment delay alert? Whoever runs the shipment should contact the carrier, get the ETA and update people; decisions above the rules go to a named approver. Wilson, by Cartage, does the routine tasks and escalates the decisions.
What should happen after a delay alert? Contact the carrier, get the new ETA and reason, notify the team and customer, and decide the recovery, in that order.
How does Wilson track loads in transit? Wilson uses the best source available for each load: the carrier's API, GPS or ELD data, or the carrier's website by PRO number. When none of those exist, it emails or calls the carrier.
Does Wilson make check calls to carriers? Yes. Wilson calls carriers and drivers for check calls and ETA follow-ups, at the frequency set in the company's SOP, and saves call transcripts on the order.
What does Wilson do when a carrier cancels or misses a pickup? In this order: contacts the carrier, notifies the team, notifies the customer if configured and initiates rebooking from the approved carrier list.
Does Wilson rebook automatically? Rebooking runs automatically or waits for approval, depending on the company's rules.
How is Wilson priced? There's no subscription fee. Pricing is a percentage of the carrier payments that run through Wilson, and that one fee covers the full shipment lifecycle.

Conclusion

An alert without an owner is noise. The work between the alert and the recovery plan (calling the carrier, getting the ETA and reason, updating people and deciding) has to happen on every delay, and it happens faster when the routine part has a default owner and the decision has a named one.

Wilson, by Cartage, does the routine part on every delay and brings the decision to the person the company chose, with the record already built. Bring one delayed load your team chased last week and watch Wilson run the follow-up from alert to recovery 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