Autopilot
Autopilot works the load until your team actually needs to.
Autopilot handles the routine work across booking and track and trace within your SOPs, giving your team the capacity to move more freight without adding headcount.
Checkpoints, not workflows
It runs on checkpoints, not a workflow you have to build.
Autopilot arrives already knowing the load lifecycle. At each checkpoint it reads the load, the tracking and the whole conversation so far, then decides whether anything needs to happen. Sometimes the right answer is to say nothing, and it will.
Every checkpoint is written in plain English and editable. Scope one to a single shipper, exclude an order type, or turn it off for one load.
Dispatch
Carrier assignedGets the driver's number, confirms they're empty and rolling, collects an ETA to pickup, and relays pickup instructions.
Pre-pickup
Morning of pickup · 7:30 AM defaultWelcome, empty-and-rolling and tracking in one message. If tracking is already live it opens with what it can see:
noticed you're about 134 miles from pickup
.At pickup
5 minutes before the appointmentConfirms check-in. On site 30 minutes with no update, it asks for loaded status. An hour without tracking, it asks for both.
Pickup number release
Inside your distance threshold, tracking liveReleases the confidential pickup number. Only then. It won't guess one, and it won't substitute the load number.
In transit
On the cadence you setLight check-ins, refreshes stale ETAs, and asks for a tracking refresh if it's gone quiet. It doesn't ask about arrival while the truck is miles out.
Pre-delivery
Hours before the appointmentAsks
Are you on track for delivery at 3:00 PM?
when it's close, and stays broad when it isn't.At delivery
At the appointmentConfirms arrival, asks for unloaded status, and requests the POD, all pages rather than just the signed one.
Post-delivery
After the appointment passesConfirms check-out, collects the out-time, asks for the POD once, and escalates if the driver has gone silent.
Exceptions
Does everything it can until it can't.
The promise isn't that AI handles everything. It's that it handles everything up to a clean line, and that the line is visible to your team.
Brings in your rep
The reps on the load get the reason, the load and the whole thread, with one click into the conversation.
Stops talking
Autopilot stops messaging the driver on that checkpoint until a person responds. It never talks over your team.
Writes it down
The escalation lands in the load thread, so the record is complete whether anyone reads the alert or not.
When it escalates
- The driver hasn't answered two checkpoint messages
- The driver asks to move an appointment
- The driver reports a personal or health issue
- The delivery appointment passes with no response
- Predictive ETA falls behind the appointment window
- It's asked something it can't answer with confidence
Then it hands back. The rep replies in the same thread, the reply goes out on the right channel, and Autopilot picks the load back up.
Restraint
Autopilot knows where the line is.
Each item is a judgment call made by people who've been on the other end of a claim.
- It doesn't make money calls on a moving load.Detention, lumpers and accessorials go to your rep. It'll coach a driver to pay the lumper and keep the receipt, then flag the rep. On booking, it negotiates only inside the rates you set.
- It doesn't reroute drivers.It asks whether the driver can reroute and works around the answer. Routing a truck is your liability, not an agent's.
- It doesn't release the pickup number early.No live tracking and no proximity means no number. It never substitutes a load number for the real one.
- It doesn't surface hours of service.Even when the ELD hands them over. Same reason as rerouting.
- It doesn't pretend to be a person.It signs as the rep on the load. If a carrier asks whether they're talking to AI, it says so and gets back to the load.
- It doesn't talk over your team.A rep reply pauses it. When a thread turns hostile, it stops sending and leaves the room.
Your SOPs
Your SOP, said the same way every time.
No fine-tuning project and no quarterly retraining. During tuning, your standing instructions go in at the agent level, and shipper-specific ones go on the checkpoint where they apply.
On one load, a driver asked to switch to Polish. Autopilot did, confirmed pickup, and pulled five reference numbers from the load without a rep in the thread.
Why it works on day one
Models don't move freight.
Every AI vendor in freight builds on the same foundation models. We do too.
What can't be rented is five years of production behavior on real brokerage loads: the eight checkpoints and what each one is allowed to say, TMS mappings that know some McLeod shops type 00:01 when an appointment is blank, knowing not to ask for an ETA while the driver is still sitting at the shipper, and the securement photo that should have a tarp in it and doesn't.
Models are a commodity. Freight behavior isn't. Ours came out of more than 3 million production loads, and before that, out of a trucking company we ran ourselves.
Questions
What brokers ask about Autopilot
Is this one agent or a collection of bots?
One. One Autopilot per load, from carrier assignment through the paperwork, across booking and tracking. One agent means one place a load can't fall between.
Do we have to replace our TMS?
No. Chain runs alongside the TMS you already have. Loads flow in; statuses, times, documents, carriers and rates flow back out, and your reps keep working where they work.
How much of this do we have to build?
None of it. There's no workflow canvas to fill in and no engineer moving into your office. Your Chain team configures the checkpoints with you during tuning, and you can edit them afterward.
Do carriers know they're talking to AI?
Autopilot signs as the rep assigned to the load, so carriers see a familiar name. If a carrier asks directly, it says it's an AI assistant and gets back to the load.
Does it do voice?
Yes, as a fallback rather than the first move: text the driver, email the dispatcher, then a call through our voice partner, then a person. Drivers answer texts, and a text costs a fraction of a call. When a call happens, the recording lands in the same load thread.
Does it work in our TMS?
Yes. Chain connects to McLeod, MercuryGate, 3G TMS, Revenova, Tai, Turvo, 3PL Systems, Sunnybrook and more, and Chain builds the field mapping. Explore the apps.
Can we turn it off on a load?
Yes. Pause it on a single conversation, cancel a scheduled checkpoint, or exclude a carrier, customer, order type or load class entirely.