Automated TeleTracking Transfer Capacity Checks
Every hour, WebRun opens TeleTracking, matches every pending inbound transfer request against open and projected bed capacity by service, posts a recommendation and a drafted response to Slack for your transfer center to review, and texts the coordinator through Twilio when capacity looks genuinely tight.
How do I automatically check bed capacity before accepting a transfer?
WebRun checks TeleTracking every hour for open and projected bed capacity by service, matches it against pending transfer requests, and posts a recommendation to Slack with a drafted response for your transfer center to review. When capacity looks tight, it also texts the coordinator through Twilio, but the accept or decline decision always stays with your team.
- Every pending transfer gets a capacity check within the hour instead of a manual phone call
- Draft responses are ready for the transfer center to review, not send blind
- Tight capacity triggers a text before a bad transfer decision gets made
Built for transfer center coordinators · bed management teams · hospital access centers · capacity management directors
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 open capacity by service
teletracking.com
WebRun opens TeleTracking to check open capacity by service. - Open TeleTracking and pull open and projected bed capacity by service for the next 4 hours
- Pull the list of pending inbound transfer requests with requested service and acuity
- Match each pending request against current and projected capacity
- Flag any request where capacity looks tight or unavailable
Done when Every pending transfer request has a capacity match against current and projected beds.
-
2
Slack - post a capacity recommendation
slack.com
WebRun opens Slack to post a capacity recommendation. - Post each pending transfer with a suggested accept, hold, or escalate recommendation to the transfer center Slack channel
- Draft a short response summarizing capacity for the transfer center to send back to the referring facility
- Leave the response as a draft. Never send it to the referring facility automatically
Done when The transfer center has a recommendation and a drafted response for every pending transfer.
-
3
Twilio - text the transfer center on tight capacity
twilio.com
WebRun opens Twilio to text the transfer center on tight capacity. - Check whether any pending transfer has no realistic capacity match in the next 4 hours
- Text the transfer center coordinator through Twilio when that happens, naming the requested service and acuity
- Skip the text when capacity comfortably covers the request
Done when The transfer center is texted only when a pending transfer has no near term capacity match.
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 accept or decline a transfer on its own?
No. WebRun only recommends and drafts a response based on current and projected capacity. Your transfer center always makes and sends the actual accept or decline decision.
Does it contact the referring facility directly?
No. It drafts a capacity summary for your transfer center to review and send. It never communicates with an outside facility on its own.
How far ahead does it project capacity?
It looks at current open beds plus discharges and transfers expected in the next 4 hours in TeleTracking, so the recommendation reflects where capacity is actually heading, not just this minute's snapshot.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.