Patient communication for dental clinics: recalls, reminders and the front desk
Where a dental practice's admin time actually goes, which patient messages repay automating, and how to handle clinical and privacy boundaries properly.
Rebecca PearsonUpdated 11 min read
On this page
Dental clinics should automate three patient messages first: recall messages to patients who are overdue for a check-up, appointment reminders, and follow-ups on treatment plans. A practice loses money when appointments do not happen and when patients quietly stop coming. Both are communication problems, and a front desk member's memory is the usual fix.
This guide covers which messages repay building, how the front desk spends its time, and where the clinical and privacy boundaries sit.
What we'll cover
Key takeaways
- Measure failed appointments and recall attendance first, because both come from the practice-management system and show where to start.
- Recalls work best as a staged sequence with a booking link in the message that stops once the patient books.
- A cancel route as easy as the confirm route turns no-shows into cancellations with notice, which the practice can refill.
- Automation should send what the clinician produced and route clinical questions to a person, never answer them.
- Symptoms, complaints, clinical results and practice-initiated cancellations stay with a person.
The two numbers that matter
Measure two numbers before building anything: the failed appointment rate and recall attendance. The practice-management system probably already reports both, and the comparison tells you which process to automate first.
Failed appointments. An empty chair is revenue the practice cannot recover, because the hour cannot be sold twice. Most practices know their failure rate roughly. Few track it by appointment type, time of day or booking lead time, which is where the actionable pattern sits.
Recall attendance. This is the proportion of patients due for a check-up who book. It is usually the larger number and the less examined one. A patient who drifts away does not leave a gap in the diary, so nobody notices.
Recalls, the larger opportunity
A recall is a patient who was due for a check-up six months ago and has not booked. Most practices work through a list when there is time, so recalls happen in quiet weeks and not in busy ones.
Make the recall automatic and staged. Send a first message when the check-up is due, a second after a fortnight and a third after a month, each different from the last. A single message with no follow-up wastes most of the recall effort.
Make booking possible from the message. A recall that tells a patient to ring during working hours converts worse than one with a booking link. This change usually matters more than the message text.
Vary by interval. A patient on a six-month recall and a patient on a two-year interval need different messages, and the practice-management system already records which is which.
Stop when the patient books. The most common complaint about automated recalls is a reminder after booking, which makes the practice look disorganised.
Report what happened. Track how many recalls went out, how many booked and over what period. Without that, nobody can tell whether the change worked.
Reminders and no-shows
Send two reminders per appointment and make cancelling as easy as confirming. A patient who cannot attend and cannot easily say so becomes a no-show, and the practice cannot refill a no-show slot.
Send two reminders, not one. Send one at booking and one the day before, with a longer-notice message for appointments booked weeks ahead.
Make rescheduling easy. A cancellation with notice is a slot you can refill. Making the cancel route as easy as the confirm route turns empty chairs into filled ones.
Match the channel to the patient. A text or WhatsApp message is read more reliably than an email. Record each patient's preference and use it.
Build the short-notice list. When someone cancels, offer the slot to patients who wanted an earlier appointment. Maintaining that list by hand is the job that does not happen on a busy morning.
Track which appointments fail. Break failures down by type, by time and by how far ahead the patient booked. A specific pattern, such as one weekday slot or long booking lead times, is actionable in a way the overall rate is not.
Treatment plan follow-up
Follow up on every treatment plan on a schedule you decide in advance. In many practices a patient receives a plan, leaves to think about it, and nothing further happens, because no mechanism exists.
Follow up on a fixed schedule. Send a message a week later and another after a month. Phrase them as an offer to answer questions, not as a sales sequence.
Send what the patient needs to decide. Include the plan, the cost, the options and any finance arrangements you offer. Patients often decline treatment for practical reasons, not clinical ones.
Get unanswered plans in front of a person. After two attempts with no response, a phone call from someone who can answer clinical questions works better than a third message.
Never automate the clinical content. The plan is a clinical document. The automation sends what the clinician produced and prompts at the right times, and nothing more.
What the front desk actually spends time on
The front desk spends its automatable minutes on four tasks: repeated questions, chasing forms, relaying messages to clinicians and post-treatment check-ins.
Answering the same questions. Opening hours, parking, accepted insurance, preparation for an appointment and the cost of a check-up all have fixed answers.
Chasing forms. Send medical history, consent and updated-details forms before the appointment, with a reminder if the patient has not completed them. This removes a queue at the desk and a delay in the surgery.
Relaying messages to clinicians. When a patient asks something the receptionist cannot answer, it becomes a note, a conversation and a callback. A routed, tracked message removes the step that gets forgotten.
Post-treatment check-ins. After an extraction or a longer procedure, a message asking how the patient is doing is clinically useful and reassuring. Busy days often skip it.
To build these, connect the practice-management system to a messaging channel with rules about who gets what and when. On CodeWords, you describe that in plain language: which patients, which messages, what should stop them, what needs a person. Cody, the automation builder, builds it, connects it to the systems you already use, and deploys it. Automations connect to more than 3,000 integrations (CodeWords pricing page, 2026). The free plan covers light use, with Pro at $39 per month and Business at $100 per month as usage grows (CodeWords pricing page, 2026). Details are on the pricing page.
Privacy and clinical boundaries
Dental practices hold health data, so keep three distinctions firm.
Contact instructions are not clinical advice. Telling a patient when the appointment is, or what to bring, is administrative. Telling a patient what to do about pain is clinical and belongs with a clinician.
Notifying the practice is not replying to the patient. An automation can route an incoming question to the right person without answering it, which is the correct design for anything clinical.
Passing a patient to a person means a real person who is available. If a patient's message needs a clinician, the automation must get it to one and not produce text that reads like an answer.
Also keep clinical detail out of message content where a generic prompt to contact the practice will do. Record consent for the channel you use, and apply your retention policy to message histories as well as records. Check what your practice-management supplier's terms permit before connecting anything to it.
What not to automate in a clinic
Do not automate symptoms, practice-initiated cancellations, complaints, clinical results or the first contact after a difficult appointment. Each needs a person.
- Anything about symptoms or pain. A patient in discomfort needs a person quickly.
- Cancellations initiated by the practice. When you must move a patient, phone them. An automated message that moves an appointment reads badly and creates more work.
- Anything involving a complaint. Route it to a person immediately, with no automated acknowledgement that could read as dismissive.
- Clinical results. A person decides what goes out and when.
- The first contact after a difficult appointment. Automated check-ins are useful in general and wrong immediately after something went badly. Build a suppression rule for those cases.
Frequently asked questions
What should a dental practice automate first?
Automate recalls first if recall attendance is lower than you want, because the revenue is larger and the process is usually the least systematic. Start with reminders if the failure rate is the more pressing number. Measure both from the practice-management system before choosing.
Will patients find automated messages impersonal?
Less than practices expect, if the messages are useful and stop when the patient acts. Patients notice a reminder that arrives after they have already booked, or a message that ignores something they told you. Fix those two problems first.
Is WhatsApp appropriate for patient communication?
Yes, for administrative contact. Many patients prefer WhatsApp and read it more reliably than email. Get consent for the channel, keep clinical detail out of message content and apply your retention policy to the conversation. Keep clinical discussion in the practice.
How do we handle patients who do not use messaging?
Record each patient's preference and use the channel they want, including post and telephone. An automation can prepare a call list as easily as it sends a message. This keeps the process consistent without forcing a channel on anyone.
Does this replace the receptionist?
No. Automation removes the repetitive part of the role: sending reminders, chasing forms and answering the same five questions. It leaves the part patients value, which is talking to someone who can help with a real problem.
How do we measure whether it worked?
Compare the failed appointment rate and recall attendance before and after, using reports from the practice-management system. Allow a full quarter. If neither number moves, change the messages or the timing instead of adding more automation.
What about patients who reply to an automated message?
Decide this before you switch anything on, because patients will reply. Replies must reach a person promptly, and an unmonitored channel is worse than no channel. Route replies to whoever is on the desk, with an alert.
Should we offer online booking as well as messaging?
Yes. Online booking serves the patient who has decided and wants a slot now. Messaging serves the patient who has a question first, which describes most patients who have drifted away. A recall that patients can also reply to converts better than a booking link alone.
How far ahead should recalls go out?
Start recalls at the due date and stage them over the following weeks. Sending before the due date sounds proactive but produces bookings that patients later cancel, because they were not ready to book.
Can this work alongside our practice-management system?
Usually, depending on what the supplier exposes. Some systems have APIs, some produce scheduled exports and a few offer neither. A scheduled export plus a separate sending channel still covers recalls and reminders. Check the supplier's terms before connecting anything.
How many messages is too many?
A booking confirmation, one reminder and a recall sequence that stops on booking is a reasonable volume. Complaints arrive when messages keep coming after the patient has acted, or when messages are promotional instead of about the patient's care.