Schedule will-call return trips without the phone tag
Every hour, WebRun checks RouteGenie for open will-call return trips, drafts an outbound scheduling message for each waiting rider via Twilio, queues every draft for dispatcher review in Slack, and logs the request so the team has a complete picture of who is still waiting.
- No credit card
- Under $0.01 per run
- Cancel anytime
How do I automate will-call return trip scheduling for NEMT riders?
WebRun checks RouteGenie every hour for open will-call return trips, drafts a scheduling SMS for each waiting rider via Twilio, and queues the batch in Slack for dispatcher review. No message goes to a rider until a dispatcher approves it, and a live waiting log tracks how long each person has been held.
- No will-call rider waits uncontacted because the check runs every hour
- Dispatchers see all waiting riders ranked by wait time in one Slack view
- Every rider message is reviewed before it is sent
Built for NEMT dispatchers · paratransit coordinators · medical transport operators
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.routegenie.comin a real browser with your saved login - no setup, no API keys. -
1
RouteGenie - identify open will-call returns
routegenie.com
WebRun opens RouteGenie to identify open will-call returns. - Open RouteGenie and filter trips to will-call status with no confirmed return time
- Capture rider name, phone number, original appointment location, and how long they have been waiting
- Skip any rider already contacted within the last 30 minutes
Done when All riders with open will-call returns are listed with their contact details and wait duration.
-
2
Twilio - draft scheduling message per rider
twilio.com How to Automate Twilio
WebRun opens Twilio to draft scheduling message per rider. - Draft an outbound SMS for each waiting rider confirming their return trip is being arranged
- Include the dispatcher callback number in the draft
- Do not send. Hold each draft for review before any message goes out
Done when One reviewed-and-held SMS draft exists for every waiting will-call rider.
-
3
Slack - queue drafts and update waiting log
slack.com How to Automate Slack
WebRun opens Slack to queue drafts and update waiting log. - Post the draft batch to the dispatch Slack channel with rider names, wait times, and message previews
- Update the pinned will-call waiting log with current open returns
- Alert the dispatcher if any rider has been waiting more than 90 minutes
Done when Dispatcher sees a Slack alert with drafts ready to release and a full current waiting-rider log.
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 message waiting riders without dispatcher approval?
No. Every outbound message to a rider is drafted and held in Slack. A dispatcher must review and release each batch before any SMS is transmitted.
How does it know a rider is ready for pickup?
WebRun reads the will-call status flag in RouteGenie each hour. Riders flagged as will-call with no confirmed return time and no recent contact are surfaced for scheduling.
What if the same rider shows up every hour?
WebRun skips riders already drafted within the last 30 minutes to prevent duplicate messages, and the pinned Slack log shows how long each rider has been waiting.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.