What it could save
Estimate · not a client result
For a 30-person freight brokerage. These numbers are assumptions, not measurements: the audit measures yours.
- By hand today
- 150 status updates a week × ~3 min each
- ≈ 7 h 30 min a week
- With the automation
- 150 status updates a week × ~30 sec to review each
- ≈ 1 h 15 min a week
- Difference
- 7 h 30 min − 1 h 15 min
- ≈ 6 h 15 min a week back
By hand: read the message, find the load, update the board, write to the customer. After: a one-click confirm on routine updates; the late loads that need the dispatcher's own words are in the average.
The job today
- Dispatchers read carrier emails and check tracking portals.
- They update the load board or spreadsheet by hand.
- They write a status email to each customer who asks.
- A late load is often spotted when the customer calls about it.
How the automation runs
- Trigger
1. Update arrives
Carrier email, tracking feed or a driver text, into one dispatch queue.
In: Dispatch inbox · SMS
- AI
2. Match the load
PO, pro number or BOL is matched to the load on your board. An update that matches no load, or two, is not applied.
In: Load board
- Your system
3. Update the board
Status, ETA and location are written to the load, with the source message kept beside the change.
In: TMS or Google Sheets
- AI
4. Check the ETA
An ETA past the delivery window, or a stale update, marks the load at risk and notifies the dispatcher.
- A person
5. Dispatcher sends
On-time customer updates go out on one click. Late or unclear ones wait for the dispatcher's wording.
- Your system
6. Customer informed
The email goes out from the dispatch address and is logged on the load.
In: Outlook
Example tools: Shared dispatch inbox · Your TMS or a Google Sheet · Carrier tracking portals. The audit confirms what you actually run.
What it checks
Before a person sees a draft, these run. A draft that fails one is held, with the reason shown.
- An update must match exactly one load by PO, pro or BOL, or it is held with the candidates listed.
- A new ETA more than 30 minutes past the delivery window marks the load at risk and is never auto-drafted to the customer.
- A status that goes backwards (delivered, then in transit) is held as a probable error.
- No update on an in-transit load for 4 hours: flagged so the dispatcher can chase the carrier.
- Customer wording is limited to the load facts: no blame, no promises of compensation.
When something goes wrong
Edge cases are planned for, not discovered in production.
- Driver text is shorthand ('at dock 4, waiting')
- It is read as 'arrived, waiting to unload', shown with the original, and applied only after a one-click confirm.
- Carrier uses a PO number that matches two loads
- Both are shown to the dispatcher; neither is updated until one is chosen.
- Tracking feed goes quiet
- The 4-hour rule raises it; the board shows 'no update since', not the last known ETA as if current.
- Customer asks a question that isn't a status
- It is routed to the dispatcher untouched and no reply is drafted.
What lands, and where
Once a person approves:
- Your TMS or the dispatch Google Sheet
- Status, ETA and location on the load, with a log of what changed it.
- Outlook
- The status email to the customer, sent from the dispatch address.
- Slack, Teams or SMS
- An at-risk alert to the dispatcher on duty.
Where a person stays in charge
Routine updates can go out on approval in one click. Anything late or unclear waits for a dispatcher, who knows the customer.
What it would cost
An Automation Build is from $8,000, with the price fixed before work starts. What moves it for this one:
- How many carriers, and whether they send structured data
- Whether the TMS has an API
- Customer-specific update rules
All prices are in Canadian dollars. GST is added where it applies.
What the audit checks first
Before anything is built, the $2,500 audit measures the job in your business, including the numbers the estimate above only assumes:
- Loads a week and updates per load
- How many customer status questions a day
- Where late loads are found today, and how late
Have a job like this one?
The AI Automation Audit is $2,500, fixed: a working session on one workflow and a written plan in 5 business days, with costed options you keep. Credited in full if you build.
Request the $2,500 auditNot ready to pay? Get a free video teardown of one workflow.
Describe your workflow
Don't see yours? Tell us about it. If it's repetitive and lives in software, we can likely automate it.