Customers keep asking where their order is. What should we send them, and when?

Driver arrival and detention guideNov 17, 202617 min read

Why do customers keep asking where their order is?

It is 9:15 on a Tuesday morning. The customer service inbox has 23 new emails. Eleven of them ask the same thing in different words: "Has my order shipped?", "Any update on PO 4471?", "Our receiving team needs a delivery time." One logistics coordinator spends the next two hours opening carrier websites, typing PRO numbers and writing replies. By noon, five more have arrived. None of these customers had a problem with their freight. They just did not know where it was.

Customers should get a short set of proactive updates from the shipment record: a pickup notice with the tracking number, a delay notice only when the carrier confirms the delay, and a delivery confirmation, with the proof of delivery for customers who need it. Send each one when the event happens, to the person who actually uses it, through the channel that person reads. When those three messages arrive on time and are correct, most "where is my order" emails stop.

The questions are a signal, not the problem. A customer who writes in is telling the team that the information they needed did not reach them. Sometimes nothing was sent. Sometimes something was sent to a buyer who never forwards it to receiving. Sometimes the update was sent but said "in transit" for four days, which answers nothing.

What the question really means

A "where is my order" email usually hides one of four real questions:

  • Did it ship? The customer needs to know the order left the building and how to track it.
  • When will it arrive? Receiving needs a date, and often a time window, to plan labor and dock space.
  • Is something wrong? The customer heard nothing for days and is starting to worry about a production line, a store shelf or their own customer.
  • Did it arrive? Accounts payable or receiving needs proof before they close the order or release payment.

Each one has a matching update. If the team sends the right one at the right moment, the question never gets written.

Why replying faster does not fix it

Many teams try to solve the problem by answering faster. They assign one person to the inbox or build a template. That helps the customer who already asked, but it does nothing for the next ten who will ask tomorrow. Reactive replies also pull the coordinator off booking, quoting and exception work, which creates the delays that cause even more questions. The way out is to move the work before the question: send the information when it changes, not when someone asks.

What it costs to keep answering

The cost is mostly time. Each lookup means finding the order, finding the carrier and the tracking number, checking the carrier's website or calling dispatch, and writing a reply. For a hypothetical team handling 15 such questions a day at six minutes each, that is 90 minutes daily, or more than seven hours a week, spent repeating information the team already had. It also costs trust. A customer who has to chase every shipment starts to wonder what else is slipping.

Let's review the "where is my order" emails your team answers. You don't need to prepare anything: Cartage maps the workflow with you on the call.

See it on your own loads. Wilson, by Cartage, is an AI logistics agent that quotes, books, tracks, audits and pays for freight with your approved carriers.

Book a demo →

Which shipment updates should customers get, and when?

Send updates at the moments the customer can act on them: when the freight leaves, when the plan changes and when it arrives. Everything in between is noise for most customers.

Update 1: Picked up

Send this as soon as the carrier confirms pickup. Include:

  • The customer's order or PO number, so they can match it in their own system.
  • The carrier name and the tracking or PRO number.
  • Number of pallets or pieces, and the weight if the customer asks for it.
  • The expected delivery date, labeled as the carrier's estimate.
  • The delivery appointment, if one is already set.

The pickup notice does most of the work. It tells the customer the order shipped, gives them a way to look it up themselves and sets the expected date. Many questions disappear with this one message.

A pickup notice should wait for confirmation. "Scheduled for pickup" is not "picked up." If the truck misses the pickup and the notice already went out, the customer now plans around a date that is wrong.

Update 2: Running late

Send this only when the carrier confirms a real change in the delivery date or appointment. Include:

  • What changed: the old date and the new date or window.
  • The reason, in plain words, if the carrier gave one.
  • What happens next: a new appointment, a call from the carrier or a follow-up from the team.
  • Who to contact with questions.

Do not send a delay notice because a tracking page went quiet for six hours. Missing scans are common, especially on LTL freight moving through terminals. Check with the carrier first. A false alarm teaches the customer to ignore the next alert. For a deeper look at timing and wording, see how to send customer updates when a shipment is delayed.

