How do I stop customers from calling to ask where their order is?
Key Takeaways
- Customers call because they don't know, not because they're impatient. Most "where is my order?" calls come from a missing update at a predictable moment.
- Four updates prevent most calls: order booked with a pickup date, freight picked up, running late (before the customer notices) and delivered.
- The late update matters most. A customer told about a delay early rarely calls twice; one who finds out on the delivery date usually escalates.
- Updates have to come from the shipment, not from memory. If someone has to remember to send them, they stop the first busy week.
- Give sales and customer service the same status the logistics team sees, so they can answer without forwarding the question.
- Wilson, by Cartage, is an AI logistics agent that sends shipment updates to the team in Slack, Microsoft Teams or email and to customers by email or SMS where configured, from the same record it uses to book and track the load.
Why do customers keep calling about their orders?
Every morning, the same thing happens. A customer emails the sales rep asking when their order ships. The rep forwards it to customer service. Customer service asks logistics. Logistics checks the carrier's website, emails the carrier, waits, and answers two hours later. By then the customer has called the main line too.
Customers call because the information they need, when their freight will arrive, isn't reaching them at the moments they need it. In B2B freight, the customer has planned around the delivery: a production line, a store shelf, a job site, a receiving crew. When they don't hear anything, they assume the worst and ask. Each call takes time from three or four people on the shipper's side, and most of them could have been avoided with one short message sent at the right time.
The calls are a symptom. The cause is usually one of these:
- No confirmation after booking. The customer placed an order and heard nothing about when it would ship.
- No pickup notice. The customer doesn't know the freight left, or which carrier has it.
- Silent delays. The carrier is running late, the shipper knows or could know, but the customer finds out when the truck doesn't show.
- No tracking reference. The customer has no PRO number or carrier name to check for themselves.
- Inconsistent answers. Sales says Tuesday, customer service says Wednesday and the carrier says Thursday. The customer calls a fourth person to find out who is right.
Which customers call most
Status questions aren't spread evenly. A handful of customers usually generate most of them: those with tight receiving schedules, those whose own customers are waiting, and those who were burned by a late delivery before. Look at two weeks of emails and calls and list who asked. That list tells you where to start, and often shows a pattern, such as one lane with a slow carrier or one customer who never received pickup notices.
What the calls cost
The cost isn't only time. Each "where is my order?" question pulls the logistics team away from the work that actually moves freight: confirming pickups, handling exceptions, booking the next load. When the team is busy answering questions about loads that are fine, it's slower to catch the ones that aren't. And customers who repeatedly have to ask lose confidence, which shows up later in reorders and in how forgiving they are when something really does go wrong.
Why the calls get worse as you grow
More customers mean more contacts, more delivery rules and more carriers, and every one of them adds status questions. A team that could answer every call personally at 20 loads a week can't at 80. The calls grow faster than the freight, because each new customer brings several people who all want to know where the order is. Fixing updates early keeps that growth from landing on the logistics desk.
Why B2B is different from parcel
Consumers get a tracking link and automatic updates from parcel carriers. B2B freight usually doesn't work that way. LTL and truckload carriers each have their own systems, many updates still arrive by email or phone, and the delivery often needs an appointment. The shipper sits in the middle, and if the shipper doesn't pass information on, nobody does.
Which updates actually stop the calls?
Four updates, sent at the right moments, prevent most "where is my order?" calls: booked, picked up, running late and delivered. Each one answers the question the customer would otherwise call about.
| Update | When to send it | What it should say | The call it prevents |
|---|---|---|---|
| Booked | When the carrier accepts the load | Order number, carrier, planned pickup date, expected delivery date | "Has my order shipped yet?" |
| Picked up | When the carrier confirms pickup | Carrier name, PRO or tracking number, expected delivery date | "Where is it now?" |
| Running late | As soon as the delivery date is at risk | New expected date, the reason in plain words, what is being done | "Why isn't it here?" |
| Delivered | When delivery is confirmed | Delivery date and time, and the POD on request | "Did it arrive?" (from someone else at the customer) |
The running-late update matters most
The late update prevents the angriest calls. A customer told on Monday that Wednesday's delivery will arrive Thursday can move their crew or warn their own customer. A customer who finds out on Wednesday afternoon, when the truck doesn't arrive, has no options left. Sending the late update early, even before the new time is certain, does more for the relationship than any other single message. "The carrier reports a delay; we expect Thursday and will confirm by tomorrow at noon" is far better than silence.
What a good late update looks like
A good late update is short and answers three questions: when will it arrive now, why, and what happens next. For example: "Your order 48213 is running late. The carrier reports a delay at its terminal and now expects to deliver Thursday instead of Wednesday. We'll confirm the delivery time by Wednesday noon. If Thursday doesn't work for your receiving team, reply and we'll look at options." It doesn't blame anyone, doesn't use freight jargon and gives the customer a way to respond. Writing this template once means nobody has to compose it under pressure.
What to say when you don't know yet
Sometimes the carrier hasn't answered and the new delivery time isn't clear. Send the update anyway. "The carrier hasn't confirmed today's delivery; we've asked and will update you by 2 p.m." tells the customer you're on it and when to expect news. Then keep that promise. A customer who receives two short, honest updates in a day rarely calls; one who receives nothing usually calls twice.
What not to send
More updates aren't better. Customers don't need every scan event or every terminal arrival. Too many messages train people to ignore them, and then they miss the one that matters. Stick to the four moments that change what the customer does, and add more only if a specific customer asks.
Who should receive them
Ask each customer who should get updates. Often it's the buyer who placed the order and the receiving contact at the delivery site, and they need different things. The buyer wants dates; the receiving dock wants the appointment and the carrier. Sending each person only what they need keeps the updates useful.
Who should send updates, and from where?
Updates should come from the record of the shipment, triggered by real events, not from someone remembering to write them. That is the difference between updates that last and updates that stop after the first busy week.
Why manual updates don't last
Many logistics teams start with good intentions: a template email for each customer, sent by hand. It works for a few weeks. Then volume goes up, someone goes on vacation, a carrier has a bad week, and the updates stop exactly when customers need them most. Manual updates fail under the same pressure that causes delays.
Tie each update to an event
Each of the four updates has a natural trigger:
- Booked: the carrier's tender acceptance or rate confirmation.
- Picked up: the carrier's pickup confirmation, a signed BOL or a tracking event.
- Running late: a new ETA past the promised delivery date or appointment.
- Delivered: the carrier's delivery confirmation or a signed POD.
When the update is tied to the event, it goes out whether the team is busy or not. The team only steps in when the event itself needs a decision, such as a delay that requires rebooking.
When the delay needs a decision
Some delays only need a message. Others need a decision: move the load to another carrier, pay for an expedite, split the order or ask the customer to accept a later date. Those decisions belong to a person, usually in logistics, sometimes with sales. The update process should flag them clearly, with the options and costs, instead of burying them in a stream of routine notices.
One shared status for everyone
The same shipment status should be visible to logistics, customer service and sales. When sales can see that the load was picked up yesterday and is due Thursday, they answer the customer directly instead of forwarding the email. Many "where is my order?" questions travel through three people inside the shipper before anyone checks the carrier. Shared status cuts that chain to one step.
Customer portals vs. pushed updates
Some shippers give customers a portal where they can look up their orders. Portals help customers who like to check, but most B2B buyers won't log in to a supplier's portal every day. Pushed updates, sent by email or SMS when something happens, reach people where they already are. A portal is a good addition; it isn't a substitute for the late update.
Keep the ERP current
If customer service works from the ERP (SAP, NetSuite, Microsoft Dynamics 365, Epicor, Infor or another system), the shipment status should flow back to the order where possible. An order that says "open" when the freight was delivered two days ago creates its own calls. For why ERP and carrier statuses drift apart, see why an ERP order can say shipped before pickup.
After delivery
Questions don't end at delivery. Customers ask for the signed POD, report a shortage or damage, or ask why the invoice doesn't match. Having the POD filed on the shipment within a day or two of delivery answers most of these quickly. If the POD shows an exception, such as a damaged pallet noted by the receiver, contact the customer before they contact you.
How do you get better status from carriers in the first place?
Customer updates are only as good as the carrier information behind them. If the shipper doesn't know where the freight is, no message template will help.
Use the best source for each carrier
Carriers share status in different ways. Some offer an API. Some share GPS or ELD data. Many LTL carriers show status on their website by PRO number. Others only answer by email or phone. A reliable tracking process uses the best source available for each load, and asks the carrier directly when nothing else is current. For how to handle conflicting estimates, see what to do when two ETAs disagree.
Ask before you're asked
The most useful habit is to check loads due today and tomorrow every morning, before customers ask. Confirm the delivery date with the carrier for anything due soon. A problem found at 8 a.m. can still be handled; one found when the customer calls at 3 p.m. usually can't.
Confirm pickups the same day
Many delays start at pickup: a carrier that didn't show, or picked up late. If pickups aren't confirmed the same day, the shipper won't know a load is behind until the delivery date. Same-day pickup confirmation is the foundation of every accurate customer update.
Delivery appointments
Many B2B deliveries need an appointment at the receiving dock. A missed or unmade appointment is a common reason freight "is late" even when the truck arrived on time. Confirm who makes the appointment, the carrier or the shipper, and include the appointment time in the pickup update. When an appointment has to move, tell the receiver directly; they are the ones planning labor around it.
Record what the carrier said
Each status from a carrier should be recorded with its source and time: "carrier dispatcher by phone, 9:15 a.m., Thursday delivery." That record lets customer service give one consistent answer, and settles later questions about who knew what and when.
A setup checklist and an example
Setting this up takes a few decisions, not a big project. Use this checklist to get from "customers call us" to "customers hear from us."
| Step | Decision to make | Done when |
|---|---|---|
| 1 | Which customers get updates | You have a list, starting with the ones who call most |
| 2 | Who at each customer receives them | Buyer and receiving contacts are recorded per customer |
| 3 | Which of the four updates each customer wants | Some want all four; some only want late and delivered |
| 4 | Channel | Email for most; SMS for receiving docks that prefer it |
| 5 | What triggers each update | Each update is tied to a carrier event, not a reminder |
| 6 | What the late update says | A template with the new date, the reason and the next step |
| 7 | Internal visibility | Sales and customer service can see the same status |
| 8 | Measurement | You count "where is my order?" questions for two weeks before and after |
Use the updates internally too
The same four updates help inside the company. Production planning wants to know when inbound materials arrive. Finance wants to know when freight was delivered so it can invoice the customer. Warehouse teams want to know which trucks are coming tomorrow. Sending the right internal update to each of these groups prevents a second wave of status questions from colleagues, which can be as large as the one from customers.
Measure it
Count "where is my order?" emails and calls for two weeks before you start, by customer. Then count again after the updates are running. The customers whose questions don't drop are the ones to look at: maybe the updates go to the wrong person, or the late update comes too late.
An example
Consider a hypothetical building products distributor that ships about 60 LTL and truckload orders a week to contractors and dealers. Its customer service team was fielding around 40 status questions a week, most of them forwarded to the one person in logistics. The distributor started sending the four updates, by email, to the buyer on each order, and a pickup notice with the carrier and PRO number to the receiving contact. Sales got access to the same status. The questions that remained were mostly about real problems: a damaged pallet, a delivery appointment the receiver had forgotten. Those are the calls worth taking.
This example is hypothetical; real results depend on the customers, the carriers and how consistently the updates are sent.
Roll it out one customer at a time
Start with the three customers who call most. Set up their contacts and preferences, send the four updates for two weeks and ask them whether the updates helped. Adjust the wording and timing, then add the next group. A gradual rollout catches problems, such as updates going to an old contact, before they reach every customer.
Common mistakes
- Sending updates only when things go well. A booked and delivered notice with a silent delay in between makes the delay worse.
- Using internal language. "Tendered," "dispatched" and "OS&D" mean nothing to many customers. Say "booked," "on the way" and "arrived with damage."
- Promising exact times the carrier hasn't confirmed. Give the carrier's estimate and say it's an estimate.
- Forgetting the customer's own customer. If your customer is a distributor, they may need to forward your update. Make it easy to forward.
How does Wilson, by Cartage, keep customers informed?
Wilson, by Cartage, is an AI logistics agent that books, tracks and delivers freight for manufacturers and distributors, and sends the updates from the same record. Traditional logistics software gives teams information. Wilson executes the work required to move shipments forward.
Because Wilson handles the steps that create each update, the updates come from real events:
- Booked: Wilson tenders the load to an approved carrier and records the written acceptance and rate confirmation.
- Picked up: Wilson confirms the pickup with the carrier and records the time and PRO number.
- Running late: Wilson tracks each load with the best source available for that carrier (carrier API, GPS or ELD data where shared, the carrier's website by PRO number, and email or calls when nothing else is current). When a load is at risk, Wilson contacts the carrier, tells the team and, if configured, tells the customer, and can start rebooking from the approved carrier list, automatically within the rules or after approval.
- Delivered: Wilson confirms delivery, requests the signed POD and files it on the shipment.
Wilson's communication follows a simple pattern. The company's own team hears about booked, picked up, running late, delivered and POD filed in Slack, Microsoft Teams or email. The shipper side gets updates by email. The consignee, the customer receiving the freight, gets updates by email or SMS for picked up, running late, delivered and POD filed, as configured. Each person gets only the updates set for that order and role.
Every message, confirmation and change is kept in the shipment's change history, so customer service can answer any question from the record. Where write-back to the ERP is in scope, the status can update the order too. 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.
What changes for the team
When updates come from the shipment record, the logistics team stops being the help desk. Customer service answers from the same status Wilson keeps, sales sees where its customers' orders are, and the logistics team spends its time on the loads that actually need attention: the delay that needs a rebooking decision, the carrier that hasn't confirmed, the receiver that refused a delivery.
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. Timing depends on scope: most teams start on a few lanes and expand from there.
For the bigger picture, see who needs to know when shipment status changes and what an AI logistics agent is.
FAQs
How do I stop customers from calling to ask where their order is?
Send four updates at the moments customers would otherwise call: booked, picked up, running late and delivered. Tie each one to a carrier event so it goes out every time. Wilson, by Cartage, an AI logistics agent, sends these updates from the same record it uses to book and track the load.
What is a WISMO call?
WISMO stands for "where is my order?" It's the name customer service teams use for status questions. In B2B freight, most WISMO calls come from a missing update after booking, after pickup or when a delivery is running late.
Which shipment update matters most to customers?
The running-late update. Telling a customer about a delay early, before the promised delivery date, lets them plan around it. Customers who find out on the delivery date are the ones who escalate.
Should we give customers a tracking link?
If the carrier provides one, it helps, especially with a PRO number. But a tracking link doesn't replace a late update: customers rarely check links until something is already wrong.
How often should customers get shipment updates?
Only at moments that change what they do: booked, picked up, running late and delivered. More frequent updates tend to get ignored.
Who should send shipment updates, logistics or customer service?
The updates should come from the shipment record, triggered by carrier events, so they don't depend on either team remembering. Both teams should see the same status so they give the same answer.
How do I get accurate delivery dates from carriers?
Use the best source each carrier offers: an API, GPS or ELD data, the carrier's website or a direct email or call. Confirm pickups the same day and check loads due in the next two days every morning.
Can shipment updates be sent by text message?
Yes. Many receiving docks prefer SMS for pickup and delivery notices. Wilson can send consignee updates by email or SMS where configured.
Do customer updates help with delivery appointments?
Yes. Including the carrier, the expected date and the appointment time in the pickup update lets the receiving dock plan labor. When an appointment has to move, telling the receiver directly prevents a refused or rescheduled delivery.
What should a delay notice to a customer say?
When the freight will arrive now, why it's late in plain words and what happens next, including when the customer will hear again. Keep it short, skip freight jargon and give them a way to reply if the new date doesn't work.
How do I reduce status emails to customer service?
Send the four updates from the shipment record, give customer service and sales the same status logistics sees, and include the carrier and PRO number in the pickup notice so customers can check for themselves.
Does Wilson replace our customer service team?
No. Wilson sends routine shipment updates from the shipment record and keeps status current, so customer service can answer from the same information. Customer service still handles the conversations that need a person, such as damage, shortages and special requests.
Sources
- Cartage, Wilson product FAQ and product scope, October 2026: https://cartage.ai
Bring a week of "where is my order?" emails and see which updates Wilson would have sent instead.