Every load, every truck, every driver. One board.
Build a load in seconds. Assign the truck that should actually take it. Then watch it move — without a single check call.
Dispatch became a phone job. It shouldn't be one.
It's six in the morning. Three rate cons to key in, four drivers to call, and a broker already asking where his truck is.
Where's my truck? Did he get loaded? When's he empty? Can he take this?
Every answer is a call, a text, or another tab in another system — and by the time you have it, it's already old.
And nobody can tell you who's open. Availability lives in a spreadsheet, a whiteboard and a group text.
The load builds itself.
Drop in the rate con and it's read for you. Take the EDI tender straight from your broker. Pull it in from the load board you booked it on — C.H. Robinson included. Or build it by hand in a few clicks.
Either way, nobody retypes a rate at 6 a.m.
Plan the lane before the truck rolls.
Sequence pickups and drops, check the windows against hours of service, and see at a glance which trucks have the capacity to take the load.
- Multi-stop trips with pickup and delivery windows
- Mileage and drive time computed per plan
- HOS fit checked before you commit
- Capacity view across the whole fleet
The board keeps itself current.
Location and hours come straight from your ELD. Arrived, loaded, empty come from your driver, one tap in the app. And when he forgets, the geofence catches it — arrived and departed land on their own.
Nobody updates a spreadsheet. Nobody asks dispatch to refresh anything. The answer is already on screen when the question comes.
Know where every truck is. So do your customers.
Position streams in from the mobile app — no extra hardware. ETAs update themselves, and the customer portal answers "where's my load?" before anyone picks up a phone.
- Real-time position on every load
- ETAs recomputed as conditions change
- Late-risk flags before they become late loads
Your customer stops calling too.
Picked up. In transit. Delivered. Your broker or shipper gets told automatically, from the same statuses your driver already tapped.
No update emails to write. No "any news on 4471?"
You find out while you can still fix it.
Late to a pickup. Sitting too long at a shipper. Hours about to run out. A load that hasn't moved when it should have.
The board tells you — instead of your customer telling you tomorrow.
The paperwork shows up with the load.
BOLs and PODs photographed at the dock and attached to the load file the moment they're signed. Not Friday. Not in a glovebox.
The load you dispatch is the load you invoice.
Most carriers dispatch in one system and bill in another, so every load gets entered twice and the two never quite agree.
Here it's one record. Dispatch it, run it, close it — and it's already an invoice, already a settlement line, already in your numbers. Nothing gets handed off. Nothing gets rekeyed. Nothing goes missing between the two.
Same record, same load ID, four contexts.
No two dispatch desks work the same way.
Yours doesn't have to bend to ours. Most TMS apps stop at integrations — we start there, then let you extend the board itself, and build whatever's still missing.
Integrations
Load boards, ELD, EDI, tracking, fuel. Dispatch keeps running on what it already runs on.
Step 2Apps
Add to the board itself — the columns, statuses and workflows your operation actually uses. 100+ apps to start from.
Step 3Build your own
Whatever's still missing. You build it, your way, live the moment you're done. No IT firm, no ticket, no six-month wait.
Apps & Builder →
Questions dispatchers and owners ask
Most of the day happens on one board — loads, trucks, drivers, hours and statuses in the same place. There's no second system to keep in step, and the load arrives already built instead of being keyed in. Dispatchers who've been burned before usually judge it in the first ten minutes of the call.
Hours and location come across from the major ELD providers, and that's what the board and the assignment view run on. Tell us which one you use and we'll say plainly on the call whether it's connected today.
Yes. Book where you book — C.H. Robinson included — and pull the load in rather than retyping it. Rate cons and EDI tenders come in the same way.
Open loads come over with your trucks, drivers, customers and lanes during the 30 days. You keep dispatching on your current setup until the new board is running, and you decide when to shut the old one off.
Less than you'd think. Hours and location come from the ELD with no input at all, and arrivals and departures are caught by geofence even for a driver who never opens the app. His taps make the board sharper; they aren't what keeps it alive.
Yes — columns, statuses and workflows. There are 100+ apps to start from, and anything still missing you build in the app yourself and use the moment you're done. No IT firm, no ticket.
Bring us one of your loads.
We'll build it, assign it and dispatch it while you watch. Twenty minutes.