Champ AI
November 20, 2026

How to Evaluate AI Voice Agents for Payer Calls: Questions for Billing Companies

What to ask before buying an AI voice agent for payer calls: which payers will take the call, what it resolves, who finishes the hard ones, and how the BAA chain works.

Trevor Tang
Trevor TangFounding GTM/Solutions Engineer

Updated November 19, 2026, based on Fidelis Care, Cigna, Blue Cross and Blue Shield of Kansas, the CAQH Index, the HIPAA Privacy Rule and the FCC as of that date.

Judge an AI voice agent for payer calls by how many requests it brings back with a usable answer, payer by payer, and by what happens when a payer won't talk to it. Dial counts, voice quality and demo calls tell you little. A billing company also needs controls that a single practice doesn't: many clients, many tax IDs, and a clean business associate chain.

Start with the questions below. They come from payer notices on automated calls, CAQH's cost data, and the HIPAA rules for subcontractors. If you want to see who sells these tools first, our roundup of AI voice agents for payer calls lists them.

Some payers refuse or screen automated calls

The first question is whether your payers will take the call at all. Several have said publicly that they won't take them, will screen them harder, or will count them against the provider.

  • Fidelis Care's provider call center policy, posted April 28, 2026, says it is "unable to accept calls from Artificial Intelligence (AI) entities or other automated systems to verify claim status, obtain remittance information, or respond to any other inquiries." It says its reps "may only engage with a live person to verify PHI" and points providers to its portal.
  • Cigna's IVR update, reposted by a provider network on April 20, 2026, cites "an increase in unapproved bot calls" reaching its advocates. Its phone menu asks callers to enter a tax ID, choose a call reason or enter a member ID, and now ends the call if the caller provides none of them.
  • Blue Cross and Blue Shield of Kansas says AI vendor calls checking eligibility count against the provider's Electronic Self-Serve incentive. It asks providers to report their AI vendors as business arrangements and supply a copy of the BAA.

Ask each vendor for its results with the payers in your own mix, not its overall rate. Ask how it authenticates in the phone menu, whether it says it is an automated caller, and what happens when a rep refuses to continue. Ask whether a person redials those calls, who that person works for, and what it costs you.

A phone call is the most expensive way to get the answer

CAQH counts portals and IVRs as "partially electronic" and phone, fax and mail as manual. In the 2024 CAQH Index, the average medical provider cost per claim status inquiry was $13.80 manual, $5.24 by portal or IVR, and $3.64 as an electronic 276/277. For eligibility and benefits, it was $8.57, $4.46 and $2.00. A claim status inquiry by phone took medical providers 25 minutes, the longest of any task CAQH measured. The 2025 CAQH Index puts the average medical provider cost at $8.03 per manual transaction and $2.65 per electronic one.

A voice agent can take much of that phone time off your staff. But when a portal or a 276/277 has the answer, CAQH's numbers show it costs less staff time than a call. Ask whether the vendor checks the 276/277 or 270/271 response and the payer portal before it dials, and what share of requests each channel resolves. If it only calls, you need another way to handle the requests that never needed a call. Our guide on claim status follow-up by portal, phone or 276 covers when each channel fits, and payers without an API covers where electronic answers run out.

Measure resolved answers, not dials

Ask for completion data split by payer and by call type, because a vendor's average hides the payers you care about. Useful numbers are:

  • the share of requests that came back with a usable answer and no human touch
  • the average attempts and minutes per resolved request
  • how often calls end in a disconnect, a refusal or a transfer loop
  • how failed, partial and escalated calls are billed

Then run a pilot on your own claims. Pick payers your staff find hard, including a Medicaid plan or a specialty carrier with an unusual phone menu. Compare each result against what your staff would have gotten, field by field.

Know who finishes the call when the agent can't

Every vendor escalates some calls. Find out where they go. Some send them back to your staff with a summary, and some have their own people finish the call. If the vendor's people do it, ask whether they are onshore or offshore, how fast they turn around an escalation, and whether your clients' contracts allow it. If your staff do it, ask what context comes with the hand-off: the reference number, what the rep said, and what is still missing.

Check the output against your work queue

