What is an AI check-call?
The boring definition
An AI check-call is an automated phone call placed by an AI voice agent to a driver (sometimes a dispatcher) on a freight load currently in transit, in order to capture status — location, ETA, fuel, detention, delivery — without a human dispatcher dialing the number. The AI does the asking, the listening, the back-and-forth, and the writing-it-down. The output is a structured tracking update on the load record in the broker's TMS, plus a stored audio transcript anyone can replay later.
Why brokers run them
The math is honest. A typical SMB freight brokerage runs roughly four to six check-calls per load per day, per the TIA Broker Operations Survey. A 200-load active book is 800–1,200 check-call attempts a day, each one 2 to 4 minutes if a human dispatcher does it. That's a full-time dispatcher seat absorbed into nobody's job description. AI check-calls compress that workload to roughly 30–45 seconds per call (drivers answer faster when the conversation is tight) and run continuously without a coffee break. The dispatcher recovered capacity goes into problem loads, carrier relationships, and the calls a human actually needs to make.
How it works, end to end
- Load and driver context get assembled. The AI check-call system reads the load record — origin, destination, equipment, pickup window, current status — and the driver's phone number captured at booking.
- The AI dials. Inside the configured time-of-day window (typically 8am–9pm local to the driver), the AI initiates the call via a telephony provider (Twilio, Bandwidth, Telnyx).
- Consent opens the call. Standard recording disclosure: "this is an automated check-call from [brokerage], the call may be recorded." Drivers who request do-not-call get marked and never called again.
- The AI asks the configured questions. Location, ETA to next stop, any delay, any issue. The conversational voice model handles back-and-forth, accent variation, and reasonable interruption.
- Structured answers write back to the TMS. Location and ETA push as a tracking update on the load. Detention or exception flags fire as alerts. The full transcript and audio store on the load timeline.
- The next scheduled check-call queues. Based on the load's urgency and the cadence the brokerage configured (every 4 hours, every 8, on-arrival-only, etc.).
What the AI is actually good at — and not
Good at: scheduled check-ins where the driver knows the call is coming, the questions are routine, and the answer fits a structured schema. ETA. Location. Fuel. Delivery confirmation. Detention flagging when the driver volunteers it.
Not as good at: free-form problem-solving (broken-down truck, rejected load, paperwork dispute) — the AI will escalate to a human, which is the right behavior but means the human still owns the exception work. Also not great with very heavy accents or extreme background noise (a Cummins idling next to a phone speaker is a hard environment for any voice model).
The compliance layer — TCPA, DNC, recording consent
Calls to commercial driver cell phones that the carrier voluntarily provided to the broker at booking are largely outside TCPA's consumer-protection scope — TCPA was built to stop consumer telemarketing. That said, credible AI check-call platforms enforce four guardrails as standard practice: (1) only call numbers explicitly provided at booking, (2) honor every do-not-call request on first ask, (3) open every call with a recording-consent disclosure, (4) respect time-of-day windows (typically 8am–9pm local to the driver). Brokers who follow those four haven't seen TCPA action in our research; brokers who cut corners on consent have.
What it costs
Two pricing patterns dominate in 2026:
- Per-call (standalone voice-AI platforms): ~$0.25–$1.50 per call depending on length and volume. Add up fast at 1,000 calls/day.
- Bundled into the broker TMS: included in load-priced or seat-priced pricing. Keelway AI at $799/mo includes the check-call module, so the marginal cost of running 4–6 check-calls per load is zero.
How it fits in a broker's day
The cleanest deployment we've seen: AI check-calls handle the routine scheduled workload — every 4 hours during transit, on-arrival at pickup, on-arrival at delivery. Dispatchers handle everything that doesn't fit that schema: problem loads, driver-relationship calls, the inbound "hey what's going on with my load" calls from shippers, the post-pickup and pre-delivery coordination. Brokerages running this pattern keep the same dispatch headcount and cover meaningfully more loads with the recovered capacity.