Trux Automated Aggregate Load Dispatch
Every morning, WebRun opens Trux, reads the day's confirmed aggregate orders, groups loads by plant, material, and jobsite, records the stacked run sheet in Google Sheets, and posts a hauler dispatch board to Slack so dispatch starts the day with every truck assigned.
How do I automatically stack and dispatch aggregate loads to my haulers each morning?
WebRun opens Trux every morning, reads the day's confirmed aggregate orders, and stacks the loads by plant, material, and jobsite to cut deadhead. It records the run sheet in Google Sheets and posts a hauler dispatch board to Slack, so your dispatcher starts the day with every load grouped and every truck proposed.
- Every load stacked and assigned before the plant opens
- Deadhead miles cut by grouping loads by plant and jobsite
- Short-truck orders flagged early enough to source a hauler
Built for aggregate haulers · dump truck dispatchers · sand and gravel suppliers · material producers
What does WebRun do on every run?
The exact actions WebRun takes, in order - in plain language, so you can adjust anything.
-
WebRun signs in and gets to work
Opens
app.truxnow.comin a real browser with your saved login - no setup, no API keys. -
1
Trux - read today's aggregate orders
truxnow.com
WebRun opens Trux to read today's aggregate orders. - Open Trux and list confirmed aggregate orders for today
- Capture plant, material type, quantity, jobsite, and requested start time for each
- Group orders by plant and material so loads can be stacked efficiently
Done when Every confirmed order for today is listed with its plant, material, and jobsite.
-
2
Google Sheets - build the stacked run sheet
google.com
WebRun opens Google Sheets to build the stacked run sheet. - Open the dispatch run sheet in Google Sheets
- Stack loads into hauler runs that minimize deadhead between plant and jobsite
- Record the suggested hauler, truck count, and load sequence for each run
Done when The run sheet shows a stacked, hauler-by-hauler plan for the day.
-
3
Slack - post the dispatch board
slack.com
WebRun opens Slack to post the dispatch board. - Post the dispatch board to the dispatch Slack channel
- Show each hauler, their assigned runs, and the first load's start time
- Flag any order still short a truck so dispatch can source one
Done when Dispatch has today's stacked hauler board in Slack.
How is each run configured?
Secure by default
Connect once, stays signed in
WebRun signs in once and keeps each session in a persistent environment, so every run picks up right where it left off.
Every action is checked against this policy before it runs.
Questions, answered
Does it dispatch trucks on its own?
No. WebRun stacks the loads and proposes a hauler run sheet, then posts it to Slack for your dispatcher to confirm and release. The final assignment stays a human decision inside Trux.
How does it decide which hauler gets which run?
It groups loads by plant and jobsite to cut deadhead, then suggests haulers by that grouping. You can weight it by preferred haulers or truck type and it will restack the board.
What if an order is short a truck?
It flags any order still missing a truck at the top of the board so your dispatcher can source a third-party hauler before the plant opens.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.