Product
The dispatcher’s work.
In software.
Dispatch does the job a dispatcher does for a truck, from the moment it goes empty to the moment the load delivers: find the freight, work the broker, book inside your rules, brief the driver, follow the load.
01
Empty
Truck 214 · Dallas, TX · 14:14
02
Booked
$2,225 · ref PE-48339
03
Moving
Louisville, KY · ETA 10:40
01The job
Six stages. One agent.
Each stage is work a dispatcher does by hand today. The status column says where each one stands; nothing here is described as live unless it is.
01Find
Refreshes the boards, filters by trailer, rate, deadhead and hours, keeps a list in their head.
Searches your board accounts, drops every load that breaks a rule and ranks the rest by rate after deadhead.
Built · external access required
Board search built; Truckstop production access not yet granted.
02Call
Calls brokers one after another, most of them twice.
Calls the broker, says it is an AI assistant, confirms the load is open and pitches your truck.
Planned
Voice module exists; no phone-line connection. No calls are placed.
03Rate
Counters from memory of what the lane paid last week.
Counters toward your number with the miles and deadhead, and never agrees below your floor.
Built · external access required
Negotiation logic built; needs the phone line to reach a broker.
04Rules
Checks the floor, deadhead, trailer, hours and broker in their head.
Checks every rule in software before it commits. Outside a rule, it asks you and waits.
Live in product
Rules, approvals and hours of service run in the app.
05Book
Reads the rate con, signs it, sends the MC and files the paperwork.
Books the load, files the rate con on the load record and keeps the evidence.
Live in product
Books inside the app. Telling the broker needs the phone line or email.
06Driver
Texts the driver, runs check calls, watches the ETA and chases the BOL.
Briefs the driver by text, runs the check calls and follows the load to delivery.
Planned
Driver texts and check calls planned; tracking needs ELD access.
02One record
Every load carries its own evidence.
One record follows the load from the posting to delivery. Anyone can open it and see why Dispatch did what it did.
- Source
- Which board, which posting, when it was seen.
- Economics
- Rate, loaded miles, deadhead and rate per mile after deadhead.
- Feasibility
- Trailer, pickup window and the driver’s hours of service, computed.
- Rules
- Every rule evaluated, with the value it was checked against.
- Decision
- Who or what approved it, when, and under which version of your rules.
- State
- Where the load is in its life, from posted to delivered.
03Under the hood
Built like an operations system.
Load lifecycle
12 states
A load moves through a fixed state machine with stops and appointment windows. It cannot skip a step.
Hours of service
11 / 14 / 70
The 11-hour, 14-hour, 30-minute break, 60/70-hour and 34-hour restart rules are computed, not guessed.
Audit
Append-only
Refusals are recorded as well as approvals. Nothing is edited after the fact.
Isolation
Row-level security
Each carrier’s data is separated in the database itself, not only in application code.
Safety
Idempotent
A retried action cannot book the same load twice. A safe mode stops new autonomous work.
Authority
Your rules
A recommendation never silently becomes a commitment. Outside your rules, it asks.
Let Dispatch take it from here.
Early access is open. Product status lists exactly what works today.