All templates
For hospital revenue cycle teams, billing follow up staff & patient financial services

Keep every resubmitted claim from going quiet

Every morning, WebRun opens Waystar, checks the status of every corrected claim resubmitted in the past 45 days, logs each one to a Google Sheet reconciliation tracker, flags in Slack any claim with no payer response past the normal turnaround time, and drafts an Outlook follow up inquiry for your team to review and send.

  • No credit card
  • Under $0.01 per run
  • Cancel anytime
14,115 templates Safe automation No code
Every day at 7:30 AM WebRun
1 Waystar check resubmitted claim status
2 Google Sheets log the reconciliation tracker
3 Slack flag claims gone quiet
4 Outlook draft the payer follow up
Run a sample
In short

How do I reconcile the status of claims resubmitted through Waystar?

Every morning, WebRun checks Waystar for the status of claims resubmitted in the past 45 days, logs each to a Google Sheet tracker, and flags in Slack any claim with no payer response past its normal turnaround. It drafts an Outlook follow up for each overdue claim, left unsent for your team to review, so a resubmission never quietly disappears.

  • No resubmitted claim goes untracked past the payer's normal response window
  • Overdue claims get a drafted payer follow up instead of a manual search through Waystar
  • The reconciliation tracker shows exactly how many resubmitted claims are still pending by payer

Built for hospital revenue cycle teams · billing follow up staff · patient financial services · denial management specialists

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

  2. 1
    Waystar - check resubmitted claim status
    waystar.com How to Automate Waystar
    WebRun in Waystar: check resubmitted claim status
    WebRun opens Waystar to check resubmitted claim status.
    • Open Waystar and pull every corrected claim resubmitted in the past 45 days
    • Capture the resubmission date, payer, claim number, amount, and current status for each
    • Compare days since resubmission against that payer's normal response turnaround

    Done when Every resubmitted claim from the past 45 days has its current status and days since resubmission captured.

  3. 2
    Google Sheets - log the reconciliation tracker
    google.com How to Automate Google Sheets
    WebRun in Google Sheets: log the reconciliation tracker
    WebRun opens Google Sheets to log the reconciliation tracker.
    • Log or update each resubmitted claim in the reconciliation tracker with status, payer, and days pending
    • Mark claims as reconciled once a final payment or denial status is recorded
    • Keep a running count of resubmitted claims still pending by payer

    Done when The reconciliation tracker reflects the current status of every resubmitted claim.

  4. 3
    Slack - flag claims gone quiet
    slack.com How to Automate Slack
    WebRun in Slack: flag claims gone quiet
    WebRun opens Slack to flag claims gone quiet.
    • Flag any resubmitted claim with no status change past the payer's normal turnaround time
    • Post the flagged claims to the billing Slack channel with claim, payer, and days pending
    • Group the flagged list by payer so a slow payer is easy to spot

    Done when Every resubmitted claim past its expected turnaround is flagged in Slack.

  5. 4
    Outlook - draft the payer follow up
    microsoft.com How to Automate Outlook
    WebRun in Outlook: draft the payer follow up
    WebRun opens Outlook to draft the payer follow up.
    • Draft a follow up inquiry in Outlook addressed to the payer for each claim flagged as overdue
    • Reference the original resubmission date and claim number in the draft
    • Leave every follow up as an unsent draft for your team to review and send

    Done when Every overdue resubmitted claim has a drafted, unsent payer follow up waiting in Outlook.

Run settings

How is each run configured?

Starting pageWhere Chrome opens at the start of each run
www.waystar.com
ScheduleRuns automatically on this cadence
Every day at 7:30 AM
DeliveryHow each run's result reaches you
Reconciliation tracker · Google Sheets · Slack
OutputWhat each run produces - A Google Sheet reconciliation tracker for every resubmitted claim, a Slack flag for overdue ones, and unsent Outlook follow up drafts.
Tracker + draft follow ups
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 the follow up inquiry to the payer on its own?

No. Every payer follow up is saved as an unsent draft in Outlook. Your team reviews and sends it. WebRun never contacts a payer directly without that review.

How does it know a claim has gone quiet?

It compares days since resubmission against that payer's normal response turnaround, so a claim is only flagged once it has genuinely exceeded how long that payer usually takes to respond, not on a single fixed deadline for everyone.

What happens once a resubmitted claim finally gets a response?

It is marked reconciled in the Google Sheet tracker once a final payment or denial status posts in Waystar, and it stops appearing in the Slack overdue flag and Outlook follow up list.

Put this on autopilot.

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