Automated Missed Pickup Escalation Alerts
Every few minutes, WebRun checks Patient Focused Systems for pickup requests that have passed their window with no porter acknowledgment, texts the on-call charge porter through Twilio with the trip ID and location, and logs every escalation to Slack so dispatch has a record.
How do I escalate a missed patient transport pickup automatically?
WebRun scans Patient Focused Systems every few minutes for pickups that pass their window with no porter acknowledgment. It texts the on-call charge porter through Twilio with the trip ID, unit, and minutes overdue, then logs the escalation to Slack, so a missed pickup gets a human response in minutes instead of surfacing later as a complaint.
- Missed pickups reach the on-call charge porter within minutes
- Every escalation is logged so dispatch can trace who was texted and when
- No pickup is escalated twice for the same miss
Built for hospital transport dispatchers · charge porters · patient transport supervisors · hospital 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
patientfocussystems.comin a real browser with your saved login - no setup, no API keys. -
1
Patient Focused Systems - find unacknowledged missed pickups
patientfocussystems.com
WebRun opens Patient Focused Systems to find unacknowledged missed pickups. - Open the trip queue and filter to requests past their pickup window with no porter acknowledgment
- Capture the trip ID, requesting unit, and minutes since the window closed
- Confirm the request has not already been escalated this cycle
Done when Every unacknowledged missed pickup is listed with its wait time.
-
2
Twilio - text the on-call charge porter
twilio.com
WebRun opens Twilio to text the on-call charge porter. - Send a text to the on-call charge porter's number with the trip ID, unit, and minutes overdue
- Use the same message format every time so escalations are easy to scan
- Send only to the internal on-call number on file, never to the patient or a family member
Done when The on-call charge porter has been texted for every missed pickup.
-
3
Slack - log the escalation
slack.com
WebRun opens Slack to log the escalation. - Post a log entry in the dispatch channel for each escalation sent
- Include the trip ID and the time the text went out
- Keep a same-day thread so escalations are easy to trace back
Done when Dispatch has a Slack record of every escalation sent this run.
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
Does the text ever go to the patient or their family?
No. WebRun only texts the internal on-call charge porter number you provide. Patients and families are never contacted by this workflow.
How long does a request wait before it's escalated?
By default it escalates once a pickup passes its window with no porter acknowledgment, and that window is set in Patient Focused Systems. You can tighten or loosen it in your run settings.
What if the same request gets escalated twice?
It checks for an escalation already logged this cycle before texting again, so the on-call porter isn't texted twice for the same missed pickup.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.