AI Patient Collections · 2026 Compliance

What an AI voice agent may and may not do in patient collections

Short answer: an AI voice can legally place patient-balance calls in 2026, but only inside a narrow lane. The FCC now treats AI-generated voices as "artificial" voices under the TCPA, so every call needs prior express consent captured before dialing. Layer FDCPA and Regulation F on top and the rules become concrete: consented number, 8am to 9pm local, no more than the Reg F cadence, instant honoring of opt-outs. The matrix below is the whole rulebook on one screen.

Permitted with a documented basis Prohibited or high-risk

The four instruments that govern the call

Four rulebooks, one phone call

A single AI collections call to a patient's mobile sits at the intersection of four live 2026 authorities. Miss any one and the call is exposed, no matter how clean the other three are.

TCPA

47 U.S.C. §227 · 47 CFR 64.1200

Prior express consent required to call a wireless number with an artificial or prerecorded voice. Prior express written consent if the call is marketing.

FCC AI-Voice Ruling

Declaratory Ruling, Feb 8 2024

AI-generated voices are "artificial" voices under the TCPA. An AI agent inherits the full prerecorded-voice consent burden.

FDCPA

15 U.S.C. §1692c / e / d

No harassment, no false statements, no third-party disclosure of the debt. Applies to third-party collectors and to first-party billing under many state mini-FDCPA laws.

Regulation F

12 CFR 1006 (CFPB)

Call-frequency ceiling, 8am to 9pm local window, limited-content messages, and a clear electronic opt-out path.

The permission matrix

May do · May not do

Each row is one capability an AI voice agent might exercise on a patient-balance call, mapped to the authority that permits or forbids it. Read the two columns side by side before you configure a single dialer rule.

✓The AI agent MAY

✗The AI agent MAY NOT

Call a consented mobile number

Dial a wireless number when prior express consent to be contacted there was captured at registration or intake.

TCPA §227(b) · 47 CFR 64.1200(a)

Auto-dial a number it was never given consent for

Skip-traced, appended, or purchased numbers do not carry consent. An AI voice call to them is a per-call TCPA exposure.

FCC AI-Voice Ruling, Feb 2024

Identify itself as an automated system

State the caller's identity and that the contact is an attempt to collect a debt, and disclose the artificial voice up front.

FDCPA §1692e(11) · Reg F 1006.18

Impersonate a live agent or a provider staffer

Presenting the AI as a human, or as clinical staff, is a false or misleading representation and an unfair practice.

FDCPA §1692e · §1692d

Call between 8:00am and 9:00pm patient-local

Place calls only inside the consumer's local convenient-time window, resolved from the patient's own time zone.

Reg F 1006.6(b)(1) · FDCPA §1692c(a)(1)

Rely on the healthcare treatment exemption

The FCC exigent-healthcare exemption covers appointment and care calls only. Billing and collections calls are expressly outside it.

FCC 2015 Healthcare Exemption (scope)

Leave a limited-content message

Voicemails may include the required business name, callback details, and opt-out without disclosing the debt to a listener.

Reg F 1006.2(j) · 1006.6(d)

Exceed the Reg F call-frequency ceiling

No more than seven call attempts within seven days per account, and no call within seven days of a phone conversation about the debt.

Reg F 1006.14(b) (7-in-7)

Deliver the validation-notice information

Convey the debt amount, creditor, and consumer rights, and route the call to a human on any dispute or hardship signal.

Reg F 1006.34 · FDCPA §1692g

Discuss the balance with a third party

The AI may not confirm or describe the debt to a spouse, relative, employer, or anyone answering who is not the patient.

FDCPA §1692c(b)

Detect and honor a revocation immediately

Recognize an opt-out spoken in any reasonable words, stop the call, and suppress future automated attempts.

FCC Revocation Order, eff. Apr 11 2025

Keep calling after consent is withdrawn

Once a patient revokes, automated calls must stop. The revocation must be fully processed within ten business days.

47 CFR 64.1200(a)(10)

Where the consent comes from

The consent chain, before a single call dials

An AI voice program is only as defensible as the record behind the number. This is the chain that has to exist for the "MAY" column to hold.

Capture at intake

Prior express consent to be contacted at the mobile number is collected during registration, in writing where the contact may be marketing.

TCPA prior express consent

Store the proof

Timestamp, source, and the exact language shown are retained. Consent that cannot be produced is consent that does not exist in a dispute.

47 CFR 64.1200 recordkeeping

Scrub before dial

Every number is checked against revocations, disputes, cease-contact requests, and the local-time window at the moment of the call.

Reg F 1006.6 · 1006.14

Log the outcome

Disclosure delivered, opt-outs captured, attempt counted against the 7-in-7 ceiling, and any human hand-off recorded.

Audit trail for FDCPA / Reg F

Two numbers that decide compliance

The revocation clock and the frequency ceiling

Most AI-collections exposure traces back to two figures a dialer either respects or ignores.

Revocation clock

Time to fully process a withdrawal of consent.

10BUSINESS DAYS MAX

Automated calls stop on the call where the opt-out is spoken.
Any reasonable method of revocation counts, per the 2025 FCC order.
Suppression must propagate across every channel within the window.

Frequency ceiling

Reg F presumptive limit, per account, per 7 days.

Seven attempts sit inside the presumption. The eighth crosses it, and a call within seven days of a live conversation is barred regardless of the count.

VoiceIQ dials inside the matrix, by design

VoiceIQ is built for the "MAY" column. It checks consent and revocation state before every dial, resolves the patient-local time window, meters attempts against the Reg F ceiling, delivers the required disclosures in a declared automated voice, and hands off to a live specialist the moment a dispute or hardship is heard. The compliance rulebook on this page is the product spec, not an afterthought bolted on later.

Talk to ASP-RCM about compliant AI patient collections

This page summarizes federal requirements as of 2026 and is general information, not legal advice. State mini-FDCPA statutes, state calling-time and consent rules, and any applicable HIPAA obligations may impose additional limits on patient-balance calls. Confirm the current text of the TCPA and 47 CFR 64.1200, the FCC's February 2024 AI-voice Declaratory Ruling, the FCC revocation-of-consent order effective April 11 2025, the FDCPA at 15 U.S.C. 1692, and CFPB Regulation F at 12 CFR 1006 with counsel before deployment.