For healthcare ops, CX, and compliance leaders

HIPAA-compliant is not a product badge. It's a BAA, an audit, and PHI controls.

No AI customer service vendor is HIPAA-certified, because no certification regime exists. The buyer's real job is to verify three things: who signs a Business Associate Agreement, what was independently audited and by whom, and where protected health information is processed and retained. This guide defines those criteria, gives you a checklist you can take into any vendor call, and compares the platforms honestly. As of June 2026.

By Amit RG, Founder, Richpanel Published 2026-06-04 Updated 2026-06-04 ~11 min read
View as Markdown →
AR
Amit RG is the founder of Richpanel, an AI-first customer service platform serving 2,000+ brands across regulated and unregulated verticals. Richpanel is HIPAA-audited (Scrut Automation, December 2025) and operates as a Business Associate. He has been hands-on in the compliance, audit, and data-handling decisions described here. On X: @realamitrg.
The short answer

What "HIPAA-compliant AI customer service" actually requires

A platform is usable for protected health information only when three things are true at once: the vendor signs a Business Associate Agreement (BAA) with you, an independent third-party auditor has assessed its controls (named auditor, stated date, stated scope, against a published framework), and the configuration keeps PHI access-controlled, logged, and retained no longer than needed. No vendor is "HIPAA-certified," because no US certification regime exists. Evaluate three to five platforms on BAA terms, named-audit evidence, PHI data residency, and whether the AI resolves real requests under access controls or merely answers questions. Below is the operational checklist and an honest platform comparison, as of June 2026.

This guide is informational and not legal advice. HIPAA compliance is a shared responsibility between you (the covered entity) and your vendor (the business associate); confirm the specifics with your privacy officer and counsel.

Why the badge is misleading. "HIPAA-compliant" stamped on a pricing page is a marketing claim, not a verified status. HIPAA is a US law enforced by the HHS Office for Civil Rights, which audits and fines but issues no certificate of compliance to any product. So the buyer cannot outsource the judgment to a badge. You have to read the BAA, name the auditor, and locate the PHI yourself.

The stakes are concrete. Under the HIPAA Breach Notification Rule, an unauthorized disclosure of PHI by a business associate is reportable, and civil penalties run into the tens of thousands of dollars per violation with annual caps in the millions, before the reputational cost. A chatbot that logs a member's diagnosis in plaintext to a sub-processor you never vetted is exactly the kind of disclosure the rule exists to catch. The evaluation work below is what stands between you and that outcome.

Get the vocabulary right first

Certified, audited, attested. Only two of these are real.

Most confusion in a HIPAA vendor evaluation comes from three words used as if they were interchangeable. They are not. Getting them straight is the single highest-leverage thing you can do before a demo, because it tells you which vendor claims to discount on sight.

HIPAA-certified does not exist. There is no US government body, and no official accreditation scheme, that certifies a product as HIPAA-compliant. The HHS Office for Civil Rights enforces the law; it does not hand out certificates. So when a vendor's site says "HIPAA-certified," the correct follow-up is one question: "Who issued the certificate?" The honest answer is that nobody can. Treat the word as a yellow flag, not because the vendor is necessarily insecure, but because someone in their marketing chose a term that overstates what is verifiable.

HIPAA-audited is real and is what you want. An independent third-party auditor assesses the vendor's controls against a published framework (for HIPAA, that framework is typically NIST SP 800-66, the HHS-referenced implementation guide for the Security Rule), on a stated date, with a stated scope, and produces findings. "Audited by Scrut Automation against NIST SP 800-66 Rev 2 in December 2025, zero non-compliant findings" is a checkable claim with a name, a framework, and a date attached. "We take security seriously" is not.

Self-attested is the floor, and it is thin. The vendor asserts its own compliance with no outside check. Self-attestation is not worthless, a vendor that has mapped its controls to HIPAA at all is ahead of one that hasn't, but it is the vendor grading its own homework. For PHI, you want the independent audit on top of the attestation, and you want the BAA that makes the obligation contractual.

