Check Calls Agent
Runs the check-call cadence and keeps status current.
- The check-call cadence
- Skip the call when ELD is live
- Status written to the load
- sweep128 active loads due a check this hour
- eld111 already pinged — those calls are skipped
- call17 silent; driver unreachable, Ridgeline dispatch confirms rolling
- updateLittle Rock, in transit — customer portal and EDI 214 pushed
How check calls actually get done
Voice Agent is the phone. Check Calls Agent is the job — who to call, on what cadence, and what gets written back. ELD and GPS are used first, so a driver who is already pinging does not get a 6 AM call.
Cadence per customer
Scheduled check calls go out by voice, SMS, or email on the clock each account expects.
Skip the call when the feed is live
ELD, GPS, and driver macros update the load first. The phone is only for loads that went quiet.
A ladder, not a shrug
Retry, text, dispatch, then a named person — each attempt logged on the load.
Customers kept current
Portals, EDI 214, and email updates go out without anyone retyping what the driver just said.
What changes on the tracking board
Every load gets checked. People only see the ones that actually went dark.
The morning list runs itself
Coverage is not limited to how many check calls a person can get through before the shift ends.
Drivers who are pinging are left alone
A live ELD update counts as the check. The call is reserved for silence.
Customers stop asking
Status reaches the portal and the inbox before a where-is-it email has a reason to be sent.
See it run on your freight
Bring one process that costs your team too much time. We will show you the same workflow running on Emulon, with the execution trace open.