Setting Up a Payment Plan on the Phone Without a Callback

A patient calls on a Tuesday afternoon and asks whether they can pay their balance over a few months. In most gastroenterology practices the honest answer is that someone from billing will call them back. That callback is where the payment plan quietly dies. The patient does not pick up, the account ages another thirty days, and the next contact is a statement that reads more like a warning than a conversation.

The mechanics of setting up a plan are not difficult. Someone has to know what the patient owes, what the practice allows, and how to record the arrangement so the payments actually draft. What makes it hard is that those three things live in three places and none of them are in front of the person who answered the phone.

The balance shows up weeks after the patient forgot the visit

GI has a specific version of this problem. The patient has a scope, goes home, and the balance does not exist yet. It appears after the claim adjudicates, often several weeks later, by which point the visit is a memory and the bill feels like it arrived from nowhere. Anything the practice did well at the front desk has already stopped helping.

MGMA benchmarking shows how much of the collection now happens after the fact. Time of service copayment collection fell to 56% in 2022 from about 90% in 2019, while collection of patient due balances at time of service rose to 39% from roughly 15% over the same period. Practices are collecting a smaller share of the easy money and a larger share of the hard money, and both trends push work onto the phone.

That is the call the practice is not staffed for. It is inbound, it is unpredictable, and it arrives during the same hours the billing team is working claims.

What the patient is being asked to absorb

The size of the balance explains why the conversation is hard. KFF’s 2025 employer survey put the average general annual deductible for single coverage at $1,886, and at firms with 10 to 199 workers the average was $2,631. A single procedure can consume a meaningful share of that in one morning, and the patient often finds out by mail weeks later.

Patients working through a deductible of that size are not deciding whether to pay. They are deciding whether they can pay it at once. A practice with no answer to that question has effectively chosen to wait.

The number the front desk quotes is often the wrong number

Here is the complication that makes this worse than it looks, and it comes up in nearly every revenue cycle conversation we have with multi site groups.

The payer’s real time eligibility response contains what the practice needs. Remaining deductible, coinsurance, the current copay. That response arrives, and then it stops. The numbers frequently never make it into the fields the front office actually looks at, so staff quote from the plan on file rather than from the response that just came back. Staff miss it consistently, not through carelessness but because nothing puts the number where they work.

So the patient is told a figure, agrees to a plan built on that figure, and the plan is wrong before the first draft. Now you have a payment arrangement that has to be unwound and a patient who was told something incorrect by the practice.

Automation is useful here in an unglamorous way. Before the conversation about terms starts, the AI reads the eligibility response and the current balance in athenaOne, compares the plan in the response against the plan on file, and flags a mismatch instead of quoting through it. That is a records hygiene job attached to a phone call, which is exactly the kind of work that never gets its own project.

What setting up the plan on the call actually requires

Once the number is right, the rest is bounded. The AI checks whether a plan already exists on the account, because a patient with an open arrangement asking for another one is a different conversation and should not become a second draft against the same card. It then offers terms from the practice’s written policy, not from its own judgment. Half down and the remainder over six months, or a longer schedule above a threshold the practice sets, or whatever the policy says. Then it creates the plan against the account so the schedule is recorded where the billing team will see it, and the confirmation goes out through the portal and by text.

Nothing in that sequence requires a person, and every step of it is currently a reason to promise a callback.

The part worth insisting on is the last one. A payment plan that is agreed verbally and typed into a note is not a payment plan, it is a promise that someone will remember. It has to land in the system that drafts the payments, on the call, or the practice has recreated the callback problem with extra steps.

Where a person has to take it

Three situations should never be resolved by automation, and the handoff needs to be immediate rather than a message left in a queue.

Hardship is the first. When a patient says they cannot pay under any schedule offered, that is a financial assistance conversation with eligibility criteria and documentation, and it belongs to a person who can apply them. The right behavior is a warm transfer during business hours and a scheduled callback with a named owner outside them.

Disputes are the second. A patient who says the charge is wrong, that they were told the procedure was preventive, or that their insurance should have covered it is describing a billing question, not a payment question. Setting up a plan on a balance the patient disputes is how a small problem becomes a complaint.

Anything outside written policy is the third. If the patient asks for eighteen months and policy allows nine, the AI does not negotiate. It records the request and routes it. The value of a policy driven system is that it is predictable, and it stops being predictable the moment it starts improvising on terms.

Write the policy before you automate the conversation

Most practices discover during this work that their payment plan policy is less written down than they thought. Minimum monthly amount, maximum duration, the balance threshold where terms change, whether autopay is required, what happens on a failed draft, who can approve an exception. Staff have been making those calls individually for years and the results vary by who answered.

That variation is worth fixing regardless of whether anything gets automated. Practices have been moving in this direction anyway. An MGMA poll found that 41% of medical groups had updated their patient payment plans or options in the preceding year, with many tightening plan duration while expanding digital payment methods.

The automation just makes the gaps visible immediately, because a system cannot offer terms that were never defined. Every practice we work with hits the same moment: a rule everyone believed existed turns out to have three versions. Better to find that in a policy conversation than in a patient’s escalation.

Key Takeaways

The callback is the failure point. A patient asking about a payment plan is at the highest willingness to resolve they will ever be, and every hour after that call reduces it.
Read the eligibility response, not just the plan on file. The remaining deductible and copay frequently never reach the fields staff quote from, which produces plans built on wrong numbers.
Check for an existing plan before offering a new one. A second arrangement drafting against the same account is a support ticket waiting to happen.
The plan has to be created in the system on the call. An arrangement recorded in a note is a promise, not a payment schedule.
Hardship, disputed charges, and any request outside written policy go to a person immediately. Automation that negotiates terms has stopped being predictable.
Write the policy first. Minimum payment, maximum duration, threshold, autopay, failed draft handling, exception approver. Most practices find three versions of a rule they thought was settled.

A GI practice does not need a better statement cycle so much as it needs fewer patients falling into it. When someone calls willing to pay something, the practice should be able to finish that conversation while they are still on the line, using the right balance and terms the practice actually wrote down. That is a narrow piece of work. It is also the difference between a resolved account and one that ages another ninety days before anyone touches it again.

Sources