Unscheduled Treatment Recovery
Every piece of diagnosed treatment gets a status, a value, an owner, an age, and a dated next action, and the follow-up branches on why the patient has not proceeded rather than sending the same reminder four times.
- Tier
- Growth
- Build order
- 4th of 7 for dental practices
- Shape of it
- 10 steps, 1 decision point, 2 escalation rules, 1 handoff to a person
- At launch
- Runs supervised, with you approving what goes out
The problem this solves
This is the largest recoverable pool in most practices, and it hides because five different stages are talked about as one.
diagnosed → presented → accepted → scheduled → completed
Treatment gets diagnosed and never presented, because the schedule ran late. Presented and never accepted, because the patient did not understand what happens if they wait. Accepted at the chair and never scheduled, because the patient walked to the front desk, the phone rang, and they left with a card. That last one is the most expensive failure in dentistry, because the patient already said yes.
Then it ages. It sits in the practice management system as treatment planned, with no owner and no next action, and it is still there eighteen months later when the tooth fractures and the crown has become an extraction and an implant.
And "let me think about it" is not one objection. It is at least five, and they need completely different answers:
Cost. The number is real. The answer is sequencing, financing, or using this year's remaining benefit and next year's, not a discount.
Fear. They are not weighing the price. The answer is sedation options, what it actually feels like, and a shorter first appointment.
Doubt about the need. They feel fine. The answer is the photograph, the radiograph, and an honest statement of what happens if they wait.
Timing. They have a wedding, a trip, a busy quarter. The answer is a date, not a nudge.
Someone else decides. A partner, or a parent. The answer is a version of the plan built to be shown to somebody who was not in the room.
All five get "just following up to see if you had any questions", if they get anything.
How it works, step by step
Every wait, threshold and branch below is a value we set with you during the build, against your stages and your language. None of it is a default we impose.
- What starts it
- It decides something
- It hands over to a person
- It escalates to a person
Step 1Trigger
Treatment planned in the chair generates a record with the procedure, the tooth or area, the value, the clinical urgency, whether it was presented, and whether financing was discussed.
Step 2
It is assigned an owner by name. The treatment coordinator, the practice manager, or the dentist. Not a queue, and not "the front desk".
Step 3A person
Same day, the patient receives the summary: what was found, what is recommended, what it costs, what their insurance is estimated to cover, and what happens if they wait. Written to be read by a person who was anxious and half-listening while somebody had their hands in their mouth.
Step 4
The system tracks whether that summary was opened. Unopened after forty-eight hours is a different problem from opened and not acted on, and it gets a different response: a call, not another message.
Step 5Escalation
At the first branch point the patient is asked one question rather than nudged: what is the part you are still weighing? The answer routes the sequence into one of the five branches above.
Step 6Branch
Each branch has its own content, approved by the dentist. The fear branch is written by the dentist, not by a marketer.
Step 7Escalation
Anything above an agreed value with no response escalates to a live call from the treatment coordinator, with the value and the clinical urgency attached.
Step 8
Clinical urgency overrides everything. Treatment the dentist flagged as time-sensitive does not sit in a nurture sequence; it goes to a person.
Step 9
A stop condition ends everything the moment the patient schedules, declines, or asks not to be contacted.
Step 10
Every closed plan gets a reason code, reviewed monthly. That is where next year's presentation and financing changes come from.
How it gets built
Built inside what you already run
- Dentrix
- Eaglesoft
- Open Dental
- Curve
- or whatever your office already runs on
Nothing to log into and nothing to license. If a system needs a record your platform does not hold, we add the field to your platform rather than starting a second one beside it.
This is the actual build order, in the phases its own steps fall into. It runs in supervised mode first, with you approving what goes out, until you are happy with the tone.
- 1
Agree
Agree the fields that make a treatment plan record complete, and make it impossible to close the appointment without them.
The thresholds, the wording and the names are yours. We write them down with you and get the consequential ones signed off.
- 2
Agree
Name the owner for each plan type. This is the step practices skip and it is the one that decides whether this works.
- 3
Build
Rewrite the treatment summary with the dentist. Most existing ones are a printout of procedure codes and a total, which is a document written for the practice management system rather than for the patient.
Built inside the software you already run, against your stages and your language.
- 4
Build
Connect financing so the monthly figure appears next to the total from the start, because those two numbers answer different questions.
- 5
Build
Build the open-tracking and the two different responses that follow from it.
- 6
Agree
Write the five branches with the dentist, including exactly what is said honestly about waiting.
- 7
Agree
Set the escalation value threshold and the clinical-urgency override.
- 8
Build
Build the stop conditions and the suppression, and test them before the sequence goes live.
- 9
Agree
Agree the reason codes and put the monthly review in somebody's diary.
- 10
Prove
Load the existing backlog of unscheduled treatment on day one, oldest and highest value first, and work it by hand before automating anything. That backlog is usually the fastest money in the entire engagement.
It runs with a person approving what goes out until you are happy with the tone. Nothing sends unreviewed on day one.
What changes after it goes live
How it runs today
This is the largest recoverable pool in most practices, and it hides because five different stages are talked about as one.
After this one is live
No treatment plan sits without an owner and a date. Unscheduled treatment becomes visible by age band and by value, which is usually the first time the owner has seen that number. And the follow-up conversation changes from "did you have any questions" to an answer to the specific thing that stopped them.
How to measure whether it worked
Your arithmeticRun with your numbers, not ours
Pull every treatment-planned procedure from the last twelve months that was never scheduled, and total the value by age band: nought to seven days, eight to thirty, thirty-one to ninety, and over ninety. Apply the practice's own historical rate of converting contacted unscheduled treatment. That number is the pool. It is typically the largest figure in this playbook and the practice has every input needed to calculate it before the call ends.
We agree the baseline before anything is built, and we do not take credit for things that were going to happen anyway. There is no figure on this page claiming what we have produced for somebody else, because there is no verified figure to publish.
What we will not do
This is from the same delivery document as everything above it. It is on the page because a supplier who has not thought about it will not tell you, and you would find out later.
Every system here touches protected health information and sends automated messages to patients in the United States. Two separate regimes apply and satisfying one does not satisfy the other. HIPAA governs the information and the vendors. The TCPA governs the calls and texts.
HIPAA
A dental practice transmitting claims or eligibility electronically is a covered entity, and its patient information is PHI.
- A signed Business Associate Agreement with every vendor that creates, receives, maintains or transmits PHI, before that vendor touches any of it. This includes the messaging platform, the SMS gateway, the hosting provider, the CRM, any analytics tool and any AI service in the path. The narrow conduit exception covers transmission-only services with no routine access; it does not cover an ordinary patient-engagement or automation platform.
- Minimum necessary. Send the fields the system needs, not the chart. A reminder needs a date, a provider and a contact number. It does not need a diagnosis.
- What goes in an unencrypted message. HIPAA does not ban PHI in SMS or email, and HHS explicitly permits appointment reminders without authorization. What does not belong in one: diagnoses, clinical findings, procedure names that reveal sensitive treatment, radiographs or images, medication details, insurance or balance information, and anything about a second patient.
- Offer and honour confidential communication requests. A patient can ask to be contacted a different way, and that request has to reach every system.
- Treatment, payment and operations do not need an authorization. Recall, appointment reminders, pre- and post-operative instructions, and a request to schedule treatment already recommended are ordinarily treatment-related. Promotion is different. "Book this month and save" is marketing whatever list it went to, and calling a sequence a recall does not make it one if the purpose is to sell.
- Financial remuneration changes the analysis. If a third party pays the practice or a vendor for a communication, HIPAA's marketing rules can apply to something that would otherwise be operations.
- Audit logs, role-based access, retention limits, a documented risk analysis and an incident response procedure, all of them boring and all of them the first thing asked for if anything goes wrong.
TCPA
HIPAA permission is not TCPA consent.
The FCC's healthcare treatment exemption can reduce the consent standard for messages from a covered entity, but it is narrow and it comes with hard conditions that shape every sequence in this playbook:
- Only to the wireless number the patient gave the practice.
- The provider's name and contact information in the message.
- Concise: generally no more than 160 characters for a text.
- No cost to the patient.
- One message per day, and no more than three per week, counting calls and texts together.
- An easy opt-out, honoured immediately.
That frequency limit is a design constraint, not a footnote. It is substantially stricter than what a normal marketing automation would send, and it means every sequence in this document has to be sparse and every message has to earn its place. A five-touch week is not an aggressive cadence here. It is non-compliant.
The exemption does not cover advertising, promotional offers, solicitation of new services, billing or debt collection, or anything unrelated to the patient's care. Those need consent on the ordinary standard, captured and documented per channel and per purpose. A phone number in the chart is not blanket permission for promotional automation.
The line that is never crossed
No automated system answers a clinical question. Ever. Not whether it will hurt, not whether a symptom is normal, not what medication to take, not whether treatment is needed. Every one of those routes to a clinician, and the patient is told a person is being reached. Every classifier in this playbook errs toward escalation, and every one of them is tested against deliberately ambiguous messages before it goes live.
Nothing in this document is legal, clinical or regulatory advice. State privacy and telemarketing law, dental board advertising rules, payer contracts and the exact sending technology can each add requirements, and this area has moved more than once recently. Every template stating a clinical or commercial term requires review by the practice's own counsel before it goes live.
Nothing here is legal advice. Rules in this area have moved more than once recently, and every template that states a commercial term or a guarantee goes to your own counsel before it goes live.
Seven systems fordental practices.
We build one at a time and prove it moved before starting the next. The tiers are the dependency order, not a price list.
Tier 1Foundational
Nothing arrives late or unowned. These come first because everything above them assumes they are true.
Tier 2Growth
The recoverable money. These work the pools the foundational systems have made visible for the first time.
- 3Open Chair Recovery & a Working ASAP ListTurns System 2's cancellations into recovered chair time.
- 4Unscheduled Treatment Recoveryyou are hereUsually the single largest recoverable pool in the practice.
Tier 3Flagship
One connected system end to end, plus what the owner reads on a Monday. Only once the pieces are proven individually.
The tiers are the dependency order for dental practices, not a price list. Most firms do not start at the first one, because the order is a default and the call is where it gets changed.
A note on sequencing this trade
Do not build all seven at once.
Each stage is proven against its agreed measure before the next begins.
One sequencing note specific to dentistry. System 4's existing backlog should be worked by hand in week one, before any of it is automated. It is the fastest money in the engagement, it proves the value of the whole programme before a single sequence goes live, and working it manually is what tells you what the five branches should actually say.
Back to the dental practices overview for the stage map and where these fit.
Is this the oneyou need first?
Often it is not. On the call we look at what is actually costing you most right now, which is frequently a different system from the one that brought you to this page. If there is nothing worth building yet, we will say so.