Recall and Rebooking Messages for Dental Patients
What's a recall message?
It's a note that invites a patient back, usually for a routine check-up. Rebooking messages do a similar job for someone who cancelled or missed a visit and hasn't set a new time.
Both are admin. They invite. They don't judge anyone's teeth, and they don't tell anyone they need treatment.
Where can AI help?
With words. Large language models can typically write, shorten and translate text.1 For reception that covers three jobs: softening a stiff template, shortening a long one, and making a plain version for patients who read English as a second language.
Give the tool a template with blanks, such as [first name], [last visit month] and [clinic phone]. Don't paste a patient list or a real record. The privacy guide explains why.
How do I avoid sounding pushy?
Ask the tool for a tone, and then read the result with a tough eye.
Pushy wording usually has a few signs: urgency that isn't real, guilt about being overdue, and a warning dressed up as a reminder. Cut those. What's left should be one friendly sentence, one clear action and one easy way to say "not now".
A calm version might run: "Hi [first name]. It's about time for your next check-up at [clinic]. Reply to this message or ring [phone] to find a time. If you'd rather hear from us later, just say so."
Some points the tool will drift towards and you should remove:
- Claims about what happens if the patient waits. That's a clinical statement, so it's the dentist's to make.
- Discounts or offers the clinic hasn't approved.
- Any hint about what's wrong with the patient's teeth.
- Repeated follow-ups in a short window.
Who decides when a patient is due?
The dentist or the clinic's policy. A tool shouldn't pick a recall interval, and it shouldn't tell a patient they're overdue by its own reckoning. The clinic's booking system holds the real due dates, and staff put those into the message.
The same line is drawn in the reception limits page. Wording is fine. Clinical judgment isn't.
What should a person check before sending?
Read each message as if you were the patient.
- Is the patient's name and visit information correct, and drawn from the booking system?
- Does it respect how this patient asked to be contacted?
- Does it mention treatment or health details that someone else could read on a phone screen?
- Does it make a promise the clinic hasn't approved?
- Is there a clear way to opt out of recall messages?
On contact preferences, one US rule applies. HIPAA's Privacy Rule asks covered entities to protect the confidentiality of how they communicate with patients.2 That applies to US covered entities. Elsewhere, look up your own regulator, such as the OAIC in Australia or the ICO in the UK.
Ahpra's guidance keeps health practitioners responsible for whatever an AI tool produces.3 A reception team isn't a practitioner, but a person should own every message the same way.
What about marketing rules?
A recall message sits close to marketing, and rules on unwanted messages differ by country. Don't guess. Check the national regulator's pages on commercial messages, such as the ACMA in Australia, the FTC and FCC in the United States, and the ICO in the UK. Keep an unsubscribe option in the wording, and let the clinic's policy decide the rest.
How many versions should I keep?
Two or three. A first-time recall, a gentle second note, and one for someone who's cancelled. Store them with the clinic's other templates and review them now and then, so a stale phone number or old address doesn't hang about for a year.
Notes and sources
- Large language model, Wikipedia
- Health Insurance Portability and Accountability Act, Wikipedia
- Meeting your professional obligations when using Artificial Intelligence in healthcare, Ahpra (Australian Health Practitioner Regulation Agency)