Automated Craneware Underpayment Recovery Worklist
Every Monday, WebRun opens Craneware, finds every claim paid below its contracted rate, builds a recovery worklist in Google Sheets ranked by dollar gap with a drafted dispute note for each, and posts your recovery team a Slack summary of the total at stake.
How do I build a worklist for recovering underpaid claims?
WebRun checks Craneware every Monday for claims paid below the contracted rate, builds a recovery worklist in Google Sheets ranked by dollar gap, and drafts a dispute note for each one citing the contracted rate versus what was paid. It posts the recovery team a Slack summary, but never files a dispute itself, your team reviews and submits every one.
- Underpaid claims get ranked by dollar gap instead of worked in whatever order they arrive
- Every dispute has a drafted starting point instead of being written from scratch
- No dispute goes to a payer without your recovery team's own review
Built for revenue integrity teams · payer contract analysts · patient financial services · revenue cycle directors
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.craneware.comin a real browser with your saved login - no setup, no API keys. -
1
Craneware - find claims paid below contract
craneware.com
WebRun opens Craneware to find claims paid below contract. - Open Craneware and pull claims where the paid amount is below the contracted rate for that payer
- Capture the claim, payer, contracted rate, paid amount, and underpayment gap for each
- Sort by dollar gap so the largest recoveries surface first
Done when Every underpaid claim from the last week is listed with its contracted rate, paid amount, and gap.
-
2
Google Sheets - build the ranked recovery worklist
google.com
WebRun opens Google Sheets to build the ranked recovery worklist. - Add each underpaid claim as a row in the recovery worklist, ranked by dollar gap
- Draft a short dispute note for each claim citing the contracted rate versus what was paid
- Leave the dispute note as a draft column for the recovery team to finalize and file with the payer themselves. WebRun never files a dispute on its own
Done when The worklist ranks every underpaid claim with a drafted dispute note awaiting the recovery team.
-
3
Slack - tell the team what to chase first
slack.com
WebRun opens Slack to tell the team what to chase first. - Post the recovery team a summary of this week's worklist, largest gap first
- Include the total dollar amount at stake across all flagged claims
Done when The recovery team has this week's ranked worklist and total in Slack.
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 file the dispute with the payer automatically?
No. WebRun only drafts the dispute note in the worklist. Your recovery team reviews, finalizes, and files every dispute with the payer themselves. Nothing gets submitted without that check.
How is an underpayment identified?
By comparing the paid amount on each claim against the contracted rate on file in Craneware for that payer, so the gap is measured against your actual contract, not a generic benchmark.
How are claims prioritized?
By dollar gap, largest first, so your recovery team spends its time on the claims worth the most before working down the list.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.