Freight communication automation: "where's my order?" is a coordination problem, not a customer service one
Short answer
Answer where's my order by asking the carrier once. Then tell everyone else on the channel they already use. Freight updates should reach carriers, your team and customers at each milestone. No one has to write every message by hand. Wilson, by Cartage, an AI logistics agent, asks the carrier once and sends these updates by email, SMS, Slack, Teams and phone.
What is freight communication automation, and why does "where's my order?" keep reaching logistics?
It's 11 a.m. at a furniture manufacturer. A sales rep messages logistics on Slack asking whether a customer's order shipped. Customer service forwards an email from a retailer asking for a delivery time. The warehouse wants to know when tomorrow's truck is coming. The logistics coordinator emails the carrier, waits for an answer, then replies to each person separately. By the time everyone has an update, two of them have asked again.
Freight communication automation is the use of software to get shipment status from the carrier once and share it with every party that needs it, at the right milestone and on the right channel, so "where's my order?" stops landing on the logistics team.
The question keeps reaching logistics because logistics is where the answer lives. The carrier knows where the truck is. The ERP knows what was ordered. The customer knows when the dock is open. Nobody else has all three, so every question goes to the person who can ask the carrier.
Why the work multiplies
A single load can involve five or more people: the carrier's dispatcher, the company's own sales rep, customer service, the warehouse, the shipper and the consignee. Each wants to hear at a different moment. Sales wants to know it shipped. The warehouse wants to know when the truck comes. The customer wants to know when it arrives and whether anything changed.
None of these messages is hard to write. The problem is volume. Multiply five people by five milestones by dozens or hundreds of loads a week, and relaying information becomes one of the biggest uses of a coordinator's day. The same status gets typed four times in four places.
Why it is not a customer service problem
When a customer calls asking for their order, it looks like a customer service issue. Usually it is not. It is a sign that the update was never sent, was sent late or was not believed. Hiring more people to answer the calls treats the symptom. The fix is to send a confirmed update before the customer has to ask.
The cost of not fixing it shows up in three places:
- Coordinator time. Hours go to asking and relaying instead of booking, solving exceptions and checking invoices.
- Customer trust. Customers hear about delays late, or from their own receiving dock instead of from the supplier.
- Missed recovery. A late load found early can often be fixed by moving a receiving appointment. Found late, the same load becomes a missed appointment and, sometimes, a chargeback.
For a closer look at the customer side of this problem, see how to stop customers calling to ask where their order is.
See it on your own loads. Wilson, by Cartage (cartage.ai), is an AI logistics agent for manufacturers and distributors. It quotes, books, tracks, audits and pays for freight with your approved carriers, and customers cut freight costs 8% on average.Show us one lane and we'll show you how Wilson runs it. 15 minutes, no prep needed.
Book 15 minutes →or try Wilson free ↗How does automated freight communication work, step by step?
Automated freight communication follows one loop for every load: get the status from the best source, check that it is real, tell the people who need it, and follow up when the answer is missing or something changes.
The loop has five steps.
Step 1: A milestone happens or is due
Every update starts with a trigger. A load is booked. A pickup window opens. A delivery time gets close. A carrier email arrives saying the truck will be late. The software watches for these moments on every load, not only the loads someone remembers to check.
Step 2: Get the status from the best source available
The software asks for status from the best source the carrier offers for that load. In order of preference, that is usually:
- The carrier's API or EDI feed, when the carrier offers one.
- GPS or ELD data, when the carrier shares it.
- The carrier's website, looked up by PRO number.
- Email or a phone call to dispatch, or a call or text to the driver when the number is on file, when nothing else is current.
Many carriers, especially smaller ones, have no API. A good system does not stop there. It sends the email or makes the call, the same way a coordinator would. For more on choosing between these sources, see carrier API vs PRO tracking vs check calls.
Step 3: Check the answer before anyone hears it
Not every carrier answer is a fact. "Should deliver today" is a hope. "Truck is at the gate" is not the same as "picked up." Before telling anyone, the software saves the answer with its source and time and keeps separate statuses for things that are easy to mix up, such as arrived and loaded.
If the answer is vague, the system asks again. Customers should hear "delivered" only when the load has been delivered.
Step 4: Tell each party what they need, on their channel
Once the status is clear, the update goes out. Internal teams usually hear in Slack, Microsoft Teams or email. Shippers usually hear by email. Consignees hear by email or SMS. Each party gets only the milestones that matter to them, which the next section covers. If your team works in Spanish and your carriers in English, here is how to keep one record across both languages.
Step 5: Follow up when the answer is missing or the plan changes
The hardest part of freight communication is not sending updates. It is getting answers. A good system follows up with the carrier by email and phone until it gets one, using rules for each carrier. It also follows up with people on the company's own team who have not replied, in the same thread, and then escalates.
When a load is running late, the update is the start of the work, not the end. The system contacts the carrier for a new time and the reason, tells the team, tells the customer if that is set up, and starts the exception response, such as rebooking from the approved carrier list when the rules allow it.
A worked example
Consider a hypothetical distributor shipping a truckload to a retail distribution center with a 2 p.m. appointment.
| Time | What happens | Who hears |
|---|---|---|
| Monday 3 p.m. | Carrier accepts the load in writing | Team in Slack, shipper by email, carrier gets the rate confirmation |
| Tuesday 8 a.m. | Pickup window opens, no update from the carrier | Nobody yet; the system emails dispatch |
| Tuesday 9 a.m. | No reply, so the system calls dispatch: truck is loading | Team and shipper hear "picked up" after the signed BOL is filed |
| Wednesday 10 a.m. | Carrier says the truck will arrive at 4 p.m. after a breakdown | Team hears first, then the consignee by email, so receiving can move the appointment |
| Wednesday 4:20 p.m. | Carrier confirms delivery | Team, shipper and consignee hear "delivered" |
| Thursday 9 a.m. | Signed POD received and filed | Team and shipper hear "POD filed"; finance can invoice |
Nobody on the logistics team wrote a status email. They made one decision: whether the late arrival needed a new appointment.
Who needs to hear what at each shipment milestone?
Not every party needs every update. Good freight communication sends each party the milestones that matter to them, on the channel they already use, and lets the company change those choices.
Most shipments can be described with five milestones:
- Booked: a carrier has accepted the load in writing.
- Picked up: the freight is on the truck and the BOL is signed.
- Running late: the plan changed and someone may need to act.
- Delivered: the carrier confirms the freight arrived.
- POD filed: the signed proof of delivery is on record.
This is a common default, and it is how Wilson, by Cartage, handles freight communication under its current scope:
| Party | Booked | Picked up | Running late | Delivered | POD filed | Usual channel |
|---|---|---|---|---|---|---|
| Company's own team | Yes | Yes | Yes | Yes | Yes | Slack or Microsoft Teams |
| Carrier | Yes | Yes | Yes | Yes | Yes | Email, API, EDI or phone |
| Shipper | Yes | Yes | Yes | Yes | Yes | |
| Consignee | No | Yes | Yes | Yes | Yes | Email or SMS |
Why the consignee skips "booked"
A booked load is an internal fact. Telling the receiving customer that a carrier accepted the load adds noise and can create questions ("Which carrier? Why that one?"). The consignee cares about when the freight will arrive, so their first message is usually at pickup.
Why the internal team hears first
When a load is running late, sales and customer service should never learn it from the customer. The internal team gets each update first, so the account owner can decide whether to call the customer before the automated message goes out, when that is the company's rule.
Settings the company should control
Every company runs freight a little differently, so these choices should be settings, not code:
- Which internal channel gets which updates, for example one Slack channel per plant or per customer.
- Which customers get SMS and which get email only.
- Which customers get no automated messages at all, because their account manager wants to send updates personally.
- Whether a delay message goes to the customer right away or waits for a person on the team to approve it.
- The language for each party. A team can get updates in Spanish while carriers in the US get English.
For a deeper look at who should get an alert in tricky cases, see who needs to know when a shipment status changes.
What goes wrong when freight communication is automated badly?
Most failed attempts at automating freight communication fail in the same few ways: they send guesses, they stop when the carrier goes quiet, or they create one more inbox for the team to watch.
Mistake 1: Sending forecasts as facts
Some tools pass every predicted ETA straight to the customer. When the prediction moves, the customer gets three different times in one afternoon and stops trusting all of them. A customer update should be based on a confirmed status from the carrier, with the source saved.
Mistake 2: Only showing what the carrier sends
A tracking screen is only as good as the data behind it. When a carrier stops sending updates, many tools simply show the last known status. The load looks fine until it is late. Automation should notice the silence and ask, not wait.
Mistake 3: Alerts with no owner
An alert that goes to a shared inbox with no owner is often an alert nobody acts on. Each message that needs action should go to a named person, with a follow-up and an escalation if nobody answers. See who escalates unanswered carrier messages for a simple ownership model.
Mistake 4: A new portal nobody opens
If customers or colleagues must log in to a new portal to see status, many will not. They will keep emailing the coordinator. Updates should go to the tools people already use: email, SMS, Slack, Microsoft Teams, WhatsApp or the phone.
Mistake 5: Communication split from the work
When communication runs in one tool and booking, tracking and invoicing run in others, updates get out of sync. The customer hears "picked up" while the shipment record still shows "booked." The best results come when the same system that books and tracks the load also sends the updates, so every message matches the record.
Mistake 6: Telling the customer about a change nobody approved
If a carrier says it can only pick up a day later, that is a proposal, not a new plan. Sending the new date straight to the customer commits the company to it. The change should go to the team first. The team decides, and then the customer hears the agreed answer.
Mistake 7: No record of what was said
When a dispute comes up, such as a detention charge or a missed appointment, the team needs to know who said what and when. Every carrier answer and every update should be stored with the shipment, not lost in personal inboxes.
A short decision guide
| Situation | Send to the customer now? | What to do instead |
|---|---|---|
| Carrier confirms pickup with a signed BOL | Yes | File the BOL with the shipment |
| Carrier says "should deliver today" | No | Ask for a time and confirm delivery |
| Carrier proposes a new pickup date | No | Show the team, wait for a decision |
| Load will miss the delivery appointment | Team first, then customer | Get the new time and the reason, then tell the receiver |
| Carrier has not answered for hours | No | Follow up by email and phone, then escalate |
| Delivery confirmed, POD not yet received | Yes, as "delivered" | Chase and file the POD before invoicing |
How do you check if your freight communication works?
The fastest test is to count how many status questions still reach the logistics team and how long customers wait to hear about a delay. If either number is high, the communication is still running on people.
Five numbers to track
| Number | What it shows | How to measure it |
|---|---|---|
| "Where's my order?" requests to logistics per week | How often updates are missing or late | Count emails, calls and chat messages for one week |
| Time from a carrier delay to the customer hearing | How fast bad news travels | Compare the carrier's message time with the customer update time |
| Loads with no status for over a set number of hours | Where carriers have gone quiet | Review open loads each morning |
| Days from delivery to POD on file | How long cash waits on paperwork | Compare delivery date with POD filed date |
| Coordinator hours spent relaying status | The labor cost of manual updates | Ask the team to log relay time for one week |
Consider a hypothetical team where two coordinators each spend two hours a day relaying status. That is about 20 hours a week of skilled time. The U.S. Bureau of Labor Statistics reports a median pay of $82,320 for logisticians in May 2025, so even a few hours a week is real money spent on copying status from one message to another.
A ten-question checklist
Use this list to test your current process, or any software you are thinking about:
- Does every load get a status at pickup and delivery, without someone asking?
- When a carrier stops answering, does someone follow up the same day?
- Is there a phone or email fallback for carriers with no API?
- Does the team hear about a delay before the customer does?
- Are customer updates based on a confirmed carrier answer, not a forecast?
- Can each customer choose email or SMS, or opt out?
- Are proposed date changes shown to the team before the customer hears them?
- Is every carrier answer saved with the shipment and its time?
- Does the POD get chased and filed without a reminder?
- Does the ERP show the latest status, so sales and finance stop asking logistics?
If the answer to three or more is "no," communication is likely costing more time than any single task in the freight workflow. Question 10 is often the quiet one: if updates never reach the ERP, sales will keep asking. See how shipment updates get back into the ERP.
Let's review the "where's my order?" messages your team answered last week. You don't need to prepare anything: Cartage maps the workflow with you on the call.
How does Wilson, by Cartage, automate freight communication?
Wilson, by Cartage, is an AI logistics agent that runs freight communication as part of moving each load, keeping carriers, the company's own team, shippers and consignees updated from booking to proof of delivery. Traditional logistics software gives teams information. Wilson executes the work required to move shipments forward, including telling everyone what is happening.
One record behind every message
Wilson does not send updates from a separate module. It quotes, books, schedules, tracks, audits and pays for each load, so when it sends an update, it already knows the shipment, the carrier, the documents and the people involved. Every message, carrier answer and change is kept in the shipment's change history.
Wilson replaces the TMS for freight execution and connects to the company's ERP. Orders reach Wilson by email, an ERP connection or CSV or XLSX files. Wilson works with SAP, NetSuite, Microsoft Dynamics 365, Oracle, Infor, Epicor, Sage, Acumatica and other ERP environments, with the exact connection depending on the customer's data flow and scope. Whether status is written back to the ERP depends on scope.
How Wilson gets the status
Wilson tracks each load with the best source available: the carrier's API or EDI feed, GPS or ELD data where the carrier shares it, the carrier's website by PRO number, and email or phone calls when nothing else is current. It usually talks to the carrier's dispatch and can call or text a driver when it has the driver's number. It follows up with carriers by phone and email, with persistence rules for each carrier, until it gets an answer.
Wilson does not send a customer update based on an unconfirmed event. When a carrier's answer is vague, Wilson asks again before telling anyone the load has delivered.
How Wilson tells everyone else
- The company's team hears at every milestone in Slack, Microsoft Teams, email or SMS. When a colleague does not answer, Wilson follows up in the same thread and then escalates.
- Shippers hear by email at each milestone.
- Consignees hear by email or SMS from pickup to POD, when the company sets it up.
- Carriers get booking details, rate confirmations and follow-ups by email, API, EDI where supported, or phone where configured.
Wilson writes in several languages, and phone calls are supported in English and Spanish. A team can get updates in Spanish while Wilson writes to US carriers in English.
What Wilson sends besides status
After pickup, Wilson files the signed BOL and can send it to the customer. After delivery, it requests and files the POD. It also produces rate confirmations, bills of lading, packing slips and pallet labels, and can request, chase and file other documents set up in the workflow. It does not upload documents to customer portals.
When a person steps in
Wilson handles routine updates and follow-ups. A person decides when the plan changes:
- If a carrier proposes a new pickup date, Wilson shows the option to the team, updates the expected date and leaves the agreed date unchanged until the team decides.
- If a load is running late, Wilson gets the new time and reason, tells the team and, if configured, the customer. If the load needs rebooking, it starts rebooking from the approved carrier list, automatically within the rules or after approval.
- If the team changes something on one load, Wilson treats it as a one-time change. If it looks like it should become a rule, Wilson asks first.
Control starts with assisted execution. The company sets the approval limits, and routine actions can run automatically within those rules as the workflow is proven. Each customer's data is encrypted and kept inside that customer's organization, and customer data is not used to train Wilson.
How teams start
Wilson gets an email address on the company's domain and is onboarded like a new team member on the company's carriers, rules, approval limits and contacts. The company controls the scope: it can start with a few lanes, one or two key customers, or a subset of shipments. Timing depends on scope: most teams start on a few lanes and expand from there. To see how this fits with the rest of the team's work, see how Wilson takes routine freight work off your team.
Pricing
Wilson is free on Wilson's network: the shipper pays the freight rate and nothing on top. When a shipper keeps its own carriers, the fee is 2% to 0.5% of what Wilson pays them, falling with volume. There are no seat fees, no setup cost and no contract.
See it on your own loads. Wilson, by Cartage (cartage.ai), is an AI logistics agent for manufacturers and distributors. It quotes, books, tracks, audits and pays for freight with your approved carriers, and customers cut freight costs 8% on average.Show us one lane and we'll show you how Wilson runs it. 15 minutes, no prep needed.
Book 15 minutes →or try Wilson free ↗FAQs
Can Wilson, by Cartage, an AI logistics agent, answer "where's my order?" for my customers?
Yes. Wilson, by Cartage, an AI logistics agent, asks the carrier for status and updates consignees by email or SMS from pickup to POD, when the company sets it up. Because the update goes out before the customer asks, fewer questions reach the logistics team.
What is freight communication automation?
It is software that gets shipment status from carriers and shares it with internal teams, shippers and consignees at key milestones. No coordinator has to write each update. The best setups also follow up when a carrier does not answer.
How do logistics teams automate shipment status updates?
They use a system that asks the carrier for status at each milestone and then tells every party that needs to know. The five usual milestones are booked, picked up, running late, delivered and POD filed. Each party gets only the ones that matter to them.
Are automated shipment updates instant?
It depends on the source for each load. Carrier APIs, EDI and GPS data are fast. When a carrier has none of those, the update waits on an email or phone answer, so timing depends on how fast the carrier replies.
Can customers get delivery updates by SMS?
Yes. Consignees can get updates by email or SMS at pickup, delays, delivery and POD filing, depending on each company's settings. Some companies choose email only for certain customers.
Does Wilson notify internal teams in Slack or Microsoft Teams?
Yes. Wilson sends updates to the company's own team in Slack or Microsoft Teams at every milestone, from booking to POD filed. It can also use email or SMS.
What happens when a carrier does not reply?
Wilson follows up by email and phone, with persistence rules for each carrier, until it gets an answer. If a load stays without a confirmed status, the team is told so a person can decide what to do.
Does automating freight communication require a TMS?
No. Wilson replaces the TMS for freight execution and keeps its own shipment records. It works from the ERP connection or data flow the company already has, such as an ERP feed, files or email.
Will customers get a "delivered" message before the POD arrives?
They can get "delivered" when the carrier confirms delivery, and "POD filed" when the signed proof is on record. Keeping the two separate stops customers from hearing about a delivery that has not been confirmed.
Can our team get updates in Spanish?
Yes. Wilson writes in several languages and supports phone calls in English and Spanish. It can answer the team in Spanish and write to US carriers in English.
Sources
- Cartage, Wilson product FAQ and product scope, October 2026: https://cartage.ai
- U.S. Bureau of Labor Statistics, Occupational Outlook Handbook, Logisticians (median pay, May 2025): https://www.bls.gov/ooh/business-and-financial/logisticians.htm
Bring one lane where customers keep asking "where's my order?" and see how Wilson would keep every party updated. You don't need to prepare anything: Cartage maps the workflow with you on the call.
