Meet Trace Live
A tracking agent that works the loads going wrong
Trace runs on live Load Market tracking and alerts in the FreightVero TMS. It chases the quiet trucks and the late ETAs, so your desk starts with the answer instead of a call list.
Every FreightVero agent drafts. A person on your team approves anything that changes a load or reaches a customer or carrier.
Short answer
Trace is the Tracking agent in the FreightVero TMS. It watches live tracking for loads that go quiet, run late or never accept tracking, pulls the carrier, the driver, the last known position and the ETA, and drafts the follow-up to the carrier’s dispatcher. Your dispatcher sends it, and the reply is logged on the load. Trace works in writing, where there is a record.
The job today
Track and trace in logistics still runs on check calls. Someone on the desk works down the list of loads in transit: call the dispatcher, ask where the driver is, write it in the notes, update the ETA, move on. Loads that are fine get the same call as loads in trouble.
The expensive ones are the loads nobody calls in time. A driver’s phone dies at noon and tracking stops. By the time anyone notices, the delivery appointment is gone and the customer is the one asking.
In the FreightVero TMS, part of that job is already handled. A tracking request goes to the driver’s phone from the load through Load Market, and the load shows position, ETA and risk on the live tracking list. ETA comes from the truck’s last position, measured against the carrier’s appointment: green, yellow or red. Tracking that goes quiet for 45 minutes is marked disconnected and the load turns red.
What’s left is the follow-up. That is the job Trace does.
How Trace works a load
Start from the exceptions
Trace reads the same alerts your team sees. Five conditions are checked every ten minutes: tracking red, tracking disconnected, tracking declined, a rate confirmation missing before pickup, and billing blocked. Loads that are on plan do not get chased.
Gather the context
For each exception, Trace pulls the carrier, the driver, the last known position, the current ETA and the appointment the carrier is working to.
Draft the follow-up
It writes the message to the carrier’s dispatcher asking for location and ETA, or asking the driver to reconnect tracking. Your dispatcher sends it. Nothing reaches a carrier that a person did not approve.
Log the answer
The reply is logged on the load next to the tracking history, so the next person who opens the load sees what happened.
Escalate what's still red
A load that stays red goes to the person who owns it, with the timeline attached.
What it checks, and what stays with your team
Alerts, not a call list
Trace acts on the five alert conditions the TMS checks every ten minutes. An alert raises once per load and clears itself when the condition resolves, so nobody works the same exception twice.
The carrier's appointment
ETA is measured against the carrier’s appointment, which is the time printed on the carrier’s rate confirmation, not the customer’s window. That gap is real information, and the on-time report measures the customer promise separately.
Quiet for 45 minutes is an exception
Tracking that stops for 45 minutes is marked disconnected and the load turns red. The check runs every ten minutes, so a stalled load is flagged within the hour.
The route on the map
The map on the load draws the real driving route along the roads, with pickup, delivery and the truck’s current position.
Tracking stops when the load does
Tracking ends the moment a load is marked delivered or cancelled, so nobody is tracked for days after they finished. Changing the driver mid-load moves tracking to the new driver and keeps the position history.
A person approves outbound messages
Every message to a carrier or a driver is drafted by Trace and sent by your team. That is a design choice. The carrier hears from a person who owns the load.
In writing, where there is a record
Trace works in writing, where there is a record: messages and email to the carrier’s dispatcher, logged on the load.
Checkpoints still hold
A driver confirming arrival on site in Load Market can move a load’s status. Nothing Trace does marks a load delivered without a POD and the signer’s first and last name.
What week one looks like
Turn Trace on and it starts where your exceptions are. A truck goes quiet at noon, the load turns red inside the hour, and the follow-up to the carrier’s dispatcher is written and waiting for your dispatcher to send. The loads running on plan stay quiet, which is the point. By the end of the week the tracking history on a load reads as a record: who was asked, what they said, and when.
Load Market is the live tracking connection. If your brokerage tracks through another provider, MacroPoint and project44 are planned integrations. For a broader look at the options, read our guide to load tracking and check calls.
Run Trace on your own freight
Tell us how many loads you track a week and how your team handles check calls now. We’ll put Trace on your tracking setup and you can watch it work your exceptions.
Frequently asked questions
How often does tracking update?
We don't publish a ping frequency. What we can say is how the TMS reacts: tracking that goes quiet for 45 minutes is marked disconnected and the load turns red. The check runs every ten minutes, so a stalled load is flagged within the hour.
Does the agent replace Load Market or MacroPoint?
No. Trace works on top of tracking data, and a tracking provider still supplies the positions. Load Market is the live connection in the FreightVero TMS. MacroPoint and project44 are planned integrations.
Will it call drivers?
Trace works in writing, where there is a record. It sends messages and email to the carrier's dispatcher and logs the reply on the load. If phone check calls are most of your tracking work, tell us on the scoping call so we can be straight about the fit.
Can my customers see tracking?
Tracking is visible to your team in the TMS, and a customer-facing status view belongs to the customer portal. For status emails to the customer, see the Customer Updates agent.