Automated Portable Sanitation Daily Route Digest
Every morning, WebRun opens Routeware, pulls each driver's assigned stops for the day including service addresses, unit types, and any route notes, formats the data into a clean per-driver digest, and posts it to your Slack ops channel so dispatchers and drivers can start the day fully briefed.
How do I automatically create a daily route digest for my sanitation drivers?
WebRun opens Routeware every morning, pulls each driver's ordered list of stops for the day including service type, unit count, and site notes, and posts a clean per-driver digest to Slack. Dispatchers and drivers start the day fully briefed with stops in route order and special instructions flagged.
- Every driver has their ordered route list in Slack before the first truck leaves
- Stops with special access or time windows are flagged so dispatchers can brief drivers proactively
- Dispatchers spend zero time manually copying Routeware assignments into messages
Built for portable sanitation dispatchers · sanitation fleet managers · porta-potty route supervisors · field service operations teams
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.routeware.comin a real browser with your saved login - no setup, no API keys. -
1
Routeware - pull driver route assignments for today
routeware.com
WebRun opens Routeware to pull driver route assignments for today. - Open Routeware and navigate to today's route assignments
- Pull each driver's list of stops including address, service type, unit count, and any site notes
- Capture estimated stop times and total route mileage where available
- Flag any stops with special access requirements or time-sensitive service windows
Done when All driver route assignments for today are collected with stop details and notes.
-
2
Slack - post formatted route digest to ops channel
slack.com
WebRun opens Slack to post formatted route digest to ops channel. - Post the route digest to the ops Slack channel, organized by driver with their stops listed in order
- Include stop address, service type, and any flagged instructions for each stop
- Show total stop count per driver at the top of each section
- Surface any stops missing a driver assignment so dispatchers can act before routes begin
Done when Complete route digest is posted in Slack with every driver's stops listed in route order.
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 send the digest to individual drivers, or just to Slack?
It posts an internal digest to your Slack ops channel only. How that information reaches individual drivers is up to your dispatcher. It does not message drivers directly.
What if routes change after the morning digest is posted?
The digest reflects Routeware data at the time it runs. Your dispatcher can re-trigger the workflow manually for an updated digest, or check Routeware directly for real-time changes.
Can it flag stops with time-sensitive service windows?
Yes. Stops with time-specific service windows or special access requirements noted in Routeware are surfaced at the top of each driver section so dispatchers can communicate them proactively.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.