For / dental-medical
Recall list automation for dental practices
Your recall list is a spreadsheet your front desk prints on monday and forgets by wednesday. We turn it into a daily queue that fills the hygiene chair on its own.
Recall list automation is not a new PMS and not another patient app. It is a thin layer of agents that read your recall report every morning, score each patient by likelihood to book, and run staggered SMS and email outreach with a booking link. Responses drop into a queue your team already checks. You keep Dentrix or Open Dental. Nothing about your stack changes.
SHT 01Systems retained
The systems you keep
We wire ai on top via legacy system modernization. Nothing about your stack changes.
SHT 02Scope of work
What we build
SHT 03Timeline
Scope and timeline
Band
Light
Timeline
1-2 weeks
This is a light build. Timeline 1-2 weeks. Fixed fee, scoped on a 30-minute discovery call. You own the code, the prompts, and the credentials. No lock-in.
SHT 05Questions
Faq
What tools do you keep
All of them. Dentrix, Eaglesoft, Open Dental, Curve, your SMS tool, your recall report. We read from them and write tasks back. Nothing gets replaced.
How long does this take
First version live in week one. Full build inside two weeks. That includes the daily reader, the scoring, the staggered outreach, the response queue, and the weekly report.
What does it cost
Fixed fee. No per-message charges, no per-seat pricing, no monthly retainer back to us. You own the code and the prompts when we hand it off.
Do we need to replace Dentrix or Open Dental
No. Your PMS is the database. We wire AI on top via the same recall exports your team already runs. If your PMS changes tomorrow, we re-point the connector and keep going.
How does it handle patients with active treatment
The agent reads treatment plan status before it sends. Patients in active perio, ortho, or pending treatment get recall messaging tied to their plan, not a generic cleaning offer. Anyone the agent is unsure about goes to the staff queue, not the patient.
What about HIPAA
Agents run on your infrastructure or a private vps you own. Patient data stays inside your stack. We sign a baa when one is required and we keep phi out of any third-party llm call.
What if patients reply with questions
Replies route to the channel your front desk already checks, slack or email, with the patient context attached. No new app to log into. The agent handles confirmations on its own and only escalates the messy ones.
SHT 06Out of scope
When this is not worth automating
SHT 07Related
Related for dental-medical
See all problems we solve for dental-medical on the dental-medical pillar.