Route emergency respite requests to your on-call team
Every few minutes, day and night, WebRun opens Alora, checks for any new respite request logged as urgent or same-day, pulls any related Twilio message thread for extra context, and posts an immediate Slack alert to your on-call coordinator with the reason, requested start time, and caregiver match status.
- No credit card
- Under $0.01 per run
- Cancel anytime
How do I make sure urgent respite requests reach my on-call team fast?
WebRun watches Alora every few minutes, day and night, for new respite requests marked urgent or same-day, pulls any related Twilio message thread for context, and immediately posts an on-call alert to Slack with the reason, requested start time, and whether a caregiver match exists, so crisis coverage can start within minutes instead of waiting for the next business day.
- Urgent requests reach the on-call coordinator within minutes, any time of day
- Every alert already shows whether a caregiver match exists
- Requests with no match are flagged for manual outreach instead of sitting quietly
Built for respite care agencies · crisis intake coordinators · on-call schedulers · family caregiver support programs
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.alorahealth.comin a real browser with your saved login - no setup, no API keys. -
1
Alora - find new urgent respite requests
WebRun opens Alora to find new urgent respite requests. - Open Alora and check for any new respite request logged as urgent or same-day
- Capture the client, requesting contact, reason for the request, and requested start time
- Check current authorization hours and the caregiver roster for a possible match
Done when Every new urgent respite request is listed with its reason and requested start time.
-
2
Twilio - pull message context for the request
WebRun opens Twilio to pull message context for the request. - Pull any SMS or call log tied to the request for extra context
- Note any detail the family provided that is not already in Alora
- Do not reply to the family. Read only, for context
Done when Each urgent request has its full context gathered from Alora and Twilio.
-
3
Slack - alert the on-call coordinator
WebRun opens Slack to alert the on-call coordinator. - Post the urgent request to the on-call channel immediately, tagging the on-call coordinator
- Include the reason, requested start time, and whether a caregiver match exists
- Mark requests with no caregiver match as needing manual outreach
Done when Your on-call coordinator has every urgent respite request in Slack within minutes of it appearing in Alora.
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 contact the family directly during an emergency?
No. WebRun only reads the request and any related Twilio thread for context. It never texts or calls the family. A human coordinator makes contact.
How fast does an urgent request reach the on-call coordinator?
Within minutes. WebRun checks Alora every 10 minutes around the clock, so an urgent request logged at 2am reaches Slack just as fast as one logged at 2pm.
What if there is no caregiver available for the request?
It still posts the alert immediately and marks it as needing manual outreach, rather than waiting until a match is found, so your team knows right away.
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.