A transcript alone doesn't help an AR team. Ask for structured fields that match what your staff record today: claim status, denial reason and codes, allowed and paid amounts, check or EFT number and date, call reference number and rep name. Ask for the recording and transcript as evidence. Then ask how results reach your practice management system: direct write-back, a file, or an API. Confirm it works with the systems your clients use, not just yours.

Billing companies need controls a single practice doesn't

A billing company runs calls for many providers under different NPIs and tax IDs. Ask whether the tool keeps each client's data, scripts and results separate, and whether it reports by client. Ask whether you can upload a batch for one client without touching another. And ask whether the vendor also sells directly to providers like your clients, since that affects how much of your process you want to share.

Get the business associate chain in writing

HIPAA's definition of a business associate includes billing done for a covered entity, so a billing company is usually a business associate of each provider client. A voice vendor that handles PHI for you is then your subcontractor. Under HIPAA's rule at 45 CFR 164.502(e), a business associate may let a subcontractor handle PHI only with satisfactory assurances that it will safeguard it, documented in a written agreement. Ask for:

  • a BAA with you as the business associate and the vendor as subcontractor
  • the list of its own subcontractors that touch PHI, such as speech, telephony and AI model providers, and whether each has a BAA
  • how long recordings and transcripts are kept, and where
  • whether your data is used to train models
  • its most recent SOC 2 Type II report

Our guide to HIPAA audit logs and BAAs for automated workflows goes deeper on what to log.

Some voice vendors also call patients about balances or appointments. In a February 2024 declaratory ruling, the FCC said the Telephone Consumer Protection Act's limits on "artificial or prerecorded voice" calls cover "current AI technologies that generate human voices." Those calls need the called party's prior express consent unless an emergency purpose or exemption applies. If patient calls are in scope, ask how the vendor captures and stores consent, and check with counsel how the rules apply to your calls.

Questions to send every vendor

  1. Which of our payers restrict or screen automated calls, and what are your results with each one?
  2. Do you check EDI and the payer portal before calling, and what share of requests does each channel resolve?
  3. What share of requests resolve with no human touch, by payer and call type?
  4. Who finishes escalated calls, where are they located, and how fast?
  5. Which fields do you return, and how do they reach our PM system?
  6. How do you separate and report on each of our clients?
  7. Will you sign a BAA as our subcontractor, and which of your vendors touch PHI?
  8. How are failed, partial and escalated calls priced?

Frequently asked questions

Can a payer refuse to talk to an AI voice agent?

Yes. Fidelis Care says it can't accept AI or automated calls for claim status, remittance or other inquiries. Cigna now ends IVR calls when the caller provides none of a tax ID, call reason or member ID. Check the provider manual and news page of each payer in your mix.

Does the FCC's AI voice ruling apply to calls to payers?

The ruling applies the TCPA's limits on artificial voices to AI-generated voices, and the TCPA is written to protect consumers from unwanted calls. Calls to a payer's provider line are a different situation from calls to patients' phones, so confirm with counsel. Payer policies like Fidelis Care's apply either way.

What should a pilot look like?

Use your own claims, your hardest payers and a fixed sample size. Compare each answer with what your staff would have recorded, and count resolved requests, attempts and minutes. Agree on the pricing for escalated calls before the pilot starts.

Do we still need portal access if we buy a voice agent?

Usually yes. In CAQH's data, portals and 276/277 transactions cost providers less per inquiry, and they often return the same answer. Fidelis Care, for one, points providers to its portal instead of the phone.

Comparing ways to handle payer calls?

Champ automates portal, document and phone work for back-office teams. We set it up and run it, so your staff sees only the finished results. If you are weighing how to take payer follow-up off your team, learn more here.

This post is general information, not legal, compliance or billing advice. Payer policies on automated calls vary by payer and change often, so confirm with each payer's provider services and your compliance counsel before acting. Champ is not affiliated with or endorsed by Fidelis Care, Cigna, Blue Cross and Blue Shield of Kansas, CAQH or the FCC.

Continue reading

See all

Do the work of fifty
without hiring one more.

Eligibility
Verification
Claims
Payroll
Carrier check-in
Patient intake
Benefits
Credentialing
Credentialing