Automated Driver Schedule Recurring Ride Reminders
Every evening, WebRun opens Driver Schedule and checks Google Calendar for tomorrow's recurring rides, such as dialysis or therapy runs, drafts a reminder text for each resident's family contact through Twilio, and leaves every message queued for your coordinator to review and send.
How do I remind families about recurring senior transportation rides without texting them automatically?
WebRun checks Driver Schedule and Google Calendar every evening for tomorrow's recurring rides, such as dialysis or therapy runs, and confirms each one is still active. It then drafts a reminder text for every resident's family contact through Twilio and leaves each message queued as unsent, so your coordinator reviews and sends the batch instead of WebRun contacting families directly.
- Every recurring ride gets a reminder drafted the night before, none sent without review
- Paused or cancelled rides are skipped automatically instead of reminding a family by mistake
- Coordinators review one queued batch instead of writing each text by hand
Built for NEMT coordinators · dialysis transportation programs · assisted living transportation staff · home care agencies
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
app.driverschedule.comin a real browser with your saved login - no setup, no API keys. -
1
Driver Schedule - find tomorrow's recurring rides
WebRun opens Driver Schedule to find tomorrow's recurring rides. - Open Driver Schedule and pull every ride tagged as recurring or standing for tomorrow
- Capture the resident, pickup time, driver, and destination for each
- Note any recurring ride that was recently changed or paused
Done when Every recurring ride scheduled for tomorrow is listed with its details.
-
2
Google Calendar - confirm the standing ride pattern
WebRun opens Google Calendar to confirm the standing ride pattern. - Cross-check each recurring ride against its calendar series
- Confirm the pattern is still active and was not cancelled for tomorrow
- Skip any ride whose series shows a pause or exception for that date
Done when Every recurring ride is confirmed still active for tomorrow.
-
3
Twilio - draft the reminder text
WebRun opens Twilio to draft the reminder text. - Draft a short reminder text for each family or resident contact with the pickup time and driver
- Leave every message queued as unsent
- Do not send anything without the coordinator's review
Done when A reminder is drafted and queued for every confirmed ride tomorrow, none of it sent yet.
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 families without anyone checking first?
No. Every reminder is drafted and left unsent in Twilio. A coordinator reviews the batch and sends it, WebRun never messages a family on its own.
What if a recurring ride was cancelled for tomorrow only?
It checks the calendar series for a pause or exception on that date and skips drafting a reminder for that one ride, so families are not reminded about a ride that is not happening.
Why check both Driver Schedule and Google Calendar?
Driver Schedule holds the ride itself, and the calendar series shows whether that day was paused or changed. Checking both catches one-off exceptions that Driver Schedule alone might miss.
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.