8:55 AM at the Front Desk
A patient is checking in. There’s a line forming behind him, the phone is ringing, and the screen shows he still owes from last visit, plus today’s copay. The person at the desk has about half a second to decide whether to bring up money with an audience present. She doesn’t. He seems stressed, the line is growing, and it’s easier for everyone if the balance goes to a statement.
That half-second of mercy is completely human, and it happens at every check-in, every day. Add up a year of those decisions and you get the collections policy your practice actually runs, whatever the meeting decided. In telehealth there isn’t even a desk: the moment where asking could happen never exists at all.
A Policy Is Not a Build
Every practice has voted, at some point, to collect at time of service. Most are still waiting for the vote to take effect, because a policy that depends on a person asking will always lose to lines, moods, and volume. The version that works removes the ask instead of coaching it: five pieces, in order, each standing on the one before it, until money moves the way appointment reminders move. The math on why timing matters this much, how collectability decays week by week, is in the collections guide. This is the build.
The Five Pieces
One: consent and policy at registration. Card-on-file consent language and a written charge threshold, signed digitally at intake, before the first visit exists. Everything downstream stands on this paper, so it goes first and it goes in writing.
Two: the card at booking. No patient enters the system without a working card on file. Captured at registration, it reads like ordinary online life; every hotel and airline already taught your patients the pattern. Requested later, after balances exist, it reads like collections. For telehealth groups the entire front door is digital, so this piece is native, which is the argument of the shift-left guide.
Three: the known number. Eligibility runs automatically ahead of the appointment, so the copay and deductible picture exists before the patient arrives. A known amount collects. A vague one becomes a statement, and statements are where balances go to age.
Four: day-of capture. The known responsibility charges the card at session close, receipt by text. No counter, no audience. The half-second never happens. That same session-close moment should also book the next appointment, per the no-show system, because it’s the highest-attention moment the practice gets all week.
Five: the tail by text. Whatever only adjudication can settle goes out as a payment link within days of the answer, never as paper in monthly cycles. A small balance gets paid from a phone the same afternoon, weeks before the old statement would have printed.
What the Build Actually Deletes
The conversation. Nobody asks, so nobody flinches, so collections stop depending on who’s at the desk and how long the line is. The mercy problem disappears because there’s nothing left to be merciful about; payment became infrastructure, like the reminder text. And the patient side improves too, which surprises owners: people would rather be charged the amount they consented to, receipt in pocket, than face the awkward counter moment now and a surprise statement in six weeks.
The Caution That Belongs in the Build
Card-on-file, estimates, and automatic charging carry rules that vary by state and by payer contract. Set the policy with your contracts and counsel in view, then automate the policy. Machinery should enforce a decision someone made, never improvise one on its own.
Two Numbers Size the Gap
The share of active patients with a working card on file, and the share of day-of responsibility actually captured day-of. The distance between those two numbers and “nearly all” is this build’s business case, priced from your own reports. For a third angle, count the statements you mailed last month. Every one of them is a conversation the build would have deleted before it was ever needed.
Where to Start
Piece one, this week; it’s paperwork, and everything else inherits from it. Then grab 30 minutes with us. Prep nothing. You’ll see money move with nobody asking anybody for it.
Questions people ask
What does automated patient collection actually mean?
Consent captured at booking, a card stored securely, the balance charged when it is known, and a text follow-up for whatever remains. It removes the moment where a staff member has to ask a patient for money face to face.
Why does a collections policy not change collections?
Because a policy tells somebody what should happen and a build makes it happen. Under pressure at a busy front desk, an unprompted ask loses to the queue every time. The policy is not being ignored, it is being outcompeted.
Is it legal to keep a card on file for a patient balance?
With explicit written consent covering what will be charged and when, yes, and the consent language matters as much as the mechanism. This is worth setting up with your own counsel rather than borrowing wording from another practice.
How much does moving collection to the visit actually recover?
Compare what you collect at the time of service against what you eventually collect on the same balances afterwards, including statement and staff cost. The gap between those two numbers is the answer, and it is specific to your practice.