The BAA is the legal spine. The independent audit is the evidence. The configuration is where PHI actually lives or leaks. A real evaluation checks all three, in that order, before it looks at a single feature.

Defined before any comparison

Seven criteria to score every vendor on.

Define the criteria before you look at any feature, so the comparison can't be reverse-engineered to flatter a favorite. These seven are ordered the way a risk-first buyer should weight them: trust evidence first, then capability.

01

BAA availability and tier.

Will the vendor sign a Business Associate Agreement with you, and on which plan? A vendor that processes PHI without a signed BAA is a HIPAA violation waiting to happen, on both sides.

Some vendors offer the BAA only on enterprise plans, or only after a security review. Some offer it freely. Some do not offer one at all and quietly route healthcare prospects elsewhere. Get the answer, the plan tier, and the turnaround time in writing before you build a business case on the platform.

How to test this: "Will you sign a BAA for my deployment, on which plan, and can I see the template?" A vendor that hedges or upsells you to a tier you don't need is telling you something.
02

Independent audit, with the auditor named.

Was the vendor's HIPAA control set assessed by a named third party, against a published framework, on a stated date, with a stated scope, or is it self-attested?

This is where "audited" earns its keep over "certified" or "compliant." You want a name (the audit firm), a framework (NIST SP 800-66 is the HHS-referenced one for the Security Rule), a date, and a scope. A report you can request under NDA is the gold standard. A logo with no document behind it is not.

How to test this: "Who audited you, against what framework, when, and can I get the report under NDA?" Four concrete answers, or it's self-attestation in a nicer font.
03

PHI data residency and retention.

Where is protected health information processed and stored, for how long, and is the retention configurable? This is the question that separates real compliance from a marketing claim.

You want the cloud and region, the retention period and whether you control it, whether PHI is redacted or minimized in logs, and a current sub-processor list. The minimum-necessary principle in HIPAA expects you to retain and expose PHI only as far as the job requires. A vendor that can't tell you where the data sits has not thought about this.

How to test this: "Where does PHI live, who are your sub-processors, what's the default retention, and can I shorten it?" If the answer is vague, the data handling is too.
04

Action depth on PHI workflows, under access controls.

Can the AI take real actions (look up a record, update an account, process a request) under role-based access controls, or can it only answer questions?

Most "HIPAA chatbots" only answer. They were never wired into a system of record, so they deflect rather than resolve. A platform that takes real actions has to do it under access controls and log every one, which is exactly what a HIPAA access-controls and audit-logging requirement wants. Action depth is therefore both a capability question and a compliance question.

How to test this: "Show me the AI completing a workflow that touches a member record, and show me the access control and the log entry it generated."
05

Resolution versus deflection.

Does the platform report what it actually resolved end to end, or does it count a customer giving up as a "containment"? In a regulated context, an unresolved member is a compliance and a care risk, not just a CSAT dip.

Ask how the vendor defines a resolved conversation and how it reports the difference from deflection. A bot tuned to never escalate looks great in a deck and fails the member who needed a human. The honest platforms distinguish the two and show you both numbers.

How to test this: "What's your definition of a resolved conversation, and how do you report deflection separately?"
06

Human-in-the-loop and QA review.

When the AI is uncertain or the intent is sensitive, does a human pick it up with full context? Is every AI conversation reviewed for quality, or only a sample?

In a PHI context the escalation logic and the QA layer are part of the safety case, not nice-to-haves. You want configurable escalation triggers (sensitive intent, low confidence, policy conflict) and a QA review layer with visible reasoning. Sampled QA leaves the long tail unreviewed; full review is the stronger posture.

How to test this: "Walk me through escalation on a sensitive intent, and show me whether QA reviews every conversation or a sample."
07

Audit logging and access controls.

Is every access to PHI logged, attributable, and exportable, and is access role-based? The audit trail is what you hand a regulator or a security reviewer when they ask "who saw what."

You want per-record access logs that name the human or agent, the action, the timestamp, and the record, exportable on request. Role-based access controls keep the agent and the AI scoped to the minimum necessary. This row is often the quiet decider in a committee review.

