Blog

Check Call Automation That Skips Loads Already on Tracking

By Connor Miller, Founder and CEO, FreightScout. Last updated 17 October 2026.

Check call automation that skips loads already on ELD or GPS tracking works on one rule: when the truck is on pace and the ping is live, the ping stands in for the routine in-transit call. It still makes the call before every appointment, it calls when the data goes quiet, and it never marks a truck arrived or loaded off a geofence. Everything else is noise you're making a driver pick up.

That's the whole post in one paragraph. The rest is why it matters, and why "automate check calls" has started to mean "call every truck every two hours from a number the driver learns to ignore."

Why are carriers blocking automated check calls?

Because a lot of them are getting called for nothing.

The truck is moving. The ELD is pinging. The driver accepted tracking at dispatch. And the phone still rings every couple of hours asking where they are. A human rep wouldn't do that, or at least wouldn't do it twice, because the driver would tell them about it. Software doesn't hear that. It just dials again.

You can watch this play out on the broker forums right now: drivers and dispatchers saying they block the numbers, brokers in the same threads saying the calls should stop once tracking is on. Both sides are right. A driver who gets called every two hours stops answering. Then the one call that actually matters, the one the night before a tight delivery, goes to voicemail.

FreightScout comes from 12 years in the business and a brokerage agency scaled into nine figures. On a real floor, the call is worth something because it doesn't happen for no reason. Software that forgets that burns the carrier relationship your reps spent years building.

What should check call automation do when a truck is already on tracking?

Let the ping do the boring part. Keep the call for the parts a ping can't answer.

Here's the rule FreightScout runs, word for word: "Check calls run from pickup to delivery on a cadence set by transit time. When the truck is on pace, the ping stands in for the call. The last check before an appointment is always a call. Nothing gets marked arrived or loaded off a geofence."

Break that down the way a floor actually runs it:

Cadence comes from transit time, not a timer. A short same-day run with a live ping might not need anything between pickup and delivery. A multi-day run needs a check that lands each day.
On pace and pinging means no routine call. The dot is where it should be. Calling to ask "where are you" wastes the driver's time and yours.
The last check before an appointment is a call. Pickup or delivery. You want a person saying they'll make it, or saying they won't, while there's still time to call the receiver and your customer.
A geofence isn't proof. It says a truck crossed a line on a map. It doesn't say the driver checked in, that the dock took them, or that they're loaded. The driver says so, or it didn't happen.

That last one protects your money too. The detention clock should start on a real check-in, not on a dot. FreightScout starts it when the driver texts check-in.

When should a tracked load still get a call?

When the data goes quiet, or stops making sense.

A stale ping. An unplanned stop. A truck off route or behind pace. A reefer out of range. None of those are "skip the call" situations. They're the moment you need a person on the phone, and how much time is left decides how fast. Plenty of slack can get a text. A tight clock gets a call right now, and your rep should hear about it at the same time.

So "skips loads on tracking" doesn't mean "ignores loads on tracking." It means the tracked load earns a call only when something about it changed. A load that goes quiet gets a check call from FreightScout. A load that's on pace doesn't.

What does a ping still not tell you?

A ping tells you where the truck is. It doesn't tell you:

the driver is about to run out of hours
the receiver pushed the appointment
the trailer was loaded short
the seal number doesn't match the BOL
the driver has been sitting at the dock for three hours and nobody's taken them

Those come from a person saying so. That's why the answer isn't "tracking replaced check calls." It's "tracking replaced the check calls that were only asking for a location."

The tracking your customer requires stays. Check call automation isn't a tracking platform. It sits next to whatever your customer already mandates and decides when a human conversation is actually needed.

How do you set this up so drivers don't tune you out?

Front-load the work and make every call count.

Get tracking accepted at dispatch. The call before dispatch prevents most of the surprise calls later. FreightScout runs it in the same order every time: photos, then tracking, then the address. If tracking's accepted up front, the in-transit calls can mostly disappear.

Ask the same questions in the same order. Where are you, are you loaded and does the BOL match, what time will you be at the receiver, do you have the hours, anything I should know. Same order every load, so the answers can be compared and logged.

Ask in the driver's language. A Spanish-speaking driver gets the same call, in the same order, in Spanish, and the texts after it too. That's how FreightScout runs it, and it's the simplest way to get a straight answer instead of "yes, yes, fine."

Bring back the answer and the customer email together. If the driver's late, the reason and the new ETA come back with the delay email to the customer already drafted, so your rep sends it with one click. Same for the pre-detention notice and a re-cover.

Hand the exceptions to a person. No answer, detention, mechanical trouble and shipper heat go to a rep. The routine dial and the note don't.

What gets written back to the TMS?

The note from the call lands on the load in the TMS your team already logs into, McLeod, Aljex, Tai, or whatever you run, so nobody re-keys it. The TMS stays the system of record.

How it connects: by API where the TMS offers one, and by reading it in place where it doesn't, set up during implementation.

Track runs supervised by default, and every action is logged and reversible.

How do you know the automation isn't over-calling?

Three things to watch in the first couple of weeks.

Calls per load on healthy trucks. If on-pace, pinging loads are still getting routine in-transit calls, the rule isn't on.

Pre-appointment coverage. Every pickup and delivery should have a real call before the appointment. If those are getting skipped because "tracking's on," you've cut the wrong calls.

Quiet-truck response time. When a ping goes stale, how long until someone (or something) is on the phone? That's the number that keeps the shipper from calling you first.

If those three look right, drivers stop getting calls they don't need, and they pick up the ones they do.

What this is not

It's not a tracking platform, and it doesn't replace the one your customer requires. It's not a TMS and not a load board. It doesn't mark a truck arrived because a dot crossed a line. And it doesn't replace the rep on the call that actually needs judgment. Automate the friction, not the relationship.

FAQ

What is check call automation that skips loads already on tracking?

It's check call software that lets a live, on-pace tracking ping stand in for the routine in-transit call, while still calling before every appointment and whenever the data goes quiet. FreightScout runs check calls that way: cadence set by transit time, ping stands in when the truck's on pace, last check before an appointment always a call.

Can an ELD or GPS ping replace a check call?

For the routine in-transit check, yes, when the truck's on pace and the ping is fresh. It can't replace the call before an appointment, and it isn't proof of arrival or loading. A geofence only says a truck crossed a line on a map.

Why do drivers stop answering broker check calls?

Usually because they're getting called when nothing has changed. A driver who gets called every two hours stops answering, and then the call that matters goes to voicemail. Cutting the calls the ping already answers is how you keep the important ones getting picked up.

When should a tracked load still get a check call?

Before every pickup and delivery appointment, and any time the data goes quiet: a stale ping, an unplanned stop, a truck off route or behind pace, or a reefer out of range.

Does FreightScout replace our tracking provider?

No. The tracking your customer requires stays. FreightScout places the check calls, captures the spoken update and the POD, writes the note back to the load, and escalates exceptions to a person.

How do check call notes get into McLeod, Aljex, or Tai?

The note lands on the load in the TMS your team already uses. By API where the TMS offers one, and by reading it in place where it doesn't, set up during implementation. The TMS stays the system of record.

Does the detention clock start off the geofence?

No. FreightScout starts the detention clock when the driver texts check-in, not when a dot crosses a line.

Book a demo: see how FreightScout decides which loads get a call and which ones the ping already covers. Book a demo

All posts: the blog index.