A HIPAA compliant AI receptionist is not a product you can buy off a certification badge. It is a contract. No federal body certifies AI phone agents, and no vendor can hand you a certificate that transfers the risk. What the HIPAA Privacy Rule actually requires is a business associate agreement containing ten specific terms, signed before the vendor touches a single call — and a duty on you, the practice, to act if the vendor breaks it.
If you are still deciding whether a phone agent belongs in your clinic at all, start with how an AI receptionist works day to day. This post assumes you have decided and you are now looking at a vendor contract.
What a HIPAA compliant AI receptionist actually is
The moment an AI receptionist answers a call for a healthcare provider, it is almost certainly a business associate. It hears the caller’s name, their phone number, why they are calling and when they want to be seen. That is protected health information, and it is being created, received and stored on your behalf by somebody who is not you.
The rule that governs this is 45 CFR § 164.504(e). Its opening line is blunt about where the obligation lives: The contract or other arrangement required by § 164.502(e)(2) must meet the requirements
set out in the paragraphs that follow. Not a certification. Not an attestation. A contract, with named terms in it.
This matters because “HIPAA compliant” is a marketing phrase that anyone can print. The regulation gives you something better than a phrase: a list you can check line by line.
The ten terms the agreement has to contain
§ 164.504(e)(2)(ii) sets out what the business associate contract must require of the vendor. There are ten sub-items, (A) through (J). In plain terms, the vendor must:
- (A)
Not use or further disclose the information other than as permitted or required by the contract
— so the contract itself defines the ceiling. - (B)
Use appropriate safeguards and comply, where applicable, with subpart C
— the Security Rule, for anything electronic. - (C)
Report to the covered entity any use or disclosure of the information not provided for by its contract
. - (D)
ensure that any subcontractors that create, receive, maintain, or transmit protected health information
agree to the same restrictions. - (E)
Make available protected health information in accordance with § 164.524
— patient access requests. - (F)
Make available protected health information for amendment and incorporate any amendments
. - (G)
Make available the information required to provide an accounting of disclosures
. - (H)
comply with the requirements of this subpart that apply to the covered entity
where it is carrying out your obligations. - (I)
Make its internal practices, books, and records relating to the use and disclosure
available to the Secretary. - (J) On termination,
return or destroy all protected health information received from, or created or received by the business associate
.
Read (J) again with a voice agent in mind. At the end of the contract, the transcripts go back or they get destroyed. If a vendor cannot tell you which, in writing, they have not thought about (J) — and a vendor who has not thought about (J) has not thought about (D) either.
Subcontractors: the clause that decides most AI vendors
Sub-item (D) is where an AI receptionist differs from a human answering service, and it is the question almost nobody asks in a sales call.
A human answering service has one subcontractor risk: the people. An AI phone agent typically has four or more. Something converts speech to text. Something generates the reply. Something turns text back into speech. Something stores the transcript and the recording. Frequently a telephony carrier sits in front of all of it. Each of those is a separate company that creates, receives, maintains or transmits protected health information — and (D) says the vendor must ensure each one agrees to the same restrictions and conditions that apply to them.
So the question to put to any vendor is not “are you HIPAA compliant?” It is: name every subcontractor in the call path, and show me that each of them has agreed to the same terms. A vendor who cannot produce that list in a week does not have it. That includes the general-purpose model providers — several will sign a business associate agreement, several will not sign one for their consumer tiers, and the difference is a configuration decision your vendor has either made deliberately or not made at all.
The duty the rule puts on you, not the vendor
Here is the part that surprises practices. § 164.504(e)(1)(ii) makes you non-compliant if you know your vendor is breaking the agreement and do nothing — unless the covered entity took reasonable steps to cure the breach or end the violation
, and, where that fails, terminated the contract.
You cannot outsource that. Signing a good BAA and never looking again is not what the rule describes. In practice that means somebody at the practice reads a sample of transcripts on a schedule, checks what the agent said when a caller volunteered something clinical, and has a written route for raising it with the vendor. Fifteen minutes a month is enough. Zero is not.
It is the same shape of problem as an accessible chatbot on the web side: a standard exists, the obligation is continuous, and nobody hands out a certificate that ends the conversation.
What this costs
The compliance work does not have its own price tag, which is exactly why it gets skipped. Our published pricing for the 24/7 AI Receptionist is $497 setup plus $497/mo, per number. A two-site practice running two numbers is $994 setup and $994/mo, or $12,922 across the first year — the BAA covers both numbers, but the review duty above scales with them, because two sites means two sets of transcripts somebody has to actually read.
For the wider cost picture, including the bills nobody quotes, see the full breakdown of what an AI receptionist costs.
The checklist to run before you sign
- Signed business associate agreement in hand before the agent takes a live call, not after the pilot.
- All ten sub-items (A)–(J) present — check them off against the list above rather than trusting a summary.
- A written list of every subcontractor in the call path, with confirmation each has agreed to the same terms.
- A clear answer on (J): what happens to transcripts and recordings at termination, and how long that takes.
- A named person at your practice who reviews transcripts on a set schedule, and a written escalation route.
- Recording and consent handled for your state, which is a separate question from HIPAA and is answered differently in different states.
When this is the wrong call
Four situations where we would tell you not to buy an AI receptionist from us, or from anyone:
Your practice management or EHR vendor already offers call handling. They already have a signed BAA with you and they are already inside your data. Adding a second business associate to save a few hundred dollars a month means a second contract, a second subcontractor chain and a second set of transcripts to review. Use theirs, even if the demo is worse.
You are solo, with low call volume and an existing answering service. If the service already holds a BAA with you and the only real problem is after-hours coverage, changing vendors buys you risk rather than capacity.
The vendor will not sign a BAA, or hedges on the subcontractor list. Walk away. This applies to us as much as to anyone else — if a vendor cannot answer (D) plainly, the price is irrelevant.
Nobody at the practice will own the monthly review. If there is genuinely no one to do it, you are buying a compliance obligation you have already decided not to meet. A voicemail box you return in an hour is a defensible choice. An unmonitored AI agent is not.
Frequently asked questions
Is any AI receptionist officially HIPAA certified?
No. HIPAA has no certification scheme for vendors. The rule requires a contract with the ten terms in § 164.504(e)(2)(ii), and a vendor claiming to be “certified” is describing an audit they paid for, not a government approval.
Do I need a BAA if the agent only books appointments?
Almost certainly yes. The fact that a named person is calling a named healthcare provider and requesting an appointment is itself protected health information. The content of the call being non-clinical does not change who is holding it.
What happens to call recordings and transcripts when I leave the vendor?
That is sub-item (J): the agreement has to require the vendor to return or destroy the information, or, where return or destruction is infeasible, extend the protections and limit further uses. Get the specific answer in writing before you sign, not at termination.
Is a HIPAA compliant AI receptionist different for dentists?
The contract requirements are identical; the call patterns are not. The operational side of that is covered in our guide to AI reception in a dental practice.
Does a Spanish-speaking or bilingual agent change anything?
Not for the BAA, but language introduces its own legal limits on what a phone agent may do — that is covered separately in where the law tells a bilingual agent to stop.
The bottom line
“HIPAA compliant AI receptionist” is not a claim you should accept from a vendor, including this one. It is a ten-item contract you can check yourself in twenty minutes, a subcontractor list the vendor either has or does not have, and a monthly review somebody at your practice has to actually do. If a vendor’s answer to any of those three is a badge on a webpage, that is your answer.
If you want to see what we set up and where the boundaries sit, our services page covers the scope, and you can book a call and bring your BAA questions to it. Bring the checklist above — we would rather answer (D) properly than close quickly.
Source: 45 CFR § 164.504(e), Uses and disclosures — organizational requirements, eCFR.