Automated TeleTracking LWBS Spike Alerts
Every hour, WebRun opens TeleTracking, checks how many patients left without being seen, compares the rate against the same hour's 4 week baseline, posts the trend to Microsoft Teams, and texts the nurse director through Twilio the moment the rate spikes above your threshold.
How do I get warned automatically when LWBS rates spike in the ED?
WebRun checks TeleTracking every hour for how many patients left without being seen, compares it against your 4 week baseline for that hour, and posts the trend to Microsoft Teams. When the rate spikes above threshold, it texts the nurse director through Twilio, so a worsening LWBS problem gets caught in the moment, not at week's end.
- Spikes get caught within the hour instead of surfacing in next month's quality report
- The whole ED team sees the same trend line in Teams in real time
- Only genuine spikes above baseline generate a text, so alerts stay meaningful
Built for ED nurse directors · emergency department operations teams · hospital quality teams · patient flow coordinators
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
www.teletracking.comin a real browser with your saved login - no setup, no API keys. -
1
TeleTracking - check the current LWBS rate
teletracking.com
WebRun opens TeleTracking to check the current LWBS rate. - Open TeleTracking and pull the count of patients who left without being seen in the last rolling hour
- Compare it against the same hour's baseline rate over the last 4 weeks
- Calculate the percentage above or below baseline
- Flag the hour as a spike if it exceeds your defined threshold
Done when The current LWBS rate is calculated and compared against baseline for this hour.
-
2
Microsoft Teams - post the trend to the ED team
microsoft.com
WebRun opens Microsoft Teams to post the trend to the ED team. - Post the current LWBS count and rate to the ED operations Teams channel
- Include the trend line against baseline for context
- Repeat hourly so the whole team can see the pattern building
Done when The ED team has the current LWBS trend posted in Teams.
-
3
Twilio - text the nurse director on a spike
twilio.com
WebRun opens Twilio to text the nurse director on a spike. - Check whether this hour's LWBS rate crossed the spike threshold
- Text the nurse director through Twilio with the current count and rate if it has
- Skip the text on any hour that stays within normal range
Done when The nurse director is texted only on hours where LWBS truly spikes above baseline.
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 text the nurse director every hour?
No. It posts the hourly trend to Teams for everyone to see, but only sends a text through Twilio on the hours where the rate actually crosses your spike threshold above baseline.
How is the baseline calculated?
It uses the same hour of day averaged over the last 4 weeks, so a normally busy afternoon hour is not compared against a quiet overnight hour.
Does the alert name specific patients who left?
No. It reports counts and rates only. No patient names or identifying details are included in the Teams post or the text.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.