Rekey Desk / Who it is for / Dental groups and DSOs
DSO Benefits Desk
Back office keying for dental groups and DSOs
A DSO buys two offices and the playbook has to run on day one. Each location posts benefits its own way, the same response gets typed twice, and someone asks whether you need more headcount (search intent, captured 2026-09-24).
Rekey Desk maps the keying at each location, writes one Field Rulebook the whole group follows, builds the Keying Build into your PMS, and routes unreadable responses to an Exception Queue. Start with the Rekey Map at your busiest office.
Request a sample run See a sample run
Last updated . Rekey Desk is run by Mike Rodgers from Denver and works remotely with operators across the United States.
What this covers in a dental group
Eligibility checks, benefits posting, claim attachments and the front desk keying around them. The payer response or attachment is read once and typed into the practice management system the office already uses. Dentrix, Eaglesoft and Open Dental are examples of where the keying lands.
The group's own words: verify insurance and post benefits across every location without adding headcount (search intent, captured 2026-09-24). The second: automate the front desk, billing and insurance without switching our PMS (search intent, captured 2026-09-24).
One Field Rulebook for every location
Every field has one source, one target, one format rule and one named decider, so location three keys it the way location one does.
- Remaining frequency: whole visits as listed, with the response date.
- Annual maximum and deductible: amounts copied exactly as shown.
- Waiting period: status text copied, not interpreted.
- Claim attachment: page order as the payer requests.
Onboarding an acquisition
The question after a deal closes is how to run your playbook at the new office from day one (search intent, captured 2026-09-24). Start with one workflow: carry the existing Field Rulebook into the new PMS, map what that office does differently, and fix the differences in writing.
For scale: a dental platform bundles a staffed revenue cycle operation for $299 a month per practice, with its own practice management system (Trust AI via PR Newswire, 2026-09-01). That trade asks you to move systems; this one does not.
What stays with your team
Your treatment coordinators present plans and estimates, your dentists decide treatment, and your team submits claims and calls payers. The build keys fields and makes no clinical or coding decisions.
You own the Field Rulebook, the exception log and the build configuration, and every exception arrives with a reason code and the source page.
What correct looks like
The checks behind this page
- Check: every step in the Rekey Map names the response it is read from and the PMS screen it types into.
- Check: every field in the Field Rulebook has a source, a target, a format rule and a named decider.
- Check: the Keying Build keys a held-back sample your staff already keyed, and every mismatch is listed.
- Check: every exception carries a reason code and the source page, and nothing is guessed.
Named owner of mistakes: Mike Rodgers. Every field your staff mark wrong is counted in the Monthly Accuracy Report, the rule behind it is fixed, and the affected records are checked again before the next batch.
Start here
Workflow Teardown, $2,500 fixed
Readout 10 business days after your de-identified sample set arrives. The $2,500 is credited in full against the Keying Build if you sign within 30 days of the readout. If the map shows the workflow is not worth automating, the readout says so, and you keep the map and the rulebook.
The Keying Build is a fixed price quoted after the teardown, and Run and Check is a monthly price quoted with it.
What your people still own
- Your front desk confirms coverage with the patient at check-in.
- Your named people decide every exception and every conflicting response.
- Your dentists decide treatment and your team submits claims.
- You own the Field Rulebook, the exception log and the build configuration.
FAQ
Questions about this page
- What does the Workflow Teardown cost?
- It is $2,500 fixed, credited against the build if you sign within 30 days. The readout arrives 10 business days after your de-identified sample set, with a sample run on 25 documents you can compare.
- Do we have to switch our PMS?
- No, the build keys into the PMS you already run, and switching systems is out of scope. Dentrix, Eaglesoft and Open Dental are examples of where this keying lands.
- How does one rulebook handle every location?
- Each field has one source, one target, one format rule and one named decider, and every location follows it. Where a location differs, the difference is written into the rulebook instead of left as a habit.
- Do you need our patient data to start?
- No, the teardown runs on de-identified or synthetic documents. A build that touches PHI starts only after a signed Business Associate Agreement and runs through accounts you control and can revoke.
Request a sample run
Tell us the workflow that eats the most typing
One short form. We reply by email with what we need for the sample run. No patient data in this form, please.
- Workflow Teardown: $2,500 fixed
- Readout 10 business days after your de-identified samples arrive
- Credited in full against the build if you sign within 30 days