A HIPAA-compliant AI receptionist is one whose vendor will sign a business associate agreement covering the exact service you switch on, and who holds signed agreements with every subcontractor that processes your call audio. Everything else, including encryption, audit logs and access controls, is implementation detail that matters, but follows from that.

The uncomfortable part: no government body certifies any product as HIPAA compliant. There is no HIPAA certification programme, no registry, no badge issued by HHS. When a vendor's page says "HIPAA compliant," that is the vendor's own assertion about itself. The regulation does not work through certification; it works through contracts and enforcement, which is what this guide covers.

Key Takeaways

• HHS explicitly names AI appointment-scheduling tools as business associates. Its guidance lists a third-party AI chatbot providing "symptom assessment, medical reminders, and appointment scheduling" as an example. That removes any ambiguity about whether HIPAA applies.
  
  

• The subcontractor chain is the most common blind spot. Voice AI strings together speech-to-text, a language model, a voice and a carrier. OCR fined a software business associate $350,000 in a case that included failing to have a BAA with its own subcontractor.
  
  

• "HIPAA compliant" is a claim, not a credential. SOC 2, HITRUST and ISO 27001 are real audited certifications and are useful proxies, but none of them is HIPAA compliance, and HHS certifies nobody.
  
  

• Impermissible disclosure and inadequate safeguards are the two most-alleged HIPAA issues of all time, and they are exactly what an AI receptionist touches on every single call.

Does HIPAA apply to an AI receptionist?

Yes, and HHS has removed the ambiguity.

Its business associates guidance lists among its examples of a business associate:

"Third-party vendor Artificial Intelligence (AI) chatbot on a provider's patient portal that provides services involving the patient's PHI such as symptom assessment, medical reminders, and appointment scheduling."

That is this product category, described by the regulator. A business associate is any person or organisation that creates, receives, maintains or transmits PHI on behalf of a covered entity. An AI receptionist that hears a patient say their name, date of birth and reason for visit is doing all four.

The consequence is specific: HHS states that a covered entity may disclose PHI to a business associate only once it has obtained satisfactory assurances, in the form of a contract or other written arrangement, that the business associate will safeguard the information. No BAA, no lawful disclosure. The vendor is also directly liable for certain HIPAA provisions in its own right; it is not only your problem.

Does HIPAA apply to a human receptionist too?

Yes, but through a different mechanism. Your own receptionist is a workforce member, covered by your policies, training and sanctions, which are the administrative safeguards. An outside vendor is not a workforce member, which is precisely why a contract is required instead.

What "HIPAA compliant" does and does not mean

This phrase is doing far too much work in vendor marketing, so it is worth separating.

What it cannot mean: that a regulator has inspected and approved the product. HHS does not certify, endorse or approve products or vendors as HIPAA compliant. Any badge implying otherwise is decorative.

What it should mean: the vendor will enter a BAA, has implemented the Security Rule safeguards, and can evidence both.

What genuinely helps you assess it:

• SOC 2 Type II. An independent audit of security controls over a period of time, not a point in time. Type II is materially stronger than Type I.
  
  

• HITRUST CSF. A healthcare-specific certification that maps to HIPAA requirements and is the most demanding of the three.
  
  

• ISO 27001. An international information security management standard.

None of these is HIPAA compliance. All three are evidence that somebody independent has checked the vendor's security claims, which is more than a badge. In our comparison of eight AI receptionist platforms, one published all three, three published SOC 2, and one named no certification at all.

The BAA: what it must actually contain

HHS specifies that the agreement must contain the elements at 45 CFR 164.504(e). At minimum, per HHS, the BAA must:

• Describe the permitted and required uses and disclosures of PHI by the business associate
  
  

• Prohibit use or further disclosure other than as permitted by the agreement or required by law
  
  

• Require Privacy Rule compliance where the business associate carries out your obligations under the Rule

The Security Rule adds requirements where electronic PHI is involved: the business associate and its subcontractors must comply with applicable Security Rule requirements, and must report any security incident they become aware of, including breaches of unsecured PHI.

