Automated NEMT Day-Before Trip Reminders
Every evening, WebRun opens Tobi, pulls all trips scheduled for the following day, drafts a day-before reminder SMS for each rider with their pickup time and address via Twilio, queues the full batch for dispatcher review in Slack, and lets the dispatcher release it with a single approval.
How do I automatically send day-before trip reminders to NEMT riders?
WebRun opens Tobi every evening, pulls all trips scheduled for the following day, and drafts a day-before reminder SMS for each rider via Twilio with pickup time, address, and dispatcher contact details. The full batch is queued in Slack for dispatcher review, and no message is sent until a human approves the release.
- Day-before reminders go out every evening without dispatchers sending them one by one
- No-show rates drop because riders are reminded the night before their trip
- Every message is reviewed by a dispatcher before reaching a rider
Built for NEMT dispatchers · paratransit coordinators · medical transport scheduling 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 - pull tomorrow's scheduled trips
tobi.io
WebRun opens Tobi to pull tomorrow's scheduled trips. - Open Tobi and navigate to the scheduled trips view
- Filter to trips scheduled for tomorrow
- Capture rider name, phone number, pickup time, and pickup address for each trip
- Exclude trips already sent a reminder today
Done when Every trip scheduled for tomorrow is listed with rider contact and pickup details.
-
2
Twilio - draft day-before reminder per rider
twilio.com
WebRun opens Twilio to draft day-before reminder per rider. - Draft a day-before reminder SMS for each rider with their name, tomorrow's pickup time, and pickup address
- Include the dispatcher callback number in case the rider needs to cancel or reschedule
- Do not include protected health information in the message text
- Do not send. Hold every draft for dispatcher review
Done when One held reminder draft exists for every rider with a trip tomorrow, unsent pending dispatcher approval.
-
3
Slack - queue batch for dispatcher review
slack.com
WebRun opens Slack to queue batch for dispatcher review. - Post the evening reminder batch to the dispatch Slack channel with total count and preview of drafts
- Prompt the dispatcher to review message text and release the batch
- Confirm in Slack once the batch has been approved and released
Done when Dispatcher has reviewed the reminder batch in Slack and released it, or flagged individual drafts for editing.
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 reminders to riders without dispatcher review?
No. The entire batch is held in Slack and no message is transmitted until a dispatcher reviews the draft text and explicitly releases the batch.
Does the reminder include any health or appointment details?
No. The reminder includes only the rider's name, pickup time, pickup address, and the dispatcher callback number. No protected health information is included.
What if a trip is cancelled after the reminder batch is released?
If a trip is cancelled before the dispatcher releases the batch, WebRun reads the current Tobi status and removes it from the drafts. For cancellations after release, the dispatcher handles follow-up directly.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.