Know where every load is. Without dialing a carrier.
LogAI.ai connects to Samsara and Motive ELDs, sends MacroPoint requests to non-integrated carriers, and places automated check calls when neither is available. Live ETA on every load—your dispatchers can spend their time managing exceptions, not requesting location updates.
How Tracking works
Multiple data sources, one unified timeline—every position ping, check call, and milestone event logged to the load record.
Samsara & Motive ELD Integration
Connect directly to Samsara and Motive via API. Location pings arrive every 15 minutes while a load is in transit—no manual tracking calls required for carriers running either platform.
MacroPoint Carrier Tracking
For carriers not on Samsara or Motive, MacroPoint sends a consent-based location request to the driver's cell phone. Location updates flow into the load record on the same timeline as ELD data.
Automated Check Calls
For loads without active ELD or MacroPoint coverage, the system places automated outbound check calls on a configurable schedule—every 2 hours by default. Driver responses are transcribed and attached to the load timeline.
Geofence Event Logging
Origin and destination geofences are drawn automatically from the facility address. When a driver enters or exits, the corresponding lifecycle event fires and the timestamp is locked to the load record.
Live ETA Calculation
ETA is calculated from current position, current speed, remaining drive time under HOS rules, and the destination address via PC*Miler routing. ETAs update with every position ping and are visible to dispatchers and shippers in real time.
Shipper & Consignee Status Feed
Share a live tracking link with the shipper and consignee. They see current location, lifecycle state, and updated ETA without calling your operations team or logging into your TMS.
Late ETA Alerting
When the calculated ETA pushes past the agreed delivery window, an alert fires to the dispatcher and an exception is opened in the Exception Monitoring module automatically. No manual monitoring required.
The four tracking milestones
Every tracking event maps to a lifecycle state on the load record. Milestone timestamps are used by the Exception module to calculate detention, by the Documents module to trigger POD requests, and by the Audit module to validate accessorial claims.
at_pickup
Triggered when the driver checks in at the origin facility or the ELD enters the origin geofence.
in_transit
Set when the loaded unit departs the origin facility. ETA calculation begins.
at_delivery
Triggered when the ELD enters the destination geofence or the driver checks in at the consignee.
delivered
Confirmed when the driver completes the delivery stop in the ELD app or the carrier submits EDI 214.