Automated Dental Fee Schedule Change Log
Every Monday, WebRun opens Denticon, detects which payer fee schedules changed in the last week, captures the specific codes and amounts that moved, drafts a plain language broadcast to office managers that waits for approval, and posts the change log to your internal Slack channel.
How do I communicate insurance fee schedule changes to all my dental offices?
WebRun opens Denticon every Monday and detects which payer fee schedules changed, capturing the exact codes, old and new amounts, affected offices, and effective dates. It drafts a plain language broadcast to office managers, left unsent in Gmail for approval, and posts the full change log to Slack, so fee changes reach offices cleanly with a human in the loop.
- Every fee schedule change is captured at the code level with old and new amounts
- The office broadcast is drafted for approval, so nothing goes out unreviewed
- The internal Slack change log becomes the record of what moved and when
Built for DSO revenue cycle teams · billing managers · office managers · dental group CFOs
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.denticon.comin a real browser with your saved login - no setup, no API keys. -
1
Denticon - detect fee schedule changes
planetdds.com
WebRun opens Denticon to detect fee schedule changes. - Open Denticon and review the payer fee schedules for changes since the last run
- Capture each changed procedure code, the old allowed amount, and the new allowed amount
- Identify which offices and plans each change applies to
- Note the effective date and whether the change raises or lowers reimbursement
Done when Every fee schedule change is captured with the codes, amounts, offices, and effective date.
-
2
Gmail - draft the office broadcast for approval
gmail.com
WebRun opens Gmail to draft the office broadcast for approval. - Draft a plain language broadcast to the affected office managers explaining what changed and from when
- Summarize the notable code level moves and what they mean for treatment estimates and collections
- Leave the broadcast as a draft in Gmail for a person to review and send. Do not send it automatically
- Keep the message scoped to the offices each change actually affects
Done when A clear office broadcast is drafted and waiting in Gmail for approval.
-
3
Slack - post the internal change log
slack.com
WebRun opens Slack to post the internal change log. - Post the full change log to the revenue cycle Slack channel
- List every changed code with old and new amounts and the affected plans
- Flag any material reimbursement drop that may need a treatment estimate review
- Keep the log as the internal record of what changed and when
Done when The revenue cycle team has the full fee schedule change log 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 the broadcast go to offices without me?
No. WebRun drafts the office broadcast in Gmail and leaves it unsent. A person reviews and sends it. Only the internal change log posts automatically to your own Slack channel.
What fee schedule detail does it capture?
It captures each changed procedure code with its old and new allowed amount, the affected offices and plans, and the effective date, so the team sees exactly what moved rather than a vague notice that something changed.
Does it change any fees in Denticon?
No. It only reads the fee schedules to detect what changed. It never edits a fee, a plan, or an estimate. Your revenue cycle team owns any updates, informed by the change log and the drafted broadcast.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.