A dental practice's guide to WhatsApp automation: what order to do it in

A dental practice should automate WhatsApp in four stages, and booking comes last. Most practices start with the most visible thing, a booking bot, and it is close to the worst place to begin. Booking is the hardest exchange to get right and it touches the diary, so a mistake produces the phone call the practice was trying to remove.

The order that works starts with automation that carries no risk to the diary and builds the channel's standing with patients before anything depends on it.

What we'll cover

• Why does the order matter?
• Stage one: be reachable
• Stage two: reminders
• Building it with CodeWords
• Stage three: the things that move the diary
• Stage four: intake and recall
• What never gets automated
• Who owns it in the practice?
• Bringing the team with you
• Making it survive
• Limits worth knowing about
• What to build first
• Frequently asked questions

Key takeaways

• Automate in four stages: be reachable, send reminders, move the diary, then handle intake and recall.
• Build stage one for a month before adding anything, because it touches nothing that can go wrong.
• Appointment reminders are the highest-return automation, and they do not write to the diary.
• Never automate clinical advice, triage, results, complaints or safeguarding.
• Name one owner for the channel, usually the practice manager, with authority to turn it off.

Why does the order matter?

The order matters because early mistakes are expensive on a channel where the phone number is the asset. Each stage earns the next, and a practice that starts at the end usually stops.

Patients need to adopt the channel before anything important depends on it, which takes months.

Messaging limits start low. WhatsApp caps how many patients a new number can message at first, so a practice cannot message its whole list on day one.

The diary is the risk. Anything that writes to the diary can create a problem that reaches a patient in the waiting room.

Small things working build confidence, and confidence makes the later stages acceptable to the team.

Stage one: be reachable

Stage one makes the practice reachable on WhatsApp without touching the diary. Nothing in this stage can go wrong in a way patients see.

Send an automatic acknowledgement that says you received the message and when somebody will reply.

Answer the questions you already answer daily: opening hours, location, parking, whether you take new patients and the cost of a check-up.

Show a route to a person from the first message.

Collect opt-in during this stage, which makes stage two possible.

Run stage one for a month before adding anything.

Stage two: reminders

Stage two sends appointment reminders. Reminders are the highest-return automation in a practice, and they still do not write to the diary.

Send appointment reminders at the intervals that suit your patient mix.

Let a person handle rescheduling by reply at first. This is the safe version and captures most of the benefit.

Watch the quality rating as volume increases, which is when it first becomes relevant.

Fall back to SMS or a call for patients not on the channel.

A practice that stops after stage two still comes out ahead.

Building it with CodeWords

CodeWords connects to more than 3,000 integrations (CodeWords pricing page, 2026), and you make each connection once and reuse it.

1. Open CodeWords and start a new automation.
2. Describe what should happen in plain language to Cody, the automation builder: the stage you are at, what it handles, and what reaches reception.
3. Authorize the connections to your practice management system and your WhatsApp Business Platform account.
4. Describe the exceptions: pain, a clinical question, a complaint, an unclear message, a patient not on the channel.
5. Run each stage for a month before starting the next.

You describe the outcome; Cody builds it, connects it and deploys it. 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.

Stage three: the things that move the diary

Stage three automates the actions that write to the calendar: rescheduling, cancellation filling and new bookings. Build them in that order, and make new bookings last.

Automate rescheduling first. It is the first action that writes to the calendar.

Fill short-notice cancellations. The value is high, and the automation must handle the race when two patients claim one slot.

Automate new bookings last. New bookings are the hardest exchange.

Have reception review everything until the mapping between what patients ask for and what gets booked is reliable.

Never hold a booking only in the conversation. That failure double-books a chair.

Check that the practice system cooperates. Some practices discover at this stage that their software will not.

Stage four: intake and recall

Stage four sends intake links and recall messages once the channel is established. Patients accept these messages because stages one to three built trust.

Send intake links ahead of appointments, with the form itself in a proper system.

Send recall messages at clinically set intervals.

Contact lapsed patients carefully. A patient who stopped attending may have a reason.

Send post-treatment instructions, which patients keep and refer back to.

Follow up treatment plans where a plan was discussed and not booked.

What never gets automated

Never automate clinical judgement or sensitive patient exchanges. A person handles each of these, and the automation should hand the patient over quickly with a clear explanation of what happens next.

• Clinical advice, in any form, including reassurance about a symptom.
• Triage, meaning how urgently somebody needs to be seen.
• Results and anything about a diagnosis.
• Complaints, which have a defined process.
• Anything to a patient in pain, beyond routing the patient to a person immediately.
• Safeguarding concerns, which follow the established route without delay or queue.

Who owns it in the practice?

A named person owns the channel, usually the practice manager. An unowned channel degrades.

The owner watches the quality rating, the message volume and what reached reception.

