Skip to main content

Guides

Who Answers Billing Questions on the Phone?

Billing calls land on whoever picks up, and the answer is usually wrong or slow. How to route balance and statement questions without growing the billing team.

6 min read

Ask a practice administrator who answers billing questions and the honest answer is usually “whoever picks up.” A patient calls about a statement, the front desk takes it because the front desk takes everything, and then one of three things happens. They guess. They put the patient on hold and go find someone. Or they promise a callback that competes with forty other things for the rest of the day.

None of those is a billing process. All three are expensive, and the most expensive one is the guess, because a wrong answer about money gets repeated to friends and posted in reviews.

Why billing calls are harder than they look

A billing question sounds like one question and is usually four. What is this charge. Did my insurance pay. Why is my portion this much. Can I set up a payment plan. Answering any of them properly means looking at the claim, the remittance and the account at the same time, and knowing which of those the patient is actually asking about.

The front desk cannot do that between patients at the counter. The billing team can, but in most practices the billing team is small, already working denials and aging claims, and not sitting on a phone queue. So the call bounces.

The volume problem underneath it is real and measured. Physicians and their staff already spend 13 hours each week completing prior authorizations alone, and 40% of physicians have staff who work exclusively on that one process (AMA). Administrative phone work is not a spare-capacity activity in a medical practice. Every call routed to the wrong desk displaces something else that was already late.

There is also a structural complication administrators underestimate. At one multi-site practice the locations are set up as distinct billing entities inside the EHR, which changes what a patient’s “last appointment” even means, and therefore which account a balance question belongs to. A caller does not know any of that. They know they got a bill.

The four calls, and where each one belongs

Most billing calls sort into four buckets. Disputes, coding questions and decisions about new payment plans belong with billing staff.

“What do I owe?” A balance lookup. It is a read, it is the single most common billing call, and it does not require judgment. It requires accurate access to the account.

“What is this charge for?” A statement explanation. The patient wants the date of service, the provider and what the line item covers. Still a read, as long as nobody is interpreting clinical content.

“Can I pay it, or split it?” Payment and documented-plan logistics. A patient can receive a secure payment link or review an existing documented plan. Creating or changing a payment plan stays with billing staff.

“I think this is wrong.” A dispute, a possible coding question, or a claim that needs to be reworked. This is the billing specialist’s call, and it should reach them with the account already open.

Routine balance lookups compete with the calls that need judgment. Clearing the reads is what creates the hours to work disputes and payment-plan decisions.

What automation handles, and where it stops

Pretty Good AI runs administrative front-office work inside athenahealth, with production access to 820+ athenaOne APIs. For billing calls that depth is the whole story, because the agent has to reach the account, the claim status and the payment surfaces together to answer a question the patient asks as one sentence.

The agent surfaces an outstanding balance and copay during a call, explains what a statement line covers using the recorded date of service and provider, reviews existing documented payment plans, and routes the dispute cases to billing staff with the context already captured. It also handles the hygiene work that quietly causes billing calls in the first place, including statement delivery and the duplicate-notice problem that generates angry inbound when a patient receives the same bill twice.

{{PAYMENTS_LINE}}

The agent does not create or set up payment plans. Those decisions stay with your billing team.

The boundary: the agent does not make coding determinations, does not decide whether a service was billed correctly, and does not negotiate what a patient owes outside the parameters the practice has set. Those are judgment calls that belong to certified coders and billing staff. What the agent removes is the hold music and the callback queue in front of that judgment.

One more thing it does not do. It does not interpret the clinical content of a visit to explain a charge. Naming the date of service and the provider a line item belongs to is administrative. Anything beyond that is a conversation for the practice.

The adjacent fix most practices miss

A large share of billing calls are not really billing calls. They are eligibility failures arriving two weeks late.

Patients frequently do not know their insurance changed, and the chart simply goes ineligible. Said almost identically by a podiatry group and a pain practice, and the fix lives before the visit, not after the bill. The mitigation runs before the appointment. Text the patient a link and have them photograph both sides of the card. Read it, match it against the plans configured in the EHR, and upload the image to the right place in the chart. Then run the eligibility check. A couple of characters on a card determine whether the plan is one you are contracted with.

Separately, a vascular group’s revenue-cycle lead asked whether the payer’s real-time eligibility response could be read, the copay extracted into the field staff actually use, and a mismatch flagged when the plan on file differs from the plan in the response. Her staff were consistently missing it. That is records hygiene rather than phone work, and it prevents the surprise-balance call entirely.

Fixing coverage before the visit is cheaper than explaining a balance after it.

What to ask a vendor

  • Can it state a current balance and explain a statement line, or only take a message about one?
  • Can it send a secure payment link, review an existing documented plan and route requests for a new plan to our billing staff?
  • How does a disputed charge reach our billing specialist, and what do they see when it arrives?
  • Does it work our multi-entity setup, where locations bill separately?
  • What does it do about duplicate statements and stale insurance, which generate the calls in the first place?

Ask for a demonstration where the patient says “I think this is wrong.” That is the call that shows whether the handoff works.

Key Takeaways

  • Billing calls land on whoever picks up, and the resulting guesses and callbacks cost more than the calls themselves.
  • Routine reads and documented-plan questions can be handled administratively; disputes, coding questions and new payment plans require billing staff.
  • Administrative phone work displaces other late work, with staff already spending 13 hours a week on prior authorization alone (AMA).
  • An AI agent can surface balances, explain statement lines, send secure payment links and review documented plans. Coding determinations, disputes and creating plans stay with billing staff.
  • Many billing calls are late eligibility failures; capturing a new insurance card and checking coverage before the visit prevents the call entirely.

The goal is not to keep patients away from your billing team. It is to make sure the calls that reach them are the ones that actually need them, with the account already open and the question already captured.

Sources

Ready to See It in Action?

See how Pretty Good AI handles balance and statement calls inside athenaOne

Schedule a Demo →

Written by Kevin Henrikson