HIPAA, TCPA and billing rules for AI voice agents in patient access: a call-level checklist
Short answer
A HIPAA-compliant AI voice agent verifies the caller's identity and authority before disclosing protected health information (PHI), shares only what the call needs, keeps voicemails minimal, and runs under a business associate agreement with every vendor handling that PHI, even ones that store nothing. Outbound AI-voice calls also need TCPA consent or an exemption, and billing calls carry federal and state rules of their own.
On this page
- What should every patient-access call be checked for?
- What does HIPAA require before the agent discloses PHI?
- Can the agent discuss a bill with a spouse or adult child?
- What can go on a voicemail, and what if the patient asks you to call elsewhere?
- Who needs a business associate agreement, and how long should transcripts live?
- Which TCPA rules apply to patient calls made with an AI voice?
- What do state medical debt laws change on a billing call?
- What does a graded patient-access call look like?
- Questions
- Sources
Your AI voice agent books visits, quotes balances and takes payments on far more calls than your team will ever hear. That's where the misses hide: a balance read to a spouse, a procedure named on a voicemail, a patient's "please stop calling this number" confirmed and never saved. HIPAA decides who may hear what on those calls. The Telephone Consumer Protection Act (TCPA) decides whether an AI voice may place them, and billing calls add a few federal and state rules of their own. This checklist covers all three, for the patient-access and revenue-cycle leads who run these agents, their compliance teams and the engineers who build them. Federal rules usually set a call's outcome, not its words, so each item says which part is law and which is your standard operating procedure (SOP) choosing how to comply.
What should every patient-access call be checked for?
Thirteen things, in the order a call meets them: ten that federal rules require (some only of certain providers), one that HHS guidance recommends and two your SOP chooses. Each is worded as the evidence a reviewer looks for.
- A BAA signed with the voice platform, which signs with its speech, model and voice vendors HIPAA 164.502(e)
- Lookups return only the fields the call uses HIPAA 164.502(b)
- Consent on file, or an exemption's conditions met, for each outbound call TCPA 64.1200(a)
- Registered business name stated in the first turn TCPA 64.1200(b)(1)
- Identity and authority verified, the match logged before the first account detail HIPAA 164.514(h)
- Family and friends hear only what relates to their role: the patient agrees, or they're a named contact on file HIPAA 164.510(b)
- Self-pay or uninsured patient told a good faith estimate is available, when booking or when cost comes up No Surprises Act
- Free qualified interpreter offered when needed, relay calls answered (providers taking federal funds) Section 1557
- A request to be reached another way saved by a tool call that returned success HIPAA 164.522(b)
- Financial assistance mentioned before the first payment ask Your SOP
- Balance quoted matches the billing lookup Your SOP
- Callback number stated before the call ends TCPA 64.1200(b)(2)
- Voicemail limited to a name, a number and a callback request HHS FAQ 198
The No Surprises Act's estimate notice must be given orally, in the patient's language (45 CFR 149.610(b)(1)(iii)). Section 1557 is the Affordable Care Act's nondiscrimination rule. Its interpreter and relay rules (45 CFR 92.201 and 92.202, applying 28 CFR 35.161) don't say whether an AI agent speaking Spanish counts. So a safe SOP rule transfers to an interpreter or bilingual staff before any financial assistance or estimate notice. Checks that span calls need the patient record and dial log; see auditing AI voice agent calls against your SOP.
What does HIPAA require before the agent discloses PHI?
Two things: identity and authority verified when either isn't known, and no more PHI moving than the call needs. Protected health information (PHI) is individually identifiable health information held by a covered entity or its business associate, and under 45 CFR 160.103 it includes information about payment for a person's care. A patient's balance is PHI. So is the fact that she has an appointment.
- Ask by name
Ask for the patient by name and give no reason for the call yet
- Verify
A tool checks the identifiers your SOP sets, such as date of birth and ZIP code
- Check authority
Anyone else on the line: her agreement on this call, or a named contact on file
- Disclose
Only after the match, and only what this call needs
45 CFR 164.514(h) requires a covered entity to verify the identity and authority of a person requesting PHI when either isn't already known. It names no method and no number of identifiers; two is an SOP choice. What it fixes is the order, so a grader checks timestamps, not the agent's word. Giving no reason for the call until she's verified best meets the duty in 164.530(c) to limit incidental disclosures.
The minimum necessary standard in 164.502(b) doesn't limit what a verified patient hears about herself. It does cover uses, disclosures and requests, including what reaches the voice vendor. A scheduling agent whose lookup returns diagnosis codes and claim history puts all of it in the transcript, and everywhere the transcript goes.
Can the agent discuss a bill with a spouse or adult child?
Yes, within limits, and HIPAA allows more than many SOPs do. 45 CFR 164.510(b) lets a provider share PHI with family, close friends or anyone the patient identifies. What it shares is limited to what's relevant to that person's involvement in her care or its payment. If she's on the line and able to decide, the test is her agreement or lack of objection. If she isn't, it's the provider's professional judgment about her best interest. HHS's guide for providers gives the billing case: a hospital may discuss a patient's bill with her adult son.
An AI agent can't supply professional judgment, and these disclosures are exempt from the verification rule. So a defensible SOP draws the agent's rule narrower: discuss the account with someone else only when the patient agrees on the call or has named that person as an authorized contact. Otherwise, take a message or transfer to staff.
Minors need their own rule. A parent is usually a minor's personal representative, treated as the patient (164.502(g)). The exception is care the minor could lawfully consent to alone: there, state law decides what the parent may learn, or the provider's judgment where state law is silent (164.502(g)(3)). An itemized balance can reveal exactly that care, so for a patient under 18, give no itemized detail and transfer to staff unless the record clears the parent.
What can go on a voicemail, and what if the patient asks you to call elsewhere?
Little more than the provider's name and number and a request to call back, and a reasonable request to be reached another way must be honored. HHS FAQ 198 covers both. Voicemail isn't prohibited, so the rest is SOP: no diagnosis, procedure, condition-revealing department or balance. Test beep detection too, or the agent reads its live script, balance included, to the mailbox. Collection agencies follow Regulation F's stricter limited-content message; see FDCPA and Regulation F rules for AI collection calls.
Under 45 CFR 164.522(b), a provider must accommodate reasonable requests to be contacted by other means or at other locations, and may not require an explanation. It may require the request in writing and, when appropriate, ask how payment will be handled. So the agent saves "don't call this number" with a tool call that succeeds, or explains how to submit it in writing. Only the dial log proves later calls respected it.
Who needs a business associate agreement, and how long should transcripts live?
Every vendor that handles the calls' PHI for you needs a BAA. Transcripts should live as long as state law and your own records policy require, because HIPAA sets no retention period for them.
A business associate is a person or company that creates, receives, maintains or transmits PHI on a covered entity's behalf, including subcontractors that do the same (45 CFR 160.103). The provider signs with the platform, and the platform with its subprocessors (164.502(e)(1)); ask to see those agreements. Loops, for example, makes a BAA available on request, alongside its NDA and DPA (security and data).
| Often assumed | What the rules say |
|---|---|
| A vendor that keeps nothing needs no BAA | Receiving PHI to process it is enough; HHS's cloud computing guidance limits the conduit exception to transmission |
| Only the voice platform signs | Its speech, language model and voice providers sign too, and so does whoever later receives transcripts, such as QA |
| HIPAA says keep recordings six years | Six years is for HIPAA documentation such as policies (164.316(b)(2), 164.530(j)); state law generally governs medical records (HHS FAQ 580) |
| A call recording isn't the patient's to see | A kept billing-call recording can be in her designated record set, the medical and billing records kept about her (164.501), open to her right of access while it exists (164.524) |
Platforms differ. Retell offers per-agent retention from one day to two years. Vapi's HIPAA mode still stores recordings, transcripts and logs in its private HIPAA-compliant storage unless you configure your own. With zero retention nothing is left to backfill, so an auditor must receive each call as it ends, under its own BAA.
Which TCPA rules apply to patient calls made with an AI voice?
The FCC's February 2024 ruling (FCC 24-17) treats AI-generated voices as "artificial" voices under the TCPA. So outbound AI calls follow 47 CFR 64.1200, including its rules to state the business name at the start and give a callback number ((b)(1), (2); FCC 24-17, paragraph 9).
| Call | Cell phone | Residential line |
|---|---|---|
| Listed care messages: reminders, pre-op instructions, lab results | No consent if free to the patient, to the number she gave, provider named at the start, generally a minute or less, one a day and three a week, opt-out offered: (a)(9)(iv) | No consent for a HIPAA "health care" message, one a day and three a week: (a)(3)(v); automated opt-out within two seconds of identification: (b)(3) |
| Billing, balance and collection calls | Prior express consent; (a)(9)(iv) excludes billing and debt-collection content | No consent for up to three non-telemarketing calls in 30 days: (a)(3)(iii); automated opt-out within two seconds of identification: (b)(3) |
Consent for billing calls usually rests on the number the patient gave with the account, a rule with this history:
- Jan 2008
FCC 07-232, the ACA International ruling (paragraphs 9 and 10): a number given in the transaction that created a debt is consent to calls about that debt, by the creditor or a collector calling for it
- 2014
Mais v. Gulf Coast Collection Bureau: the Eleventh Circuit applies that to a number on hospital admission forms
- 2015
FCC 15-72, paragraph 141: narrower than often quoted, because footnote 473 ties its "healthcare calls" to HIPAA's definition of health care, which describes care, not payment
- 2025
McLaughlin Chiropractic v. McKesson: district courts now read the statute for themselves, so treat the FCC's rulings as persuasive, not settled
A patient can revoke by any reasonable means, including on the call, honored within ten business days (64.1200(a)(10)). More in TCPA consent for AI voice calls after the FCC's 2024 ruling.
What do state medical debt laws change on a billing call?
They change what the agent may say about credit reporting and how it sizes a plan, above a federal floor for tax-exempt hospitals. That floor is the 501(r) rule. At least 30 days before its first extraordinary collection action (credit reporting or selling the debt, for example), a hospital must send a written notice and a plain language summary of its financial assistance policy. It must also make a reasonable effort to tell the patient about that policy orally. Most such actions must wait 120 days after the first post-discharge bill (26 CFR 1.501(r)-6(c)(3), (c)(4)). An AI billing call can supply the oral part only.
Colorado bars consumer reporting agencies from reporting adverse medical debt information, with narrow exceptions (C.R.S. 5-18-109(1)(f)). It also bars a collection agency from falsely saying a medical debt will appear on a report or affect a credit score (C.R.S. 5-16-107(1)(r)). Both came from HB23-1126, and the statute repeals both effective July 1, 2028. New York's S4907A (2023) bars providers from reporting medical debt to credit bureaus. Colorado also caps payment plans for patients who qualify for Hospital Discounted Care, so an agent that sizes a plan from the balance alone can break the law:
4%
of monthly household income: the most a plan may take on the hospital's bill
C.R.S. 25.5-3-503(1)(b), (c)
2%
on each licensed professional's separate bill, or 6% on one combined bill
C.R.S. 25.5-3-503(1)(b), (c)
36
months of payments, after which the bill is paid in full
C.R.S. 25.5-3-503(1)(b), (c)
The reporting bans carry a question mark:
- Jul 2025
A federal court in Texas vacates the CFPB's medical debt rule and writes that a state ban on reports with coded medical information would be preempted
- Oct 28, 2025
The CFPB publishes an interpretive rule reading the Fair Credit Reporting Act to preempt state laws on what reports contain and what furnishers report, medical debt included, while stating it has no binding effect
- Nov 2025
ACA International sues to block Colorado's HB23-1126 as preempted
- Sep 2026
Still undecided: Colorado's July 8 motion to dismiss has no ruling on the docket
Source: Cornerstone Credit Union League v. CFPB, 90 FR 48710, ACA International v. Fulford (D. Colo.)
The SOP rule that holds up either way: the agent never raises credit reporting on a medical bill.
What does a graded patient-access call look like?
Like this, with each verdict tied to a timestamp or a tool result.
Agent: Hi, this is Ava, an automated assistant calling for Birchwood Community Hospital, on a recorded line. May I speak with Maria Chen?
Patient: Speaking.
1.1 met registered name, automated assistant and recording stated by 00:05; no reason given before verification
Agent: Thanks, Maria. To protect your privacy, what are your date of birth and ZIP code?
Patient: October 18, 1983, and 60614.
1.2 met verify_patient returned a match at 00:19, before any account detail
Agent: There's a balance of $412.50 from your visit on August 12. Would you like to pay that today with the card on file?
2.1 met $412.50 matches get_balance at 00:21
2.3 missed payment requested at 00:24 with no mention of financial assistance
Patient: Not today. And please stop calling this number, my husband answers it. Use my cell, three one two, five five five, zero one [inaudible].
3.2 needs review new number partly inaudible at 00:41; a person should confirm what was saved
Agent: Of course. I've updated how we'll contact you.
3.3 missed log_contact_preference returned an error at 00:44; the agent confirmed the change anyway
Agent: If you have questions, our billing office is at 312-555-0148.
1.3 met callback number stated at 00:49, before the call ended
3.4 not checked no calls to the old number after ten business days; needs the dial log
A listen-through would pass most of this call. Rule 3.3 sounds compliant, but the tool record shows the preference was never saved, so the next call goes to the number the patient refused. Rule 2.3, an SOP rule, also carries the 501(r) oral notice at a tax-exempt hospital. And "stop calling this number" revokes TCPA consent, so rule 3.4 stays not checked until the dial log arrives.
This is general information, not legal advice; confirm with counsel how these rules apply in your states.
Turn the checklists into numbered SOP rules with named evidence, mark which need the patient record or dial log, and grade a month of calls. Loops grades every call against rules your compliance lead approves, quotes the line behind each verdict and checks that tool calls succeeded. A free 30-day audit grades your calls once the rules are approved; if your platform keeps no transcripts, it grades new calls from the day you connect.
Questions
Do patients have to consent before an AI agent handles their billing calls?
Not under HIPAA. The Privacy Rule lets a covered entity use and disclose PHI for its own treatment, payment and health care operations without the patient's authorization (45 CFR 164.506(c)), and billing and collection are payment activities. You do need a business associate agreement with each vendor that handles the PHI, and TCPA consent or an exemption for outbound calls made with an AI voice.
Do we need consent to record patient calls and send them to a QA vendor?
HIPAA has no separate recording rule, but state recording law does. California requires every party's consent to record a confidential call (Penal Code 632), and in 2025 a federal court let a privacy claim proceed against a vendor whose AI transcribed and analyzed other companies' support calls (Ambriz v. Google, N.D. Cal.). Announce the recording at the start, and have counsel confirm the disclosure covers every vendor that receives the audio, a QA auditor included.
Does an AI voice agent have to tell patients it isn't human?
HIPAA doesn't require it. California does when a health facility, clinic or physician's office uses generative AI for communications about clinical information, unless a licensed provider reviewed them: say so at the start and end of the call and explain how to reach a person (Cal. Health and Safety Code 1339.75). Scheduling and billing are excluded. Utah requires people in licensed occupations to disclose it at the start of a high-risk spoken interaction, which includes collecting health data (Utah Code 13-77-103).
What should the agent do when a caller fails identity verification?
Disclose nothing about the account, including whether one exists, and offer a callback to the number on file or a way to reach staff. HIPAA requires verification when identity or authority isn't known (45 CFR 164.514(h)) but doesn't script the failure path, so your SOP should: how many attempts, what the agent may say, and that the failed attempt is logged for review.
Is a collection agency calling about medical bills covered by HIPAA and the FDCPA?
Usually both. Collection is a payment activity under the Privacy Rule (45 CFR 164.501), so an agency collecting a provider's bills generally acts as its business associate and needs a BAA. Its calls generally fall under the FDCPA too, though a vendor working accounts before default may not (15 U.S.C. 1692a(6)(F)(iii)). A provider collecting its own bills is outside the FDCPA but may be inside state acts such as California's Rosenthal Act (Civ. Code 1788.2(c)).
Sources
- 45 CFR 164.514, Other requirements relating to uses and disclosures of protected health information (verification, minimum necessary), eCFR, National Archives
- 45 CFR 164.502, Uses and disclosures of protected health information: general rules (minimum necessary, business associates, personal representatives), eCFR, National Archives
- 45 CFR 164.522, Rights to request privacy protection for protected health information, eCFR, National Archives
- 45 CFR 149.610, Requirements for provision of good faith estimates of expected charges for uninsured (or self-pay) individuals, eCFR, National Archives
- 45 CFR 92.201, Meaningful access for individuals with limited English proficiency (Section 1557), eCFR, National Archives
- 47 CFR 64.1200, Delivery restrictions (TCPA rules), eCFR, National Archives
- Request of ACA International for Clarification and Declaratory Ruling (FCC 07-232), released January 4, 2008, Federal Communications Commission
- Guidance on HIPAA and Cloud Computing, U.S. Department of Health and Human Services, Office for Civil Rights
- 26 CFR 1.501(r)-6, Billing and collection (financial assistance notification before extraordinary collection actions), eCFR, National Archives
- Fair Credit Reporting Act; Preemption of State Laws, interpretive rule, 90 FR 48710 (October 28, 2025), Consumer Financial Protection Bureau, via GovInfo