The "where's my load?" call is the most predictable interruption in trucking dispatch. A broker doesn't know where the truck is. They call. A dispatcher stops what they're doing, looks it up, calls them back. The whole exchange takes 5 to 10 minutes and produces no value. Multiply that by 20 active loads and it becomes the reason dispatchers can't book more freight. AI Updater removes the call from the equation entirely by making sure brokers never have to ask.

How Does AI Updater Know When to Send Broker Status Updates?

AI Updater is triggered by real operational events, not by time intervals or dispatcher action. The system watches two data sources: ELD and GPS position data from integrated telematics, and geofence events generated when a truck enters or exits a defined location boundary.

When a driver's truck crosses into the pickup geofence, that's a trigger. When they leave the pickup location, that's another. Arrival at delivery, departure from delivery, the same. Between those events, ELD data provides real-time position that feeds into in-transit ETA calculations. The broker update goes out the moment the operational event happens, with accurate information, without anyone in the dispatch office doing anything.

What Are the 6 Stages Where AI Updater Sends Automated Updates?

Every load moves through six communication stages. AI Updater covers all of them:

Stages 2 through 6 require no dispatcher action. The driver's location does the triggering. The system handles the communication. The broker gets accurate updates at every stage without calling anyone.

Can Dispatchers Override AI Updater Messages Before They Are Sent?

Yes. AI Updater operates in two modes, and dispatchers can choose how much control they want to keep:

• Auto-send mode: emails go out automatically when the trigger fires. No dispatcher action required at any stage. Best for fleets with high load volume and standardized freight where the automated communication matches every situation.

• Manual approval mode: the system drafts the email and queues it for dispatcher review before sending. The dispatcher approves or edits it, then sends. Best for high-value loads, non-standard situations, or brokers who require more personalized communication.

The setting can be configured globally across all loads or per load type. A fleet might run auto-send for standard dry van loads and manual approval for oversized freight. Dispatchers always have override capability regardless of mode, and every outgoing email is logged and auditable. The AI Updater deep-dive covers the configuration options in detail.

How Does AI Updater Use ELD and GPS Data to Generate Accurate ETAs?

This is where the ETA quality difference between AI Updater and manual updates becomes most visible. When a dispatcher manually sends an ETA update, they're estimating. When AI Updater sends it, the ETA is calculated from the truck's actual current position, current speed, and remaining distance to the delivery location, pulled directly from the integrated ELD.

Datatruck's ELD integrations connect to 30+ providers including Samsara, Motive, Verizon Connect, and Geotab, pulling position data every 30 minutes. The in-transit update the broker receives reflects where the truck actually is, not where the dispatcher guessed it would be based on the departure time. When traffic or delays push the ETA back, the next in-transit update reflects the new reality automatically.

Does AI Updater Handle Broker Phone Calls as Well as Emails?

Yes. AI Updater includes two call automation capabilities alongside the email workflow:

• AI broker calls: 24/7 voice agents that handle inbound "where's my load?" calls from brokers. The agent verifies the caller, pulls real-time load status from ELD data, and provides an accurate update without transferring to a dispatcher. Escalation happens when the situation genuinely requires human judgment.

• AI driver calls: proactive outbound calls to drivers triggered by specific events, when an engine is off or idling unexpectedly, when the driver's ETA slips past the delivery window, or when a check-in doesn't register at the expected time. The system reaches out before the broker has to.

The combination of email automation and call handling means broker communication runs completely without dispatcher involvement for the vast majority of loads. Dispatchers handle the exceptions that actually require their attention.

How Does Automated Broker Communication Reduce Dispatcher Workload?

The time math is direct. A dispatcher managing 15 active loads and manually handling broker communication sends roughly 90 emails per day across 6 stages per load. At 2 to 3 minutes per email, that's 3 to 4.5 hours of communication work per day. Add inbound broker calls and the number climbs further.

With AI Updater active, that same dispatcher reviews exceptions and handles the calls that actually need human judgment. The hidden costs of manual dispatching covers how that reclaimed time translates to load volume capacity. The industry average across Datatruck customers is a 70% reduction in communication time. For a dispatcher team, that's the equivalent of adding capacity without adding headcount.

Ray Cargo scaled to 350+ trucks without proportional growth in their dispatch team. Read the Ray Cargo story.

Can AI Updater Be Customized Per Broker or Per Load Type?

Yes. Customization options include:

• Email templates per stage: each of the 6 stages has its own template, editable with the carrier's preferred language and format

• Placeholder support: driver name, load number, truck and trailer info, ETA, and other load-specific fields populate dynamically from the TMS record

• Multi-recipient configuration: multiple broker contacts can receive updates on the same load

• Timezone localization: timestamps in outgoing emails reflect the correct timezone for pickup and delivery locations

• Per-load override: auto-send can be turned off for specific loads where manual review is preferred

The template system means the communication a broker receives from a carrier using AI Updater looks like it came from the carrier's team, not from a generic automation tool. The TMS for carriers page covers how AI Updater fits into the full automated workflow from load creation through invoice. See it send a live update during a demo. Book a demo and run a load through all 6 stages.

FAQs

How does AI Updater know when to send broker status updates?

AI Updater is triggered by real operational events: ELD position data and geofence entries and exits at pickup and delivery locations. When the truck enters a pickup geofence, the check-in email goes out automatically. When it leaves, the check-out email with BOL attached goes out. Each stage triggers from what the truck is actually doing, not from a dispatcher remembering to send an update.

What are the 6 stages where AI Updater sends automated updates?

Dispatched (load assigned), check-in at pickup (driver arrives at shipper), check-out at pickup (driver departs with BOL), in transit (live ETA from ELD position), check-in at delivery (driver arrives at consignee), and check-out at delivery (driver departs with POD attached). All six run automatically once configured.

Does AI Updater handle broker phone calls as well as emails?

Yes. AI broker call agents handle inbound "where's my load?" calls 24/7 using real-time ELD data to answer accurately without involving a dispatcher. AI driver calls proactively reach out to drivers when ETAs slip or unexpected idling occurs, before the broker has to call.

Can AI Updater be customized per broker or per load type?

Yes. Each of the 6 stage templates is editable with carrier-specific language, dynamic placeholders for load-specific fields, multi-recipient support, and timezone localization. Auto-send can be toggled globally or overridden per load for situations that warrant manual review.