Field notes · FN-004 · How dental clinics actually book — and why no-show recovery is mostly listening
Drawing G2-FN-004 · Field journal · entryIndustry view

How dental clinics actually book — and why no-show recovery is mostly listening

By Andrew Maryasov · Grow2.ai2024-10-09 · 8 min
Entry FN-004
Filed 2024-10-09
Read 8 min
Category Industry view
Languages — EN
Entry №
FN-004
Field log

Before Grow2.ai built the booking daemon for Clinica Via, two engineers spent six weeks at the front desks of three Ukrainian dental clinics — one downtown Lviv, one suburban Lviv, one Kyiv. We listened to ~1,800 patient calls and read every confirmation message the receptionists sent. This is what actually moves the no-show needle, and it isn't what we expected.

What we expected

We expected the bottleneck to be cadence — too few reminders, sent too late. The literature on healthcare no-shows talks about cadence. Reception's own complaints were about volume — "we don't have time to call everyone". So we'd ship a daemon that called everyone, on a rigorous schedule, and watch no-shows drop.

What we found instead

Patients who no-showed didn't fail to be reminded. They were reminded; they just didn't reschedule. The reception script for confirmation calls was efficient and impersonal: "Доброго дня, нагадую про візит завтра о 14:00, чи буде зручно?" The patient, who had a colonoscopy that morning or a sick child or a work emergency, would say "так" and not show up. The receptionist marked it confirmed.

The deeper finding: patients didn't lie. They said "yes" because the question was binary. There was no easy way to say "actually, can we move it?" without feeling rude. Reception was so brisk that proposing a reschedule felt like more friction than just not showing up.

What the daemon does differently

The Booking Daemon's confirmation message is not "will you be there". It is:

"Hi! Reminder of your appointment with Dr. K. tomorrow at 14:00. If something has come up and you'd rather move it, just reply with the day or two that'd work better — I'll find you a slot. No need to call."

That message gives the patient three options: confirm by silence, reply "yes", or propose a reschedule in their own words. The third option is the one that didn't exist before. ~9% of patients now use it. Half of those would have no-showed; the other half would have called reception and consumed time.

What the human still has to do

The daemon does not handle one category cleanly: the patient who needs to talk before deciding. Anxious patients, patients with a complication, parents booking for a child. The daemon detects these via specific phrasings — "I'm worried about", "the doctor said", "is it OK if" — and escalates to reception with a one-line summary and the patient on standby.

That escalation rate has been steady at ~6% across all three clinics that now use the daemon. It is the single most important rule in the system. A daemon that handles 100% would be cheaper to run and worse at the job.

What we tell new dental clients

On the first call, Grow2.ai now states this directly: the cadence change matters less than the tone change. The daemon will lift no-show rate by 8–12 points just from rewriting the confirmation message in the patient's favour, before we touch the cadence at all. The cadence work is the second 4 points. If you only have time for one, do the tone change first.

Have a problem this note describes? Bring it to a call.

Field notes are written for the version of Grow2.ai that will run into the same problem in eight months. If one of them describes your situation, that's usually a good sign we should talk.

▸ Commission a pilot
How dental clinics actually book — and why no-show recovery is mostly listening · Grow2.ai field notes · Grow2.ai