All templates

Automated Sigmund Insurance Authorization Tracking

Every morning, WebRun opens Sigmund Software, reviews every active authorization for days and sessions remaining, logs the ones expiring within 5 business days to a tracker sheet, and drafts a renewal request email to the payer's utilization review contact for your billing team to review and send.

Runs on WebRun · Strict Lockdown policy
Every morning at 6:30 AM WebRunorchestrates each step
1 Sigmund Software check active authorizations
2 Google Sheets log authorizations expiring soon
3 Gmail draft renewal requests for review
In short

How do I stop eating disorder treatment authorizations from lapsing?

WebRun reviews every active authorization in Sigmund Software each morning, flags the ones expiring within 5 business days or running low on sessions, and logs them to a tracker sheet sorted by urgency. It then drafts a renewal request to the payer's utilization review contact for each one, leaving the email unsent in Gmail until your billing team reviews and sends it.

  • No authorization lapses because every one is checked 5 business days ahead
  • Renewal drafts are ready for the billing team before an urgent gap appears
  • Already renewed authorizations drop off the list automatically from live Sigmund Software data

Built for eating disorder treatment centers · utilization review teams · billing and revenue cycle staff · residential and PHP program directors

Step by step

What does WebRun do on every run?

The exact actions WebRun takes, in order - in plain language, so you can adjust anything.

  1. WebRun signs in and gets to work

    Opens www.sigmundsoftware.com in a real browser with your saved login - no setup, no API keys.

  2. 1
    Sigmund Software - check active authorizations
    sigmundsoftware.com
    WebRun in Sigmund Software: check active authorizations
    WebRun opens Sigmund Software to check active authorizations.
    • Open Sigmund Software and pull every active authorization across levels of care
    • Calculate days and sessions remaining on each authorization
    • Flag any authorization expiring within 5 business days or with fewer than 3 sessions left
    • Capture the payer, authorization number, and utilization review contact for each flagged case

    Done when Every authorization expiring within 5 business days is listed with its payer and session count.

  3. 2
    Google Sheets - log authorizations expiring soon
    google.com
    WebRun in Google Sheets: log authorizations expiring soon
    WebRun opens Google Sheets to log authorizations expiring soon.
    • Open the Authorization Tracker sheet
    • Add a row for each flagged authorization with payer, expiry date, sessions remaining, and level of care
    • Mark whether a renewal request has already been sent for that authorization
    • Sort the sheet by days remaining, soonest first

    Done when The tracker sheet lists every at risk authorization sorted by urgency, with its renewal status noted.

  4. 3
    Gmail - draft renewal requests for review
    gmail.com
    WebRun in Gmail: draft renewal requests for review
    WebRun opens Gmail to draft renewal requests for review.
    • Draft a renewal request to the payer's utilization review contact for each authorization without a request already in progress
    • Reference the authorization number, current level of care, and clinical justification pulled from Sigmund Software
    • Save every draft unsent in Gmail for the utilization review team to check and send. Never submit a payer request automatically

    Done when A reviewable Gmail draft exists for every authorization that needs a renewal request, waiting on the utilization review team.

Run settings

How is each run configured?

Starting pageWhere Chrome opens at the start of each run
www.sigmundsoftware.com
ScheduleRuns automatically on this cadence
Every morning at 6:30 AM
DeliveryHow each run's result reaches you
Authorization tracker · Google Sheets
OutputWhat each run produces - A tracker row per at risk authorization and a Gmail draft renewal request for the utilization review team to send.
Spreadsheet + drafts
Setup & safety

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.

Your credentials stay in your own private environment - WebRun never stores your passwords.
Strict Lockdown

Every action is checked against this policy before it runs.

Domains ALLOWLIST
Typed input ALLOW
Shell command BLOCK
File uploads BLOCK
Runs in a contained environment More on policies
Good to know

Questions, answered

Will it send renewal requests to the payer on its own?

No. Every renewal request is saved as a Gmail draft for your utilization review team to check and send. WebRun never submits anything to a payer without a human reviewing it first.

How early does it flag an expiring authorization?

By default, 5 business days before expiry or when fewer than 3 sessions remain, whichever comes first. Both thresholds can be adjusted in your run settings to match your program's timeline.

What if an authorization was already renewed in Sigmund Software?

It reads the live authorization status each morning, so a renewed or extended authorization reflects the new expiry date and drops off the at risk list automatically.

Put this on autopilot.

Turn it on in minutes - or have our team set it up for you.