Automated XSOLIS Authorization Expiry Warnings
Every morning, WebRun opens XSOLIS, finds every authorization expiring within 48 hours or already lapsed, logs each one to a Google Sheet with the payer and units remaining, drafts the extension request in Outlook, and posts your UM team a Slack alert ranked by how soon coverage runs out.
How do I stop payer authorizations from expiring mid stay?
WebRun checks XSOLIS every morning for payer authorizations expiring within 48 hours, logs each one to a Google Sheet with units and payer detail, and drafts the extension request in Outlook for a coordinator to review and submit. It posts a ranked Slack alert flagging anything under 12 hours in red, so no authorization lapses mid stay.
- No authorization lapses mid stay because the 48 hour window is checked every morning
- Extension requests are drafted and ready, not started from scratch under time pressure
- Authorizations already renewed drop off the tracker automatically from live XSOLIS status
Built for utilization review coordinators · hospital UM departments · case management directors · revenue cycle teams
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
dragonfly.xsolis.comin a real browser with your saved login - no setup, no API keys. -
1
XSOLIS - find expiring authorizations
xsolis.com
WebRun opens XSOLIS to find expiring authorizations. - Open XSOLIS and filter authorizations to those expiring within 48 hours or already lapsed
- Capture the payer, authorized units, units used, and expiry date or time for each
- Note whether an extension has already been requested for that authorization
Done when Every expiring or lapsed authorization is listed with payer, units, and expiry.
-
2
Google Sheets - log every expiring authorization
google.com
WebRun opens Google Sheets to log every expiring authorization. - Open the Authorization Expiry Tracker sheet
- Append a row for each expiring authorization not already logged today
- Sort by hours remaining, soonest first
Done when The tracker sheet reflects every expiring authorization sorted by urgency.
-
3
Outlook - draft the extension request
microsoft.com
WebRun opens Outlook to draft the extension request. - Draft an extension request in Outlook for each authorization without one already pending, naming the payer, patient, and units needed
- Leave every request unsent in Outlook Drafts for the UM coordinator to review and submit to the payer
Done when A drafted, unsent extension request is waiting for every authorization that needs one.
-
4
Slack - alert the UM team
slack.com
WebRun opens Slack to alert the UM team. - Post a Slack alert to the UM channel ranking authorizations by hours remaining before expiry
- Flag any authorization expiring in under 12 hours in red
Done when The UM team has a live, ranked Slack alert for every expiring authorization.
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 submit the extension request to the payer automatically?
No. WebRun drafts the extension request in Outlook and leaves it unsent. A UM coordinator reviews and submits every request to the payer.
How far ahead does it flag an expiring authorization?
It flags anything expiring within 48 hours and separately marks anything under 12 hours as urgent, so there's real time to act before coverage lapses.
What if an authorization was already extended in XSOLIS?
It reads the live authorization status each morning, so any authorization already extended or renewed drops off the tracker and the alert automatically.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.