HIPAA Compliant AI Receptionist: What a Small Clinic Has to Check Before Going Live

The demo goes fine until someone asks about the BAA

A dental office owner watches an AI receptionist demo, loves it, and then asks the sales rep one question: will you sign a business associate agreement? What happens next decides whether the project is a $200 a month win or a compliance problem. Some vendors say yes at a price. Some say yes only on an enterprise plan. Some do not know what you mean.

This guide is for owners of small medical, dental, therapy and similar practices in the US. It explains what HIPAA asks of you in plain terms, what the main voice platforms say and charge, and how to cut your exposure by collecting less. It is not legal advice, and a lawyer or compliance officer should look at your final setup.

What counts as patient information on a phone call

If you are a HIPAA covered entity, a caller's name, phone number and the reason they are calling can all be protected health information once tied to your practice. "This is Maria Lopez, I need to reschedule my root canal" is PHI. So is a voicemail about test results.

Any company that handles that information for you is a business associate. The HHS guidance on cloud computing is clear that a service provider storing only encrypted data, even without holding the key, is still a business associate. The covered entity needs a signed business associate agreement (BAA) first. Using such a vendor without one is a violation on your side, not just theirs. HHS also does not certify or endorse specific products, so a vendor's "HIPAA compliant" label is a marketing claim until you have the paper and have checked it covers your use.

Note that HIPAA generally applies to human health care providers. A veterinary clinic is usually outside it, though state privacy laws may apply. The vet receptionist build documented on this site (builtwithagents.ai/strategy/voice-ai-receptionist-veterinary-clinics) would not need these steps in the same way, but a dental or medical build would.

Every vendor in the chain

An AI phone call passes through several companies. List them all.

The phone carrier or number provider. Twilio will sign a BAA, but only for accounts on its Security Edition or Enterprise Edition, and only for the products on its HIPAA eligible list. Trial and standard accounts cannot get one. Check the current eligible-services list before you rely on voice or messaging.

The voice platform. Vapi's pricing page lists a HIPAA add-on at $2,000 a month (as of October 2026), described as HIPAA eligible data handling with a standard data processing agreement and BAA. An older post on this site quoted $1,000; the page is the authority, so check it again. Retell's pricing page lists HIPAA and a custom BAA in its Enterprise column, but Retell's own help center says a BAA does not require an Enterprise plan and can be signed from the dashboard. Where a pricing table and a help article disagree, get the answer in writing from sales. Retell's usage rate runs from $0.07 to $0.31 a minute, with a sample configuration at $0.11. Synthflow's reviews I found describe HIPAA as an Enterprise-only feature with quote-based pricing; I could not confirm figures on Synthflow's own site, so ask them directly.

The AI model, speech-to-text and text-to-speech providers. Many platforms route to third parties. Ask whether the BAA covers the whole stack or only the platform's own servers. Retell's guidance, for example, says outside tools that receive transcripts need their own BAAs.

Your automation tools. This is where small builds break. If the assistant sends caller details to Make, n8n, Zapier, a Google Sheet or an email inbox, each of those becomes part of the chain. A free Google Sheet that logs "Maria Lopez, root canal, reschedule" is a PHI store with no BAA behind it. Self-hosted n8n on your own compliant server is different from a cloud tool you have not checked.

Your calendar or practice management system. If the AI writes to it, that vendor needs to be covered too, and it likely already is if it is a healthcare product.

What it costs

The honest comparison is a $2,000 a month add-on versus usage pricing that scales with calls. On Vapi, HIPAA handling alone is $24,000 a year before a single minute of usage. That makes sense for a multi-location group or a company selling the service, but not for a single dental office. For a one-location practice, platforms where the BAA is available without a large fixed fee, or healthcare-specific products that include it, are the realistic path. Confirm prices in writing.

On Retell's published example of $0.11 a minute, a front desk handling 1,500 minutes a month would spend about $165 on usage (an estimate, before any add-ons such as PII removal at $0.01 a minute). Twilio's Security Edition adds its own cost, which you should get from their sales team. Count your lawyer's or compliance consultant's review time too.

One builder on this site documents a healthcare voice agent that sells to clinics at $10,000 setup plus a monthly retainer, with insurance verification and booking (builtwithagents.ai/strategy/healthcare-voice-agent-patient-intake-10k). The price is self-reported, and it is a reminder that serious clinical work is sold as a service, not as a $30 hobby build.

Step by step: a safer way to launch

Step 1: Decide what the AI is allowed to collect

Write one sentence: "The assistant takes a name, a callback number and a request type (new patient, reschedule, billing question, urgent). It does not ask about symptoms, diagnoses, medications or insurance details." Smaller scope means less PHI and a simpler vendor list. Add an urgent rule: anything that sounds like an emergency gets the instruction to hang up and call 911, plus a transfer to a staff member.

Step 2: Map every tool the call touches

Draw a line from the caller's phone to your calendar and write each company on it. Include where transcripts, recordings and logs are stored. If you cannot list them, you are not ready.

Step 3: Get BAAs in writing, from each vendor that stores or processes the call

Email each vendor: "Do you sign a BAA for [service]? Which plan is required? What do you cover and what is excluded?" Keep the replies and the signed agreements in one folder. If a vendor refuses, remove that vendor from any path that carries patient information.

Step 4: Remove PHI from side tools

Turn off transcript forwarding to email and sheets. If you need a log, store the minimum in your practice management system, not a spreadsheet. If your platform offers PII redaction or zero retention for transcripts, turn it on and test that it works.

Step 5: Handle recording and disclosure

Many states require consent from everyone on a call before it is recorded. Have the greeting say that calls are handled by an automated assistant and may be recorded, and give a way to reach a person. Check your state rules.

Step 6: Write the policy and do the risk analysis

HIPAA expects a documented security risk analysis and staff policies. Add the AI assistant to both: what data it sees, who can access the logs, how long they are kept, and what staff do when it fails. A short written document beats nothing.

Step 7: Test with fake patients, then go live in limited hours

Run 20 test calls with made-up names. Check where each piece of data lands: platform logs, the calendar, any sheet or email. Then switch the assistant on for after-hours calls only for a couple of weeks, reviewing transcripts, before you let it take daytime overflow.

What goes wrong

The most common failure is a good vendor and a bad side channel: the platform signs a BAA, and the transcript still lands in an unprotected sheet. The second is scope creep, where someone adds "ask about insurance" to the prompt and the assistant now collects far more than planned. The third is assuming the BAA moves the responsibility: it does not. You remain responsible for how you configure the system.

Accuracy matters too. The vet clinic prototype documented on this site reached about 60 percent accuracy at first, with hallucinated slots and bad name capture. In a clinic, a wrong time or the wrong patient is a patient safety and privacy problem, not just an annoyance.

When not to do this

If you cannot get a BAA from every vendor that touches patient information, do not put patient information through the assistant: use it only to answer general questions about hours and location, with a transfer to staff for anything else. If your practice handles very sensitive categories such as behavioral health or substance use treatment, get advice before you start, since additional rules can apply. And if the practice is small enough that a person can return calls within an hour, a voicemail system may be the smarter choice.

Frequently Asked Questions