Update 3: Delivered

Send this when delivery is confirmed. For many customers, the confirmation alone is enough. Others need the proof of delivery attached, especially if their payment terms start at delivery or their receiving team signs for many loads a day. Note any exceptions on the POD, such as shortages or damage, so the customer is not surprised later.

Be careful with "delivered" status that comes from a tracking event before the POD exists. A carrier can mark a load delivered while the driver is still at the dock, or by mistake. If the customer acts on a delivery message and then cannot find the freight, the update has created a problem. The guide on stopping a delivered notification before the POD arrives covers that case.

Optional updates some customers want

Some customers want more. Agree on these one customer at a time:

  • Out for delivery on the day of delivery, for receivers who staff the dock by the hour.
  • Appointment set, when the team or the carrier books a delivery slot.
  • Order ready to ship, for customers who arrange their own pickup.
  • A daily summary of every open shipment for a high-volume customer, instead of one email per load.

A simple update schedule

Event When to send Who usually needs it What to include
Picked up When the carrier confirms pickup Buyer and receiving PO, carrier, tracking or PRO number, pieces, estimated delivery
Appointment set When the slot is confirmed in writing Receiving Date, time window, PO, carrier
Running late When the carrier confirms a new date or time Buyer and receiving Old date, new date, reason, next step
Out for delivery Morning of delivery, if requested Receiving Expected window, carrier, PO
Delivered When delivery is confirmed Buyer, receiving, accounts payable Delivery time, POD if requested, exceptions noted
Daily summary Once a day, if requested High-volume buyers Every open order with status and expected date

How do you set up customer updates that actually stop the questions?

Start from the questions customers already send, decide what each customer needs, and send every update from one shipment record. The setup is mostly a list of decisions per customer, and it can begin with the customers who ask the most.

Step 1: Count the questions

Pull the last two weeks of "where is it" emails and calls. Group them by customer and by question type: did it ship, when will it arrive, is something wrong, did it arrive. The pattern tells you where to start. If one distributor sends half the questions, start there. If most questions are about delivery dates, the pickup notice is missing or the expected date is not in it.

Step 2: Name the right recipients

The buyer who placed the order is often not the person waiting for the truck. Ask each customer who should get which update. Common answers:

  • The buyer gets pickup and delay notices.
  • The receiving lead gets appointment and out-for-delivery messages.
  • Accounts payable gets delivery confirmations with the POD.

One customer may want everything sent to a shared inbox. Another may want text messages to the dock supervisor. Write it down on the customer's record, not in a coordinator's notes.

Step 3: Choose the channel

Email works for most buyers and for anything with an attachment, such as a POD. Text messages work better for receivers who are on the floor, not at a desk, and for time-sensitive changes like a late truck. Keep messages short on text: PO, new time, one line of reason.

Step 4: Decide what each update says

Write a short template for each event. Keep the same order every time so customers learn where to look: PO first, then what happened, then what comes next. Leave out internal details, such as which carrier quoted lower or why the team picked this one. Keep the tone plain and factual.

Step 5: Connect updates to confirmed events

Each update should trigger from a confirmed event on the shipment: the carrier's pickup confirmation, a confirmed new delivery time, a delivery confirmation or a filed POD. If updates trigger from guesses, such as "pickup date has passed so it must have shipped," they will be wrong often enough to break trust.

Step 6: Keep one record

Every update sent, every reply from the customer and every change from the carrier should be saved on the same shipment. When the customer calls anyway, whoever answers can see what the customer was already told. Without one record, two people send two different answers, and the customer trusts neither.

Step 7: Review after a month

Count the questions again. If they dropped for some customers but not others, look at those customers' settings. The recipient may be wrong, the channel may be ignored or the update may be missing the detail they actually need.

Where does the tracking information come from?

Updates are only as good as the tracking behind them, and tracking comes from different sources on different loads. Knowing which source to trust on each load prevents most wrong messages.