The owner reviews unanswered questions weekly. That list shows what to improve.

The owner can turn it off, which matters on a bad day.

The clinical team decides the boundaries. The practice manager does not make that call.

Plan for about fifteen minutes a week of ongoing work once the channel is running. This is our working estimate from the review tasks above.

Bringing the team with you

Bring the team with you by answering the headcount question directly and starting with what reception dislikes. The practice team hears "automation" and reasonably wonders what it means for their jobs, and how you handle that decides whether the channel is used or worked around.

Say what happens to the time. The unspoken question is about headcount, and staying silent is worse than any answer.

Start with what reception dislikes, such as the same five questions and the voicemail backlog, rather than something they were proud of handling.

Let them keep the override. A receptionist who cannot intervene stops trusting the automation and goes back to the phone.

Involve them in the wording. They know how patients actually ask things.

Show them what it caught: the evening enquiry, the cancellation filled, the form completed in advance.

Watch for a parallel system. A notebook by the phone means the automation is not covering something real. Treat that as information, not disobedience.

Making it survive

A practice automation survives when the practice system stays the source of truth and a manual route exists.

Treat the practice system as the source of truth for anything about the diary.

Keep a manual route that works when the automation does not.

Watch the quality rating from the first message, not from the first problem.

Keep opt-in records in a form you can produce.

Report the outcome: messages received, handled automatically, reaching reception, and left unanswered.

Limits worth knowing about

Practice systems, patient adoption and messaging limits set the pace.

Practice management systems vary, and some do not integrate at all.

Patient adoption takes months, and some patients never use the channel.

Messaging limits start low and rise as your messages show good quality.

Regulatory requirements for patient communication and record-keeping apply here as elsewhere.

Automation does not create clinical capacity. It removes administration, which is worth saying to a team worried about what automation means for them.

What to build first

Build stage one, complete, and run it for a month: an acknowledgement, the answers you already give daily, a visible route to a person and opt-in collection. Stage one touches nothing that can go wrong, removes a real share of the phone volume, and makes every later stage safe to attempt.

Two habits make the difference. Do not let anything write to the diary until the practice system is the confirmed source of truth and reception has reviewed a month of bookings, since a double-booked chair costs more than the efficiency gained. And name one person who owns the channel, because an unwatched automation on a channel where the number is the asset is a risk.

Frequently asked questions

Where should a practice start?

Start with an acknowledgement, the answers you give daily, a visible route to a person and opt-in collection. Do not start with booking, which is the hardest exchange and touches the diary. Stage one cannot go wrong in a way patients see.

Why does the order matter?

The order matters because patients take months to adopt the channel, messaging limits start low, and anything that writes to the diary can cause a problem a patient meets in the waiting room. Each stage earns the next, and the order lets you stop at any point with something useful already working.

What is the highest-return automation?

Appointment reminders are the highest-return automation, and they do not write to the diary. A practice that completes only stages one and two still comes out clearly ahead, because reminders reduce missed appointments without any risk to the diary or the clinical record.

When should booking be automated?

Automate booking last. Reception should review every automated booking until the mapping between what patients ask for and what gets booked is reliable, and no booking should live only in the conversation. Every booking belongs in the practice diary, where the team can see and change it.

What must never be automated in a practice?

Never automate clinical advice (including reassurance about symptoms), triage, results or diagnoses, complaints, anything to a patient in pain beyond immediate routing, or safeguarding concerns. A person handles each of these, and the automation should hand the patient over quickly with a clear explanation of what happens next.

Who should own it?

A named person, usually the practice manager, should own it. The owner watches the quality rating and the weekly list of unanswered questions, and can turn the channel off. The clinical team sets the clinical boundaries, and the owner makes sure the automation stays inside them.

How much ongoing work is it?

Plan for about fifteen minutes a week once the channel is running. The work covers checking the quality rating and message volume, and reviewing what the automation could not answer. The unanswered list shows which new answers to add next.

Will this reduce the need for staff?

The automation removes administration rather than creating clinical capacity. Say this plainly to the team, because staff will wonder what automation means for their jobs. Explain which tasks move off their desks and which decisions stay with them, so nobody is surprised when the rollout starts.

How do I introduce this to the practice team?

Answer the headcount question directly, start with what reception actively dislikes, keep their ability to override the automation and involve them in the wording. Reception knows how patients actually ask things, so their wording makes the automated replies sound natural and reduces confusion.

What does it mean if reception keeps a notebook by the phone?

A notebook by the phone means the automation is not covering something real. Treat it as information rather than resistance: the notebook's contents are the most accurate list of what to fix. Review it weekly and add each recurring item to the automation.

Related reading

• Automated dental booking over WhatsApp
• Reducing dental no-shows with reminders
• Patient intake forms over WhatsApp