There is also an obligation that works in both directions. Where you know of a pattern of activity that constitutes a material breach of the BAA by the vendor, you are required to take reasonable steps to cure it, and if that fails, to terminate the agreement if feasible. A BAA is not a document you sign and file.

The scope trap

Read what the BAA actually covers. A BAA that covers "the platform" may not cover a specific AI feature, a beta capability, or a new transcription add-on you enable six months later. Ask explicitly: does this agreement cover every feature we will switch on, including the AI ones? Get it in writing before, not after.

The subcontractor chain, where this usually breaks

This is the part most buyers miss, and it is the part with an enforcement record behind it.

A modern voice AI system is assembled from parts. A call typically passes through a telephony carrier, a speech-to-text model, a large language model, and a text-to-speech voice, often from four different companies. Several of those process the actual content of a patient conversation.

HHS is explicit: a business associate must establish a BAA with its subcontractor before disclosing PHI to it, and all downstream subcontractors are themselves business associates, contractually responsible for complying with their own BAAs.

So the question is never "are you HIPAA compliant." It is:

Which subcontractors process our call audio or transcripts, and do you hold a signed BAA with each one?

A vendor that cannot answer within a minute has not done the work.

The $350,000 example

In March 2023, OCR settled with MedEvolve, Inc., a business associate providing practice management, revenue cycle management and analytics software. A server containing the PHI of 230,572 individuals had been left unsecured and accessible on the internet. Among the potential violations: MedEvolve had failed to enter into a business associate agreement with a subcontractor.

The settlement was $350,000, plus a corrective action plan requiring a thorough risk analysis, a risk management plan, and revised written policies distributed to its workforce.

Note what that case is not. It is not a hospital being fined for a hack. It is a software vendor being fined, in part, for a missing contract one layer down its own supply chain. That is structurally identical to an AI receptionist vendor that has not papered its model provider.

The conduit exception will not save you

Vendors occasionally argue that they merely transmit data. HHS's conduit exception is narrow by design: it covers entities that only provide transmission services, such as the postal service and its electronic equivalents, including temporary storage. HHS states plainly that entities accessing PHI on a regular or frequent basis to perform a service are not conduits.

A system that listens to a call, interprets it, and books an appointment is doing considerably more than transmitting.

What OCR actually enforces

Compliance conversations tend to float free of evidence, so here is the record.

Two things in that data matter for this decision.

First, the ranking of issues. OCR's most frequently alleged compliance issues, cumulatively and in order, are: impermissible uses and disclosures of PHI; lack of safeguards of PHI; lack of patient access; lack of administrative safeguards of ePHI; and use or disclosure of more than the minimum necessary.

The first two are precisely what an AI receptionist does on every call. It discloses information to whoever is on the line, and it either safeguards or fails to safeguard the recording and transcript afterwards.

Second, who gets cited. The most commonly cited covered entities are general hospitals, then private practices and physicians. This is not a large-enterprise problem.

The honest framing is that formal penalties are rare: 152 across two decades against 374,321 complaints. The common outcome is a corrective action plan, which is less expensive but still consumes months of practice time.

Five safeguards to verify before you sign

The Security Rule requires safeguards appropriate to your risk analysis. For an AI receptionist, five are load-bearing.

1. Encryption in transit and at rest. Call audio, transcripts and any extracted data. Ask specifically about recordings, which are often stored longer than anyone expects.
   
   

2. Audit controls. Can you get a log of who accessed what, and when? If a disclosure goes wrong, this is how you establish scope.
   
   

3. Access controls and minimum necessary. Does the system collect only what the call requires? An AI that captures a full clinical history to book a flu shot has exceeded minimum necessary.
   
   

4. Retention and deletion. How long are recordings and transcripts kept, where, and can you delete them on request? Get a number, not a policy link.
   
   

5. Model training. Will your patient data be used to train the vendor's models, or any subcontractor's? The answer must be no, and it must be in the contract, not just the FAQ.

What stays your responsibility

Signing a BAA transfers some risk. It does not transfer accountability for your own obligations.

• Your risk analysis. Adding an AI receptionist changes your threat surface, which means the analysis needs updating. MedEvolve's corrective action plan began with exactly this.
  
  

