Is an AI Receptionist HIPAA Compliant? What Practices Should Ask

A practice manager gets the same pitch three times in a month: an AI receptionist that answers every call, books appointments and never calls in sick. Each one says HIPAA compliant somewhere on the page. The question that matters is what that phrase actually guarantees, and the honest answer is: on its own, nothing.

This guide explains what the HIPAA rules require when software answers a medical practice’s phone, what the major voice AI platforms offer as of November 2026, and the questions to ask before any patient call goes through a new vendor. It is general information, not legal advice. Your counsel and your HIPAA privacy officer make the final call.

Is there such a thing as a HIPAA certified AI receptionist?

No. HHS states that it does not endorse or otherwise recognize private organizations’ HIPAA certifications, and that such certifications do not absolve covered entities of their legal obligations. A badge on a vendor’s website may reflect real work, such as a third-party audit, but it is not a government approval, and it does not move responsibility off the practice.

What HIPAA does require is a relationship, documented in writing. Under 45 CFR 164.502(e), a covered entity may let a business associate handle protected health information only after obtaining satisfactory assurance that the business associate will safeguard it, and that assurance must be documented in a written contract or agreement. That document is the Business Associate Agreement.

Does HIPAA apply to your practice’s phone calls?

HIPAA applies to covered entities, and for providers the test is specific. Under 45 CFR 160.103, a health care provider is a covered entity if it transmits health information electronically in connection with a standard transaction, such as an insurance claim. CMS puts it plainly: providers who submit HIPAA transactions, like claims, electronically are covered. Most medical, dental and therapy practices that bill insurance meet that test. Some cash-only practices, including some med spas, may not, and CMS offers a covered entity decision tool for exactly that question.

If HIPAA does apply, phone calls are not exempt. The regulation defines health information as information whether oral or recorded in any form, and HHS guidance on individually identifiable health information covers information about the provision of health care to a person together with identifiers such as a name or address. A recorded call in which a patient gives their name and asks to move a follow-up appointment is the kind of data the rules were written for.

When does an AI phone vendor need a BAA?

A business associate is anyone that creates, receives, maintains or transmits protected health information on a covered entity’s behalf. HHS gives an example that fits AI receptionists closely: a third-party chatbot on a provider’s patient portal that provides services involving patients’ health information, such as symptom assessment, medical reminders and appointment scheduling. HHS also makes clear that subcontractors of a business associate, such as the telephony, speech and AI model providers underneath a voice product, are business associates too and need their own agreements.

Two details catch practices out. First, HHS guidance on audio-only telehealth says a BAA is needed with a vendor that is more than a mere conduit, for example one that stores recordings or transcripts. Most AI receptionists store both by default. Second, encryption does not remove the requirement. HHS cloud guidance says a cloud provider is a business associate even if it stores only encrypted data and lacks the key.

The penalties are real. HHS’s current civil penalty tiers, unchanged for 2026, range from $145 per violation where the entity did not know, up to $2,190,294 per calendar year for the most serious tier. HHS has settled several cases over missing BAAs, including $31,000 from the Center for Children’s Digestive Health in April 2017, $500,000 from Advanced Care Hospitalists in December 2018, and $750,000 from Raleigh Orthopaedic Clinic, which HHS described as a reminder that BAAs are more than a mere check-the-box paperwork exercise.

Which voice AI platforms will sign a BAA?

Most AI receptionists are built on a small number of underlying platforms, so the platform’s terms often decide what the product above it can promise. Here is what each platform’s own documentation says as of November 2026. Terms change, so confirm on the vendor’s current pages before relying on any of it.

• ElevenLabs (ElevenLabs Agents): offers BAAs, but only for Enterprise tier subscriptions, which have custom pricing. Its Zero Retention Mode means raw audio and transcripts containing patient information are not retained.
• Retell AI: offers a BAA for self-signing on its click-agreements site and states there is no additional fee to sign. A signed BAA is required before sending patient information through Retell, and retention of transcripts and recordings can be set per agent from one day to two years, or turned off.
• Vapi: offers HIPAA as a paid compliance add-on, listed at $2,000 a month on its pricing page, with a BAA sent by email to sign. HIPAA mode applies to the whole organization and cannot be combined with Vapi’s zero data retention option.
• Bland AI: says it is HIPAA compliant with a signed BAA. Its pricing grid shows the BAA on the Enterprise plan, while its healthcare page says a BAA is included with healthcare deployments, so confirm the plan directly with Bland.
• Synthflow: signs a BAA with customers who turn on its HIPAA Setting, which is off by default. Every Synthflow deployment is sold as an annual enterprise agreement, and its trust listing describes its HIPAA status as self-attested.
• Twilio (the phone network layer under many products): signs a Business Associate Addendum only for customers on its Security or Enterprise editions, and only for services on its HIPAA-eligible list, which includes call recordings, transcription and media streams.
• OpenAI API: offers a self-serve BAA without an enterprise agreement for organizations with an established history of API usage, and requires a retention setup it calls Modified Retention. Its realtime and audio endpoints are listed as eligible.
• Anthropic (Claude API): eligible organizations can sign a BAA and enable HIPAA readiness in the Claude Console, or contact sales. Some features are excluded, and the setting is permanent once turned on.
• Google Cloud: one BAA covers the Google Cloud infrastructure, with a published list of covered services that includes Speech-to-Text and its generative AI agent platform, at the same pricing as other customers.

The pattern is consistent: the BAA exists, but it usually sits on a specific plan, costs extra, or requires a particular data setting. A product built on a platform’s standard plan generally cannot offer a BAA covering that layer.

What should a practice ask an AI receptionist vendor?

These questions come from HHS’s sample BAA provisions and audio telehealth guidance, and from the American Medical Association’s vendor intake checklist. A vendor that answers them clearly in writing is worth a closer look; a vendor that answers with a badge is not.

• Will you sign a BAA with us before any patient calls go live?
• Which subcontractors touch patient data, such as the phone carrier, speech recognition, AI model and cloud host, and do you have a BAA with each one?
• Does the plan we are buying include the BAA, or is it a separate tier or add-on?
• Do you store call recordings and transcripts? Where, for how long, and can we shorten retention or turn storage off?
• Is data encrypted in transit and at rest, and who holds the keys?
• Who can access recordings and transcripts, and do you support individual logins, multi-factor sign-in and audit logs?
• How quickly will you tell us about a breach? HHS allows up to 60 days; the HHS sample agreement suggests negotiating a shorter deadline.
• Will our patients’ data be used to train models or for any other purpose?
• If we cancel, can we export our data and get written confirmation that it was returned or destroyed?
• Can you share a third-party audit report, such as SOC 2 or HITRUST, and recent penetration test results?

What can an AI receptionist do without handling patient information?

Some practices narrow the job instead of expanding the contract. An AI line can answer general questions such as hours, location, parking and the insurance plans accepted, and route callers, without asking for anything clinical. Even then, a caller may volunteer a name and a reason for the visit, and once a vendor records or transcribes that call, it is holding information about a patient. Whether a narrow setup changes your obligations is a question for your privacy officer, not a way around the rules.

The short version

A HIPAA compliant label is a starting point for questions, not an answer. The thing to ask for is a signed BAA from the vendor you contract with, confirmation that every subcontractor in the call path is covered by its own agreement, and clear written answers on recordings, retention, access and breach notice. If a vendor cannot provide those, it is not ready to answer a covered practice’s phones, whatever its website says.

Frequently asked questions

← Back to all articles