The case gets accepted in the operatory and lost on the walk to the front desk

Case Acceptance Lab earns a commission if you sign up for HighLevel through our link. We only write about things we've built and tested ourselves.

Ask a practice where cases die and you'll hear about the follow-up. Nobody called back, the sequence stopped at one text, the treatment coordinator was out that week. All true, and all downstream of something smaller.

The patient said yes in the chair. Then they stood up, walked twenty feet to the front desk, and the yes had to survive the trip. Most of the time nothing malicious happens on that walk. The doctor moves to the next operatory. The assistant turns the room over. The person at the desk sees a patient approaching with no idea what was just discussed, so they ask the only question they can ask: "do you want to schedule something?" And the patient, who said yes to a treatment plan four minutes ago, now says the thing people say when they're asked an open question they weren't ready for. "Let me check my calendar and call you."

That patient is now a follow-up problem. They didn't have to be.

What actually gets dropped

Three things live in the operatory and almost never make it to the desk in usable form.

What was presented. Not the codes - the plan in the patient's language, and the number. The desk needs to be able to say "the crown and the build-up, $1,840 after your insurance estimate" without opening the chart and reading it aloud like a stranger.

What the hesitation was. Cost, time off work, fear, a spouse who wasn't in the room, wanting a second opinion. Every one of those has a different next move, and the person who heard it is not the person about to handle it.

What was promised. "We'll get you a financing estimate." "I'll email you the photos." "Front desk can check whether your benefits reset in January." A promise made in the chair and not written down is a broken promise on a two-day delay.

The handoff is a record, not a conversation

Practices try to fix this with a verbal handoff - the assistant walks the patient up and explains. It works when the desk isn't on the phone, the assistant isn't behind, and nobody forgets. It works maybe half the time, and it leaves nothing behind for tomorrow.

The fix is that leaving the operatory writes a record. Whatever you use to capture it - a form on the operatory iPad, a tablet at the desk, a text-to-form link the assistant taps - the requirement is the same: four fields, filled before the patient reaches the desk.

• Plan presented, in plain words, with the patient's out-of-pocket number.
• Response: scheduled, thinking about it, or declined - and if it's the middle one, the reason in the patient's own words.
• The promise, if one was made, and who owns it.
• Next touch date.

Four fields takes about forty seconds. It is the highest-return forty seconds in the practice, because it converts the most valuable thing that happened all day - a patient telling you what they're actually worried about - from a memory into a record that a follow-up can be built on.

What the desk does with it

The desk now has a script instead of an open question. "Dr. Ellis mentioned the crown on the upper left - she wants to get that done before it splits. She's got Tuesday at 2:10 or Thursday at 8:40. Which is easier?" Two specific times, tied to what the patient just heard, from someone who clearly already knows.

If the answer is still not now, the desk isn't improvising either. Cost gets the financing conversation and an estimate sent the same day. Timing gets a hold with a real date. Spouse gets the plan emailed in a form that can be shown to someone who wasn't there. Second opinion gets a genuinely relaxed "of course - can I put a soft hold on Thursday so it's there if you want it?"

Building it so it can't be skipped

In HighLevel this is a small build, and the shape matters more than the specific clicks.

The capture form writes to the contact record and moves the opportunity into the treatment-plan pipeline at the right stage - presented, accepted-not-scheduled, or declined. The hesitation reason is a dropdown, not free text, because a dropdown can drive a branch and a paragraph cannot. Each reason routes to its own follow-up sequence, so "cost" and "spouse" never get the same message.

The promise becomes a task with a named owner and a due time, not a note. The next-touch date becomes the wait step. And any opportunity that sits in accepted-not-scheduled with no activity for a set number of days raises a task rather than quietly aging - because the one failure mode that survives every good build is the case nobody looked at again.

One more thing worth wiring: if the form is never filled for a patient who was seen for a consult, that should be visible. Not as a scolding report - as a queue the coordinator works at the end of the day. A handoff system that depends on everyone remembering is the same system you already have.

The number to watch

Track the gap between cases presented and cases scheduled the same day. Most practices can't produce it, which is why it never improves. When the handoff record exists, that number falls out of the pipeline for free, and it moves fast - not because anyone is selling harder, but because the patient stopped being asked to make a decision twice.

The second decision is the one you lose.