Automated Yeti Driver Clock-In Alerts
Every morning as routes start, WebRun opens Yeti Software, checks each driver's clock-in status against their scheduled start time, texts the supervisor by Twilio about anyone not clocked in 15 minutes past their start, and posts the full day's attendance to Slack.
How do I get alerted when a snow removal driver misses clock-in?
Every morning as routes start, WebRun checks each driver's clock-in status in Yeti Software against their scheduled start time. If a driver hasn't clocked in 15 minutes past their start, it texts the supervisor by Twilio with the driver and route, then posts the full day's attendance to Slack once every route is underway.
- No-shows are caught within 15 minutes of a missed route start
- Supervisors get one attendance summary instead of checking every driver by hand
- Routes get reassigned before a customer notices a delay
Built for snow removal contractors · dispatch supervisors · multi-driver snow operations · fleet 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.yetisoftware.com/loginin a real browser with your saved login - no setup, no API keys. -
1
Yeti Software - check each driver's clock-in status
yetisoftware.com
WebRun opens Yeti Software to check each driver's clock-in status. - Open Yeti Software and pull each driver's scheduled route start time
- Check whether each driver has clocked in against that time
- Mark anyone not clocked in 15 minutes past their start time
Done when Every scheduled driver has a current clock-in status.
-
2
Twilio - text the supervisor about any no-show
twilio.com
WebRun opens Twilio to text the supervisor about any no-show. - Text the supervisor the name and route of any driver not yet clocked in
- Include how many minutes past their start time it is
Done when The supervisor has been texted about any current no-show.
-
3
Slack - post the day's attendance summary
slack.com
WebRun opens Slack to post the day's attendance summary. - Post the day's full attendance summary once all routes have started
- Note which no-shows were resolved and which routes needed reassignment
Done when Today's attendance summary is posted to 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 reassign the route automatically?
No. It only alerts the supervisor so they can reassign or call the driver. WebRun never moves a route to another driver on its own.
How long does it wait before flagging a no-show?
15 minutes past the driver's scheduled route start time, so a short delay in traffic does not trigger a false alert.
What if a driver clocks in late but before the alert?
It reads live clock-in status from Yeti Software, so a driver who clocks in inside the 15 minute window is never flagged.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.