The Carrier Did Not Answer. Make the Demo Prove the Second Ask

Key Takeaways

A carrier follow-up demo passes or fails on the second attempt: what the software does after the first pickup-confirmation request goes unanswered.
Stage the silence yourself, with one booked load, a carrier inbox and phone line your team controls, and your follow-up rule written down before the demo starts.
Require four kinds of evidence: timing that matches your rule, a channel switch where one is configured, an entry on the shipment record, and an escalation that arrives with context.
Grade what was recorded on the shipment, not what the presenter says would happen in production.
Wilson, by Cartage, follows up by email, API, EDI where supported and phone calls where configured, records each attempt in the shipment history and escalates when the company's rules require a person.

What counts as passing the second-attempt test?

A demo passes when the software, with nobody on the vendor side touching it, sends the follow-up at the time your rule sets, moves to the next allowed channel, writes every attempt to the shipment and hands a named person a clear decision once silence has lasted too long. Anything less is a first message with a reminder attached.

The broader question of which category of software should own the follow-up is covered in which software owns the second ask. The acceptance test settles it for one product, on one of your loads, with a result you can write down as pass or fail.

Keep the test narrow on purpose: one load, one approved carrier, one silence. Testing several failures in a single run, as in making the freight AI fail in the demo, is worth doing, but when five things break at once it gets hard to say which behavior you actually saw. For the second ask, isolate it.

Pickup confirmation is the best request to leave unanswered because its silence has a deadline, the pickup window, so you can judge whether the software knew when to stop trying and ask for help.

How do you set up the non-response before the demo?

The setup decides whether the result means anything. Agree on these six points with the vendor in advance, but don't tell them exactly when you will stay quiet.

Pick a booked, unconfirmed load. Use a recent shipment with a real origin, destination, pickup window, reference number and an approved carrier from your list.
Control the carrier side. Ask that the carrier contact point to an email inbox and phone number your team owns. If vendor staff play the carrier, they tend to reply helpfully at exactly the right moment.
Write your follow-up rule as it runs today. One or two sentences is enough: when to follow up, on which channel, when to call, and when an unconfirmed pickup goes to a person. The test is whether the software executes your rule, not the vendor's default.
Agree on a compressed clock. Real intervals are usually hours. Shorten them for the demo and write the real values next to the shortened ones, so the timing check is judged against what was agreed.
Script your carrier behavior. Stay silent after the first request. Stay silent after the follow-up. Then either answer the call with a changed pickup time or let it ring out.
Run it twice if you can. Once ending in a carrier answer, once ending in escalation. One tests whether a reply becomes shipment data; the other, whether silence becomes a decision for a person.

What evidence should the second attempt leave behind?

Ask for the evidence on the shipment itself, not in a separate log or the presenter's inbox. Four kinds matter.

Timing

Note when the first request went out. The follow-up should land when your rule says, not earlier because a default fired and not later because a queue was slow. Then test the reverse: reply to the first request just before the follow-up is due. The queued attempt should be cancelled. Chasing a carrier who already answered shows the software is running a timer, not tracking the conversation.

Channel switch

If your rule moves from email to phone, the call should go to the dispatch contact on file for that carrier and mention the shipment reference, pickup address and window. If calling isn't configured for the demo environment, say so and judge only the channels that are. A follow-up that resends the same email with "Following up" on top passes the timing check and fails the context check.

Record

Each attempt should appear on the shipment with time, channel, recipient, what was asked and the outcome: no answer, voicemail, auto-reply or an answer. When the carrier answers by phone with a new pickup time, that time should replace the old one on the shipment, with who confirmed it and when.

Escalation

When your rule says silence has gone on too long, a named person should get a message in the channel your team uses, such as Slack, Microsoft Teams or email. It should state what was requested, each attempt made, how much time is left before the pickup window and what decision is needed: wait, try another contact or move the load to another approved carrier.

How should a buyer grade the edge cases?

