Sales asks logistics for shipment status all day. How do we stop the interruptions?
Short answer
Send sales the update before they have to ask. Pick a few key moments, like pickup confirmed, picked up, delayed and delivered. Send each one to the rep who owns the order, in their usual chat tool. Only send status the carrier has confirmed. Most questions stop once reps trust these updates. Wilson, by Cartage, an AI logistics agent, sends these milestone updates in Slack, Teams or email.
Book 15 minutes with the team →Sales asks logistics for shipment status all day. How do we stop the interruptions?
It is Tuesday at a building products manufacturer. Before 10 a.m., the logistics coordinator has answered nine messages from sales. "Did PO 4471 ship?" "My customer says the truck never came." "Can you check on the Denver order?" Each question takes five to ten minutes: find the order, find the carrier, check the carrier website or call dispatch, then reply. Three of the questions were about loads that were fine. One was about a delay the coordinator already knew about but had not told sales. By lunch, the coordinator has not booked a single new load.
To stop the status interruptions, send sales a confirmed update at a few key milestones, to the person who owns the order, in the channel they already use, from one shipment record that everyone trusts. When sales hears about pickups, delays and deliveries before its customer asks, most questions never get sent. The remaining questions get faster answers, because the record already has them.
Asking sales to "check the system first" rarely works on its own. Sales asks a person because the system has not given it an answer it trusts. The fix is to give sales that answer at the right moment, without being asked.
What the interruptions really cost
Each status question looks small. Together, they take a large part of the logistics day. The cost is not only the time to answer. It is the switch away from booking, quoting and exceptions, and the time to get back into that work. A coordinator who answers 30 status questions a day has little time left for the work that keeps freight moving.
Sales pays too. A rep who waits an hour for an answer cannot give the customer one. A rep who hears about a delay from the customer looks unprepared.
A hypothetical week of questions
Consider a hypothetical log of status questions that sales sent to logistics in one week. Sorting them by type shows where the fix should start.
| Type of question | Count in the week | Already known by logistics? | Milestone that would have answered it |
|---|---|---|---|
| "Did it ship?" | 42 | Yes | Picked up |
| "When will it arrive?" | 31 | Mostly | Picked up, with expected date |
| "Customer says it's late" | 9 | Yes, for 7 of 9 | Delay or change |
| "Can I get the POD?" | 12 | Yes | POD filed |
| "Is the pickup booked?" | 15 | Yes | Pickup confirmed |
In this example, almost every question had an answer that logistics already knew. The work was not finding new information. It was passing known information to the right person at the right time. That is the part to fix first.
Who should own the fix
The fix sits between logistics and sales, so it needs an owner from each. Logistics owns the status: what happened, when and from which source. Sales owns what it needs to know and when it tells the customer. Agree on both before setting anything up. The broader pattern is covered in freight communication automation, which explains why "where's my order?" is a coordination problem, not a customer service one.
Want to see which questions could stop?
Let's review the status questions your sales team sent last week. 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.15 minutes with the team behind Wilson. No prep needed.
Book 15 minutes →Why does sales keep asking logistics for status?
Sales asks logistics for status because it cannot find a trusted answer anywhere else, and because its customers ask first. Each reason below points to a part of the fix.
Sales has no view of the shipment
Many sales teams can see the order in the ERP but not the shipment. The ERP may show "released" or "shipped" without a carrier, a pickup time or a delivery date. The detail lives in the logistics team's email, carrier websites and spreadsheets.
The ERP status is stale
When the ERP does show shipment status, it may be hours or days behind. If someone updates it by hand at the end of the day, a rep checking at 11 a.m. sees yesterday's picture. After a few wrong answers, reps stop checking and ask a person instead.
The customer asked
Most status questions start with a customer. The customer's receiving team wants to plan the dock, or its buyer wants to know if a stockout is coming. The rep is passing the question along. If the rep had heard first, the question would not have reached logistics.
Nobody told sales about the delay
Logistics often knows about a problem before sales does: a missed pickup, a truck breakdown, a weather delay. If there is no rule for telling sales, the rep hears it from the customer. After that happens a few times, reps start checking on every order, just in case. The guide on when a freight delay should reach production or sales covers how to set that rule.
Different people give different answers
If one coordinator says the load picked up and another says it has not, sales stops trusting either answer and asks again later. That is a record problem, not a communication problem. The guide on keeping one shipment record when two people get two answers goes deeper.
Sales does not know who to ask
On a team where several coordinators handle loads, a rep may ask whoever answered last time. That person then has to find the right coordinator. The question gets handled twice.
Which updates should sales get, and when?
Sales should get a short, confirmed update at the few milestones that change what it tells the customer. More messages do not mean better information. Too many updates train people to ignore them.
The milestones that matter
Most sales teams need to hear about:
- Pickup confirmed. A carrier has accepted the load and confirmed the pickup date and time.
- Picked up. The freight left the dock, with the carrier and the expected delivery date.
- Delay or change. Anything that moves the delivery date or puts it at risk, with the new date if known and what is being done.
- Delivered. The freight arrived, with the delivery time.
- POD filed. The signed proof of delivery is on file, which matters for invoicing and disputes.
Some teams also want a note when a pickup is missed or a carrier cancels, even if a new carrier is found quickly. Others only want to hear when the delivery date changes. Decide this with sales.
Milestones in one table
| Milestone | Who gets it | What it says | Why sales cares |
|---|---|---|---|
| Pickup confirmed | Rep who owns the order | Carrier, pickup date and time window | Can tell the customer the order is scheduled |
| Picked up | Rep who owns the order | Pickup time, carrier, expected delivery date | Can give the customer a delivery date |
| Delay or change | Rep, plus manager for key accounts | What changed, new date if known, next step | Can warn the customer before it calls |
| Delivered | Rep who owns the order | Delivery time | Can close the loop and follow up on the sale |
| POD filed | Rep and billing | POD attached to the shipment | Can answer delivery disputes and support invoicing |
Who gets each update
Send each update to the person who owns the order, not to a group channel where every rep sees every load. A rep with 40 open orders does not want 2,000 messages a week about orders that belong to others. If the company uses account managers or customer service reps, route updates to whoever talks to that customer.
For key accounts, a manager may also want delay updates. Write that as a rule by customer, not as a habit.
Where updates should go
Send updates where sales already works. For most teams that is Slack, Microsoft Teams or email. A separate tracking portal that reps must log into adds a step, and many will skip it. Keep the format short: order number, customer, milestone, time and one line on what is next.
How many messages is too many
A useful test is the number of messages a rep receives per order. Three to five per order, from pickup confirmed to POD, is easy to read. If a rep gets ten messages for one load, some of them are noise. Delays are the exception: when a load is in trouble, the rep may need an update each time the plan changes. Even then, each message should say something new.
Some reps prefer one short summary at the start of the day for their open orders, plus immediate messages only for delays. That can work well for reps with many small orders. Let each sales team choose, but keep the delay messages immediate.
What a good update looks like
Consider a hypothetical update for the Denver order:
"PO 4471, customer Denver DC. Picked up today at 2:15 p.m. by the approved carrier. Expected delivery Thursday by noon. Appointment confirmed for Thursday 8 to 10 a.m."
And a delay update:
"PO 4471, customer Denver DC. Carrier reports a mechanical delay in Nebraska. New expected delivery Thursday afternoon. The 8 to 10 a.m. appointment is being moved. Next update once the new appointment is confirmed."
Both tell the rep what to tell the customer. Neither needs a follow-up question.
How do you set up status updates that sales trusts?
Set up updates in a fixed order: one shipment record, agreed statuses, confirmation before sending, routing to the right person and a status in the ERP that matches. Skip a step and sales will go back to asking.
Step 1: Keep one record per shipment
Every update should come from the same shipment record: the order, the carrier, the booking, every status event with its time and source, and the documents. If logistics updates a spreadsheet, the ERP and an email thread separately, the three will drift and sales will get three answers.
Step 2: Agree what each status means
"Shipped" can mean the order was released, the BOL was printed or the truck left. Agree on a short status list and what each one means. Picked up should mean the carrier has the freight, not that the dock printed a label.
Step 3: Confirm before you send
Status should come from a source you can name. The carrier's API or EDI feed, GPS or ELD data the carrier shares, the carrier's website by PRO number, or a direct answer from dispatch or the driver. An estimate is useful, but call it an estimate. The guide on asking the carrier before you tell the customer covers this step.
Step 4: Route to the order owner
Each order needs a named owner on the sales side. Usually that comes from the ERP's sales order. Updates go to that person. If the owner is out, a backup is named.
Step 5: Update the ERP status
Many reps will still look in the ERP. Make sure the shipment status there matches the record. How much can be written back depends on the ERP and the setup. Even a simple status and delivery date in the ERP cuts many questions.
Step 6: Make questions easy to answer
Some questions will still come. Give sales one place to ask, and make sure the answer comes from the record. A question asked in a chat channel and answered from the record is far faster than a question that sends a coordinator to three websites.
Step 7: Measure the questions
Count status questions from sales for a week before the change and a few weeks after. Look at which questions still come. Each one points to a missing milestone, a wrong owner or a status that was not trusted.
A simple rollout plan
Start with one sales team or a few key customers. Agree the milestones and the owner for each order. Run the updates for two or three weeks while logistics still answers questions as usual. Then sit down with the reps. Ask which updates they used, which they ignored and which questions they still had to send. Adjust the milestones, the wording and the routing. Then add the next sales team.
Do not switch off the human answer on day one. Reps will test the updates against what logistics tells them. Once the two match for a few weeks, reps start trusting the updates and the questions drop on their own.
The same fix helps other teams
Sales is rarely the only team that asks. Customer service, the warehouse, production planners and finance all send status questions too, each with a slightly different need. The warehouse wants to know which trucks arrive today. Planners want to know when inbound material lands. Finance wants to know what delivered by month end. Once the shipment record and the milestone updates work for sales, the same setup can serve these teams with their own short list of milestones. Start with sales, because it usually sends the most questions, then add the next team.
Plan for customers who want direct updates
Some customers will ask to get updates directly instead of through the rep. That can cut questions further, but it changes who speaks to the customer. Agree with sales which customers get direct updates, by which channel, and which messages still go through the rep first, such as a delay on a key account.
What goes wrong when you push status updates to sales?
Most failures come from too many messages, unconfirmed status, the wrong recipient or a record that does not match the ERP. Each one sends sales back to asking a person.
Mistake 1: Sending every event
If reps get a message for every carrier scan, they stop reading. Send only the milestones that change what they tell the customer.
Mistake 2: Sending estimates as facts
An ETA from a map can be wrong. If sales tells the customer "Thursday by noon" based on an estimate, and the truck arrives at 4 p.m., the rep loses trust in the updates. Label estimates and confirm with the carrier before a delivery date goes to the customer.
Mistake 3: Telling sales about a problem with no next step
"Load delayed" with no new date and no owner creates a new question. Every delay update should say what is being done and when the next update will come.
Mistake 4: Sending to the whole sales team
Group channels with every load quickly become noise. Route each update to the person who owns the order.
Mistake 5: A new portal nobody opens
Asking reps to log into one more tool usually fails. Send updates to the channel they already use.
Mistake 6: The ERP says something else
If the update says delivered and the ERP still says open, the rep does not know which to believe. Keep the ERP status in line with the record, as far as the setup allows.
Mistake 7: Logistics still answers by hand
If coordinators keep answering questions from memory, their answers will not always match the updates. Answer from the record, every time.
A short decision guide
| Question sales keeps asking | Likely gap | Fix |
|---|---|---|
| "Did it ship?" | No picked-up update | Send a picked-up milestone to the order owner |
| "When will it arrive?" | No expected delivery date | Include the expected date in the picked-up update |
| "Why didn't you tell me it was late?" | No delay rule | Send delay updates with the new date and next step |
| "The ERP says it's still open" | ERP status out of date | Update ERP status from the record, as the setup allows |
| "Who do I ask about this order?" | No owner | Name the logistics owner on each shipment |
| "Can you send me the POD?" | POD not shared | Send a POD-filed update with the document attached |
How does Wilson, by Cartage, keep sales updated without asking logistics?
Wilson, by Cartage, is an AI logistics agent that quotes, books, tracks, audits and pays freight for manufacturers and distributors, and it sends status updates at milestones from the same shipment record the logistics team uses. Traditional logistics software gives teams information. Wilson executes the work required to move shipments forward. Think of it as a free logistics department: what big shippers build over years, Wilson does from day one, in four parts.
The labor. Wilson does the work from the first quote to the final POD: quotes, bookings, paperwork, tracking and carrier follow-ups, by email, phone calls, texts, Slack and Microsoft Teams. Wilson tracks each load with the best source available: 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 can call or text a driver directly when it has the driver's number. Wilson updates the team in Slack, Microsoft Teams, email or SMS at milestones. When something goes wrong, such as a missed pickup, a cancellation or a delay, Wilson contacts the carrier, tells the team and tells the customer if configured. It requests and files PODs. Who on the sales side gets which update depends on the setup.
The data. Wilson keeps every order, load, quote, rate, document and contact on record as it works, connected to the company's ERP. Wilson replaces the TMS for freight execution and connects to the company's ERP. Every message, confirmation and change is kept in the shipment's change history, so the answer a rep gets matches what the logistics team sees. People can reach Wilson by email, Microsoft Teams, Slack, WhatsApp, text or phone. Writing status back to the ERP depends on scope.
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.
The network. Wilson gets better freight rates on every lane because the shipper's volume counts with every other Wilson customer's. The network includes carriers and brokers. The company still approves who hauls its freight.
The payments. Wilson audits every 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.
Control stays with the company. Wilson starts with assisted execution, the company sets approval limits, and routine actions can run automatically within those rules as the workflow is proven.
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.
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.15 minutes with the team behind Wilson. No prep needed.
Book 15 minutes →FAQs
Can Wilson keep our sales team updated without asking logistics?
Wilson, by Cartage, an AI logistics agent, tracks each load and updates the team in Slack, Microsoft Teams, email or SMS at milestones, from the same shipment record logistics uses. Which reps get which updates depends on the setup. The goal is that sales hears about pickups, delays and deliveries before it has to ask.
Why does sales keep asking logistics where orders are?
Usually because sales cannot see the shipment, the ERP status is out of date or a customer asked first. Reps also ask when they have heard about delays from customers before hearing from logistics.
Which shipment updates should sales receive?
Pickup confirmed, picked up, delay or change, delivered and POD filed cover most needs. Agree the list with sales so updates match what reps tell customers.
Should every rep see every shipment update?
No. Send each update to the person who owns the order, plus a manager for key accounts if needed. Group channels with every load turn into noise.
Should we give sales a tracking portal?
Most reps will not log into another tool. Sending updates to Slack, Microsoft Teams or email works better because it reaches them where they already work.
How do we stop sending wrong ETAs to sales?
Confirm status with the carrier before a delivery date goes to the customer, and label estimates as estimates. A wrong date damages trust in every update that follows.
Can Wilson write shipment status back to our ERP?
Wilson connects to the company's ERP. How much shipment status is written back depends on the ERP, the data flow and the scope agreed at the start.
What if a rep still has a question?
People can reach Wilson by email, Microsoft Teams, Slack, WhatsApp, text or phone. The answer comes from the shipment record, so it matches what the logistics team sees.
How do we know if the interruptions are going down?
Count status questions from sales for a week before the change and for a few weeks after. Look at which questions still come in, and fix the missing milestone or owner behind each one.
Who should own shipment updates to sales?
Logistics owns the status: what happened, when and from which source. Sales owns what it needs to know and what it tells the customer. Name an owner on each side before setting up any updates.
Does Wilson tell our customers about delays too?
When configured, Wilson tells the customer about exceptions by email or SMS. Whether customers hear directly or through the sales rep is the company's choice.
Sources
- Cartage, Wilson product FAQ and product scope, October 2026: https://cartage.ai
Let's review the status questions your sales team sent last week. You don't need to prepare anything: Cartage maps the workflow with you on the call.
