# AI IVR replacement for healthcare: Let patients say what they need

A patient who calls about a refill should not have to work out whether that belongs to the pharmacy line, billing, or the front desk before pressing anything. An AI voice agent asks what the patient needs and then answers, routes, or hands the call to staff, so a phone menu stops doing that sorting for the caller.

## What does an AI IVR replacement do for healthcare?

An AI IVR replacement for healthcare is an AI voice agent that answers a practice's or health system's phone line by talking with the caller, in place of a menu that asks them to press a key. The agent does the same front-door job as an IVR by asking and listening, and Bland's guide to [what an IVR is](/ai-ivr) explains how those menus work.

A healthcare line takes calls from patients, from family members and caregivers calling for a patient, from pharmacies, from referring offices, and from insurers. Each has a different reason to call, and a menu that offers four or five departments fits only some of them.

A caller worried about a symptom is the person least able to sit through a six-option menu. A caller whose bill is wrong because a visit was denied is billing, insurance, and the clinic at once, and the menu makes them pick one. A [phone tree](/phone-tree) has no way to ask that caller which of the three it is.

Bland builds AI phone agents that answer inbound calls and place outbound calls. Your team builds and edits them in plain English with Norm or in Bland's visual builder, with no engineers needed on your side. Enterprise customers also get Bland's forward-deployed engineers.

That covers both directions: the agent that takes a patient's inbound question can sit alongside outbound calls that a team decides belong to an agent, such as a reminder before a visit. For the general case, see Bland's pages on [IVR replacement](/solutions/ivr-replacement) and the [best AI IVR replacements](/blog/best-ai-ivr-solutions).

## Which healthcare calls should an AI voice agent answer first?

The first calls to give an agent are the high-volume ones where a caller wants an answer or a simple task done and no clinical judgment is involved. In healthcare, that list looks like this:

- Scheduling, rescheduling, and canceling a visit.
- Prescription refill requests: the agent takes the details and sends them to the clinical team, because approving a refill stays with staff.
- Referral questions, such as whether a referral was sent and where to go next.
- Billing questions, such as a balance, a statement, or how to pay.
- Insurance questions, such as which plans a practice accepts and what to bring to a visit.
- Hours, locations, parking, directions, and preparation instructions for a visit.
- Whether a lab or imaging result is ready, without discussing what it shows.

A knowledge source can be a file, a site, a block of text, or a synced document, and an agent it is attached to searches it during the call, so hours, location pages, and visit instructions can come from material your practice already keeps.

### Which calls should stay with a person?

A person should take anything clinical: a caller describing a symptom, a question about what a result means, a medication reaction, or a caller in distress. A team can write the agent's instructions so that a caller describing an emergency is directed to emergency services, and a caller who sounds urgent after hours goes to the on-call line.

Handoff depends on the phone system around the agent. On Five9, Bland's SIP connection is built and tested once in Five9's partner environment and reused for each customer. Calls go from Five9 to a Bland agent and transfer back to Five9 skills or agents, with call data in SIP headers.

On any other line, a team decides which calls go to a person and writes that into the agent's instructions. Have the practice's clinicians read that list of calls before the agent takes its first one.

## How does a healthcare team build one without engineers?

A team describes what it wants in plain English, and Norm builds, edits, tests, and debugs its agents. A practice administrator might start by typing instructions like this invented example into [Norm](/norm).

```text
Answer calls for [clinic name]. Greet the caller and ask what they need.
Book, move, or cancel visits using the clinic's open appointment slots.
For a refill, collect the patient's name, date of birth, and medication, then send the request to the nurse line.
```

The same example then sets the safety and handoff rules:

```text
If a caller describes chest pain, trouble breathing, or any emergency, tell them to hang up and call 911.
Transfer anything clinical, and any caller who asks for a person, to the front desk.
```

A new Bland account can talk to its first agent in a browser, or have the agent ring a phone number, before buying a phone number or a plan. A new Bland account shows a "Let's get this agent talking" checklist: create an agent, talk to it, promote it to production, and see what happened.

Salesforce, HubSpot, Cal.com, Calendly, Notion, and Slack connect from Bland's dashboard. Anything else connects through Bland's REST API and webhooks, which Bland's forward-deployed engineers can help with on Enterprise. A scheduling or records system that offers an API follows that second path, and Bland's [integrations](/integrations) page lists the first.

## How does a healthcare team keep control of it?

Control comes from how versions move. Every agent has development, staging, and production environments, and live calls run the pinned production version. Evaluations score an agent's calls, and a passing run can be required before a version is promoted, so a change to refill wording can be scored before patients hear it.

Every enterprise customer runs on its own isolated infrastructure, run by Bland: dedicated compute, containers, and resources, with releases the customer chooses when to adopt and canary deployments on a share of real calls. Bland self-hosts its models and uses no third-party model providers.

For a healthcare team, the compliance fact that matters most is that Bland is HIPAA compliant with a BAA.

Bland's Trust Portal holds its SOC 2 Type II report, a penetration test summary, its Data Processing Agreement, and its Business Associate Agreement, and security teams can file a security review request or ask for customer references. Bland has a 99.9% uptime SLA, and Bland's [trust and security](/trust-security) page has the rest.

Whether a particular call flow meets a healthcare organization's own obligations is a question for that organization's compliance team, and it belongs in the review before the first patient call.

## What does an AI IVR replacement cost a healthcare provider?

Bland charges $0.14 a minute on the self-serve Start plan. Enterprise pricing is custom, set with Bland's sales team. Phone is billed separately, on a customer's own carrier or Bland's at pass-through cost.

An IVR you own today is priced in licenses, seats, or a contract with a phone vendor, and a per-minute rate follows how long patients talk. Comparing the two takes your own monthly call minutes and a count of how many of those calls an agent finishes, so start with call volume. Bland's [pricing](/pricing) page has the plans, and Bland's [enterprise](/enterprise) page covers Enterprise.

For a closely related set of calls, see Bland's page on [IVR replacement for dental offices](/solutions/ivr-replacement-for-dental-offices), and for claims and policy calls, [IVR replacement for insurance agencies](/solutions/ivr-replacement-for-insurance-agencies).

## Frequently asked questions

### Can an AI voice agent replace a clinic's IVR completely?

It can take the front door, and a team decides how much of the old menu stays. A Bland agent can sit in front of, or alongside, a Five9 contact center, so a health system with Five9 can send only chosen calls to an agent. Calls that need a person still go to one.

### Is Bland HIPAA compliant?

Yes. Bland is HIPAA compliant with a BAA, and Bland's Trust Portal holds its Business Associate Agreement. Whether a specific call flow meets a practice's own obligations is for that practice's compliance team to decide.

### Can it make outbound calls?

Yes. Bland builds AI phone agents that answer inbound calls and place outbound calls, so the agent that takes over from a patient phone menu is not limited to one direction.

### What happens when a patient needs a person?

A team decides which calls go to a person and writes that into the agent's instructions. On Five9, a call transfers back to Five9 skills or agents, with call data in SIP headers.

### Does it connect to a records or scheduling system?

Salesforce, HubSpot, Cal.com, Calendly, Notion, and Slack connect from Bland's dashboard. Any other system connects through Bland's REST API and webhooks, which Bland's forward-deployed engineers can help with on Enterprise.

### Do healthcare teams need developers to build an agent?

No. Norm, Bland's AI assistant, builds voice agents using natural language descriptions, and Bland's dashboard includes a visual builder for non-technical users.

### How much does it cost?

Bland charges $0.14 a minute on the self-serve Start plan. Enterprise pricing is custom, set with Bland's sales team. Phone is billed separately, on a customer's own carrier or Bland's at pass-through cost.