The usual sources

  • Carrier API or EDI status messages. Structured and fast when the carrier supports them, but some events arrive late or out of order.
  • GPS or ELD location data, where the carrier shares it. Good for knowing where the truck is, less useful for knowing whether it will make the appointment.
  • The carrier's website by PRO number. Common for LTL. Updates come at terminal scans, so there can be long gaps between them.
  • Email or phone calls to dispatch. Slow to collect, but often the only way to get a confirmed new time when something has gone wrong.

When sources disagree

A tracking feed can say "on time" while the dispatcher says the driver is two hours behind. In that case, the person who talked to the carrier has the better answer. The rule is simple: an update to the customer should state what the carrier confirmed, not what a feed estimated. When sources conflict, check with the carrier before telling the customer anything. The article on carrier email and tracking feeds that disagree walks through that decision.

Gaps are not delays

LTL freight often goes quiet for a day while it sits at a terminal or moves on a linehaul. That silence is normal. A good tracking process knows the usual gap for each carrier and lane, and only follows up when the gap is longer than usual or the delivery date is close. Following up on every quiet hour floods carriers with emails and gets slower answers on the loads that matter.

Confirming before sending

The safest pattern is to check before every customer-facing change:

  1. A tracking source shows something unusual, such as a missed scan, a new estimate or a "delivered" event.
  2. Someone asks the carrier to confirm.
  3. The carrier confirms or corrects it.
  4. The update goes to the customer with the confirmed answer.

This takes a little longer than forwarding the raw status. It also means the customer never has to hear "sorry, our last message was wrong."

What mistakes make customer tracking updates backfire?

Most failures come from sending too much, sending too early or sending to the wrong person. Each has a simple fix.

Mistake 1: Forwarding every carrier scan

Customers do not need "departed terminal" and "arrived at terminal" five times. A stream of scans buries the one message that matters. Send the events that change what the customer does: shipped, late, delivered.

Mistake 2: Calling a load late before the carrier confirms it

A delay message triggered by a missing scan creates worry and a phone call. Then the freight arrives on time and the customer learns to ignore alerts. Confirm first.

Mistake 3: Updating the buyer but not the receiver

The buyer gets a delay notice. The receiving team, who planned labor around the old time, does not. Ask who needs each update, and send it to them directly.

Mistake 4: Promising a time the carrier never gave

"Arriving at 10:00" sounds precise, but if the carrier only committed to a delivery date, the customer will hold the team to a time nobody agreed to. Say "expected Thursday, carrier estimate" until there is an appointment.

Mistake 5: Sending the POD too late

If payment terms start at delivery, a POD that takes ten days to reach the customer slows cash. Request the POD as soon as delivery is confirmed and send it when it arrives. For more on that, see pod collection automation.

Mistake 6: Different answers from different people

Customer service tells the customer one date. The coordinator tells the buyer another. The sales rep says a third. Send every answer from the same shipment record and save what was said there.

Decision rules for customer updates

Situation Send an update? What to do
Carrier confirms pickup Yes Send pickup notice with tracking number and estimated delivery
Tracking page has no new scan for several hours No Check usual gap; follow up with the carrier only if it is longer than normal
Carrier confirms a new delivery date Yes Send delay notice with old and new date and next step
Feed and dispatcher disagree Not yet Confirm with the carrier, then send the confirmed answer
Carrier marks delivered, no POD yet Depends on the customer Confirm delivery; send POD when it arrives if the customer requires it
Customer asks for a status that was already sent Yes, short Resend the last update and check whether the recipient list is right
Delay caused by the receiver's closed dock Yes State the facts and the redelivery plan; tell the team about possible charges

How does Wilson, by Cartage, keep customers updated on their orders?

Wilson, by Cartage, is an AI logistics agent that quotes, books, tracks, audits and pays freight for manufacturers and distributors, and it keeps customers informed from the same shipment record it works from. Traditional logistics software gives teams information. Wilson executes the work required to move shipments forward.

