Automated Arborgold Snow Event Dispatch
Every few minutes during an active storm, WebRun checks Arborgold for a confirmed snow event, pulls each crew's assigned properties and route order, texts every driver their stop list through Twilio, and posts a Slack summary of who is dispatched and where so the ops manager can see the whole storm at a glance.
How do I automatically dispatch crews when a snow event starts?
WebRun watches Arborgold for a snow event marked active, then pulls every crew's route and property list the moment it is confirmed. It texts each crew leader their stops through Twilio and posts a live Slack summary of who is out and what is covered, so a whole storm's dispatch goes out in minutes, not phone calls.
- Every crew has their route within minutes of a snow event being called
- The ops manager sees who is dispatched and where from one Slack summary
- No driver waits on a phone call to learn their stops for the storm
Built for snow removal contractors · commercial snow plow operators · landscaping companies with snow contracts · Arborgold users
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.arborgold.com/loginin a real browser with your saved login - no setup, no API keys. -
1
Arborgold - confirm the snow event and pull routes
arborgold.com
WebRun opens Arborgold to confirm the snow event and pull routes. - Open Arborgold and check for a snow event marked active for this storm
- Pull each crew's assigned properties, route order, and service level: plow, salt, or walk
- Note any property with a gate code, access restriction, or priority flag
Done when Every active crew has a route pulled with property order and service level.
-
2
Twilio - text each crew their stops
twilio.com
WebRun opens Twilio to text each crew their stops. - Text each crew leader their stop list in route order with addresses and service scope
- Include any gate codes or access notes for that crew's stops
- Skip any crew already texted for this storm event
Done when Every active crew has received their route by text.
-
3
Slack - post the dispatch summary
slack.com
WebRun opens Slack to post the dispatch summary. - Post a dispatch summary to the ops channel listing crews out, stops per crew, and total properties covered
- Flag any property not yet assigned to a crew
Done when Ops manager has a live count of crews dispatched and any unassigned stops.
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 text my customers when a snow event starts?
No. The texts go only to your own crews with their route assignments. Customers are never contacted by this workflow.
What counts as an active snow event?
Whatever you mark active in Arborgold. WebRun checks for that flag every few minutes and only dispatches once a human has called the event.
What if a crew's route changes mid storm?
Run it again after you update Arborgold and it texts only the crews whose stop list changed, so nobody gets a stale route.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.