Multi-Channel Capture & Instant Response
Every new patient enquiry, from any channel, at any hour, becomes one patient record and receives a real answer within minutes, with anything clinical routed to a clinician rather than answered.
- Tier
- Foundational
- Build order
- 1st of 7 for dental practices
- Shape of it
- 8 steps, 1 decision point, 2 escalation rules
- At launch
- Runs supervised, with you approving what goes out
The problem this solves
Dental enquiries arrive when the office is busiest and when it is closed. A missed call during a procedure, a web form at 11pm, an Instagram message on Sunday, a Google Business message nobody has ever opened. The front desk cannot watch all of them while also seating patients and running the phone.
So enquiries get triaged by whichever channel somebody happened to check, and the rest wait. A patient in pain does not wait. They call the next practice on the list, and the practice that answered first gets a patient who will be worth years of hygiene and restorative work.
There is a second failure underneath it: the caller with a broken tooth and the caller asking about whitening get the same treatment, because the queue is ordered by who was answered first rather than by what the appointment actually is.
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
- A timing rule you set
- It escalates to a person
Step 1Trigger
A patient calls, misses, fills a form, or messages on any connected channel.
Step 2
Whatever the channel, one patient record is created, or matched to an existing one, so a patient of record is never treated as a stranger.
Step 3
The record is stamped with the source, the reported reason, and the time it arrived.
Step 4Branch
The enquiry is classified against a triage ladder agreed with the dentist:
Most urgentLeast urgent- 1Trauma, swelling, uncontrolled bleeding, or facial infection
- 2Pain that is keeping the patient awake
- 3Broken tooth, lost crown, lost filling, or a failed restoration
- 4New patient exam
- 5Hygiene or recare
- 6Cosmetic enquiry with no clinical urgency
Step 5Timing
Within minutes a reply goes out on the channel they used, naming the reason they contacted the practice, and offering real availability for the right appointment type and length.
Step 6Escalation
Anything clinical is not answered. It is flagged, routed to the dentist or the clinical lead, and the patient is told a clinician will respond personally. There is no exception to this and no cleverness in the classifier: it errs toward escalation every time.
Step 7Escalation
The top two rungs escalate on a timer. If nobody has acknowledged a swelling or a trauma inside the agreed window, it goes to the dentist directly.
Step 8
Every enquiry that has not reached an outcome stays on one list until it does. Calls that were abandoned before anyone answered are on that list too, with the number.
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
Map
Inventory every channel an enquiry can arrive through, including the ones nobody owns: the old tracking number on a bus stop advert, the Google Business chat, the practice Instagram.
Nothing is designed until we have looked at what already exists, including the parts nobody officially owns.
- 2
Build
Connect each into a single inbox and confirm a test enquiry from each creates one correctly attributed record.
Built inside the software you already run, against your stages and your language.
- 3
Build
Build the matching rule against name, date of birth and phone so patients of record are recognised, not duplicated. Duplicate records are the quiet cause of most of the reporting problems in a practice.
- 4
Agree
Write the triage ladder with the dentist and get the clinical rungs signed off in writing. This is a clinical review step, not a copywriting one.
The thresholds, the wording and the names are yours. We write them down with you and get the consequential ones signed off.
- 5
Build
Build the classifier and test it against deliberately ambiguous messages ("my tooth feels weird and my face is a bit puffy"). Err toward escalation.
- 6
Agree
Set the escalation windows and name the person at each level, including who covers when that person is in a procedure.
- 7
Build
Connect booking to real appointment types with real lengths, so an emergency is not booked into a twenty-minute hygiene slot.
- 8
Prove
Run in supervised mode first, with every outbound message reviewed before it sends, until the dentist signs off on the tone.
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
Dental enquiries arrive when the office is busiest and when it is closed. A missed call during a procedure, a web form at 11pm, an Instagram message on Sunday, a Google Business message nobody has ever opened. The front desk cannot watch all of them while also seating patients and running the phone.
After this one is live
Enquiries stop being sorted by luck. The Sunday message and the Tuesday phone call get the same response. The front desk opens one list instead of five inboxes, already ordered by what the appointment is. Clinical questions reach a clinician faster than they did when a human was triaging, because the routing no longer waits for somebody to be free.
The abandoned calls become visible for the first time, which is usually the most uncomfortable and most useful thing this system does.
How to measure whether it worked
Your arithmeticRun with your numbers, not ours
Run it on the practice's own numbers. Pull last month's inbound contacts, count how many were abandoned or never returned the same day, and apply the practice's own booking rate, its new patient show rate, and its average first-year value of a new patient. That figure is the recurring cost of the current response gap, and it is demand already paid for.
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.
- 1Multi-Channel Capture & Instant Responseyou are hereFastest visible result, lowest clinical risk, and it earns the trust everything else depends on.
- 2New Patient Preparation, Insurance & Show-Up ProtectionProtects the chair time already booked and fixes the estimate, which System 4 is built on top of.
Tier 2Growth
The recoverable money. These work the pools the foundational systems have made visible for the first time.
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.