AI automation for dental offices

Recall is a list, not a vibe. Hygiene overdue by your interval, exams due, and treatment a dentist already diagnosed and the patient has not scheduled. The source of that list should be the practice software, with rules the office manager can read: how many months, which appointment types, who to exclude because they asked not to be contacted or because a hold is on the account. A model that "finds people who might want a cleaning" from old emails is the wrong tool.

The message can be drafted for text or email in the practice's voice, with the real phone number and a request the front desk can fulfill. If the schedule system cannot expose openings, the message should ask for a preferred window, not offer a chair time that does not exist. Staff approve the batch or the template before it sends. A recall campaign that books into a fictional slot creates the angry call you were trying to avoid.

Patients who need a clinician, not a reminder, stay off the automated path. Swelling, a broken tooth, post op concerns: those are calls, transferred to a person, not a cheery overdue cleaning text. We will write the exclusion with you. We will not let a recall workflow swallow an emergency because the keyword "tooth" appeared.

A review request should follow a completed visit the practice is willing to stand behind, not every form fill and not a no show. The timing is usually after the patient has left and had a chance to decide they were treated fairly. The link should go to the review site you actually use. Asking twice, on three platforms, in the same week, is how you train people to ignore you.

The draft can thank them for the visit type in general language. It should not describe the diagnosis, the tooth number, or the fee in a text message that lives on a personal phone and in a marketing tool. If a patient replies with a clinical complaint, the automation stops and a person at the practice takes it. A bot that argues with a review, or offers a refund to change one, is a liability with a login.

Staff decide who is excluded: a visit that ended in a dispute, a patient who opted out, a minor where you need a parent's channel and a parent's consent to contact. We do not buy reviews, and we do not write the review for the patient. The request is for their words.

The front desk answers the same plan questions all week. A draft FAQ can turn the list you maintain into short answers: plans you participate with, plans you do not, how a pre estimate works in your office, what the patient should bring. The draft is only as true as the list. Date it. When a plan changes, a person updates the source and the answers get regenerated, not hand edited in twelve places until they drift.

The automation should refuse what it does not know. "Do you take my plan" gets an answer only if the plan is on the list. If it is not on the list, the answer is that a coordinator will confirm, not a guess. Benefits advice, remaining maximums, and "will this crown be covered" are not FAQ material. Those depend on a chart and a payer, and a wrong sentence costs the practice the relationship.

An example, labelled as an example: the office keeps a one page plan list, a monthly job turns it into a website FAQ and a short script for the front desk, and the office manager checks the diff before it publishes. A patient who names a plan that is absent gets a callback task, not a confident no or yes. That is a workflow sketch. It is not a claim about fewer cancellations.

New patient packets are full of fields that do not need a model: name, contact, the plan name they think they have, and a preferred time. Automation can check that the packet is complete and route the incomplete ones back with a specific missing item. It should not infer a medical history from a sentence, and it should not store that history in a chat tool because the chat tool was convenient.

What stays with staff is anything clinical or anything that creates a commitment. Confirming identity before discussing an existing chart. Deciding whether a described symptom is an emergency under your protocol. Quoting a fee that depends on an exam. Telling a patient what treatment they need. Changing the chart. Those are not drafts we quietly send. A coordinator can use a summary. The coordinator remains the one who acts.

Internal drafts are fair game when a person edits them: a recap of a phone call for the chart note that the clinician reviews, a list of unscheduled treatment pulled from the software, a handoff at the end of the day. The pattern is the same. The software prepares. The practice decides. If we cannot name the person who decides, the workflow is not ready.

• Recall rules written down, with exclusions for opt outs and clinical concerns
• Review requests only after a completed visit, with complaints routed to staff
• Insurance answers only from the plan list the office maintains
• Incomplete forms bounced back for the missing field, not for a medical essay
• Chart changes, fees, and treatment decisions left with the practice

A dental office handles health information. Recall status, appointment reasons, recordings, and forms can be that information depending on what you collect and where it goes. HIPAA is a set of duties: agreements with vendors who touch the data, minimum necessary collection, access controls, and a practice that can say where a message lives. It is not a badge we put on the website because a workflow uses software.

Before a workflow sends patient information to a model vendor, we ask whether a business associate agreement is required and whether that vendor will sign one. If the answer is no, we do not route that data there. A de identified operations problem, such as rewriting your public FAQ from a plan list with no patient names, is a different conversation from summarizing today's patients. We will not blur those.

We also will not claim the practice is compliant because this automation exists. Compliance is the practice's program, your counsel, and the vendors' terms, reviewed for the actual data path. Our job is to keep the path small and legible. A demo that says "HIPAA compliant" in the corner of a slide is not a scope of work, and we will not repeat it as if it were.