How to test this: "Show me an access log entry for a PHI record and the export format. Show me how roles scope what an agent can see."
The honest comparison

How the platforms compare, as of June 2026.

Scored on the seven criteria above. No platform wins every column, and each row names where the vendor is the better call. Competitor facts are drawn from each vendor's public documentation; pricing and compliance posture move, so re-verify before you sign.

Platform Signs a BAA Independent audit Resolves vs answers Where it wins
Richpanel Yes (Business Associate; AWS BAA in place; confirm customer BAA in eval) HIPAA-audited (Scrut, NIST SP 800-66 Rev 2, Dec 2025, zero non-compliant). SOC 2 Type II and GDPR audited Resolves end to end and takes real actions; QA AI reviews every conversation Compliance and resolution in one platform, no second tool, no double-meter
Zendesk Yes, on qualifying plans with the Advanced Data Privacy and Protection add-on Long-established third-party audit program Resolves with Advanced AI; autonomous AI bundled, governance mature Broadest enterprise governance and a long-running BAA program for multi-department orgs
Zoho Desk Yes, BAA offered for healthcare customers Independent audits across the Zoho suite Answers and routes; AI assist is improving but lighter on real actions Lowest entry price, HIPAA inside a broad low-cost suite (the current default snippet pick)
Comm100 Yes, marketed for regulated and government chat Independent audit program for security controls Live chat plus bot; resolution depth varies by integration Native, fully self-owned live chat for regulated and government deployments
Freshdesk Yes, on higher plans Independent audits across Freshworks Answers with Freddy; AI Agent billed per session, stops when sessions exhaust App-marketplace breadth and an IT-style help desk under one roof
Niche compliant-LLM tools (e.g. BastionGPT, Hathr AI) Yes, BAA is the core offer Varies by vendor; verify the named audit Internal compliant chat, not a customer-facing helpdesk A private, HIPAA-aware LLM for staff drafting and internal use

Each platform name links to the vendor's primary product page. Cells reflect each vendor's public documentation as of June 2026. If your reading of any cell is materially different from current product reality, email amit@richpanel.com and we'll update. The goal is accuracy, not gratuitous negativity.

The honest read: every serious platform on this list will sign a BAA and can point to an independent audit, so the BAA and the audit are table stakes, not a differentiator, among real contenders. The split is along two axes. First, depth of action: the niche compliant-LLM tools answer but cannot resolve a customer request, while the helpdesks and Richpanel can. Second, whether compliance and resolution live in one tool or two: Richpanel is the AI-native cut that handles both in a single platform with QA review on every conversation, and it is not the right pick if you need native voice as your primary regulated channel, where you'd lean on Comm100's owned chat or a voice-led stack instead.

What resolution-plus-review looks like in production

Aeons, a premium UK supplements brand founded by Dr. Sarah Brewer in a health-adjacent category, ran the AI on 60% of every inbound message at 4.43 / 5 CSAT, higher than its own human team's 4.25, with QA review on the work.

Aeons is wellness, not a HIPAA-covered entity, so this is an analog, not a healthcare claim. What it shows is the operating posture a regulated team should demand: the AI resolving real volume autonomously while a QA layer reviews the work, rather than a deflection widget that answers and disappears. Read the full case study →

Per-option analysis

Where each platform is the right call, Richpanel included and not.

The comparison table is a starting point, not a verdict. Here is the honest read on when each option is the better choice, including the situations where Richpanel is not.

The claim worth holding onto is narrow and verifiable: among platforms that resolve customer requests, Richpanel is HIPAA-audited, operates as a Business Associate, and reviews every conversation rather than a sample. That is a strong position for a healthcare support team that wants real resolution. It is not the answer to every regulated buying scenario, and the section above says exactly which ones it isn't.

For your vendor evaluation

Eight questions to ask every HIPAA AI customer service vendor.

Take these into your RFP, your demo calls, and your security review. Trust evidence comes first; a vendor who can't answer the first three concretely should be disqualified before you ever look at the demo.

