How to route urgent shipment alerts to the right manager
Key Takeaways
To route urgent shipment alerts to the right manager, write a routing table that matches each exception type, customer, and site to a named manager and a backup, then send each alert with the facts, the decision needed, and a deadline. An AI logistics coordinator should handle routine follow-up itself and route only the decisions that need a manager.
- An urgent alert is one that needs a decision soon to protect a delivery, a production line, a key customer, or a large cost.
- Most alerts do not need a manager. Routing every alert upward trains managers to ignore them.
- The right manager depends on the decision: rates go to whoever owns cost, carriers to whoever owns approvals, customers to whoever owns the account.
- Every route needs a backup for when the first manager is away.
- An alert should arrive with the facts and the options, so the manager can decide in one reading.
- Wilson, by Cartage, is an AI logistics coordinator that follows up on exceptions within the customer's rules and sends out-of-rule decisions to the logistics team through configured channels.
Why do urgent alerts reach the wrong person?
Urgent alerts reach the wrong person because most teams route by habit, not by decision. An AI logistics coordinator should route each alert to the person who owns the decision it requires, because a well-written alert in the wrong inbox still waits.
A common setup sends every alert to one shared inbox or one logistics manager. That manager becomes a bottleneck. Alerts about customer promises wait behind alerts about carrier rates. When the manager is in a meeting or on vacation, everything waits. Other teams send alerts to everyone, and nobody acts because everyone assumes someone else will.
The table below compares common routing approaches.
| Approach | What happens | Main problem |
|---|---|---|
| Everything to one shared inbox | Alerts pile up | Nobody owns the decision |
| Everything to one manager | Manager becomes the bottleneck | Delays when the manager is busy |
| Everything to everyone | Many people read, few act | Diffused responsibility |
| Routed by decision type with backups | The owner gets what they can decide | Requires a written routing table |
Where supply chain visibility software fits
Supply chain visibility software often creates the alerts in the first place. It sees a late truck, a stalled container, or a missed scan. Many visibility tools are good at detection. Routing is a separate step: deciding who must act and making sure they do. An AI logistics coordinator connects the two by taking the alert, doing the follow-up it is allowed to do, and routing only the remaining decision to a person.
Signs your routing is broken
Routing is broken when managers hear about problems from customers first. Other signs include a shared inbox with hundreds of unread alerts, the same question asked three times in a group chat, and decisions made after the deadline has passed. An AI logistics employee can show how long alerts waited before someone acted, which turns a feeling into a fact.
Alerts versus decisions
An alert says something happened. A decision says what to do about it. Many alerts do not need a decision from a manager, because the next step is already covered by the rules. A missed pickup with an approved backup carrier at an acceptable rate can be rebooked within rules. The manager only needs to know. An AI logistics employee should separate alerts that need a decision from alerts that are for information.
The cost of slow decisions
Slow decisions cost freight options. A replacement carrier available at 7 a.m. may be gone by 10 a.m. A receiver who could move an appointment today may be full tomorrow. A plant that hears about a late part early can change its schedule; one that hears late cannot. Routing the decision to the right person quickly protects those options.
Urgency depends on the load
The same exception can be urgent on one load and routine on another. A one-day delay on a restock to the company's own warehouse may need no decision. The same delay on a production-critical part or a retailer's strict appointment may need one within the hour. An AI logistics coordinator should read the load's priority from the order or the customer and set urgency to match.
Who counts as "the right manager"
The right manager is the person with authority over the decision and enough context to make it. For a rate above limits, that may be the logistics manager or finance. For a key customer delay, it may be the account manager. For a new carrier, it may be whoever owns carrier approval. The routing table should name these people by role and by name.
How do you build a routing table for urgent alerts?
Build a routing table by listing the decisions that need a manager, then matching each one to an owner, a backup, a channel, and a deadline. An AI logistics coordinator should apply the table to every alert it cannot resolve within the rules.
Example routing table
| Decision needed | Primary owner | Backup | Channel example | Deadline to decide |
|---|---|---|---|---|
| Rebook above rate limit | Logistics manager | Transportation lead | Direct message | Within 1 hour on same-day loads |
| Approve a new carrier | Carrier approval owner | Logistics manager | Direct message and email | Before tender |
| Tell a key customer about a major delay | Account manager | Customer service lead | Email and call | Within 2 hours of confirmation |
| Change a production schedule | Production scheduler | Plant manager | Team channel and call | Before the shift starts |
| Hold or release a disputed payment | Finance approver | Controller | Before the payment run | |
| Suspected theft or fraud | Security owner | Operations director | Phone | Immediately |
These owners and deadlines are examples, not a standard. Each company should fill in its own.
Route by site and customer too
Large teams need more than one route per decision. A plant in Ohio and a plant in Texas may have different schedulers. Key accounts may have their own account managers. The routing table can add columns for site and customer. An AI logistics employee can read the site and customer from the order and pick the right row.
Decision rights in writing
Write down what each owner can decide on their own and what needs a second approval. A logistics manager may approve rebooking up to a set amount; above that, finance must agree. A customer service lead may promise a new delivery date; a credit or discount may need the account manager. Clear decision rights stop alerts from bouncing between people. An AI logistics employee can route to the owner whose rights cover the decision.
Name a backup for every route
Every route needs a backup. Managers travel, take time off, and sit in long meetings. A rule might say: if the primary owner does not respond within half the deadline, send the alert to the backup. The AI logistics coordinator should record who received it and who decided.
Customer-facing decisions need the account owner
When an alert affects what a customer will hear, the account owner should decide or at least know first. A customer that hears about a major delay from an automated message before its account manager calls may feel neglected. The routing table can send major customer-impact alerts to the account owner before any external message goes out. An AI logistics coordinator can hold the external message until the account owner approves or the deadline passes.
Choose the channel by urgency
The channel should match the urgency. A decision needed within an hour should go to a channel the owner checks often, such as a direct message in Slack or Microsoft Teams. A decision needed by tomorrow can go by email. A suspected theft needs a phone call. Wilson sends internal updates through channels such as Slack, Microsoft Teams, or email, depending on the customer's setup.
After-hours routing
Urgent decisions do not stop at 5 p.m. Some loads move at night and on weekends. The routing table should name an on-call owner for after-hours decisions, or state which decisions can wait until morning. An AI logistics coordinator can apply that rule, handling routine follow-up overnight within the rules and waking the on-call owner only for decisions that cannot wait.
Keep the table short
A routing table with 50 rows will not be maintained. Start with the six to ten decisions that cause the most delay today. Add rows only when a new kind of decision keeps getting stuck.
What should an urgent alert include?
An urgent alert should include what happened, what has already been done, the decision needed, the options with their costs, and the deadline. An AI logistics coordinator should write every urgent alert in the same structure, so managers learn where to look.
The alert template
| Element | Example |
|---|---|
| What happened | Carrier canceled load 3390 at 6:10 a.m.; pickup was 10 a.m. |
| What was done | Two approved carriers declined; one quoted $1,620 |
| Rule that stopped action | Quote is 18 percent above the rebooking limit |
| Decision needed | Approve $1,620 or move pickup to tomorrow |
| Impact of each option | Approve: delivery holds. Move: delivery one day late, retailer fee possible |
| Deadline | Carrier holds the truck until 8:00 a.m. |
| Who else knows | Dock informed pickup may change |
Lead with the decision
Managers read alerts on phones between meetings. Put the decision and the deadline in the first line. For example: "Decision by 8:00 a.m.: approve $1,620 rebook for load 3390 or delay to tomorrow." Details follow. An AI logistics employee should keep the first line short enough to read in a notification.
State the cost of waiting
Some options disappear with time. Include what happens if the manager does not decide by the deadline. For example: "If no decision by 8 a.m., the carrier releases the truck, and the next option is tomorrow." The cost of waiting helps the manager prioritize this alert over others. An AI logistics coordinator should include it whenever an option expires.
Include what was already tried
A manager who does not know what was tried will ask, and that costs time. Listing the carriers contacted, the responses, and the rules applied lets the manager decide without a follow-up call.
Use plain words
Write alerts in plain words, without internal codes. "LTL load 3390 to Kroger Atlanta" is clearer than "Shp#3390/LTL/KR-ATL." Managers outside logistics, such as account managers or plant schedulers, may not know the codes. An AI logistics coordinator should write alerts that anyone on the routing table can understand without a glossary.
Make the reply easy
The manager should be able to reply with one word or one tap: "approve," "delay," or "call me." The AI logistics coordinator should then act on the reply within the rules and confirm what it did.
Hypothetical example: an alert with no decision
This example is hypothetical and does not describe a real customer. Before changing its process, a manufacturer's logistics manager received alerts like "Load 2215 delayed." Each one required opening the tracking system, calling the carrier, and working out the impact. A typical alert took 20 minutes before any decision was possible.
After the change, the AI logistics coordinator first confirms the delay with the carrier, checks the delivery window, and contacts the receiver. Only if a decision is needed does it send the manager an alert, with the facts and options already gathered. Most delays now arrive as information in a daily summary, and urgent ones take a few minutes to decide.
Hypothetical example: a two-minute decision
This example is hypothetical and does not describe a real customer. A distributor's carrier cancels a load at 6:10 a.m. The AI logistics coordinator tries the approved list and gets one quote above the rebooking limit. At 6:45 a.m., it sends the logistics manager a direct message with the template above. The manager reads it at 7:02 a.m. and replies "approve." The coordinator books the carrier at 7:05 a.m., tells the dock, and records the approval. The delivery holds.
How do you keep urgent alerts from becoming noise?
Keep urgent alerts from becoming noise by sending managers only the decisions they own, combining related alerts, and reviewing the routing table regularly. An AI logistics coordinator should handle routine follow-up within the rules and send the rest as information, not as urgent decisions.
Separate urgent, routine, and information
| Type | Example | Who receives it |
|---|---|---|
| Urgent decision | Rebook above limit with a deadline | Named owner and backup |
| Routine action within rules | Missed pickup rebooked with an approved carrier at target | Logistics team, as information |
| Information only | ETA moved 20 minutes within the window | Dashboard or daily summary |
Repeat alerts only with new facts
If the manager has not answered, a repeat alert should add something: the backup has been notified, the deadline is closer, or an option has expired. Sending the same message again only adds noise. An AI logistics employee should repeat only with new facts.
Combine related alerts
One weather event can delay ten loads on the same lane. Ten separate urgent alerts overwhelm the manager. One summary alert with the ten loads, the cause, and the decision needed is better. An AI logistics employee can group alerts by cause, lane, or customer when they share a decision.
Confirm the action after the decision
After the manager decides, the alert should close with a confirmation: what was done and when. For example: "Approved at 7:02 a.m. Carrier booked at 7:05 a.m. Dock informed at 7:06 a.m." The manager knows the decision took effect and does not need to check. An AI logistics employee should send this confirmation in the same thread as the alert.
Daily summaries for the rest
Managers still want to know what happened, even when no decision was needed. A daily summary can list exceptions handled within rules, the outcomes, and any patterns. This keeps managers informed without interrupting them.
Hypothetical example: one storm, one alert
This example is hypothetical and does not describe a real customer. A snowstorm closes a highway and delays twelve loads from one distribution center. Instead of twelve urgent alerts, the AI logistics coordinator sends the regional logistics manager one alert: twelve loads affected, new verified ETAs for nine, three still unconfirmed, two key customers affected. The decision needed is whether to call the two key customers personally. The manager asks the account managers to call, and the coordinator sends the other customers standard updates.
Let managers set preferences
Managers differ. One wants every urgent alert by direct message. Another prefers a call for anything over a set cost. Let each owner choose a channel within the team's rules. An AI logistics employee can follow each owner's preference as configured, which makes alerts more likely to be read quickly.
Review the table monthly
Review the routing table each month at first, then each quarter. Look for alerts that went to the wrong person, decisions that waited too long, and managers who received alerts they could not act on. Update the table. The AI logistics coordinator can show how long each decision took and who made it.
Common routing mistakes
- No backup. Alerts wait while the manager is away.
- No deadline. Managers decide when convenient, not when needed.
- Every alert marked urgent. Managers stop trusting the label.
- Alerts without options. Managers must investigate before deciding.
- No record of decisions. The team cannot learn which decisions are slow.
How should you evaluate alert routing in shipment tracking software?
Evaluate alert routing by triggering several exceptions that need different managers and checking who receives each one, how fast, and in what form. An AI logistics coordinator should route each decision to its owner, fall back to the backup on time, and act on the reply.
Demo tests for alert routing
| Buyer requirement | Demo test | Evidence to see |
|---|---|---|
| Routing by decision type | Trigger a rate decision and a customer decision | Each reaches a different owner |
| Routing by site or customer | Trigger the same exception for two sites | Each site's owner receives it |
| Backup routing | Leave the primary owner silent | Backup receives it at half the deadline |
| Alert structure | Read the alert | Decision, options, and deadline first |
| Easy reply | Reply "approve" | Action taken and confirmed |
| Noise control | Trigger ten related delays | One grouped alert |
| Record | Review the decision | Who received, who decided, when |
Demo questions about alert routing
- How is the routing table set up, and who can change it?
- Can routes vary by site, customer, mode, and exception type?
- Which channels can each route use?
- How does the AI logistics coordinator handle a manager's reply?
- How are related alerts grouped?
- Can the team see how long each decision took?
Test a manager on vacation
Mark the primary owner as away during the demo. Watch whether the alert goes to the backup right away rather than waiting for the primary to not answer. Out-of-office handling is a common gap. An AI logistics coordinator that knows who is away saves the full wait time.
How to measure alert routing work
Track the time from alert to decision for each decision type. Count how many alerts reached a backup. Check how many urgent alerts were acted on before their deadline. These measures show whether the AI logistics employee gets decisions made in time.
Involve the managers in the test
Ask the managers who will receive alerts to take part in the test. They should receive real-looking alerts on their phones and reply as they would on a busy day. Their reaction to the alert format is the best test of whether it works. If a manager has to call someone to understand an alert, the format needs work.
Scoring the alert routing demo
Score each test as pass, partial, or fail. A pass means the right owner received a clear alert and the decision was carried out. A partial means the alert reached the right person but lacked options or a deadline. A fail means the alert reached a shared inbox or the wrong person.
Warning signs in an alert routing demo
- All alerts go to one inbox.
- There is no backup routing.
- Alerts are long and bury the decision.
- Replies require logging into another system.
- Urgent and routine alerts look the same.
Where does Wilson fit in routing urgent shipment alerts?
Wilson, by Cartage, is an AI logistics coordinator that follows up on exceptions within the customer's rules and sends out-of-rule decisions to the logistics team. It replaces the TMS for freight execution and connects to the company's ERP through a method that fits the customer's environment.
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. Rates outside the customer's limits go to the logistics team. Payments above approval limits or outside the rules wait for a person.
How Wilson communicates
Wilson sends internal updates through channels such as Slack, Microsoft Teams, or email, depending on the customer's setup. It can notify consignees by email or SMS where configured. It keeps searchable shipment records with change history, including decisions and approvals.
Records that show where decisions stall
The decision record shows which decisions take longest and who makes them. If above-limit rebooking always waits for one manager, the team may raise the limit or add a second approver. An AI logistics coordinator can keep that record so the team improves routing over time with facts.
What Cartage asks about alert routing in discovery
Cartage asks who makes which freight decisions today, where decisions get stuck, and which channels each team uses. Typical questions also cover sites, key customers, and backups. These answers shape how an AI logistics coordinator routes decisions from the first load.
What Wilson does not do for alert routing
Wilson does not decide who owns each decision; the customer does. Specific routing rules, backup timing, and reply handling should be confirmed in a demo for the customer's setup. Exact ERP connection details depend on the customer's systems.
Routing changes as teams grow
Routing tables change as teams change. A new plant, a new key account, or a new manager means new rows. The table should be easy to update without a project. An AI logistics coordinator should apply the new table from the moment it changes, and keep the old version in the history so past decisions can be understood.
Where teams start with alert routing
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 decision that waits longest today, such as above-limit rebooking.
Teams designing routes can read about routing freight alerts to the right person. Teams assigning ownership can see how a freight exception responsibility matrix works. Both topics shape the routing table an AI logistics coordinator follows. Teams connecting alerts to action can review how to move from a delay alert to a recovery plan owner.
FAQs
How do you route urgent shipment alerts to the right manager?
Write a routing table that matches each decision type, site, and customer to a named owner and backup, with a channel and deadline. An AI logistics coordinator should send each alert with the facts, options, and deadline.
Which shipment alerts should go to a manager?
Only alerts that need a decision outside the rules, such as above-limit rates, new carriers, or major customer delays. An AI logistics employee should handle routine follow-up within the rules.
What should an urgent freight alert include?
What happened, what was tried, the decision needed, the options and their impact, and the deadline. An AI logistics coordinator should put the decision and deadline in the first line.
What if the manager does not respond?
Send the alert to a named backup after a set time, such as half the deadline. An AI logistics employee should record who received it and who decided.
Sources
- Cartage, Wilson product scope, October 2026: https://cartage.ai
Ask Cartage to show how an AI logistics coordinator routes an above-limit rebooking to your logistics manager with a two-option alert, falls back to the backup, and acts on a one-word reply: talk to the Cartage team.