Simplorify
All case studies
ListeningWorkflow redesignWebsite + reminders

Why a Queens dental practice's no-show problem wasn't actually a scheduling problem

A six-chair family dental practice thought they needed a new booking system. Time spent watching the front desk revealed the real bottleneck — and a fix that cut no-shows by 43%, recovered ~$60K in formerly-empty-chair revenue per year, and didn't replace a single tool they were already using.

Client
A family dental practice
Location
Forest Hills, Queens
Timeline
Workflow audit + build
Outcome
43% drop in no-shows · ~$60K/yr in recovered chair revenue · 28% lift in patient satisfaction · 10+ hrs/week of front-desk time returned

Where it started

A six-chair family dental practice reached out with what sounded like a straightforward ask: "we need better scheduling software." Their no-show rate was running around 18% — well above industry average — and they were losing real money to empty chairs.

We spent meaningful time at the practice before quoting anything.

What we found by listening

The scheduling software wasn't the problem. Their system worked fine. What we watched, over the course of a morning at the front desk, was this:

  • Every new patient got a six-page PDF intake form emailed after booking.
  • About half filled it out beforehand. The other half arrived confused, and the admin lost 15 minutes per appointment wrangling paperwork.
  • That friction at the front desk translated into longer waits, frustrated patients, and a slow-motion reputation drag. The no-shows weren't random — they clustered around appointments where the experience had felt clunky the last time.

So the "booking problem" was actually a patient experience problem, living entirely in the intake paperwork and the reminder flow.

What we built instead

Nothing about the scheduling software changed. Instead, we focused on the two frictions that were actually causing the drop-off:

  • A mobile-first intake site at a memorable short URL on their existing domain, so patients could complete forms on their phone during downtime. The six-page PDF became three screens with conditional logic — most patients finished in under four minutes.
  • A layered reminder sequence via SMS and email — 72h before, 24h before, 2h before — with intake-completion status baked in. Patients who hadn't completed the form got a gentle nudge; the ones who had got a lighter "see you then."
  • A staff dashboard that flagged incomplete forms 48 hours pre-appointment so the front desk could call the patient proactively, instead of reacting at check-in.

Everything was HIPAA-compliant, ran on the practice's existing domain, and played nicely with the practice management system they were already using. No new logins for the staff to learn.

The outcome

Ninety days post-launch:

  • No-show rate dropped from 18% to around 10% — squarely in line with industry best practice.
  • Roughly 10 hours of front-desk time recovered per week, mostly from not wrangling intake paperwork at check-in.
  • Patient satisfaction scores up 28% on the "how easy was it to prepare for my visit" question.
  • ~$60,000 a year in recovered chair revenue. The 8-point drop in no-show rate translates directly to filled chairs that used to sit empty. The engagement paid back inside the first quarter and has been compounding since.

"We didn't need new dental-specific software. We needed the experience we were already offering to stop being painful. They figured that out without us having to explain it twice." — Practice Owner, the Queens dental practice

Why it worked

We watched before we prescribed. The ask was a new booking system — a six-figure category of project that solved none of the actual frictions. The real problem was a friction-filled patient onboarding that the booking system had nothing to do with.

Naming that correctly — and being willing to say "the software you have is fine, the work is upstream of it" — was the value. Everything we built lives on their infrastructure, owned by them, and continues to compound chair revenue every month it runs.

Want results like this?

The problems that look unique usually aren't. We've seen the version of this a dozen times. Let's talk through yours.