Recall attendance up 23% in 60 days — a 4-clinic dental group's dormant database, back in the chair

Who they were

A 4-clinic dental group in South-East Queensland. 32 staff including 8 dentists. ~$8.5M/yr revenue. ~14,000 active patient records across the four sites. Owner-principal cared deeply about patient relationships but admitted the recall process was “different at every clinic, depending on which receptionist was on.”

What was broken

The recall workflow varied by clinic:

• Site A: monthly batch of letters + SMS, run by the practice manager when she had time
• Site B: occasional SMS reminders, no consistent cadence
• Site C: post-it notes in the patient files (literally)
• Site D: had a recall report nobody read

Outcomes:

• Active recall attendance rate: 58% (industry benchmark 70-80%)
• ~3,200 patients overdue for recall at any given time
• No view across sites of who was overdue or who’d been contacted
• The principal couldn’t tell you, on a given Monday, how many recalls were due that week

The number we agreed to move: active recall attendance from 58% to 70%+ within 90 days.

What we built

A reactivation engine inside their existing patient management system (Dental4Windows), with these layers:

1. Recall identification — daily query against the database identifying everyone overdue for recall, segmented by treatment type, time since last visit, prior attendance pattern
2. Personalised messaging — SMS or email (per patient preference), drafted with the patient’s name, the dentist they last saw, the type of recall, and a direct booking link
3. Cadence logic — first message at 2 weeks overdue, second at 6 weeks if no response, third at 12 weeks, then archived after 16 weeks (configurable per clinic)
4. Direct booking — the link in the message pre-fills the patient’s preferred clinic and their preferred dentist, showing only available slots
5. Cross-clinic visibility — single dashboard showing per-clinic recall stats: due, contacted, booked, attended

We also rebuilt the post-appointment recall trigger so every patient leaving an appointment had their next recall set automatically based on treatment plan.

Deployed inside: Dental4Windows + their existing SMS gateway + Microsoft 365.

Time to live: 33 days end-to-end (slightly over the 30-day target due to integration testing on the patient-data side — we kept building at no extra cost per the guarantee).

What changed on the books

Metric	Before	After (60 days post go-live)
Active recall attendance rate	58%	71%
Overdue patient backlog	~3,200	~1,400
Patients reactivated from 6+ month dormancy	0/month	~190/month
Recall-related admin time across all sites	~22 hours/week	~4 hours/week
Cross-clinic visibility	none	live dashboard, refreshed daily

Annual benefit:

• ~$120K/yr in additional treatment revenue from recovered recall attendance (conservative estimate based on average appointment value × incremental visits)
• ~$80K/yr in admin time freed across the four practice managers
• Plus the harder-to-quantify upside: better continuity of care, reduced chair downtime, happier dentists

Conservative total: $200K/yr in defensible recurring benefit.

What they said

“We always knew the recall was leaky, but we couldn’t see how leaky. Now I get a Monday-morning dashboard showing me four clinics’ recall numbers on one page. The team’s not chasing patients in their spare time anymore — the system’s doing the chasing, and the team’s actually doing dentistry.”

Principal, 4-clinic dental group

What’s next

• Treatment plan acceptance automation (Phase 2, scoped) — automated follow-up on quoted treatment plans that haven’t been accepted
• Internal knowledge base assistant (Phase 3, in discussion) — staff queries against the group’s clinical and operational SOPs

The recall engine has been running for 60 days. The 71% number is settling. The principal is now asking the right question: “what’s the next thing leaking that we can’t see?”