Debt CollectionNov 19, 20266 min read

TCPA Compliance for AI Debt Collection Calls: What the FCC Ruling Means for You

In February 2024 the FCC ruled that AI-generated voices count as "artificial" voices under the Telephone Consumer Protection Act.

Last updated: November 2026

Direct answer: In February 2024 the FCC ruled that AI-generated voices count as "artificial" voices under the Telephone Consumer Protection Act. For debt collection, that means calls to cell phones using an AI voice generally need the consumer's prior express consent, and you must honor opt-outs. This is general information, not legal advice. Review your program with counsel.

What happened in 2024

Many collectors had the same question as AI voice technology matured: do these calls fall under the TCPA's rules on artificial or prerecorded voices? The Federal Communications Commission answered in a declaratory ruling in early 2024. It said yes. A voice produced by artificial intelligence is an artificial voice for TCPA purposes.

That ruling settled a debate, and it changed one thing for voice AI in collections: nobody can claim these calls sit outside the statute. They sit inside it. The question is no longer whether the TCPA applies. It is whether your consent and opt-out practices hold up.

What the TCPA cares about

The TCPA is a consent law. In plain terms, it restricts calls and texts made with automatic dialing systems or artificial and prerecorded voices, especially to mobile phones, unless the consumer has given the right kind of permission.

For collections, three ideas do most of the work.

Prior express consent. For calls to a cell phone using an artificial voice or an autodialer, the caller generally needs the consumer's prior express consent. Under long-standing FCC guidance, a consumer who gives a creditor their number in connection with the debt can be treated as having consented to related calls. How and when the number was provided matters, so your records matter.

Revocation. Consumers can revoke consent. The FCC has adopted rules on how revocation must be honored, including how quickly. Check the current deadline and scope with counsel, because these rules have shifted in recent years.

Wrong numbers. Phone numbers change hands. A call to a reassigned number can create liability if you have no consent from the new owner. Scrubbing against reassigned-number data is a standard defense.

At a glance

TCPA issueWhat to doWhy it matters
Consent on fileStore how and when each number was providedYour defense in a dispute
Opt-out requestsHonor immediately and record the requestRevocation is a legal right
Reassigned numbersScrub numbers regularlyAvoid calling a new owner
AI voice disclosureFollow your counsel's guidance on identificationThe FCC treats AI voices as artificial
State lawsCheck state telephone rulesSome states add their own limits

Where AI voice agents add risk

Scale is the double edge. A human collector can only make so many mistakes in a day. A system that works thousands of calls at once can make a mistake thousands of times before anyone notices.

If your consent data is wrong, an agent will call numbers it should not. If your opt-out handling is slow, an agent will call someone who asked to stop. If your reassigned-number scrub is stale, an agent will reach strangers.

The fix is not to avoid automation. It is to build the controls into the system so the agent cannot act outside them.

Where AI voice agents reduce risk

Automation also helps, if it is built well.

It follows the rules every time. A person might forget to log an opt-out. A system logs it the moment the consumer says it.

It leaves evidence. A transcript of every utterance shows what the consumer said and how the agent responded. If someone claims they asked you to stop, the record answers the question.

It enforces limits. Hours, call counts and stop flags can be checked before each call, not after a complaint.

It handles requests consistently. When a consumer says "stop calling me," the response is the same every time.

What good vendors do

Vodex builds its collections agents around the TCPA alongside FDCPA and Reg F. In practice that means a few behaviors you can test.

It checks before it dials. The agent confirms the account is eligible, the number is flagged as consented and no stop request is on file.

It listens for opt-outs. If the consumer asks to stop being called, the agent acknowledges the request, records it and flags the account so no other system dials it.

It logs everything. Each utterance is stored and attached to the account.

It sits inside a secure platform. Vodex holds SOC 2 Type II and ISO 27001 credentials, along with HIPAA for healthcare portfolios.

It integrates with your data. Vodex connects with CRMs and skip tracing tools, so consent flags and opt-out requests live in your system of record, not in a silo.

No vendor can make you compliant by itself. Consent data is yours, and so are your policies. A good vendor gives you the controls and the records. You still own the program.

A word on state law

Federal rules are the floor, not the ceiling. A number of states have their own telephone rules, some with tighter calling hours, extra disclosure duties or private rights of action. If your portfolio spans many states, your compliance map should too. Ask counsel which states in your book need special handling, and build those rules into the agent's configuration so they apply on every call, not only on the ones someone remembers to check.

A pre-launch checklist

Before any AI agent calls a consumer, walk through this list with your compliance team.

  1. Consent source. Can you show where each number came from?
  2. Consent scope. Does the consent cover automated or artificial-voice calls?
  3. Opt-out path. What happens in the system, in real time, when a consumer revokes?
  4. Cross-system sync. Does every dialing and messaging tool see the same stop list?
  5. Reassigned numbers. How often do you scrub?
  6. State rules. Which states in your portfolio add their own requirements?
  7. Recording consent. Some states require all parties to agree to recording. How does the agent handle that disclosure?
  8. Audit access. Can you pull a full record for any call in minutes?

If any answer is "I think so," keep working until it is "yes, and here is the proof."

Common mistakes

Assuming a vendor's compliance is yours. Certifications describe the vendor's security. They do not replace your consent program.

Syncing nightly instead of instantly. An opt-out at 10 a.m. that reaches the dialer at midnight is a day of risk.

Ignoring state law. Several states have telephone solicitation or collection rules that differ from federal ones.

Testing with friendly callers only. Run a test where the consumer says "stop calling me" in six different ways. Mumbled, angry, polite. The agent should catch them all.

Frequently asked questions

Yes. The FCC ruled in 2024 that AI-generated voices are artificial voices under the TCPA.

Calls to cell phones using an artificial voice or autodialer generally require prior express consent. Confirm your consent standard with counsel.

The agent should acknowledge, record the request and flag the account across every system. Review the current revocation rules with counsel.

Vodex builds its agents around TCPA, FDCPA and Reg F, with logging and controls. Your own consent data and policies remain your responsibility.

No. It is general information. Speak with a qualified attorney.

SOC 2 Type II · ISO 27001 · 24/7 support

Ready to supercharge
your engagement?

Join the enterprises already using Vodex to turn reminders, collections and follow-ups into recovered revenue.