The problem, mechanically
The front desk drowns at lunch and 4pm.
Every practice knows its flood hours by feel. Almost none has measured what actually drowns in them — because the desk is too busy drowning to count. Four mechanics.
1. The noon collision is two schedules colliding
Working people can only call practices when THEY'RE free — lunch, and the minutes after work. Your desk's load peaks at the identical moments: checkouts stack, the waiting room cycles, the schedule churns. The collision isn't bad luck; it's two populations sharing one clock. In a live practice we measure, inquiries landing in uncovered moments reached bookings at a third of the covered-moment rate — and your flood windows are your least covered moments of the staffed day.
2. Correct triage loses the phone — every time
A good front desk at capacity makes the right call: the human standing at the counter beats the ringing phone. That's proper service to the patient in the building and a silent loss of the one on the line — who experiences ring-ring-voicemail and dials the next practice. The desk isn't failing. It's succeeding at an impossible brief: be fully present for two people at once.
3. The 4pm wave is the noon flood with homework
End of day adds its own load: tomorrow's confirmations, checkout surges, school-run callers, the provider's add-ons. Same collision, worse recovery — because a 4:40 missed call's voicemail gets checked at 5:15 by someone closing out, and the callback slides to tomorrow. In our measured data, that overnight slide is where inquiries go to die: aged threads mostly never engaged.
4. Recovery starts after the race ends
"We call everyone back after the rush" is the standard system, and it enters every race late: the noon caller is back at work by 1:30, the phone tag begins, and a third of threads — the measured number for next-steps that live in memory — quietly lose their follow-up. The flood doesn't just miss calls. It manufactures phone tag at scale, daily.
Why "hire another person" isn't the automatic answer
Sometimes it is — the discovery will say so if the measurement supports it. But a second body solves a two-hour daily problem with an eight-hour salary, still lunches, still peaks, and still leaves nights and weekends dark. The alternative the measurement often supports: an automated floor under the flood — missed calls get an instant text with a booking path, overflow routes somewhere owned — for less than a month of that salary, covering every flood forever. Structure first, staffing second, evidence before either.
Which flood is drowning your desk?
The assessment scores your peak windows, recovery speed, persistence, and channels — and names your worst first.
Score your peak hours