• Workforce training. Staff need to know what the AI does, when to take over, and what to do if a patient reports a wrong disclosure.
  
  

• Configuration. If you configure the system to read back more than it should, that is your decision, not the vendor's.
  
  

• Monitoring. Review failed and transferred calls. A vendor cannot tell you that your escalation rules are wrong for your patient population.
  
  

• Breach response. If something goes wrong, notification obligations run to you as the covered entity. Know in advance how quickly the vendor must tell you.

The questions to ask before signing

Put these in writing and keep the answers. Sully.ai publishes its own compliance position on the AI Receptionist page.

1. Will you sign a BAA covering every feature we enable, including AI capabilities added later?
   
   

2. Which subcontractors process call audio or transcripts, and do you hold signed BAAs with each?
   
   

3. Do you hold SOC 2 Type II, HITRUST or ISO 27001, and can we see the current report?
   
   

4. Is call audio encrypted in transit and at rest, and for how long is it retained?
   
   

5. Will our patient data ever be used to train models, yours or a subcontractor's?
   
   

6. Can we obtain audit logs of access to our data?
   
   

7. Within what timeframe will you notify us of a security incident?
   
   

8. On termination, can we export and then require deletion of all our data?

Frequently Asked Questions

Is an AI receptionist HIPAA compliant?

It can be, but not inherently and not because a website says so. Compliance depends on a signed BAA covering the services you use, BAAs with every subcontractor processing PHI, and implemented Security Rule safeguards. HHS does not certify products, so there is no list of approved vendors to check against; you have to verify it contractually.

Are any AI agents HIPAA compliant?

Several vendors will sign BAAs and hold independent security certifications, which is the practical bar. General-purpose consumer AI assistants will not sign a BAA and must not be used with PHI. The distinction is not the technology; it is whether the vendor has accepted business associate obligations in a contract.

Does HIPAA apply to a receptionist?

Yes. An employed receptionist is a workforce member subject to your policies, training and sanctions. An outsourced or AI receptionist is a business associate, which requires a BAA instead. Both routes are covered; the mechanism differs.

Which AI service is HIPAA compliant?

The wrong question, because no service is compliant in the abstract. The right question is which vendor will sign a BAA covering your use case and evidence their safeguards. Among AI receptionist platforms, published certifications vary widely: some hold ISO 27001, SOC 2 and HITRUST, others state nothing at all. Ask for the current audit report, not the badge.

What happens if the AI discloses PHI to the wrong person?

It is treated like any other impermissible disclosure. You assess whether it constitutes a breach of unsecured PHI, and notification obligations run to you as the covered entity. Your BAA should require the vendor to report the incident to you promptly, so agree the timeframe before you sign, because the statutory clock does not pause while you chase them.

Is a HIPAA certification for AI vendors a real thing?

No. There is no HIPAA certification issued or recognised by HHS. Vendors sometimes describe third-party assessments as "HIPAA certification," which is marketing language for an audit against a framework. HITRUST CSF is the closest healthcare-specific equivalent, and it is still not HIPAA compliance.

Do we need a BAA if the AI only takes messages and never accesses records?

Almost certainly yes. A message containing a patient's name and reason for calling is PHI. The conduit exception is limited to entities that only transmit information, and a system that interprets and records a call is not a conduit.

Sources

1. U.S. Department of Health & Human Services: Business Associates guidance. Business associate definition and examples including AI chatbots, BAA requirements at 45 CFR 164.504(e), subcontractor obligations, conduit exception, cure-or-terminate obligation.
   
   

2. HHS Office for Civil Rights: HIPAA Enforcement Highlights, enforcement results as of 31 October 2024. Complaint volumes, 152 settlements/penalties totalling $144,878,972, ranked compliance issues, cited entity types, 2,419 DOJ referrals.
   
   

3. HHS Office for Civil Rights: MedEvolve resolution agreement. $350,000 settlement, 230,572 individuals affected, failure to enter a BAA with a subcontractor, corrective action plan.
   
   

4. U.S. Department of Health & Human Services: Sample Business Associate Agreement Provisions.