Automated NEMT Standing Order Confirmations
Every Monday, WebRun opens Tobi, identifies active standing orders scheduled for the coming week, drafts a brief confirmation message for each recurring rider via Twilio, queues every draft for coordinator review in Slack, and flags any standing order that has not been confirmed in the prior two weeks.
How do I automatically confirm standing order trips with recurring NEMT riders?
WebRun opens Tobi every Monday, reads all active standing orders scheduled for the coming week, and drafts a confirmation message for each recurring rider via Twilio. Coordinators review the full batch in Slack and release messages, while orders that have gone unconfirmed for two or more weeks are flagged for special attention.
- Every recurring rider is confirmed weekly without coordinators making individual calls
- Orders unconfirmed for two or more weeks are flagged before they become a problem
- No message reaches a rider without explicit coordinator approval
Built for NEMT coordinators · paratransit scheduling teams · medical transport operations 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
app.tobi.ioin a real browser with your saved login - no setup, no API keys. -
1
Tobi - pull active standing orders for the coming week
tobi.io
WebRun opens Tobi to pull active standing orders for the coming week. - Open Tobi and navigate to standing orders or recurring trips
- Filter to orders active for the coming week
- Capture rider name, phone number, recurring schedule, pickup address, and destination for each order
- Flag any standing order not confirmed in the prior 14 days
Done when All active standing orders for the coming week are listed with rider details and confirmation history.
-
2
Twilio - draft confirmation message per recurring rider
twilio.com
WebRun opens Twilio to draft confirmation message per recurring rider. - Draft a brief confirmation message for each recurring rider: confirm scheduled days, pickup time, and pickup address
- Include the coordinator callback number in each draft
- Do not send. Hold every draft for coordinator review
Done when One held confirmation draft exists for every active standing order, unsent pending review.
-
3
Slack - queue drafts and flag exceptions for review
slack.com
WebRun opens Slack to queue drafts and flag exceptions for review. - Post the weekly standing order summary to the coordinator Slack channel: total active orders, drafts ready for review, and flagged exceptions
- List each flagged standing order with the last confirmed date
- Prompt the coordinator to release confirmation drafts
Done when Coordinator has a Slack summary with all standing order confirmation drafts ready to review and any exceptions highlighted.
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 confirmations to recurring riders automatically?
No. Every confirmation message is drafted and held in Slack for a coordinator to review before any message is sent to a rider.
What if a standing order was cancelled or paused?
WebRun reads the current status of each standing order in Tobi. Cancelled or paused orders are excluded from the draft batch automatically.
How does it handle standing orders that have not been confirmed in a while?
Orders not confirmed in the prior 14 days are flagged separately in the Slack summary so coordinators can decide whether to confirm, update, or close them.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.