Automatic Idle Porter Rebalancing Alerts
Every 15 minutes, WebRun opens Patient Focused Systems, checks which floors or zones have idle porters and which have a growing trip backlog, and posts the dispatch channel a Slack suggestion for which porter to reassign so no zone is left waiting while another sits idle.
How do I rebalance idle porters against backlogged transport zones?
WebRun checks Patient Focused Systems every 15 minutes for porters idle more than 15 minutes and zones with 3 or more pending requests. When it finds both at once, it posts dispatch a Slack suggestion naming the idle porter and the nearest backlogged zone, so reassignment happens before patients in one wing wait behind an idle porter in another.
- Idle porters get matched to backlogged zones within 15 minutes
- Dispatch only sees a Slack post when an actual imbalance exists
- Reassignment decisions stay with the dispatcher, WebRun only suggests
Built for patient transport dispatchers · transport department supervisors · hospital operations managers · charge porters
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 - compare idle porters to backlogged zones
patientfocussystems.com
WebRun opens Patient Focused Systems to compare idle porters to backlogged zones. - Open the porter roster and flag anyone idle for more than 15 minutes
- Open the trip queue and flag any zone with 3 or more pending requests
- Match idle porters to the nearest backlogged zone by current location
Done when Every idle porter is matched to the nearest backlogged zone, if one exists.
-
2
Slack - suggest a reassignment to dispatch
slack.com
WebRun opens Slack to suggest a reassignment to dispatch. - Post the suggested reassignment to the dispatch channel, naming the porter and the backlogged zone
- Skip the post entirely if no zone is currently backlogged
- Leave the actual reassignment to the dispatcher in Patient Focused Systems
Done when Dispatch has a reassignment suggestion whenever an imbalance exists.
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 WebRun reassign the porter itself?
No. It only suggests a reassignment in Slack, naming the idle porter and the backlogged zone. The dispatcher makes the actual reassignment in Patient Focused Systems.
What counts as an idle porter?
Anyone with no active trip assigned for more than 15 minutes. That threshold is adjustable in your run settings if your floors run differently.
Will it post if there's no imbalance to fix?
No. It skips the Slack post entirely when every zone is keeping pace with its porters, so the channel only sees a message when there's an actual suggestion worth acting on.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.