No category
The carrier replied by email. Did the shipment record change?
Key Takeaways
A carrier email can change the plan without changing the record. A new pickup time, a revised ETA or an added charge sits in one inbox while the record shows the old plan.
5 carrier replies should always update the record: tender acceptance or decline, pickup changes, ETA changes, charges and delivery confirmation.
The cost shows up downstream: customer service promises the old date, nobody reconfirms the new pickup, and accounts payable gets a charge nobody recorded.
Wilson, by Cartage, is an AI logistics agent that reads carrier replies, records the change on the shipment, takes the next step and notifies the people the company has chosen.
The test for any tool: forward a real carrier email and see whether the record and next action change with no retyping.
Why does the shipment record fall behind carrier emails?
The shipment record falls behind because carrier replies arrive as emails and calls addressed to one person, while updating the record is a separate manual step. When that person is busy or reading on a phone between meetings, the reply changes the plan but not the record. Everyone else keeps working from the old version.
This hits hardest at manufacturers and distributors that move freight with their own carriers and coordinate it through inboxes and spreadsheets. Every carrier follow-up (a message or call chasing a carrier for an answer) can produce a reply that moves a date, a time or a cost. Visibility is already thin: in a March 2025 survey of 240 supply chain leaders, BCI Global found only 35% reported end-to-end visibility. When the record lags the inbox, even that visibility is wrong.
One load, one email, three wrong decisions
Here's a single full truckload (FTL) shipment. Times and amounts are for example.
Monday 2:15 p.m.: the coordinator tenders the load, formally offering it to a carrier at an agreed price, for a Tuesday 10 a.m. pickup. The carrier accepts and sends the rate confirmation, the document that records the agreed rate and pickup and delivery details. The booking, the carrier's confirmed commitment, goes into the spreadsheet.
Monday 6:50 p.m.: the carrier dispatcher emails: "Driver out of hours. Can do Wednesday 7 a.m. Detention after 2 hours at $75 an hour." The coordinator replies "OK" from her phone.
Tuesday 8:30 a.m.: customer service sees a Tuesday pickup in the spreadsheet and tells the customer the order ships today.
Wednesday 7:00 a.m.: the truck arrives, the dock has planned other work, and loading takes three hours.
Two weeks later: the invoice includes detention, an accessorial (a charge for a service beyond the base rate). AP finds no detention on the rate confirmation and holds the invoice until the coordinator digs up the email.
One reply produced a wrong customer promise, an unprepared dock and an invoice dispute, because it never reached the record.
Which carrier replies should update the shipment record?
Five types of carrier replies should update the record every time: tender acceptance or decline, pickup changes, ETA changes, charges and delivery confirmation. Each changes a field someone else depends on and triggers a next step.
Carrier reply | What changes on the record | Next step it triggers | Who relies on it |
|---|---|---|---|
Tender acceptance or decline | Carrier and booking status | Confirm the pickup, or tender to the next approved carrier | Coordinator, customer service |
Pickup change | Pickup date and window | Reconfirm with the carrier; tell the dock and customer | Dock, customer service |
ETA change | Delivery ETA and reason | Update the consignee and team | Customer service, sales |
Charges | Expected cost and accessorials | Check against the rate confirmation | Accounts payable |
Delivery confirmation | Status: delivered | Request the POD | Billing, accounts payable |
The POD, or proof of delivery, is the signed document showing the consignee received the freight. Billing and claims depend on it.
Not every reply is a change. “Checking with the driver” belongs in the history but shouldn’t overwrite a date, and “should be there tomorrow” needs one more follow-up for a specific time. Phone calls count too: a dispatcher who gives a new time on a call has changed the plan as much as one who emails it.
What goes wrong when the record isn't updated?
When the record isn't updated, the team decides on a plan that no longer exists, and the cost appears in customer service, at the dock and in accounts payable. A pickup that moved by email doesn't get reconfirmed, which raises the risk of a missed pickup, meaning the carrier doesn't arrive within the agreed window.
Common mistakes
Treating the inbox as the record. When the coordinator is out, nobody can answer "what did we agree?"
Updating the date but not the reason. The team can't separate carrier-caused delays from its own, which weakens detention disputes and carrier reviews.
Agreeing to charges by reply without recording them. The invoice arrives weeks later with a charge AP can't match.
Overwriting instead of logging. The original plan disappears, so nobody can show the carrier what changed.
Updating the record but not the people. The customer still hears the old date.
How does Wilson, by Cartage, keep the record in step with carrier replies?
Wilson reads each carrier reply, records the change on the shipment, takes the next step and tells the people the company has chosen. Traditional logistics software gives teams information. Wilson executes the work required to move shipments forward.
The reply and the record live in one place. Wilson replaces the TMS as both the system of record and the execution layer, and it connects to the company’s ERP. Carriers reach Wilson by email, phone or API, plus EDI where supported, and Wilson has its own email address, like a new hire.
Step | Trigger | What Wilson does | When a person steps in |
|---|---|---|---|
1. Read | A carrier replies by email, phone, API or EDI | Reads the reply on its shipment | Not required |
2. Record | The reply changes the plan | Updates pickup, ETA, status or expected cost | Not required |
3. Reconfirm | A pickup time moved | Confirms the new window and reconfirms it before pickup | If the carrier can’t confirm |
4. Act | The carrier declines or misses the pickup | Moves to the next approved carrier, or contacts the carrier and initiates rebooking | Above the approval rules, or if no approved carrier accepts |
5. Notify | The change affects others | Updates the team in Slack or Microsoft Teams, the shipper by email, the consignee by email or SMS | Not required |
6. Close | The load delivers | Requests, follows up on and files the POD | If the POD is missing past the set window |
When an ETA slips, Wilson gets the new ETA and the reason for the delay and tells everyone the company has set to be notified.
Approval rules. Wilson starts with assisted execution. The company decides which actions need a person, such as bookings or rebookings above a cost threshold, carrier selections or customer notifications. Actions within the rules proceed; the rest wait, and autonomy expands step by step. Charges added by reply are checked again at invoice time, because Wilson audits and reconciles each invoice against what was booked before paying.
Escalation and history. Wilson escalates when a carrier can’t confirm, when no approved carrier accepts, or when a decision exceeds the approval rules. Every message, confirmation and change is recorded in the change history, and call transcripts are saved on the order. ERP write-back is optional: a CSV or Excel file by email, a shared table, or an API where available.
What Wilson doesn’t do here. It books only carriers the company has approved. It coordinates pickup times with carriers but doesn’t manage dock slots inside the facility today, so the dock hears about a moved pickup through the notifications the company configures.
What should you ask a vendor to show in a demo?
Ask the vendor to process one of your real carrier emails live and watch whether the record, the next action and the notifications change with no retyping.
What to ask a vendor to show in a demo
Forward a carrier email with a new pickup time. Show the pickup field change and the reconfirmation go out.
Open the change history. Show the old value, the new value, the message that caused it and the time.
Send a reply that adds an accessorial. Show where it’s recorded and how it’s checked when the invoice arrives.
Have a carrier decline by email. Show what happens next and which approval rule applies.
Let a carrier go silent. Show when the tool calls, how often and when it escalates.
After go-live, compare the lanes Wilson runs with how they ran before: manual touches per load, missed pickups and time from exception to notification. See also who owns the next step after a carrier replies and when the carrier email and tracking feed disagree.
FAQs
How do I make sure carrier replies update the shipment record? Send replies to the system that runs the shipment. Wilson, by Cartage, reads carrier replies, records the change, takes the next step and keeps every message in the change history.
Which carrier replies should update the record? Tender acceptance or decline, pickup changes, ETA changes, charges and delivery confirmation. Status messages without a firm time go in the history but shouldn't overwrite dates.
Does Wilson read carrier emails? Yes. Carriers reach Wilson by email, phone or API, plus EDI where supported, and Wilson acts on the reply under the company's rules.
What if the carrier calls instead? Wilson calls carriers and drivers for check calls, appointments and ETA follow-ups, and call transcripts are saved on the order.
Is there a record of what changed? Yes. Every message, confirmation and change on each shipment is recorded in a change history.
Who gets told when a carrier moves a pickup? Each company chooses who's notified and how: typically the team in Slack or Microsoft Teams, the shipper by email and the consignee by email or SMS.
Does Wilson update our ERP? Yes, if the company wants it. Write-back is optional and set up per customer.
How is Wilson priced? There's no subscription fee. The company preloads a wallet, Wilson pays carriers from it after each invoice is audited and reconciled, and pricing is a percentage of those payments, covering create, quote, tender, track, audit and pay.
Conclusion
A carrier reply only helps if it changes the record everyone else works from. Otherwise customer service promises the wrong date, the dock isn’t ready and AP disputes a charge someone already agreed to. Treat five reply types as record changes, log the reason with each one and push the update to the people who depend on it. For how an agent runs this work end to end, see what is an AI logistics agent?
Wilson, by Cartage, does this as part of running the shipment: it reads the reply, updates the record, reconfirms or rebooks under your rules and notifies the right people, with every step in the change history. Bring one carrier email that moved a pickup last week and watch Wilson update the record and reconfirm the carrier in a demo at cartage.ai.
Sources
BCI Global, March 2025: https://www.bciglobal.com/bci-global-report-no-visibility-no-resilient-supply-chain
Cartage, Wilson product FAQ, October 2026: https://cartage.ai
Other latest news and success stories
January 25, 2022
Best AI Tools for Carrier Follow-Up in 2026
Read more →
January 25, 2022
Best Bill of Lading (BOL) Software for Manufacturers in 2026
Read more →
