Blog

How Do You Keep Load Updates Out of Personal Texts and On the Load?

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

Short answer: pick one place the truth lives, and make it the load in your TMS. Every update that changes what happens next (loaded, running late, new ETA, new rate, detention coming, POD in) gets written on the load, by whoever heard it, before they do anything else. Put carriers and shippers on shared numbers and shared inboxes instead of reps' cell phones, keep the same questions on every check call so the notes look the same, and treat anything that isn't on the load as if it never happened. Software can do the writing for you, but the rule has to come first.

Why does this keep happening on small floors?

Because it's the fastest way to get the answer in the moment. A driver texts your rep's cell because that's the number he called from last week. A shipper's dock lead sends a new appointment in a chat app because that's how she talks to everybody. A carrier agrees to a rate bump on the phone and nobody updates the load because the truck's already rolling.

None of that is laziness. It's a rep doing the job with whatever's in their hand. The problem shows up later. A load goes sideways at 6 a.m., the person who's been handling it isn't in yet, and the person who is in has the TMS, an empty load note and no idea that the driver said he was out of hours at midnight.

Put plainly: updates like loaded, running late or new rates end up in someone's personal chat, and when a load goes sideways at 6 a.m., nobody has the full picture. If you've run a desk, you've lived that morning.

What actually belongs on the load?

Not every message. "Thanks" and "10-4" don't need to be logged. What belongs on the load is anything that changes what the next person on that load should do.

Update	Why it has to be on the load	Who usually hears it first
Loaded, and the BOL matches	Proves the freight's on the truck and the paperwork's right before it rolls	The driver, on a call or text
New ETA or running late	The customer needs to hear it from you before they find it	The driver or carrier dispatch
Out of hours, mechanical, weather	Decides whether you re-cover or reschedule	The driver
Appointment moved	Changes the clock for detention, layover and the next check	The shipper or receiver
Rate change or accessorial agreed	It's money, and it'll be fought over at billing	The carrier and your rep
Detention started	Your notice to the customer has to go out before detention starts	The driver at the dock
POD and lumper receipt	Delivered isn't done. Billed is done.	The driver, usually by text or email

If it's in that table and it's only in a phone, it's a problem waiting for the wrong morning.

How do you set this up without buying anything?

You can get most of the way there with rules and a little discipline. Here's what works on a small floor.

Give carriers and shippers a shared number and a shared inbox. Put the brokerage's dispatch line and ops inbox on the rate con and the load tender reply, not a rep's cell. If a driver texts a personal phone anyway, the rep forwards it to the shared line or logs it, every time.

Make the load note the first thing, not the last. The habit you want is "hang up, write the note, then act." A check call that lives in somebody's head didn't happen. Same for a rate bump agreed on the phone.

Ask the same questions in the same order. Are you loaded, does the BOL match, what time will you be at the receiver, do you have the hours, anything I should know. When every check call note reads the same way, the 6 a.m. person can read a load at a glance.

Write the money down the same day. A new rate or an agreed accessorial that isn't on the load is an argument at billing. Put the amount, who agreed and when on the load before the truck delivers.

Hand off by load, not by memory. At shift change or end of day, the open problem loads should be readable from the TMS alone. If a rep has to explain a load out loud for it to make sense, the note isn't done.

Tag email by load number. If you're running out of a shared inbox, put the load or reference number in the subject on every reply so the thread can be found from the load later.

Where does this break down?

Volume. Tagged email folders plus TMS check-call notes only work when you're moving a small number of loads a week, and that matches what most of us have seen. At low volume a good rep can keep it all straight. Once the floor's busy, the logging is the first thing that slips, because the next load is always more urgent than writing up the last one.

That's the honest version: the rules are right at any size, but the re-keying is what gets skipped. So the real fix is to stop asking people to re-key it.

How does software keep updates on the load?

The job you're buying is simple to describe. The update gets captured where it happens, written to the load in the TMS you already run, and anything that needs a person goes to a person with the load in front of them.

Here's how FreightScout handles the pieces of that today.

Check calls. FreightScout places the pickup, transit and delivery check calls, captures the spoken update and the POD, and writes the note back to the load in McLeod, Aljex, Tai or any other TMS your team already logs into, so the floor doesn't re-key it. When the truck's on pace, the tracking ping stands in for the call. The last check before an appointment is always a call.
Exceptions. It watches every rolling load for an unplanned stop, a stale ping, an off-route truck, a truck behind pace or a reefer out of range. No answer, detention, mechanical trouble and shipper heat go to a person, not to voicemail.
The customer note. When a load's late, the driver's reason and the new ETA come back with the delay email to the customer drafted for one-click send. The pre-detention notice is drafted the same way, and the detention clock starts when the driver texts check-in, not off a geofence.
The inbox. Forwarded tenders become loads, and PODs that arrive by email are matched to the load with the lumper receipt and every photo. Missing paperwork is chased by text, call and dispatcher on a clock.
The carrier and the rate. It writes the booked carrier, the agreed rate and the load back into your TMS.

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

What it won't do is fix a rep's habit of agreeing to things in a personal chat app. If the update only ever exists on someone's cell, no software sees it. That's why the shared-number rule comes first, with or without a tool.

Who stays in control?

You do. FreightScout runs supervised by default: it drafts and stages the work, and your people say yes. You can turn actions up to autopilot per team and per action when you trust them, and every action is logged and reversible. The TMS stays the system of record. FreightScout isn't a TMS and isn't a load board, so nothing about where your team looks for the truth changes. It just stops being empty at 6 a.m.

Questions brokers ask

How do I stop reps from handling loads on their personal phones?

Put the brokerage's shared dispatch number and ops inbox on every rate con and tender reply, and make "forward it or log it" the rule for anything that still lands on a personal phone. Then check it: the open loads should make sense from the TMS alone.

What should go in a check call note?

Whether the truck's loaded and the BOL matches, the ETA to the receiver, whether the driver has the hours, and anything that changes the plan. Same questions, same order, every load, written on the load as soon as you hang up.

Is a shared inbox enough to keep load updates organized?

At low volume, often yes, especially if every reply carries the load number in the subject. As volume grows, the re-keying from the inbox to the TMS is what slips, which is where automating the write-back helps.

Can AI read updates from a rep's personal text messages?

Don't plan on it. FreightScout captures updates from the check calls it places, the inbox it's connected to and the driver texts in its own flow, and writes them to the load. Anything that only lives on a rep's personal phone stays invisible until someone logs it.

Does the check call note go back into my TMS automatically?

With FreightScout, yes. The note lands on the load in McLeod, Aljex, Tai or any other TMS your team already logs into. Check calls run supervised by default, and exceptions come to your people with the load already in front of them.

Do I need to switch TMSs to keep everything on the load?

No. FreightScout isn't a TMS. It works on the one you already run, and your TMS stays the system of record.

What happens when a load goes wrong overnight?

The goal is that whoever's in first can read the whole story off the load: the last call, the reason for the delay, the new ETA and whether the customer's been told. If it's not on the load, assume nobody knows it.

All posts: the blog index.