1. Will you sign a BAA, on which plan, and can I see the template?

If the answer is no, the vendor cannot legally process PHI for you. If it's "only on enterprise," price that in before you build the case.

2. Who audited you, against what framework, when, and can I get the report?

A name, a framework (NIST SP 800-66 for the Security Rule), a date, a scope. "HIPAA-certified" is a non-answer; ask who issued the certificate.

3. Where does PHI live, who are your sub-processors, and what's the default retention?

Cloud, region, retention period, whether you can shorten it, and whether PHI is redacted in logs. Vagueness here is a red flag.

4. Can the AI take real actions under access controls, or only answer?

Ask to see a workflow touching a member record, the access control on it, and the log entry it generated. Answer-only tools deflect; they don't resolve.

5. How do you define a resolved conversation, and how do you report deflection separately?

If the vendor conflates resolution with a customer giving up, the reporting is hiding the failure rate.

6. Is every AI conversation reviewed for quality, or only a sample?

Sampled QA leaves the long tail unreviewed. In a PHI context, full review with visible reasoning is the stronger posture.

7. Show me an access log entry for a PHI record and the export format.

Per-record, attributable, timestamped, exportable. This is what you hand a regulator or a security reviewer who asks "who saw what."

8. Connect me with a customer in a regulated vertical at my scale.

A reference running PHI workflows in production is the most reliable signal there is. More reliable than a badge, more reliable than demo polish.

Richpanel answers every one of these in writing. The starting points: HIPAA-audited by Scrut Automation against NIST SP 800-66 Rev 2 (December 2025, zero non-compliant findings), Business Associate with an AWS BAA in place, AI that resolves under access controls with QA review on every conversation, and a 50% automation in 30 days guarantee with your money back if it misses. The deeper security artifacts, SOC 2 Type II, the HIPAA and GDPR audit reports, are available on request via the security page.

Frequently asked

HIPAA and AI customer service, in plain English.

What makes AI customer service HIPAA-compliant?

Three things together, not any one alone: a signed Business Associate Agreement (BAA) between you and the vendor, an independent third-party audit of the controls (with a named auditor, a date, and a defined scope), and the configuration that keeps PHI access-controlled, logged, and retained only as long as needed. A vendor that markets HIPAA but will not sign a BAA cannot legally process PHI for you. A vendor that self-attests but has no independent audit has not been checked by anyone but itself.

Is Richpanel HIPAA-compliant, and does it sign a BAA?

Richpanel is HIPAA-audited. Scrut Automation completed a HIPAA audit in December 2025 against NIST SP 800-66 Rev 2 with zero non-compliant findings; Richpanel operates as a Business Associate and has an AWS BAA in place. On the customer BAA itself, talk to us during the evaluation so we can confirm the terms for your specific deployment rather than over-claim here. We do not claim to be HIPAA-certified, because no US HIPAA certification regime exists for any vendor.

What is the difference between HIPAA-certified and HIPAA-audited?

There is no official US body that certifies a product as HIPAA-compliant, so "HIPAA-certified" is not a real status. The HHS Office for Civil Rights enforces HIPAA but issues no certification. What a credible vendor can show is an independent audit: a named third-party auditor assessing controls against a published framework such as NIST SP 800-66, on a stated date, with a stated scope and findings. If a vendor says "HIPAA-certified," ask who issued the certificate. The honest answer is that nobody can.

Where does the AI customer service platform store PHI, and for how long?

This is the question that separates marketing from real compliance, so ask it directly and get it in writing. You want the data residency (which cloud, which region), the retention period and whether it is configurable, whether PHI is redacted or minimized in logs, and which sub-processors touch the data. Richpanel runs on AWS under an AWS BAA, logs are access-controlled and exportable, and HIPAA workspaces are tenant-isolated. Always confirm the specifics for your deployment in the BAA and the sub-processor list.

Can a HIPAA-compliant AI take real actions, or only answer questions?

