Automated Concrete Truck Reassignment
Every few minutes, WebRun opens Dispatch360, finds jobs where trucks are waiting or stacking because the pour has slowed, drafts a suggested reassignment of the next truck to another ready order, posts the plan to Slack for dispatch to approve, and pings Telegram if no one responds in time.
How do I reassign concrete trucks when a pour is delayed?
WebRun protects your loads when a pour stalls. Every five minutes it finds jobs where trucks are stacking in Dispatch360, drafts a reassignment of the next truck to a ready order, and posts it to Slack for approval, escalating to the on-call dispatcher on Telegram if no one responds before drum time runs down.
- Idle trucks get redirected before their loads go stale
- Every reassignment is approved by a dispatcher first
- Urgent moves reach the on-call dispatcher within minutes
Built for concrete dispatchers · ready mix producers · fleet managers · plant managers
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
www.dispatch360.comin a real browser with your saved login - no setup, no API keys. -
1
Dispatch360 - spot delayed pours and idle trucks
WebRun opens Dispatch360 to spot delayed pours and idle trucks. - Open Dispatch360 and find jobs where on-site or waiting trucks exceed the pour rate
- Read which trucks are idle, their loads, and their time in drum
- Identify other ready orders that could take the next truck without going short
Done when Every delayed pour has its idle trucks and candidate orders identified.
-
2
Slack - propose a reassignment to approve
WebRun opens Slack to propose a truck reassignment for approval. - Draft a reassignment plan naming the truck, its load, and the suggested new order
- Post it to the dispatch Slack channel as a proposal, not an action
- Leave the actual reassignment for a dispatcher to confirm in Dispatch360
Done when A reassignment proposal sits in Slack for dispatch to approve.
-
3
Telegram - escalate if no one responds
WebRun opens Telegram to escalate an unanswered reassignment. - Watch for a dispatcher response to the Slack proposal
- If no one responds within the set window and drum time is running down, ping the on-call dispatcher on Telegram
- Include the same truck, load, and suggested order so they can decide fast
Done when An unanswered urgent proposal has reached the on-call dispatcher on Telegram.
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
Will it move trucks without a dispatcher?
No. WebRun only drafts a reassignment and posts it for approval. A dispatcher confirms the move in Dispatch360, so no truck is redirected automatically.
How does it know a pour is delayed?
It reads Dispatch360 and finds jobs where waiting or on-site trucks exceed the pour rate, meaning trucks are stacking up faster than the crew can place concrete.
What if no one sees the Slack proposal?
If no dispatcher responds within your window and drum time is running down, WebRun pings the on-call dispatcher on Telegram with the same details so an urgent decision is not missed.
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.