An alert is not a resolution: what happens after a shipment exception is detected
Key Takeaways
- Shipment visibility tells a logistics team that something went wrong. Exception execution is the work required to fix it: contacting the carrier, updating internal teams and customers, and moving the load to another carrier when needed.
- Detecting a delay and resolving it are separate problems. Many teams already detect exceptions and still resolve them by hand, one call and email at a time.
- A complete exception response usually has five steps: detect, confirm with the carrier, notify internal teams, notify the customer, and rebook or escalate.
- Wilson, by Cartage, is an AI logistics agent that executes those steps for manufacturers and distributors. It initiates rebooking only from the company's approved carrier list, with or without approval depending on the company's rules.
What is the difference between shipment visibility and exception execution?
At 10:15 on a Tuesday morning, a building-materials distributor learns that a truckload headed to a key customer is running six hours behind. The alert is clear and it arrived on time. Now the work starts. The logistics coordinator emails the carrier for a new ETA and waits for a reply. Then the coordinator messages the sales rep, calls the customer’s receiving team to move the delivery window, and checks whether another approved carrier could cover tomorrow’s load on the same lane. By the time the plan is settled, two more alerts have come in.
The alert did its job. The problem is everything that has to happen after it.
Shipment visibility is the ability to see where a shipment is and whether it’s on schedule. Exception execution is the work of acting on a problem once it’s detected, so that the shipment and everyone depending on it stay on track.
Both matter, and they solve different parts of the problem:
| Stage | Question it answers | Typical work involved |
|---|---|---|
| Detect | “Is something wrong?” | Tracking updates, ETA changes, missed milestones |
| Confirm | “What exactly happened and what’s the new plan?” | Contacting the carrier for status and a revised time |
| Communicate | “Who needs to know?” | Updating internal teams, the shipper and the consignee |
| Resolve | “How does the freight still get there?” | Rebooking with an approved carrier or escalating to a person |
Visibility tools are built mainly for the first row. The remaining rows are coordination work, and in many logistics teams that work still happens manually.
Visibility platforms and AI logistics agents solve different problems. They address different stages of exception management, and the right fit depends on whether the main gap is seeing problems or acting on them.
| Category | Best for | Primary capability | Workflow coverage | Deployment approach |
|---|---|---|---|---|
| Visibility platforms | Networks that need broad, deep multimodal tracking | Tracking, ETA prediction and alerting | Mainly detection | Depends on deployment |
| TMS exception modules | Teams that run transportation planning in a TMS | Exception records and workflows inside the TMS | Depends on configuration | Part of a TMS implementation |
| AI logistics agents, such as Wilson, by Cartage | Teams whose bottleneck is the manual work after an alert | Executes carrier contact, notifications and rebooking from the approved carrier list | Detection through resolution, as part of the full shipment lifecycle from create to pay | Replaces the TMS and connects to the ERP; also works from a spreadsheet, email or file drop |
Buyers whose main need is deep multimodal tracking across a large network should evaluate tools designed for that use case. Teams whose logistics coordinators spend a large share of their day on carrier follow-ups, status updates and rebooking are usually facing an execution gap, and that is the gap an AI logistics agent is designed to close.
Why alerts alone often don't prevent delays
Alerts often don't prevent delays because the response still depends on a person having time to act, and exceptions tend to arrive when the team is already busy.
Each alert creates a small project: find the carrier contact, send the message, wait for a reply, decide what to do, and tell everyone affected. When a team handles a few exceptions a week, that's manageable. When it handles several a day on top of quoting, booking and routine follow-ups, response times stretch. An alert that arrives at 10 a.m. may not get a full response until mid-afternoon.
For manufacturers and distributors, the cost of that gap goes past the shipment itself. A late inbound load can hold up a production schedule. A late outbound load can miss a customer's receiving window, which leads to rescheduling fees, unhappy buyers or a lost delivery slot. When customers aren't told in time, the logistics team ends up answering status calls instead of fixing the problem.
This is also why more alerts don't automatically mean better outcomes. A team that gets faster, more detailed notifications but has the same capacity to respond may simply end up with a longer queue of exceptions to work through.
What a complete exception response looks like
A complete exception response covers five steps. The value of automation comes from executing all of them consistently, not just the first one.
Detect. A missed pickup, a cancellation or a delay is identified from carrier updates.
Confirm with the carrier. Someone asks the carrier what happened and gets a revised time or confirms the load can’t move.
Notify internal teams. Sales, customer service, production or warehouse teams learn about the change.
Notify the customer. The consignee or customer hears about the new plan before they have to ask.
Rebook or escalate. If the original carrier can’t recover the load, it moves to another approved carrier or goes to a person for a decision.
| Step | Manual process | With an AI logistics agent |
|---|---|---|
| Detect | Coordinator notices an alert or a missed update | Ongoing monitoring flags the exception |
| Confirm | Emails and calls to the carrier, then waiting | The agent contacts the carrier and follows up until it gets an answer |
| Notify internal | Messages sent one by one | Configured updates go out through Slack, Microsoft Teams or email |
| Notify customer | Often delayed until the plan is clear | Configured updates go out by email or SMS |
| Rebook or escalate | Coordinator calls backup carriers | The agent initiates rebooking from the approved carrier list, or escalates |
Which exceptions to automate first. The best exceptions to automate first are the ones that happen often, have a clear expected response, and cause real damage when the response is slow. Three exception types usually meet those criteria:
| Exception | Why it matters | Typical configured response | Good first fit |
|---|---|---|---|
| Missed pickup | Freight sits at the dock and downstream appointments are at risk | Contact the carrier, confirm a new pickup time, notify internal teams, and initiate rebooking if needed | Strong |
| Carrier cancellation | The load has no truck | Notify internal teams and initiate rebooking from the approved carrier list | Strong, with approval rules |
| In-transit delay | The delivery window is at risk | Get a revised ETA and the reason from the carrier and update the internal team and consignee | Strong. Low risk |
Exceptions that need judgment, such as damaged freight, claims or disputes with a carrier, are better left with the logistics team, with the agent handling the notifications around them. Teams can map which exception workflow has the highest impact in their current setup on their own or with the Cartage team.
How Wilson, by Cartage, handles shipment exceptions
Wilson, by Cartage, is an AI logistics agent that detects shipment exceptions and executes the configured response: it contacts the carrier, notifies internal teams, notifies the customer when configured, and initiates rebooking from the company's approved carrier list. Traditional logistics software gives teams information. Wilson executes the work required to move shipments forward.
Exception handling is one part of how Wilson coordinates freight. Wilson covers the full shipment lifecycle in six stages (create, quote, tender, track, audit and pay), which means that when something goes wrong, it already has the shipment context, the carrier and the stakeholders it needs.
How Wilson monitors shipments. Wilson uses the best source available for each load: the carrier's API, GPS or ELD data from the truck, or the carrier's website by PRO number. When none of those exist, Wilson emails or calls the carrier, and it follows up when a reply doesn't come. If a load is running late, Wilson gets the new ETA and the reason for the delay. Customers can follow their shipments on a tracking link with the company's branding.
How Wilson communicates. When a load is running late, Wilson asks the carrier for status and informs everyone else:
- The company's own team gets updates through Slack or Microsoft Teams.
- The shipper gets updates by email.
- The consignee gets updates by email or SMS.
The same communication applies at pickup, delivery and POD filing, and the company's team and the shipper also hear at booking. Each company chooses who's notified and how.
How Wilson rebooks. When the original carrier can't recover a load, Wilson initiates rebooking from the company's approved carrier list. Depending on the company's rules, the rebooking either proceeds without manual approval or waits for a person to approve it. Wilson only books carriers the company has approved. Cartage can introduce carriers from its network, and they're available to Wilson only after the company approves them. If no approved carrier accepts, Wilson escalates to the team.
What Wilson is and isn't. Wilson is not a visibility platform: a visibility platform shows where a load is, while Wilson acts on what it finds. Wilson replaces the TMS: it is the system of record for shipments and the execution layer that does the work, and teams can use its dashboard the way they would use a traditional TMS. It connects to the company's ERP, not to another TMS, and also takes orders from a spreadsheet, email or a scheduled file drop. Wilson is not a freight broker; carrier relationships and rates stay with the company.
Approval rules for exception response. With Wilson, human approval isn't hardcoded. Each company decides which exception steps run without a person and which wait for approval. A common starting setup for exceptions:
- Runs within the rules: contacting the carrier, requesting a revised ETA, internal notifications and routine consignee updates.
- Requires approval: rebooking that adds cost above a set threshold, changes for high-priority customers, and delays beyond a defined window.
- Stays with a person: claims, damaged freight, carrier disputes and anything the rules don't cover.
Wilson starts with assisted execution, and the scope of execution is expanded step by step as the company gains confidence in the workflow, so companies can begin with more steps approval-gated and relax them as results hold. Every message, confirmation and change on each shipment is recorded in a change history.
How to measure exception response on a few lanes
Exception response should be measured by how quickly and consistently each step happens after detection, compared with how the same lanes ran before.
Most customers start Wilson on a few lanes and expand from there. Impact is measured by comparing the lanes Wilson runs with how those lanes ran before. Useful metrics:
- Time from detection to carrier contact.
- Time from detection to customer notification.
- Exceptions resolved before a missed appointment, compared with those discovered after the fact.
- Coordinator hours reclaimed from follow-ups and status updates.
These metrics measure the response itself, which is where most of the delay usually is. A count of alerts received says nothing about that.
FAQs
- What is the difference between shipment visibility and exception management? Visibility shows where a shipment is and flags when something goes wrong. Exception management is the work of responding: contacting the carrier, updating stakeholders and rebooking when needed.
- Can AI respond to shipment exceptions automatically? Yes, within rules the company sets. Wilson, by Cartage, contacts the carrier, notifies internal teams and customers when configured, and initiates rebooking from the approved carrier list, with or without approval depending on the company's rules.
- Does Wilson replace a visibility platform? Not necessarily. Wilson is not a visibility platform: it monitors loads as part of executing them and acts on what it finds, while dedicated visibility platforms focus on deep multimodal tracking. Companies whose main need is that kind of tracking should evaluate tools built for it.
- How does Wilson track shipments? Wilson uses the best source available for each load: the carrier's API, GPS or ELD data from the truck, or the carrier's website by PRO number. When none of those exist, it emails or calls the carrier. Late loads get a new ETA and a reason.
- Will Wilson book a carrier the company hasn't approved? No. Wilson only books carriers the company has approved. Cartage can introduce carriers from its network, and they're available to Wilson only after the company approves them.
- Does Wilson require a TMS? No. Wilson replaces the TMS: it is the system of record for shipments and the execution layer. It connects to the company's ERP, not to another TMS, and also works from spreadsheets, email or a scheduled file drop.
- 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: create, quote, tender, track, audit and pay. Pricing scales down as volume grows, and Enterprise pricing is custom.
Conclusion
Most logistics teams don't lack alerts. What they often lack is the capacity to act on every alert quickly and consistently. For manufacturers and distributors whose coordinators spend hours after each exception on carrier calls, status updates and rebooking, Wilson, by Cartage, closes that gap by executing the response within the rules and approvals the company sets. The practical first step is to choose the exception that costs the most when the response is slow, usually missed pickups or carrier cancellations, start Wilson on a few lanes and compare them with how those lanes ran before. Teams can set Wilson up themselves or with the Cartage team.
Sources
- Cartage, Wilson product FAQ, October 2026: https://cartage.ai