Automated NEMT Driver Credential Expiry Tracking
Every Monday, WebRun opens Tobi, checks every active driver's credential expiry dates, drafts a renewal reminder for any driver within 30 days of an expiry, queues each draft for manager review before sending, and posts an expiry status report to the operations Slack channel.
How do I automatically track and remind drivers about expiring credentials?
WebRun opens Tobi every Monday, reads every active driver's credential expiry dates, and flags anyone within 30 days of a lapse. It drafts a renewal reminder SMS per driver via Twilio and queues each one in Slack for manager review, so no credential expires without advance notice and explicit staff approval before any message is sent.
- Credential lapses are flagged weeks in advance, not after a driver is already out of compliance
- Operations team sees a ranked expiry list every Monday without manual spreadsheet checks
- Driver-facing reminders are reviewed by a manager before sending
Built for NEMT fleet managers · paratransit compliance officers · medical transport HR 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
app.tobi.ioin a real browser with your saved login - no setup, no API keys. -
1
Tobi - check driver credential expiry dates
tobi.io
WebRun opens Tobi to check driver credential expiry dates. - Open Tobi and navigate to the driver compliance or credential management section
- Read each active driver's license expiry, medical certificate expiry, and background check renewal date
- Flag any credential expiring within the next 30 days
- Note any credential already expired
Done when All active drivers have been checked and those with credentials expiring within 30 days are listed.
-
2
Twilio - draft renewal reminder per driver
twilio.com
WebRun opens Twilio to draft renewal reminder per driver. - Draft an SMS renewal reminder for each flagged driver, naming the specific credential and its expiry date
- Include the HR or compliance contact number in each draft
- Do not send. Hold every draft for manager review
Done when One held SMS draft exists for every driver with a credential expiring within 30 days, unsent pending review.
-
3
Slack - post expiry report and queue drafts for review
slack.com
WebRun opens Slack to post expiry report and queue drafts for review. - Post an expiry status report to the operations Slack channel: total drivers checked, credentials expiring this week, credentials expiring within 30 days, and any already expired
- List each flagged driver by name, credential type, and days remaining
- Prompt the manager to review and release the SMS drafts
Done when Operations team has a Slack expiry report and manager can release reminder drafts with one action.
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 send a reminder to the driver without manager approval?
No. Every driver-facing SMS is drafted and held. A manager reviews the Slack report and releases each draft before any message is sent to a driver.
Which credentials does it track?
It tracks any credential with an expiry date stored in Tobi, including driver licenses, medical certificates, and background check renewal dates. Add more credential types in your Tobi setup.
What happens if a credential is already expired?
Already-expired credentials are surfaced at the top of the Slack report and flagged separately from upcoming expiries so the operations team can take immediate action.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.