Think of Wilson as a free logistics department with four parts: the labor, the data, the network and the payments. Each one matters for customer updates.

The labor: tracking and follow-up done for the team

Wilson does the labor start to finish, from the first quote to the final POD. On tracking, it uses the best source available for each load: the carrier's API or EDI, 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 follows up with carriers by phone and email, with persistence rules per carrier, until it gets an answer. The team does not spend the morning typing PRO numbers into carrier websites.

When something goes wrong, such as a missed pickup, a cancellation or a delay, Wilson contacts the carrier, tells the team and, if configured, tells the customer. Customers and consignees can get updates by email or SMS where configured. Wilson requests the POD when delivery is confirmed, files it on the shipment and can send it to the customer.

The data: one record behind every update

Wilson keeps every order, load, quote, rate, document and contact on record as it works. That is the data. Each customer's preferences, such as who gets pickup notices or which receiver wants a text before delivery, can be kept as rules the team can see and edit. Every message, confirmation and change is kept in the shipment's change history, so anyone answering a call can see exactly what the customer was told and when.

Wilson keeps every load, rate and document on record, so teams don't need a TMS. Wilson replaces the TMS for freight execution and connects to the company's ERP. 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 and tracking numbers are written back to the ERP depends on scope.

The network and the payments

The network gives the shipper better freight rates on every lane, because its volume counts with every other Wilson customer's. The network includes carriers and brokers, and the company still approves who hauls its freight. The payments close the loop: Wilson audits each carrier invoice against the rate confirmation and the POD before money moves, then pays carriers from the Wilson Wallet. Invoices over the rate or outside the rules wait for a person.

What stays with the team

The team decides which customers get which updates, through which channel and in what words. Wilson starts with assisted execution, and routine actions run automatically within the company's rules as the workflow is proven. Teams reach Wilson by email, Slack, Microsoft Teams, text, WhatsApp or phone. Timing depends on scope: most teams start on a few lanes and expand from there, often with the customers who ask the most questions.

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.

FAQs

Can Wilson send customers tracking updates?

Wilson, by Cartage, an AI logistics agent, can send customers and consignees updates by email or SMS where configured. It tracks each load with the best source available, confirms changes with the carrier and tells the customer about exceptions such as delays if the company sets it up that way. Every update is saved on the shipment record.

What updates should a customer get for every shipment?

At minimum, a pickup notice with the tracking number and estimated delivery, a delay notice when the carrier confirms a change and a delivery confirmation. Some customers also want the POD, an appointment notice or an out-for-delivery message. Agree on the list with each customer.

Should we send customers the carrier's tracking link?

Yes, in the pickup notice. A tracking or PRO number lets the customer check without writing in. It does not replace the delay and delivery updates, because carrier tracking pages often go quiet for hours and do not explain what a gap means.

How quickly should a delay update go out?

As soon as the carrier confirms the new date or time. Waiting until the original date has passed leaves the receiver planning for a truck that will not come. Sending before confirmation risks a false alarm.

Who should receive tracking updates at the customer?

Usually more than one person. The buyer wants to know it shipped and whether it is late. Receiving wants appointment and delivery times. Accounts payable may want the POD. Ask each customer and keep the list on their record.

Should updates go by email or text?

Email suits buyers and anything with an attachment. Text messages suit receivers on the floor and urgent changes. Many customers want both for different events.

What if the tracking feed and the carrier say different things?

Trust what the carrier confirms, and check before telling the customer anything. Send the confirmed answer, not the feed's estimate.

Does Wilson replace our customer service team?

No. Wilson handles the shipment updates and the carrier follow-up behind them. The team still owns the customer relationship, decides the update rules and handles questions that go beyond the shipment.

How do we know if proactive updates are working?

Count the "where is my order" emails and calls before and after. If they drop for most customers but not some, check those customers' recipients, channel and the details included in each update.

Sources

Let's review the "where is my order" emails your team answers. You don't need to prepare anything: Cartage maps the workflow with you on the call.

Add Cartage as a preferred source on Google