All posts Prior authorization
AI prior authorization calls. How voice agents follow up with payers.

An AI prior authorization call is a phone call a voice agent places to a payer to check the status of a submitted authorization. The agent navigates the payer's phone tree, waits on hold, captures the status and the reference number, and writes both back to the order. This kind of prior authorization automation covers the follow-up. Submission and clinical decisions stay with your team.
What is prior authorization, and where do phone calls come in?
Prior authorization is a health plan process that requires advance approval from the plan before a service or medication qualifies for payment. The work has several steps: determine whether authorization is needed, submit the request, follow up on its status, answer any request for more information, and record the outcome so the patient can be scheduled.
The phone carries much of the follow-up. In the 2025 AMA prior authorization physician survey, physicians reported phone as the most commonly used method for completing prior authorizations for medical services. The same survey found that practices complete an average of 40 prior authorizations per physician per week, and that physicians and their staff spend 13 hours each week on them.
A status call is simple in content and expensive in time. Someone dials the authorization line, works through the menu, waits on hold, gives the member and case details, hears "approved," "pending" or "we need more information," and types the result into the order.
What does prior authorization automation cover?
Prior authorization automation is a broad term, and vendors use it for different parts of the process. It helps to separate three:
- Electronic submission. Sending the request through a payer portal or an electronic prior authorization transaction in the EHR.
- Payer interfaces. APIs that payers expose so providers can check requirements and exchange requests and decisions electronically.
- Phone follow-up. Voice agents that call the payer for status and bring the answer back to the order.
Automated prior authorization calls belong to the third group. When you compare products, ask which of the three each one covers.
What is CMS changing about prior authorization?
The CMS Interoperability and Prior Authorization Final Rule (CMS-0057-F) sets new requirements for what CMS calls impacted payers: Medicare Advantage organizations, state Medicaid and CHIP fee-for-service programs, Medicaid managed care plans, CHIP managed care entities and Qualified Health Plan issuers on the Federally Facilitated Exchanges.
According to the CMS fact sheet:
- Beginning in 2026, impacted payers other than Qualified Health Plan issuers on the Federally Facilitated Exchanges must send prior authorization decisions within 72 hours for expedited requests and seven calendar days for standard requests.
- Beginning in 2026, impacted payers must give a specific reason when they deny a prior authorization request.
- Impacted payers must implement a Prior Authorization API beginning January 1, 2027.
- These prior authorization policies do not apply to drugs.
The rule has a defined scope. For payers and requests outside it, status is still checked by portal or by phone. Whatever channel delivers the answer, the order is not released until the status is recorded in it.
How does a voice agent make a prior authorization call?
A voice agent makes the same call a staff member would, without the staff member waiting on hold. With Contour the workflow runs in this order:
- Trigger. An order waits on a payer past the threshold you set.
- Read. Contour reads the order before the call, so the agent has the case details it will be asked for.
- Call. The agent dials the payer's authorization line, navigates the IVR menus, waits in the hold queue and asks for the authorization department.
- Capture. The agent locates the case and captures the status, the reference number, the representative reached and any item the payer says it still needs.
- Write-back. Contour writes the status and reference number to the authorization field on the order, with a note. When the authorization is approved, the order is released to scheduling.
- Escalate. Denials and pends are routed to your team with the context so far.
Every attempt is logged with who was reached, and the status is visible to your team in Trace.
What does the agent write back to the order?
The agent writes back whichever of four outcomes the payer gives:
- Approved. The status and reference number are written to the order, and the order is released.
- Denied. The denial and the reason are written back and routed to your team.
- Pended. The status is recorded and routed to your team.
- More information needed. The specific item the payer asked for is recorded.
The write-back fields are configured per workflow. In an imaging center that is typically the authorization field in the RIS. In a health system or clinic it is the encounter in the EHR.
What happens when a payer needs more documentation?
When a payer needs a note, a code or a form, the follow-up moves to the ordering office. Contour identifies the exact item the payer asked for, requests it from the ordering office, and logs the request against the authorization. The agent asks for the specific missing item and nothing more.
What does a voice agent not do in prior authorization?
A voice agent for payer calls has a narrow job, and the limits matter to anyone evaluating it.
- It does not submit authorizations. Contour follows up on submitted authorizations and gathers missing items. Submission itself stays with your workflow.
- It does not argue medical necessity. Peer-to-peer reviews and medical necessity arguments are clinical conversations and stay with clinicians.
- It does not decide what to do about a denial. The denial and its reason go to your team, who decide whether to appeal, resubmit or reschedule.
How should you evaluate automated prior authorization calls?
Ask each vendor to show a real call against a real payer line, then check these points:
- Phone trees and hold. Whether the agent navigates IVR menus, waits on hold and reaches the authorization department without a person staying on the line.
- What is captured. Status, reference number, representative reached and any item the payer needs.
- Where it is written. Whether the result lands in the authorization field of your RIS or EHR, or in a separate list someone has to retype.
- Escalation. What your team receives on a denial or a pend, and how quickly.
- Audit trail. Whether every attempt is logged with who was reached, and whether the recording and transcript are kept with the order.
- HIPAA terms. Whether a Business Associate Agreement is executed before any PHI is handled.
For a wider checklist, see AI voice agents for healthcare.
Where Contour fits
Contour calls payers, navigates the phone tree, captures authorization status and reference numbers, and writes them back to the order. The details are on the prior authorization and payers page.
Contour runs payer follow-up for imaging centers, where pending authorizations hold up the schedule, and for health systems and clinics, where authorization and eligibility questions hold up care. The same platform handles referrals and order intake, including calls to referring offices for missing order details.
Contour is HIPAA compliant and SOC 2 Type 2 certified. See the platform, security and integrations pages, or the FAQ.