AI voice agents and TCPA compliance: what collections teams need to know

The FCC ruled AI and cloned voices are “artificial voice” under the TCPA. Here’s what that means for an AI collections agent — consent, Reg F, the software-vs-collector line, and the frequency ledger nobody ships.

In February 2024 the FCC confirmed that AI-generated and cloned voices count as an “artificial or prerecorded voice” under the TCPA. For collections — an industry already built on strict calling rules — that ruling reshapes what an AI agent must do.

The consent rule is not optional

An artificial-voice call to a cell phone needs the called party’s prior express consent. There is no personal or informational carve-out that removes the requirement; the tier of consent changes, the need for it does not. On top of the TCPA sits Reg F: a rebuttable presumption of a violation past seven calls per debt in seven days, mini-Miranda disclosure in the language of the call, and the ban on false or misleading representations — the exact provision an undisclosed, human-sounding agent stresses.

Software to a licensed collector — never the collector

The single most important structural choice is the software-vs-service line. Sell tooling to a licensed collector and licensing attaches to them, not to you. Let your own agents converse with consumers and bill on collections activity, and you risk becoming a “principal purpose” debt collector yourself — subject to the FDCPA and state licensing like California’s DCLA. Design as software from day one.

The cross-channel frequency ledger nobody ships

Reg F caps phone contact. New York City’s SHIELD rule goes further — three communications per account per seven days across all channels combined — and it takes effect January 2027. Tracking frequency across phone, SMS, and email in one ledger is an engineering requirement most systems haven’t built. It is also the cleanest differentiator available to a new entrant.

Recording consent and disclosure

Default to all-party recording consent — an audible notice at the top of the call — so a call touching California, Illinois, or any all-party state is covered. Pair it with an AI-disclosure line, which several states already require and the FCC is moving to mandate. Do both at the top of the call and you satisfy two obligations in one breath.

Compliance here is not overhead — it is the product. The vendors that win collections sell the audit trail, the consent records, and the frequency ledger as features, because that is what a regulator-aware buyer is actually buying.