All templates

Automated Spravato Prior Auth Tracking

Every morning, WebRun opens Osmind, reviews all open Spravato esketamine and TMS prior authorizations, flags the ones pending too long, nearing a payer decision deadline, expiring soon, or freshly approved, logs each status to Google Sheets, and sends your billing team a Telegram digest so no start date waits on an unworked auth.

Runs on WebRun · Strict Lockdown policy
Every day at 7:00 AM WebRunorchestrates each step
1 Osmind review open prior authorizations
2 Google Sheets log auth status and deadlines
3 Telegram digest the auth worklist for billing
In short

How do I keep Spravato and TMS prior authorizations from stalling start dates?

WebRun opens Osmind every morning and reviews all open Spravato and TMS prior authorizations. It flags the ones pending too long, nearing a payer deadline, expiring soon, or newly approved, logs each status to Google Sheets, and sends your billing team a Telegram digest, so no treatment start date waits on an unworked authorization.

  • Stalled authorizations surface every morning before they delay a start date
  • Approvals nearing expiry are flagged in time to act
  • Newly approved auths reach scheduling the day they clear

Built for psychiatric billing teams · interventional psychiatry clinics · prior authorization specialists · practice revenue cycle managers

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 app.osmind.org in a real browser with your saved login - no setup, no API keys.

  2. 1
    Osmind - review open prior authorizations
    osmind.org
    WebRun in Osmind: review open prior authorizations
    WebRun opens Osmind to review open Spravato and TMS authorizations.
    • Open Osmind and go to the prior authorization and benefits section
    • List all open Spravato esketamine and TMS authorizations and their current status
    • Read the submission date, payer, expected decision window, and any approval expiry date
    • Capture patient initials, treatment, payer, status, days pending, and the next deadline for each

    Done when Every open Spravato and TMS authorization is listed with its status, days pending, and next deadline.

  3. 2
    Google Sheets - log auth status and deadlines
    google.com
    WebRun in Google Sheets: log auth status and deadlines
    WebRun logs each authorization's status and deadline in the tracker.
    • Open the Prior Auth Tracker sheet
    • Update each open authorization row with today's status, days pending, and next deadline
    • Flag authorizations pending beyond your expected turnaround and any approval expiring within two weeks
    • Sort by urgency so the auths at risk of delaying a start date sit at the top

    Done when The tracker reflects the current status of every open auth with at-risk ones flagged and sorted.

  4. 3
    Telegram - digest the auth worklist for billing
    telegram.org
    WebRun in Telegram: digest the auth worklist for billing
    WebRun sends the prior-auth worklist to the billing channel.
    • Send a morning digest to the billing Telegram channel with counts of pending, at-risk, and newly approved auths
    • List the authorizations pending too long or nearing a deadline so the team can follow up with the payer
    • Call out newly approved auths so scheduling can book the start, and link the full Google Sheet

    Done when The billing team has a Telegram digest of pending, at-risk, and approved authorizations for today.

Run settings

How is each run configured?

Starting pageWhere Chrome opens at the start of each run
app.osmind.org
ScheduleRuns automatically on this cadence
Every day at 7:00 AM
DeliveryHow each run's result reaches you
Auth worklist · Telegram
OutputWhat each run produces - A Google Sheet tracking every open Spravato and TMS prior authorization by status and deadline, plus a Telegram digest of what is pending, at risk, or newly approved.
Spreadsheet + digest
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

Does it submit or resubmit authorizations to payers?

No. WebRun tracks the status of open authorizations and surfaces the ones needing attention. Your billing team submits, follows up, and communicates with payers after reviewing the daily worklist.

How does it decide an authorization is at risk?

It reads each auth's submission date and expected turnaround in Osmind and flags any pending beyond that window or nearing a payer decision deadline. Approvals expiring within two weeks are surfaced too, so nothing lapses.

Is any patient information sent outside our tools?

No. The Telegram digest and Google Sheet use patient initials, payer, and status only, and both stay inside your own connected workspace, so no protected health information leaves your systems.

Put this on autopilot.

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