The practice runs on people remembering.
Here is the layer that remembers for them.
A 30-person outpatient orthopedic PT practice, CareCloud at the center, 30 new patients a week, 500 claims a week. This is what an operating layer on top of CareCloud does for it, in the order we would build it, with the numbers from our call.
The preview is the same practice, running. Every view is clickable. All names and rows are fictional.
What we heard
The practice as you played it, and the one sentence that names the real problem.
Four Ops, in order
Front Door, Follow-Through, the Denial Workbench, then the habit rail. Each with an honest alternative.
The math and the after
Hours turned into dollars with your inputs, what twelve months looks like, and how we start.
Where You Are: a practice that is good at the clinical part
You described an independent outpatient orthopedic PT practice, about 30 people, where the owner still treats. A patient calls, the front desk takes their information, someone at the desk or in the small in-house call center verifies insurance by phone or portal, the patient gets a callback with benefits, comes in for an evaluation, and the clinician schedules the plan of care. Notes go into CareCloud, billing submits from CareCloud, and the patient gets one follow-up call after the first visit. Salesforce handles marketing. A separate dashboard tracks cancellations. You said that stack covers 99% of what you need, and nothing is on the wishlist.
The numbers you gave: verification runs 2 to 40 minutes per patient, 30 patients a week. About 500 claims a week, 15% denied, 45 to 60 minutes to work each one. The worst part of a denial is not the work, it is reaching a human at the insurer, sometimes 45 minutes on hold, even with batch calling and portals already in use.
The softer things: clinician notes run late, mostly because people don't use their own schedule well, and that spills into evenings and stresses billing. The habits you have trained (walking patients out, watching exercise, checking the waiting room) need re-teaching. Written scheduling strategies exist and are not followed. You are proudest of patient results, and they show up as referrals and reviews.
On Tuesday you added the two numbers that matter most for a front desk: practices miss about 30% of their calls, and of the ones they answer, about 20% don't capture everything needed, which turns into denials and clinicians who walk into an eval without the picture.
"If I knew, honestly, I would work on a solution."
On what stops communication and adoption from sticking · discovery call, Sunday
The Bottleneck: nothing in the practice enforces what the practice already knows
The strategies are written. The training happened. The scripts exist. What is missing is the thing that makes them happen on a Tuesday at 4 PM when the phone rings and the front desk is short a person. Every pain you named is the same pain: a process that lives in people's memory, and memory under load.
Three things are true at the same time:
- The phone leaks. Roughly a third of calls go unanswered and a fifth of the answered ones are incomplete. A missed call is a patient who calls the next clinic. An incomplete intake is a denial six weeks later.
- The denial desk is a job nobody was hired for. 75 denials a week at 45 to 60 minutes each is 56 to 75 staff-hours, the work of one and a half to two full-time people, most of it waiting.
- What is taught does not stick. Late notes, unwalked patients, the empty waiting-room check. You can coach it, and you do. Coaching without a system that reminds, records and escalates is coaching on repeat.
Missed calls and incomplete intake at the front door. Referrals and reviews are strong but untracked.
One follow-up call per plan of care. Drop-off is caught late. Notes and habits depend on the person.
15% denials, an hour each, and a hold queue you can't control. The biggest hour count in the building.
What We Looked At: the layer between the phone and CareCloud
CareCloud stays. Salesforce stays. The metrics dashboard stays. A Practice OS sits in the gap those three leave: the phone and texting are not connected to the schedule, follow-up after a visit is manual, denial work happens in inboxes and on hold, and owner-level reporting gets rebuilt by hand. That is the same gap in every specialty we reviewed, from WebPT and Prompt in PT to Dentrix in dental to athenahealth in medical.
The categories we compared before recommending anything: patient-communication platforms (Weave, Solutionreach), medical answering services, AI phone agents built for clinics, denial-management and clearinghouse tools (Waystar, Availity Essentials), and outsourced revenue-cycle firms. Each Op below carries an Ideal path and an honest Alternative from those categories, so a practice can take the recommendation or the cheaper road and still get most of the value.
Vetted tool selection, a sequenced rollout and the math behind it is normally the output of a mid-market operations consulting engagement. We productize it for practices that would never get quoted by those firms, and we build and run the result instead of handing over a deck.
The Diagnosis: three Drivers, four Ops
Each Op maps to one Driver from Section 02. They are listed in build order, the same order as the Priority Stack in Section 05. Each one says what happens today, what changes, and the two ways to get there.
Front Door
Today about 30% of calls go unanswered and 20% of answered ones miss something. Front Door answers every call, first ring, including before open and over lunch. It runs the full intake script every time (name, callback number, insurance, referring physician, reason for the visit in the patient's words), starts the benefits check through the payer portal where one exists, and books the evaluation into CareCloud's schedule. The front desk sees a complete record and a transcript, not a sticky note. Calls that need a human get a human, with the intake already done.
Because you told me to force this part: the same door tracks where every new patient came from (which physician, which search, which former patient) and asks for a review on discharge. That feed goes to Salesforce, so the marketing and sales work you are building has real source data instead of "how did you hear about us" guesses.
AI phone agent on the practice's own number, portal-first verification
- Overflow and after-hours first, then all calls once the staff trust it (usually week 2)
- Intake checklist enforced on every call; nothing books until it is complete
- Portal benefits check kicked off automatically; phone-only payers queued for staff
- Source tracking and review requests built in
Human answering service plus a written intake form
- Covers missed calls after hours and overflow
- Intake quality depends on the service's script and turnover
- No benefits check, no booking into CareCloud, no source data
Follow-Through
This one is your idea from Tuesday, and it is the right one. Today a patient gets one call after visit one. Follow-Through sends a short check-in after every visit: how did today go, anything to flag, here is your next appointment. Routine answers are logged. Anything non-routine (pain that got worse, a question about the exercises, a scheduling problem) goes to the treating clinician as a flag, not a voicemail. Patients who cancel, no-show, or go quiet get a recall touch before they become a dropped plan of care.
The peer-reviewed number behind this: a PT patient who misses more than a fifth of visits in the first month is 3.5 times more likely to drop out entirely (JOSPT Open, 2024). Catching the second missed visit is worth more than any marketing you will do this year. It also feeds your adoption problem from the other side: the patient-facing steps happen whether or not the front desk remembered.
Automated check-in after every visit, clinician flags, recall on silence
- Text within two hours of checkout, two questions, generic wording, opt-out every time
- Non-routine replies flagged to the clinician's queue the same day
- Missed or cancelled visit → rebooking offer; two silences → recall to the front desk
- Review request on discharge, tied to the referral tracking in Op 1
Front desk calls after visit one and visit four
- What you do today, extended to a second checkpoint
- Costs staff time at the busiest hours of the day
- Nothing catches the patient who quietly stops after visit six
Denial Workbench
Honest first: the 45 minutes on hold with the insurer is outside our control, and we will not pretend otherwise. What the Workbench removes is everything around the hold. Today a denial lands, someone reads it, decides whether it is coding or documentation, chases the provider for a note, drafts the appeal, and calls the payer. The Workbench reads every denial as it arrives from CareCloud, sorts it by reason code, sends the documentation request to the right clinician with the due date attached, drafts the appeal from the note and the payer's own rules, and batches the calls that still need a human by payer so one hold covers ten claims. Every step is logged with a timestamp, so the owner sees where the time goes instead of guessing.
The second effect is upstream. The 20% of intakes that miss something are a share of the 15% that get denied. Front Door closes that gap at the source, so the denial rate itself comes down over the first quarter.
OS workbench on top of CareCloud's claim responses and the payer portals
- Triage by reason code within minutes of the remittance
- Documentation requests routed to the clinician with a due date; nudges until the note is in
- Appeal drafts for review; the billing lead sends, never the system
- Hold time and resolution time measured per payer, so the practice can see which contracts cost the most to keep
Outsourced denial management
- A revenue-cycle firm works the denials for a share of what they recover
- Removes the hours, not the causes; intake gaps keep generating denials
- Reporting is theirs, on their schedule
Habit rail
This is the answer to the magic-wand question, and it comes last on purpose, because it only works once the first three Ops have taught the team that the system is on their side. The habits you keep re-teaching become checks the OS runs: a note that is not signed by end of day gets a nudge to the clinician, then a line on the owner's morning view; a patient who checked in and has not been brought back in twelve minutes shows up on the front-desk screen; discharge without a walk-out note gets a question. None of it replaces your coaching. It is the part of coaching that happens when you are not in the room. You handle Leadership, Culture and Strategy. This is the O.
Flagged for development after the first three Ops are live. Scope depends on what CareCloud exposes for note status and check-in events; we confirm that during build.
The Priority Stack: start here, in this order
- 1Front DoorWeeks 1–2Fastest proof, no clinical workflow touched, and it starts shrinking the denial rate from day one.
- 2Follow-ThroughWeeks 2–3Rides the consent and texting rails Front Door sets up. Your idea, visible to every patient by week three.
- 3Denial WorkbenchWeeks 3–6The biggest hour count. Needs CareCloud's claim responses connected, which is the longest single setup step.
- 4Habit railAfterOnce the team trusts the first three. Scoped with the owner, one habit at a time.
How It Runs: three rules that make this different from another tool
- Nothing clinical leaves CareCloud. The OS works from appointment status, claim status and call events. Notes, diagnoses and plans of care stay where they are. That keeps the automation layer out of most of the PHI exposure and keeps the BAA simple.
- Every action has a receipt. A ✦ mark and a timestamp on anything the system did, in a feed the owner can read in two minutes each morning. Adoption stops being a feeling.
- The practice sets the leash. Green actions run on their own (answering, reminders, check-ins). Yellow actions are drafted and wait for a person (appeals, patient balance notes). Red actions never run without a click (money, anything that touches the record). The preview shows the switches.
And the part that matters to you specifically: we build and run it. Your LOCS work sets the behavior; the OS is the machinery that makes it stick between sessions. Neither one replaces the other.
The Math: your numbers, in dollars
You asked for a real number, so here is the calculator with your inputs already in it. Move anything you disagree with. The loaded hourly cost is our assumption; a front-desk salary of about $38,700 a year (Salary.com, June 2026) lands near $19 an hour before benefits and overhead, and billing staff run higher, so $30 is a round, conservative loaded figure.
Assumptions, all editable above: 50 working weeks; calls that become a started plan ≈ new patients ÷ 0.7 answered ÷ 0.8 complete; the "1 in 10 never calls back" share is deliberately conservative (CallRail's 2025 survey puts the share who call a competitor after an unanswered call far higher, but that is a consumer survey, not a clinic study). None of this counts the denials Front Door prevents, or the plans of care Follow-Through finishes. Those are real and we would rather show them on a live practice than estimate them here.
What the engagement costs
One number, sized to the practice, no per-seat line items. For practices up to about 20 active users the published shape is a setup of $7,500 to $10,000 and $800 to $1,500 a month, twelve-month initial term, then month to month. A 30-person practice is sized individually inside that same shape, one flat monthly number, and it needs single sign-on against the practice's Google or Microsoft directory so an ex-employee's access ends the day their account does. The setup covers the build of all three Ops; the monthly covers running it: the answering, the check-ins, the triage, the monitoring, the changes as the practice changes.
For context. The denial desk alone is one and a half to two full-time people. A front-desk hire is about $38,700 a year before benefits, and the front desk is the highest-turnover seat in the building. The monthly lands at roughly one answering service plus one patient-communication tool, and well under one salary.
Never a hostage. The practice's data is exportable in standard formats on request, at no fee, cancellation included. The price is fixed for the term. If they ever want to own the system outright, that price is printed in the agreement, not negotiated later. If they leave, they get thirty days of transition help.
Anything that stores or moves protected health information for the practice needs a Business Associate Agreement; we sign one. The design above keeps clinical data in CareCloud and triggers on appointment and claim status, not on diagnoses. Patient texts need consent at intake, generic wording, a sender name and an opt-out every time. The TCPA rules around automated texting became less settled after the Supreme Court's 2025 McLaughlin decision, not more. Before any of this is sold to a practice, a healthcare attorney reviews the consent language and the BAA. This roadmap is not legal advice.
The After: what twelve months looks like
The phone. Nobody at the practice remembers the last time a call went to voicemail. New patients arrive with a complete record and a benefits check already run. The front desk starts its day from a list, not from a backlog.
The desk. Denials arrive sorted. The billing lead reviews appeal drafts instead of writing them, and makes payer calls in batches with a purpose. The owner's morning view shows which payer cost the most hours last month, which turns into a contract conversation instead of a complaint.
The clinician's evening. A note that is not signed by five gets a nudge, not a lecture. Patients who are struggling say so in a text at 6 PM and the clinician knows before the next visit. Fewer surprises, fewer notes done at the kitchen table.
The owner's month. The conversations that used to repeat once a month have a receipt behind them: here is what the system caught, here is what the team did with it. Coaching turns into calibration.
Financial impact. Using the inputs above as they stand, the denial desk alone is worth about — a year in staff time; halving the handling around the hold recovers about —, and the missed-call number puts roughly — a year of plans of care back in play. Against a monthly in the low four figures, the return is there in the first quarter, before counting a single prevented denial.
And the L, C and S. The practice you coach on leadership, culture and strategy has an operations layer that holds the line between sessions. That is a different offer than coaching alone, and it is one you can put in front of every LOCS client without building a software arm.
What Happens Next
- Poke the preview. The Practice OS preview is this practice, running. Click into Messages for the 7:12 AM call, Claims & money for the denial batch, and Today for the switches that set the leash.
- Thirty minutes when you are back. Walk the four Ops, argue with the calculator, tell me which parts your clients would recognize and which they would not.
- Pick the first practice. This preview is the free one. The first real practice is a paid pilot at the terms above, built on their own numbers, and it becomes the reference every LOCS client after it gets to see.
- How the two of us work. The practice contracts with ADVANCE.DESIGN; you bring the practice and the L, C and S. We settle the shape of that on the call, in writing after.
This roadmap is yours to keep, and it will be updated here as the thinking changes.