Visibility software found the problem. Who resolves the freight exception?
Key Takeaways
Once visibility software finds a freight exception, a named owner must resolve it: routine fixes should be handled under written rules, often by an AI logistics coordinator, and judgment calls should go to named people with authority. The key is deciding ownership before the exception happens, so the alert turns into action instead of waiting in an inbox.
- A freight exception is any event that breaks the shipment plan, such as a missed pickup, a delay, a cancellation, a short delivery, or a missing document.
- Detection and resolution are different jobs. Many visibility tools are strong at detection. Resolution needs someone to act.
- Most exceptions follow a pattern and can be resolved under rules: contact the carrier, rebook from approved carriers, update the receiver.
- Some exceptions need judgment: paying a large premium, approving a new carrier, or handling a major customer impact.
- A simple responsibility table names the owner of each exception type and each decision.
- Wilson, by Cartage, is an AI logistics coordinator that resolves routine exceptions within the customer's rules and sends out-of-rule decisions to the logistics team.
Why does an exception go unresolved after it is found?
An exception goes unresolved after it is found because detection does not assign ownership. An AI logistics coordinator, or a named person, must own the next step, or the alert sits until someone happens to act.
A visibility platform flags a late truck at 2 p.m. The alert reaches a shared inbox. The logistics coordinator thinks customer service will call the customer. Customer service thinks logistics is handling the carrier. The plant thinks someone will warn them. By 5 p.m., the truck is still late and nobody has done anything. The problem was found. It was not resolved.
The table below separates the jobs in an exception.
| Job | What it means | Typical owner |
|---|---|---|
| Detect | Notice the plan is broken | Visibility software, carrier feed, AI logistics coordinator |
| Confirm | Get verified facts from the carrier | AI logistics coordinator or coordinator |
| Decide | Choose the response within or outside rules | Rules for routine cases; named person for others |
| Act | Rebook, reschedule, request documents | AI logistics coordinator or coordinator |
| Inform | Tell internal teams and customers | AI logistics coordinator, account owner for major issues |
| Record | Save what happened and why | AI logistics coordinator |
An alert is a question, not an answer
Every alert asks a question: what happened, and what should we do? Visibility software asks the question. Someone must answer it. If nobody owns the answer, the question sits. An AI logistics coordinator that owns the routine answers lets people focus on the questions that need their judgment.
Detection is the easy part
Detection has improved a lot. Many tools can show when a truck is late or a scan is missing. The harder part is what happens next. Each exception needs several messages, a decision, and often a booking. If the tool stops at the alert, people do the rest. An AI logistics employee can take on much of that work.
Exceptions cross team lines
Many exceptions touch several teams. A late inbound truck affects logistics, production, and purchasing. A short delivery affects logistics, customer service, and finance. Without a clear owner, each team handles its own piece and nobody handles the whole. An AI logistics coordinator can own the freight side end to end and bring each team in at the point where it must act.
Why shared inboxes fail
A shared inbox has many readers and no owner. Each reader assumes another will act. Alerts age. Customers call before anyone has a plan. Assigning each exception type to a named owner, or to an AI logistics coordinator under rules, fixes the gap.
Resolution is a different skill from detection
Detection needs good data. Resolution needs relationships, rules, and judgment. Contacting a dispatcher, negotiating a replacement rate, and choosing what to tell a customer are coordination tasks. An AI logistics coordinator is built for coordination: it reaches carriers through their channels, applies the shipper's rules, and records each step. That is a different job from watching data feeds.
The cost of unowned exceptions
Unowned exceptions cost money and trust. A missed pickup that waits four hours may lose the day's last available truck. A delay nobody reports becomes a surprise for the customer. A missing POD delays billing. A POD, or proof of delivery, is the signed record that the receiver took the freight. Each cost grows with time.
Who should own each type of freight exception?
Each exception type should have a primary owner, a backup, and a clear line between what the owner can resolve under rules and what needs a manager. An AI logistics coordinator can own the routine path for most exception types.
Start from the exceptions you have
Build the table from your real exceptions. Look at the last month: which exceptions happened most, which took longest, and which caused customer complaints. Give each one an owner and a routine response. An AI logistics coordinator can then apply the table to the same exceptions next month.
A responsibility table
| Exception | Routine resolution | Who handles routine | Who decides outside rules |
|---|---|---|---|
| Stale ETA | Get a verified update from the carrier | AI logistics coordinator | Logistics manager if carrier unreachable |
| Missed pickup | Reschedule or rebook from approved list | AI logistics coordinator | Logistics manager for above-limit rates |
| Cancellation after acceptance | Rebook from approved list | AI logistics coordinator | Logistics manager for new carriers |
| Delivery delay | Confirm new time, update receiver | AI logistics coordinator | Account owner for key customers |
| Missing POD | Request from carrier, then receiver | AI logistics coordinator | Logistics manager after set days |
| Short or damaged delivery | Record on POD, notify | AI logistics coordinator | Claims owner and account owner |
| Invoice mismatch | Hold for review | AI logistics coordinator | Finance approver |
These are examples. Each company should fill in its own owners.
Most exceptions are routine
In many freight operations, most exceptions follow a few patterns: late updates, missed pickups, small delays, and missing paperwork. These patterns have known answers. Writing those answers into rules lets an AI logistics employee resolve them quickly and frees people for the rarer cases that need judgment. The more exceptions that fit a rule, the more time the team saves.
Routine versus judgment
A routine exception has a known response under written rules. A missed pickup with an approved backup carrier at an acceptable rate is routine. A judgment exception needs a person to weigh trade-offs. A missed pickup where the only option costs double, or where the customer may cancel the order, needs judgment. The AI logistics employee should handle the first and route the second.
Write limits in numbers
Rules work best with numbers. "Rebook within 10 percent of the original rate" is clear. "Rebook at a reasonable rate" is not. "Escalate if the carrier does not answer within two hours" is clear. "Escalate if the carrier is slow" is not. An AI logistics employee can only follow rules it can measure, so write limits in hours, dollars, and percentages.
Review the table each quarter
Ownership changes as people change roles and the business grows. Review the responsibility table each quarter. Look for exception types that waited too long, owners who received decisions they could not make, and new exception types that need a row. The AI logistics coordinator can show how long each type took and who acted.
Backups for every owner
Owners take time off and attend meetings. Every owner needs a backup. The AI logistics coordinator should route to the backup when the primary does not respond in time.
Owners need authority, not just responsibility
An owner who must ask permission for every step cannot resolve anything quickly. Give each owner clear authority within limits: a logistics manager can approve rebooking up to a set amount; an account owner can promise a new date to a customer. An AI logistics coordinator should route each decision to someone who can actually make it.
Hypothetical example: ownership changes the outcome
This example is hypothetical and does not describe a real customer. A distributor's visibility tool flags a missed LTL pickup at 6 p.m. Under the old process, the alert went to a shared inbox and was seen at 9 a.m. the next day. Under the new process, the AI logistics coordinator owns missed pickups. It contacts the carrier at 6:05 p.m., learns the driver skipped the stop, and books a first-thing pickup that keeps the delivery date. The logistics manager sees a summary in the morning. No decision was needed.
How should an exception move from detection to resolution?
An exception should move through a fixed set of steps: confirm, decide, act, inform, and record. An AI logistics coordinator should start the steps as soon as the exception is detected and pause only where a person must decide.
A practical resolution workflow
Confirm the facts. Ask the carrier what happened and get a verified status.
Classify the exception. Match it to a type in the responsibility table.
Check the rules. Is there a routine response within limits?
Act or route. Act if routine; send options to the owner if not.
Inform. Tell the internal team and, where configured, the customer.
Confirm the fix. Check that the action worked, such as the new carrier picking up.
Record. Save the facts, decision, action, and result.
Speed matters most early
The first hour after detection is often the most valuable. Carrier capacity, dock slots, and customer patience are all easier to find early. An AI logistics employee that starts confirmation within minutes of detection gives the owner more options than one that starts the next morning. Set expectations for how fast each step should start.
Classify quickly
Matching an exception to its type should take seconds. Is it a missed pickup, a delay, or a missing document? The type decides the owner and the rule. An AI logistics coordinator should classify each exception on detection.
Confirm before acting
A detection alert can be wrong. A late scan may make a delivered load look overdue. A location gap may make a moving truck look stopped. The AI logistics employee should confirm with the carrier before rebooking or telling a customer. Acting on a false alarm wastes money and trust.
Inform in the right order
Tell the internal team first, then the customer when the plan is clear. A customer who hears about a problem before the shipper's own team knows the plan will ask questions nobody can answer. An AI logistics employee should send internal updates as soon as the facts are confirmed, and customer updates once the new plan or time is set.
Decide within rules
Rules make routine decisions fast. A rule might say: rebook a missed pickup with the next approved carrier if the rate is within 10 percent of the original. The AI logistics coordinator applies the rule and books. Outside the rule, it sends the owner the facts and options.
Tell people what was done, not only what happened
When an exception is resolved under rules, the team still wants to know. A short summary such as "Missed pickup on load 5512; rebooked with Carrier B at original rate; pickup tomorrow 8 a.m.; delivery date unchanged" keeps people informed without asking them to act. An AI logistics coordinator can send these summaries in a daily digest or as single messages, depending on the team's preference.
Close the loop
An exception is resolved only when the fix works. A rebooked load is not resolved until the new carrier picks up. A requested POD is not resolved until it arrives and is checked. The AI logistics coordinator should keep the exception open until the evidence shows it is closed.
Hypothetical example: a judgment call
This example is hypothetical and does not describe a real customer. A medical supplies distributor's truckload is delayed by a breakdown, and the delivery will miss a hospital's Monday deadline. The only approved carrier that can recover the time quotes double the original rate. The AI logistics coordinator confirms the facts and sends the account manager two options: pay double to deliver Monday, or deliver Tuesday at no extra cost. The account manager calls the hospital, which says Tuesday is not acceptable for critical items. The manager approves the premium. The coordinator books the replacement and records the decision.
Common mistakes in resolution
- Acting on unconfirmed alerts. False alarms cause wasted rebookings.
- Closing on action, not result. The new carrier also fails, and nobody notices.
- Telling the customer before the plan is set. The customer hears two different stories.
- Not recording the cause. The same exception repeats.
How do visibility tools and execution fit together?
Visibility tools and execution fit together when detection feeds directly into a resolution process with clear owners. An AI logistics coordinator can sit between them, taking detection signals and doing the execution work within rules.
Visibility data improves resolution
Good visibility data makes resolution faster. A verified location tells the coordinator whether a delay is real. A terminal event shows where freight is stuck. An AI logistics employee can use visibility data as one source when it confirms facts, alongside carrier replies and calls.
Different tools, different strengths
Some teams use a separate visibility platform for detection and another system or team for execution. Others use a single system that both tracks and executes. Either can work. The important question is whether the handoff from detection to action is owned. Many visibility platforms describe workflow and alerting features; buyers should test whether those features actually complete the follow-up for their own carriers and rules.
Ask whether the visibility tool resolves or only reports
When reviewing a visibility platform, ask which exceptions it resolves end to end and which it only reports. Some platforms offer workflow features, while others focus on data. The answer depends on the vendor and your setup. Testing a few of your real exceptions is the fairest way to find out. An AI logistics coordinator can fill the gap where follow-up is still manual.
Where execution software adds value
Execution software adds value where people currently spend time: contacting carriers, rebooking, rescheduling, and informing. Freight execution software is software that books, tracks, and coordinates the movement of freight. An AI logistics employee that handles these steps under rules reduces the work that starts after an alert.
Share context between systems
When detection and execution happen in different tools, context can be lost. The visibility tool knows the container's last event. The execution side knows the drayage booking and the warehouse appointment. Passing the detection event into the execution record, with its time and source, keeps one story per load. An AI logistics employee can attach the detection event to the shipment record when the data flow allows it.
Avoid duplicate alerts
If both a visibility tool and an execution tool send alerts for the same event, people receive two messages and may act twice. Decide which system sends which alert. Often the execution side should send alerts to people, because it knows what has already been done.
Keep one record per load
Whatever tools detect the problem, the load should have one record that shows the exception, the decision, and the result. Separate records in separate tools make audits and reviews harder. An AI logistics coordinator can keep that single record, with links to the detection source where useful.
Hypothetical example: two tools, one owner
This example is hypothetical and does not describe a real customer. A manufacturer uses a visibility platform for ocean containers and an AI logistics coordinator for domestic freight. The visibility platform flags a vessel delay. The coordinator reads the new arrival date, adjusts the drayage appointment, and updates the warehouse. The team receives one message from the coordinator with the new plan, not two separate alerts.
How should you evaluate who resolves exceptions in your freight software?
Evaluate exception resolution by triggering common exceptions and checking who acts, how fast, and whether the exception closes with evidence. An AI logistics coordinator should resolve routine exceptions under rules and route judgment calls to named owners.
Demo tests for exception ownership
| Buyer requirement | Demo test | Evidence to see |
|---|---|---|
| Ownership table | Configure owners for five exception types | Each exception routed to its owner |
| Routine resolution | Trigger a missed pickup within rules | Rebooked without a person |
| Judgment routing | Make rebooking exceed limits | Owner receives facts and options |
| Confirmation first | Trigger a false late alert | Carrier confirms; no wasted action |
| Close with evidence | Rebook a load | Exception closes only after pickup |
| Backup routing | Leave the owner silent | Backup receives the decision |
| Record | Review the exception | Facts, decision, action, result saved |
Bring your coordinators
Ask the people who handle exceptions today to watch the test. They know which exceptions eat their day. They will notice if the AI logistics coordinator leaves the hard part to them.
Demo questions about exception ownership
- How is the responsibility table configured, and who can change it?
- Which exceptions can the AI logistics coordinator resolve under rules?
- How does it confirm facts before acting?
- How does it decide an exception is closed?
- How does it work alongside an existing visibility platform?
- Can the team see open exceptions by owner and age?
Ask for the open-exception list
Ask the vendor to show a list of open exceptions sorted by age and owner. This list is the daily tool a logistics manager needs. If it does not exist, exceptions will be managed from inboxes. An AI logistics coordinator should maintain this list as exceptions open and close.
How to measure exception ownership work
Track the time from detection to resolution by exception type. Count exceptions resolved without a person. Measure how many exceptions stayed open longer than a set time. These measures show whether the AI logistics employee turns detection into resolution.
Include a cross-team exception
Include at least one exception that needs another team, such as a short delivery that needs customer service and finance. Watch whether the AI logistics coordinator brings in the right people at the right step, rather than sending everyone the same alert.
Scoring the exception ownership demo
Score each test as pass, partial, or fail. A pass means the exception reached the right owner, was resolved under the rules, and closed with evidence. A partial means it was resolved but a person did the routine work. A fail means the exception stayed in an inbox.
Warning signs in an exception ownership demo
- Alerts go to a shared inbox with no owner.
- Every exception needs a person.
- Exceptions close when an action is taken, not when it works.
- The system acts on alerts without confirming.
- Open exceptions cannot be listed by owner.
Where does Wilson fit in resolving freight exceptions?
Wilson, by Cartage, is an AI logistics coordinator that resolves routine freight exceptions within the customer's rules and sends out-of-rule decisions to the logistics team. Traditional logistics software gives teams information. Wilson executes the work required to move shipments forward.
Wilson replaces the TMS for freight execution and connects to the company's ERP through a method that fits the customer's environment. It is not a standalone visibility platform; it tracks each load as part of executing it, using the best source available for each load.
What Wilson does after an exception
When Wilson detects a missed pickup, a cancellation, or a delay, it contacts the carrier, notifies the internal team, notifies the customer where configured, and initiates rebooking from the approved carrier list within the customer's rules or with approval. Wilson starts with assisted execution, and approval limits are set by the customer. Routine actions can run automatically within those rules as reliability is proven.
What Cartage asks about exception ownership in discovery
Cartage asks which exceptions take the most time, who owns them today, and where decisions get stuck. Typical questions also cover existing visibility tools and how alerts flow. These answers shape the responsibility table an AI logistics coordinator follows.
What Wilson does not do for exception ownership
Wilson does not decide who owns each exception type; the customer does. It does not make large judgment calls outside the customer's rules. Specific routing and approval rules should be confirmed in a demo. Exact ERP connection details depend on the customer's systems.
Learn from resolved exceptions
Each resolved exception teaches something. A carrier that often misses pickups on one lane may need a review. A receiver that often refuses partial loads may need a different shipping rule. Wilson can use shipment data from the loads it runs to produce carrier-performance and lane-rate reports on request. Teams can use those reports to reduce the exceptions that keep coming back.
Where teams start with exception ownership
Most teams start their AI logistics coordinator on a few lanes and expand from there. Timing depends on scope. Cartage helps identify the first workflow during discovery. Teams often start with the exception type that sits longest in their inbox.
Teams assigning owners can use a freight exception responsibility matrix. Teams setting approvals can read about who approves when a shipment goes wrong. Both topics shape how an AI logistics coordinator routes exceptions. Teams turning alerts into plans can review how to move from a delay alert to a recovery plan owner.
FAQs
Visibility software found the problem. Who resolves the freight exception?
A named owner for that exception type. Routine exceptions can be resolved under rules by an AI logistics coordinator; judgment calls go to named people with authority.
Which freight exceptions can be resolved under rules?
Stale ETAs, missed pickups with approved backups, cancellations with in-limit rebooking, missing PODs, and routine delays. An AI logistics employee can handle these within your limits.
Which exceptions need a person?
Above-limit costs, new carriers, major customer impacts, and claims. An AI logistics coordinator should send the owner the facts and options.
When is a freight exception resolved?
When the fix has worked, such as the new carrier picking up or the POD arriving. An AI logistics employee should close the exception only with evidence.
Sources
- Cartage, Wilson product scope, October 2026: https://cartage.ai
Ask Cartage to show how an AI logistics coordinator takes a missed-pickup alert, confirms it with the carrier, rebooks within your rules, and routes an above-limit decision to your manager: talk to the Cartage team.