Is an AI voice agent HIPAA compliant?
No product is HIPAA compliant by itself. HIPAA applies to how a covered entity, such as a medical or dental practice, and its vendors handle protected health information. If an AI voice agent records, transcribes or stores calls in which patients share health information, the vendor is a business associate and the practice needs a signed business associate agreement (BAA) with it before the first patient call. HHS does not certify software. Botcadence does not sign a BAA today and makes no HIPAA claim, so a practice that needs one should choose a vendor that offers it. This guide explains what to check, with links to HHS. It is general information, not legal advice. For what the agent does on a clinic's line, see the medical answering service voice agent.
Key takeaways
- A vendor that creates, receives, maintains or transmits protected health information for a practice is a business associate, and a BAA is required.
- HHS says a cloud service provider is a business associate even when it holds only encrypted information and has no key.
- A phone carrier that only passes a call through is a conduit. A vendor that records or transcribes the call is not.
- HHS says it does not endorse or recognize private "HIPAA certifications".
- Several voice platforms offer a BAA only on higher plans. On prices read November 12, 2026, Vapi lists a HIPAA add-on at $2,000 a month, and Bland AI, Retell AI, ElevenLabs and PolyAI list a BAA on enterprise plans.
When is a voice AI vendor a business associate?
HHS's guidance on business associates describes one as a person or entity that creates, receives, maintains or transmits protected health information on behalf of a covered entity, and says a written contract, the BAA, is required. Subcontractors that handle the information for the business associate are included.
Two HHS guidance pages settle the usual arguments:
- "We only store encrypted data." HHS's cloud computing guidance says a cloud service provider that maintains electronic protected health information is a business associate "even if" it stores only encrypted information and lacks the decryption key.
- "We are just the phone line." HHS's audio-only telehealth guidance says no BAA is needed with a telecommunications provider that is a mere conduit with only transient access. It also says a BAA is needed when a vendor creates, receives or maintains the information, and it mentions recordings and transcripts as stored electronic protected health information.
An AI voice agent that transcribes speech, sends it to a language model, and keeps a transcript or summary is doing far more than passing a call through. So are the speech and model providers behind it, which is why the vendor's own subcontractor agreements matter.
What a phone call can contain
| On the call | Is it health information? |
|---|
| "I need to reschedule my appointment" with a name | It links a person to a provider; treat it as protected |
| "I'm having chest pain" or a symptom description | Yes |
| A medication name for a refill request | Yes |
| Insurance member details | Yes |
| "What are your hours?" from an unnamed caller | No |
A practice cannot control what patients say, so plan as though every call may contain health information.
There is no HIPAA certification
HHS's FAQ on certification says there is no requirement to certify compliance, and that HHS does not endorse or otherwise recognize private organizations' certifications. A badge on a vendor's website is the vendor's own statement. What counts is the signed BAA and the safeguards behind it.
What vendors publish about BAAs
Read on each vendor's own site on November 12, 2026:
| Vendor | What its site says |
|---|
| Vapi | A HIPAA add-on at $2,000 a month |
| Bland AI | A BAA on the Enterprise plan |
| Retell AI | "HIPAA / BAA" listed under Enterprise |
| ElevenLabs Agents | BAAs for healthcare customers on Enterprise |
| PolyAI | A BAA on Enterprise |
| Aircall | A BAA on request |
| Synthflow | A signed BAA on its home page; "self-attested" on its pricing page |
| Botcadence | No BAA offered and no HIPAA claim made |
Plans change. Ask each vendor for the BAA itself, the plan it requires and the price, in writing.
Questions to ask a voice AI vendor
- Will you sign a BAA, on which plan, and at what cost?
- Which subcontractors process call audio and text (speech recognition, the language model, voice synthesis, hosting), and do you hold a BAA with each?
- Are recordings and transcripts kept? For how long, and can I set a retention period or switch recording off?
- Is call data used to train models?
- Where is the data stored, and is it encrypted in transit and at rest?
- Who at your company can open a transcript, and is access logged?
- How will you notify me of a breach, and how fast?
- Can you delete a patient's data on request, and prove it?
What the practice still has to do
A BAA does not make the practice compliant. The practice remains responsible for:
- Minimum necessary. Script the agent to ask only what it needs to book or route the call.
- Its own risk analysis covering the new system.
- Access. Limit who in the practice can read transcripts.
- Patient notices and consent to recording, which is also a state-law question.
- Outbound calls. Appointment reminders have their own treatment under telemarketing rules, and marketing calls need authorization.
Where Botcadence stands
Botcadence does not offer a BAA and does not describe itself as meeting HIPAA requirements. Inbound call recording is off by default and can stay off, but transcripts and summaries are still created and stored, and there are no retention controls or redaction of personal data in call records today. A practice whose calls include patient health information should use a vendor that will sign a BAA. Botcadence is a fit for businesses outside HIPAA's scope, and for healthcare-adjacent uses that carry no patient information. For other compliance topics see are AI phone calls legal? and call recording consent by state; the voice agent page describes the product.