These rules keep grading consistent when a demo lands between pass and fail.

An auto-reply or out-of-office counts as no answer. The software should keep the request open and continue the sequence.
A partial answer is not confirmation. "We'll try to get a truck there" should be recorded, and the pickup should stay unconfirmed.
A reply from a different person or in a new thread should still match. If dispatch answers from a personal address, the answer should land on the right shipment. If it lands nowhere, the second ask failed even though it was sent.
Duplicate messages fail timing. Two follow-ups sent together, or a call and an email to the same contact at once, show the sequence isn't controlled.
Vendor clicks count as manual steps. Any action by vendor staff in the test path is a step your coordinators would take. Note each one.
"It does that in production" means not shown. Record it as not demonstrated and ask to rerun that step on your own lanes.
A conditional pass needs an owner. If the behavior works but depends on configuration you would have to set up, write down what the configuration is and who on your side owns it.

Three outcomes fail the test whatever else went well: the shipment shows confirmed without a carrier confirmation, the load moves to a carrier your company hasn't approved, or the escalation arrives without the attempt history.

The second-attempt acceptance sheet

Fill in one row per check during the demo. Leave the presenter's description out of the evidence column.

Check	Ask to see	Pass	Fail
Clock start	Timestamp of the first request on the shipment	Matches what you observed	Not recorded, or recorded elsewhere
Follow-up timing	Timestamp of the second attempt	Within the agreed interval	Early, late or duplicated
Reply cancels the queue	Shipment after an early carrier reply	No further chasing	Carrier chased after answering
Channel switch	Channel used for each attempt	Follows your configured order	Same email resent, or a channel you didn't allow
Message context	Text of the follow-up or call summary	Reference, pickup address and window included	Generic "any update?"
Phone answer captured	Pickup time on the shipment after the call	New time, who confirmed it, when	Old time still showing
Escalation content	The message the person received	Request, attempts, time left, decision needed	"Carrier not responding" with no history
Carrier boundary	What happens next if nobody decides	Approved carriers only, or waits for a person	Unapproved carrier tendered

Worked example (illustrative)

Your rule: request pickup confirmation at 8:00 a.m., follow up by email at 9:00, call dispatch at 10:00, and escalate to the operations lead if still unconfirmed at 11:00, three hours before a 2:00 p.m. pickup window.

In the first run, you ignore the request and the email, then answer the 10:00 call: "Truck's running behind, pickup at 3:15." A pass shows 3:15 on the shipment, with the dispatcher's name, the call time and a note that it falls outside the original window, and the team gets the update under your notification rule. In the second run, the call goes to voicemail. A pass is an 11:00 message to the operations lead listing the three attempts, the voicemail and three hours left before the window, and asking whether to keep trying or move the load to another approved carrier.

How Wilson, by Cartage, handles the second ask

Wilson, by Cartage, is an AI logistics agent that follows up with carriers at the frequency set in the company's SOP and keeps the request open until there is a usable answer or a person decides. Traditional logistics software gives teams information. Wilson executes the work required to move shipments forward.

Channels: Wilson reaches carriers by email, API, EDI where the carrier supports it and phone calls where configured, and updates the team in Slack, Microsoft Teams, email or SMS.
Record: messages, confirmations and changes are recorded in each shipment's history, so the acceptance sheet can be filled from the shipment rather than from memory.
Escalation: when the rules say a person should decide, Wilson escalates with what was requested and what was already tried.
Carrier boundary: Wilson uses only carriers the company has approved. Rebooking from the approved list runs within the rules or waits for approval, and if no approved carrier accepts, Wilson escalates.
Control: Wilson starts with assisted execution, the company sets the approval boundaries, and the scope expands step by step as the team gains confidence.

Wilson replaces the TMS for freight execution and connects to the company's ERP or existing order data flow, so the test load can come from where your orders already live.

Bring one booked load, your written follow-up rule and a carrier inbox your team controls, and we'll run the second ask on it with you.