Most HIPAA-marketed chatbots only answer questions; they cannot look up an order, process a refund, or update an account because they were never wired into your systems of record. A resolving platform takes real actions under access controls and logs every one. The compliance value of action-taking is that the audit trail captures who (or which agent) did what, when, against which record, which is exactly what an access-controls and audit-logging requirement expects.

Make the call

The decision tree, not a verdict.

Work top to bottom. The first branch that matches your reality is your answer. There is no single best HIPAA AI customer service platform; there is the right one for your channel mix, your committee, and your appetite for resolution versus deflection.

Choose by your dominant constraint

The vendor won't sign a BAA, or can't name its auditor
Stop here. This is disqualifying for PHI regardless of how good the demo is. Do not proceed to a feature comparison with a vendor that fails the first two criteria.
Your primary regulated channel is voice, or fully self-owned live chat
Lean toward Comm100 for owned chat in government and regulated deployments, or a voice-led stack. Richpanel integrates with Aircall, Dialpad, and JustCall rather than hosting voice, so a voice-first single-pane requirement is not its strength.
You need the lowest entry price and mostly answering, not action-taking
Zoho Desk gives you HIPAA coverage inside a broad, inexpensive suite. Accept that its AI leans toward answering and routing rather than resolving end to end.
A security and procurement committee will only sign the most-established enterprise brand
Zendesk is the lowest-friction approval. You trade some cost (add-on stacking, per-resolution AI) for maximum maturity perception.
What you actually need is a private compliant LLM for internal staff use
Look at BastionGPT, Hathr AI, and peers. These are not customer-facing helpdesks and shouldn't be compared as if they were.
You want compliance and real resolution in one platform, charged once
This is the Richpanel case: HIPAA-audited Business Associate, AI that resolves under access controls, QA review on every conversation, no per-resolution double-meter, and a 50% automation in 30 days guarantee with your money back if it misses. Validate it the way this guide says to: BAA, named audit, PHI residency, then a live workflow on a member record.

Whichever branch you land on, run the eight-question checklist above against the finalist, and get the BAA and the audit scope in writing before you sign. A demo proves the AI is fluent. The BAA, the named audit, and the PHI residency answer prove it is safe to put protected health information through.

Sources & references

Where the claims come from.

The regulatory definitions in this guide trace to the public sources below. Competitor compliance posture is drawn from each vendor's own documentation as of June 2026; Richpanel's audit facts are from the reports named in the text.

  1. HHS, HIPAA for Professionals (Office for Civil Rights). The primary US source on the Privacy, Security, and Breach Notification Rules, business associate obligations, and enforcement. Cited for the points that OCR enforces HIPAA, that no certification is issued, and that breaches by a business associate are reportable. hhs.gov/hipaa/for-professionals
  2. NIST Special Publication 800-66 Rev 2 (2024). “Implementing the HIPAA Security Rule: A Cybersecurity Resource Guide.” The HHS-referenced framework an independent auditor assesses controls against. Cited as the framework named in Richpanel's December 2025 HIPAA audit. csrc.nist.gov/pubs/sp/800/66/r2/final
  3. HHS, Business Associate Contracts guidance. The OCR sample Business Associate Agreement provisions and the rule that a business associate may not create, receive, maintain, or transmit PHI without a BAA. Cited for criterion 1 (BAA availability). hhs.gov, sample BAA provisions
  4. Richpanel third-party audit reports (2025). HIPAA audited by Scrut Automation against NIST SP 800-66 Rev 2 (December 2025, zero non-compliant findings); SOC 2 Type II by Percilchofe CPA LLC (May–October 2025, zero exceptions); GDPR audited by Scrut Automation (December 2025). Reports available under NDA on request via the security page or amit@richpanel.com.

v1.0 (2026-06-04): initial publication. This guide is informational and not legal advice; HIPAA compliance is a shared responsibility between the covered entity and the business associate.

Keep reading

Go deeper on the trust questions.

Put your BAA and audit questions to us directly.

30 minutes. We confirm the BAA path for your deployment, walk through the HIPAA audit scope, show the AI resolving a real workflow under access controls, and hand you the audit reports under NDA. No slide deck.

Book my 30-min demo →