Flag loads that sit too long in the drum
Every few minutes, WebRun opens Dispatch360, reads the batch time and drum turns for every load still on a truck, works out the elapsed time in the drum against your limit, and posts Slack an alert for any load approaching or past its maximum time or turns so dispatch can act before it sets.
- No credit card
- Under $0.01 per run
- Cancel anytime
How do I flag concrete loads exceeding their max time in the drum?
WebRun warns dispatch before concrete overstays the drum. Every five minutes it reads the batch time and drum turns of each active load in Dispatch360, computes the elapsed time against your maximum time and turns, and posts a Slack alert as a load nears its limit and an escalated one if it passes, so it can be poured or returned in time.
- Loads are poured or returned before they set in the drum
- Dispatch gets a warning while there is still time to act
- Rejected concrete and short pours from stale loads drop
Built for concrete dispatchers · ready mix producers · QC 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 - check time in drum per load
dispatch360.com How to Automate Dispatch360
WebRun opens Dispatch360 to check time in drum for each active load. - Open Dispatch360 and list loads still on a truck and not yet fully poured
- Read the batch time and the running drum turn count for each
- Compute elapsed time in the drum and compare it to your maximum time and turns
Done when Every active load has its elapsed drum time and turns computed.
-
2
Slack - alert dispatch before the limit
slack.com How to Automate Slack
WebRun opens Slack to alert dispatch before a load passes its drum limit. - Post a Slack alert for any load within the warning window of its time or turns limit
- Escalate a second alert for any load already past the limit
- List the ticket, truck, job, minutes in drum, and turns so dispatch can pour or return it
Done when Dispatch has a Slack alert for every load near or past its drum limit.
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 return or reject a load by itself?
No. WebRun only posts an internal Slack alert with the elapsed time and turns. A dispatcher decides whether to pour, redirect, or return the load, so no action happens without a person.
What limit does it use?
The maximum time in drum and turn count you set, commonly a 90-minute rule and a turns cap. WebRun compares each load's elapsed time and running turns against those thresholds.
When does it warn versus escalate?
It sends a first alert once a load enters the warning window before its limit, then a second, escalated alert if the load actually passes the time or turns limit.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.