All posts Voice AI
AI voice agents for healthcare. What they do and how to evaluate one.

An AI voice agent for healthcare is software that makes and answers phone calls for a healthcare organization, holds a spoken conversation, and records the outcome in the organization's systems. Healthcare voice AI fits routine, time-sensitive operational calls: scheduling, results delivery, prior authorization status, referrals and patient outreach. It does not fit calls that need clinical judgment, and a sound deployment hands those to a person.
What is an AI voice agent for healthcare?
An AI voice agent is a program that speaks and listens on a phone line, follows a defined workflow, and takes actions in connected systems. Three things separate a healthcare voice agent from older phone automation:
- Conversation. The agent understands spoken answers, interruptions and corrections. The caller does not press keys to move through a menu.
- Context. The agent reads the order, the schedule or the result from the system of record before the call starts.
- Write-back. Write-back is the step where the agent records the outcome of the call in the system of record: the status, the note, the recording and the audit entry.
A voice agent can work inbound, outbound or both. Inbound, it answers a line, verifies the caller, answers from live data and routes what needs a person. Outbound, it places a call when a trigger fires in your systems, such as a signed report, an incomplete order, a missed appointment or a pending authorization.
Which calls do healthcare voice agents handle?
The calls that suit a voice agent are operational: high in volume, repeatable, bound to a script and tied to a record. Contour groups them by call type:
- Scheduling. Booking, rescheduling, reminders and no-show follow-up from the live schedule. See scheduling.
- Results and critical findings. Delivering results to ordering providers, confirming critical findings with read-back and answering status requests. See results and critical findings.
- Prior authorization and payers. Calling the payer, navigating the phone tree, capturing the status and reference number and writing them to the order. See prior authorization.
- Referrals and order intake. Answering the referral line, requesting missing order details and confirming back to the referrer. See referrals.
- Patient outreach. Reminders, prep instructions and follow-up calls. See patient outreach.
Many of these calls are between organizations, not with patients. A teleradiology group calls a hospital. A lab calls a collection site. A pharmacy calls a prescriber's office. An imaging center calls a payer. These calls run through switchboards, phone trees and hold queues, so an agent built for them has to navigate menus, ask for a person by name and department, and wait on hold.
Where do voice agents not belong?
A voice agent does not belong on a call that requires clinical judgment. Contour's agents handle routine operational calls that require no clinical judgment, and the boundaries are worth stating plainly.
- Clinical decisions. Triage, diagnosis and treatment advice stay with clinicians. An agent can deliver a finding exactly as the radiologist signed it. It should not explain what the finding means for the patient's care.
- Decisions that belong to a licensed professional. A question for a pharmacist goes to a pharmacist. A prior authorization denial goes to the team that decides what to do about it.
- Conversations outside the script. Complaints, billing disputes and callers in distress need a person.
- Calls with no record behind them. If there is nothing to read before the call and nowhere to write the outcome after it, an agent adds little.
The test of a deployment is what happens at the boundary. When a call leaves the workflow, the agent should transfer it to your staff with the context so far, so nothing has to be repeated.
How should you evaluate a healthcare voice agent?
Evaluate five things: integration depth, verification before protected health information (PHI), the audit trail, escalation, and HIPAA terms.
Integration depth
Ask what the agent reads before the call and what it writes after it. A voice agent that cannot see the order or the schedule can only take a message.
Contour connects to the RIS, PACS, EHR, LIS or pharmacy system to retrieve context before each call and update records after it. Integrations include RamSoft, NexHealth and custom HL7 interfaces, configured with your team. Each workflow names the fields it updates and the attachments it adds, so ask any vendor to show the write-back in your own system.
Verification before PHI
The HIPAA Privacy Rule requires a covered entity to verify the identity and authority of a person requesting PHI when that person is not already known to it (45 CFR 164.514(h)). On a phone line, that means identifiers. Ask:
- Which identifiers does the agent check, and can you configure them per workflow?
- What does the agent say before verification is complete?
- What does the agent do when it reaches voicemail?
With Contour, callers are verified on the identifiers you configure before an agent shares any PHI, and nothing is spoken before that point. On voicemail the workflow decides: leave a scripted message without PHI, retry later, or send a text.
Audit trail
An audit trail is the record of what happened on each call: who was reached, what was said, what the agent read and what it wrote, with timestamps. Ask whether every call is recorded and transcribed, whether the log can be exported, and whether a reviewer can see why the agent did what it did.
Contour logs every call, read and write with a timestamp, and the log is exportable on request. Trace shows what the agent heard, decided, read and wrote on each call.
Escalation
Escalation is the rule for what happens when the script ends or the right person cannot be reached. Ask who receives the transfer, what context arrives with it, and how many attempts are made before a person is notified. In Contour, escalation paths are configured per workflow and per site, and every attempt is logged.
HIPAA and the Business Associate Agreement
Under HIPAA, a party that creates, receives, maintains or transmits PHI on behalf of a covered entity is a business associate (45 CFR 160.103). A covered entity may disclose PHI to a business associate once it has satisfactory assurances, documented in a written contract, that the information will be safeguarded (45 CFR 164.502(e)). A voice agent vendor that handles your calls is in that position.
Ask for the Business Associate Agreement before any PHI is handled. Ask for the SOC 2 report, how data is encrypted, who can listen to recordings, and whether your data is used to train models. Contour is HIPAA compliant and SOC 2 Type 2 certified, executes a Business Associate Agreement before any PHI is handled, and never uses customer data to train models. The controls are listed on the security page.
What rules apply to AI voices on outbound calls?
Outbound calls to patients raise a consent question as well as a privacy one. In February 2024 the Federal Communications Commission ruled that calls made with AI-generated voices are "artificial" under the Telephone Consumer Protection Act (FCC news release). An outbound patient calling program that uses a voice agent should be reviewed with counsel against those rules before it starts.
How do teams usually start?
Most teams start with one line, the one that takes the most staff hours, and expand workflow by workflow. A typical sequence:
- Connect the systems of record, with read access to the schedule, orders and results and write access for notes and outcomes.
- Configure the workflow: scripts, verification steps, escalation rules and phone trees.
- Go live on one line and review the calls.
- Add lines, sites and call types as the data supports it.
Where Contour fits
Contour builds voice AI agents for the operational phone calls healthcare organizations run on, integrated with the systems of record. Contour works with teleradiology groups, imaging centers, diagnostic labs, pharmacies and health systems and clinics.
To go further, read how the platform works, which systems Contour connects to on the integrations page, and common questions in the FAQ. Related articles: