# Hospital answering service for your main line

A hospital's main line carries visitors asking about visiting hours, callers looking for a department, and people who need a person right now, all on one number. Bland's agents answer a main line from information you supply, route each caller, and transfer a call to a number you choose.

Larger teams begin at [Bland's Enterprise page](/enterprise), because a main line's volume and its need for a BAA are Enterprise questions. The smaller answering service pages sit under [Bland's AI answering service hub](/ai-answering-service), and [Bland's home health answering service page](/solutions/home-health-answering-service) covers agencies whose clinicians work in patients' homes.

## What does a hospital answering service do on Bland?

A hospital answering service on Bland is an AI phone agent on your main line that replies to general questions from your documents and transfers a call to a number you choose.

Your agent does the part of the job that is answering a general question or handing a call on, and a person on your team takes every call that needs one. A hospital decides in its own instructions which calls those are, what a caller with an emergency hears, and which number each transfer goes to.

You write the instructions in plain English with [Norm](/norm) or in Bland's visual builder, setting where calls route and when your agent hands off to a person.

## Why does a hospital's main line belong on Enterprise?

A hospital's main line belongs on Bland's Enterprise plan, because Enterprise sizes concurrency to your volume, carries unlimited daily and hourly call caps, and includes a BAA.

Start takes 10 calls at once, 100 calls an hour, and 100 calls a day. Build takes 50 calls at once, 1,000 calls an hour, and 2,000 calls a day. If your main line can bring more than 50 callers at once, Enterprise's concurrency sized to your volume is the plan to price.

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. Bland's forward-deployed engineers come with Enterprise too.

A BAA comes with Enterprise, and neither self-serve plan includes one, so an agent that handles patient information runs on Enterprise. Hospital security teams can check Bland's credentials: SOC 2 Type II, HIPAA compliant with a BAA, GDPR compliant with a DPA, and PCI DSS v4.0.1 self-attested. Your hospital's compliance advisor decides how HIPAA applies to its calls, and [Bland's HIPAA compliant voice AI page](/hipaa-compliant-voice-ai) explains Bland's side.

## How does a hospital keep its phone system and add a Bland agent?

Bland connects your own carrier, PBX, or contact center over SIP for inbound calls, outbound calls, and transfers, so a hospital whose carrier or PBX connects over SIP can keep both.

Bland's SIP transfers go to a DID, extension, or SIP URI, so your agent can hand a caller to a department's extension on your own phone system. Bland's SIP guides also cover 3CX, Bandwidth, Telnyx, and Twilio. A separate page lists Bland's regional SIP endpoints, what to allow-list on your firewall, and the TLS, SRTP, and codec requirements for your network team.

If you bring your own telephony provider, you handle carrier costs directly and Bland charges only the per-minute AI rate. [Bland's VoIP answering service page](/ai-answering-service/voip-answering-service) goes through the setup, and [Bland's inbound answering service page](/ai-answering-service/inbound-answering-service) covers how an agent handles a steady stream of callers.

## How does your agent route a caller to the right department?

Bland's agent routes a caller from the instructions and pathways you write, and every transfer goes to a number you choose.

A pathway is a flow you lay out yourself, with steps you place and the connections you draw between them. It does not run until you set its routing condition, which decides when a conversation enters it, so check that condition before you promote your agent.

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. Bland reads a domain's sitemap to pull in a website, and a daily auto-sync switch syncs it again each day.

Enterprise has unlimited knowledge bases, against 10 on Start and 50 on Build, so a hospital can keep a knowledge base for each department.

Change control matters on a main line. 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. Before callers arrive, Source testing lets you put a visitor's questions to your agent's knowledge.

## How much does a hospital answering service cost on Bland?

As of November 2026, Bland's self-serve rates are $0.14 on Start and $0.12 on Build, both per talk minute, with phone billed separately, and a hospital's main line is priced on Enterprise.

Enterprise pricing is custom, set with Bland's sales team. Bland contracts Enterprise to your volume, and a 99.9% uptime SLA applies on every plan.

### What the self-serve rates look like at scale

For scale only, and for building and testing, 3,000 talk minutes in a month bills $420 before phone on self-serve Start (3,000 at $0.14) and $659 before phone on self-serve Build, made of Build's $299 monthly fee and $360 of talk time. A main line is sized against Enterprise's custom terms, and the self-serve figures show the shape of a per-minute bill.

### What phone costs on top

Phone is billed separately, on a customer's own carrier or Bland's at pass-through cost. A phone number bought from Bland costs $15 a month, in the United States or Canada. Bland works with more than 250 enterprise customers. The three plans sit side by side on [Bland's pricing page](/pricing).

A housing finance agency has little in common with a hospital, and this is what one Bland customer there reports:

Idaho Housing and Finance Association saves $750,000 a year by replacing its IVR with Bland, which handles 4,000 inbound calls a day and cut average call time by 20%.

> "We save thousands of dollars a day."

Greg Blake, Chief Information Officer, Idaho Housing and Finance Association

## Frequently asked questions

### Does Bland have a no-code option?

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

### Is Bland only for outbound calls?

No. Bland's agents answer inbound calls and place outbound ones, and a hospital's main line is inbound work.

### Can your agent diagnose a caller or decide who needs care?

Keep those decisions with your clinicians. Give your agent a narrower job: answer general questions from your documents, and transfer a call to a number you choose.

### Does Bland sign a BAA?

Yes. A BAA comes with Enterprise, and neither self-serve plan includes one, so an agent that handles patient information runs on Enterprise.

### Can your agent connect to your hospital's other systems?

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 system with no API of its own can't be connected, and your agent takes the details instead. The full list of connections is on [Bland's integrations page](/integrations).

### Can callers reach a person?

Yes. Your agent transfers a call to a number you choose, and over SIP a transfer can go to a DID, extension, or SIP URI on your own phone system.

A single practice can begin at [Bland's AI phone agents page](/small-business/ai-phone-agents), and [Bland's AI receptionist page](/solutions/ai-receptionist) shows the same idea at a front desk.
