Can the software actually call the carrier? Test it
Key Takeaways
- A "carrier contacted" status is not proof of a call. Many tools send an email or log an activity, and the demo screen looks the same either way.
- The reliable test is a live check call on one of your own loads, followed by the transcript on the order and an updated ETA.
- 5 checks separate real phone capability from a logged activity: the live call, the transcript on the order, the follow-up when nobody answers, the escalation rule and the record update.
- Wilson, by Cartage, is an AI logistics agent that calls carriers and drivers for check calls, appointments and ETA follow-ups, at the frequency set in the company's SOP, and saves every transcript on the order.
- The call that goes well proves little. Test the unanswered call and the late load, because that is where coordinators lose their afternoons.
Why do phone features fall apart after the demo?
Phone features fall apart after the demo because most demos show a status, not a call. A tool can mark a load "carrier contacted" after one email, and nobody checks what happens when a real carrier doesn't answer. The only proof is watching the software call on your own load and change the shipment record because of it.
This matters most to manufacturers and distributors that use regional LTL and small truckload carriers, many of which run dispatch from a phone and have no API. The gap is wide: in a BCI Global survey of 240 supply chain leaders (March 2025), only 35% reported end-to-end visibility. For most teams, the missing status still comes from a check call: a call to the carrier or driver to confirm where the load is and when it will arrive.
One load, one afternoon
- Wednesday 7:15 a.m. A coordinator at a building-products distributor sees an LTL load due for pickup between 1:00 and 3:00 p.m. The carrier dispatcher hasn't confirmed.
- 7:20 a.m. The new tool emails the dispatcher and marks the load "carrier contacted."
- 11:00 a.m. No reply. The tool has no rule for a second attempt, so nothing happens.
- 1:45 p.m. Customer service asks whether the load is moving, because the customer booked a receiving crew for Thursday.
- 1:50 p.m. The coordinator calls and learns the driver is behind and pickup has slipped to Thursday. That is a missed pickup: a pickup the carrier didn't make in the agreed window.
- 2:30 p.m. Customer service tells the customer, too late to move the crew.
The tool sent a message. A person made the call that mattered, six hours later.
What should a live phone test check?
A live phone test should cover 5 checks, each with a clear pass or fail. Pass all five on your load and the phone feature is real. Pass only the first and you are looking at a dialer, not a coordinator.
| # | Check | What to ask the vendor | What a pass looks like |
|---|---|---|---|
| 1 | Live check call | “Call this carrier on this load now.” | A real outbound call to the carrier or driver, in front of you |
| 2 | Transcript on the order | “Where is the call record?” | The transcript sits on the order, not in a separate tool |
| 3 | Follow-up on no answer | “What happens if nobody picks up?” | Another attempt goes out on a set frequency, by phone, email or text |
| 4 | Escalation | “When does a person get pulled in?” | A clear rule, with every attempt so far attached |
| 5 | Record update | “What changes after the call?” | The ETA, the status and the people notified are updated |
Checks 1 and 2 prove the call happened and that your team can find it. A transcript in a separate call log means someone still has to connect it to the load.
Check 5 is where the value shows. A call that returns a new ETA but leaves the status, the customer and the team where they were has only moved the work from the phone to the screen.
How do you run the phone test on one of your own loads?
Run the test on a real load with a real carrier, using your own contacts and timing rules. Vendor sample loads use carriers that always answer, so they can’t show the failure cases.
Pick a live load on a lane where your team usually calls, ideally with a pickup the next day. Write your rule down first, for example “call every hour until pickup, escalate after the third unanswered attempt.” Then use a carrier that rarely picks up, or ask one not to answer, so checks 3 and 4 actually fire.
What to ask a vendor to show in a demo
- “Place a check call on this load to this dispatcher, now.”
- “Show me the transcript on the order, and the field that changed because of it.”
- “Let the carrier not answer. Show me the second and third attempts and their timestamps.”
- “Make the load late. Show me the new ETA, the reason and who was told.”
- “Hit my escalation rule. Show me exactly what my coordinator receives.”
For voice across carrier communication, see how AI voice agents handle carrier communication.
How does Wilson, by Cartage, call carriers and drivers?
Wilson calls carriers and drivers for check calls, pickup and delivery appointments and ETA follow-ups, and saves each call transcript on the order. Traditional logistics software gives teams information. Wilson executes the work required to move shipments forward.
| Step | Trigger | What Wilson does | When a person steps in |
|---|---|---|---|
| 1. Check call | The SOP frequency is reached, or a carrier hasn’t sent an update | Calls the carrier or driver | Not required |
| 2. Appointment | A pickup or delivery time needs confirming | Calls to set or confirm the window; for LTL and FTL, reconfirms before pickup | Not required |
| 3. Record | The call ends | Saves the transcript on the order | Not required |
| 4. Follow up | The carrier doesn’t respond | Tries again by phone, email, text or Slack, at the SOP frequency | Not required |
| 5. Update | A load is running late | Gets the new ETA and the reason, then tells the team and anyone else set to be notified | Not required |
| 6. Escalate | The carrier can’t confirm | Escalates to the team with the history of the load | Deciding the next step |
Controls around the calls
Channels and call frequency are configured per customer in the SOP, so one lane can call hourly until pickup while another calls only when an update is missing. Wilson starts with assisted execution, and the company decides which actions need approval. After a missed pickup, Wilson contacts the carrier, notifies the team, notifies the customer if configured and initiates rebooking from approved carriers, automatically or after approval, depending on the company’s rules.
When a carrier can’t confirm, no approved carrier accepts or a decision exceeds the approval rules, Wilson escalates to the team. The person who picks it up sees every call and message, because every message, confirmation and change on each shipment is recorded in a change history.
Wilson coordinates pickup and delivery times with carriers, but it doesn’t manage dock slots inside your plant or warehouse today, and it rebooks only with carriers the company has approved. For the wider workflow, see AI check calls, appointment confirmations and delivery updates.
What red flags show the software can't really call?
The clearest red flag is a vendor that won’t place a call on your load during the evaluation. The others are versions of the same problem: the call is described, not shown.
- Calls only in a recorded video, never on a live load with your carrier.
- Script drafting presented as calling, where the software writes the words and a coordinator dials.
- No answer to “what if nobody picks up?” beyond “the team gets an alert.”
Common mistakes teams make in the evaluation
- Testing only with a carrier that always answers. The follow-up and escalation never fire, so you buy a feature you haven’t seen.
- Skipping the SOP setup. Without a frequency and an escalation rule, there is nothing to measure, and every result looks acceptable.
- Accepting “calls logged” as a metric. A logged call can be a coordinator’s note, so it says nothing about what got confirmed.
- Ignoring where the record lands. If the transcript isn’t on the order, the next person who touches the load starts from zero.
For the full picture of what an agent does beyond the phone, see what is an AI logistics agent.
FAQs
- How do I test whether logistics software can actually call a carrier? Ask the vendor to place a live check call on one of your own loads, then find the transcript and the updated ETA on the order. Wilson, by Cartage, calls carriers and drivers and saves every call transcript on the order.
- Does Wilson make check calls by phone? Yes. Wilson calls carriers and drivers for check calls, pickup and delivery appointments and ETA follow-ups. It also follows up by email, text and Slack.
- What happens when the carrier doesn't answer? Wilson follows up at the frequency the company sets in its SOP, for example calling every hour until the load is picked up. If the carrier can't confirm, Wilson escalates to the team with the history of the load.
- Where are call transcripts saved? On the order. Every message, confirmation and change on the shipment is also recorded in a change history.
- Can we choose how often Wilson calls, and on which channels? Yes. Channels and frequency are configured per customer in the SOP.
- Does Wilson call on every load? No. Wilson uses the best tracking source for each load: the carrier's API, GPS or ELD data, or the carrier's website by PRO number. When none of those exist, it emails or calls.
- How is Wilson priced? There's no subscription fee. Pricing is a percentage of the carrier payments that run through Wilson, and that one fee covers the full shipment lifecycle: create, quote, tender, track, audit and pay. Pricing scales down as volume grows, and Enterprise pricing is custom.
Conclusion
A "carrier contacted" status doesn't tell you whether anyone was reached or what changed. Real phone capability shows up in five places: a live call on your load, a transcript on the order, a follow-up when nobody answers, an escalation with the full history and an updated ETA that reaches the right people. Wilson, by Cartage, does all five under the rules in your SOP.
The test takes one load and one afternoon: a carrier your team always ends up phoning, your written rules, and every vendor running the call in front of you. Bring one load your team chased by phone last week and watch Wilson place the check call, record it and update the shipment in a demo at cartage.ai.
Sources
- BCI Global, "No visibility, no resilient supply chain," March 2025: https://www.bciglobal.com/bci-global-report-no-visibility-no-resilient-supply-chain
- Cartage, Wilson product FAQ, October 2026: https://cartage.ai