1. Home
  2. Blog
  3. Collections compliance

TCPA consent for AI voice calls after the FCC's 2024 ruling: what's settled and what isn't

Short answer

Under the FCC's February 2024 declaratory ruling (FCC 24-17), AI-generated voices are "artificial" voices under the TCPA, so AI voice calls need the same consent as prerecorded calls: prior express consent for informational calls to cell phones, prior express written consent for telemarketing, and limits on calls to residential lines. Each message must identify the caller, and consent can be revoked by any reasonable means.

On this page
  1. Is an AI voice call an artificial or prerecorded call?
  2. What's settled and what isn't?
  3. What consent does an AI voice call need?
  4. What must an AI voice message say?
  5. How can a consumer revoke consent, and when do the 2024 rules apply?
  6. What happened to the one-to-one consent rule?
  7. What are the damages for an AI voice call without consent?
  8. How do you prove consent call by call?
  9. Questions
  10. Sources

Your AI voice agent can say everything right on a call it was never allowed to place. Whether a call needed consent, and whether you had it, lives in consent records and dial logs. No transcript shows them. And an agent that improvises an offer can turn a routine account call into telemarketing that needed written consent.

The Telephone Consumer Protection Act (TCPA) is the 1991 federal law, at 47 U.S.C. 227, that restricts calls made with an autodialer or an artificial or prerecorded voice. The FCC confirmed in February 2024 that it covers AI voice agents. Three things have moved since: how consumers revoke consent, the one-to-one consent rule, and how much weight courts give the FCC. This is where each stands on September 23, 2026. The FCC votes on September 30, 2026 on a draft order about revocation, and we'll update this post after the vote.

Is an AI voice call an artificial or prerecorded call?

Yes. The FCC said so in a declaratory ruling, FCC 24-17, adopted February 2, 2024 and effective on its release on February 8. The TCPA's limits on "artificial or prerecorded voice" calls cover "current AI technologies that resemble human voices and/or generate call content using a prerecorded voice." The ruling made no new rule. It applied the existing statute and the rules at 47 CFR 64.1200 to AI calls.

Two lines matter most for voice agents. The TCPA "does not allow for any carve out of technologies that purport to provide the equivalent of a live agent," so a conversational agent gets no exemption for sounding human. And the FCC applied the reasoning of its 2020 soundboard ruling to AI. That ruling held that a live agent choosing prerecorded clips doesn't take a call outside the TCPA.

The artificial-voice rule also stands apart from the autodialer rule. An autodialer, under 64.1200(f)(2), is equipment that can store or produce phone numbers using a random or sequential number generator and dial them. Whether or not your dialer meets that narrow definition, the AI voice alone brings the call under the TCPA.

The ruling's weight changed in 2025. In McLaughlin Chiropractic Associates v. McKesson Corp. (June 20, 2025), the Supreme Court held that district courts in TCPA enforcement suits aren't bound by the FCC's reading of the statute. They must interpret it themselves, "affording appropriate respect to the agency's interpretation." So FCC 24-17 persuades a court rather than binding it. The statute's words point the same way, though. The FCC cited a Ninth Circuit decision describing an artificial voice as "a sound resembling a human voice that is originated by artificial intelligence." Build as if the ruling holds.

What's settled and what isn't?

The AI-voice ruling, any-reasonable-means revocation and the end of one-to-one consent are settled. Revoke-all, exclusive opt-out methods and an AI disclosure rule are not.

What changed for AI voice calls, 2023 to 2027
  1. Dec 2023

    FCC narrows written consent to one seller at a time, due January 27, 2025

  2. Feb 8, 2024

    FCC 24-17 takes effect: AI-generated voices are "artificial" voices under the TCPA

  3. Feb 2024

    FCC 24-24 adopts revocation by any reasonable means

  4. Aug 2024

    FCC 24-84 proposes AI-call disclosure rules

  5. Jan 24, 2025

    Eleventh Circuit vacates one-to-one consent before it takes effect

  6. Apr 11, 2025

    Revocation rules take effect; revoke-all is waived to April 11, 2026

  7. Jun 20, 2025

    McLaughlin: courts interpret the TCPA themselves, with respect for the FCC's reading

  8. Aug 29, 2025

    FCC restores the earlier written-consent definition

  9. Sep 9, 2026

    FCC releases a draft order narrowing revoke-all

  10. Sep 30, 2026

    FCC votes on that draft

  11. Jan 31, 2027

    Revoke-all waiver ends, under DA 26-12

Still open compared with Settled
Still openSettled
One revocation stops all of a caller's robocalls: waived to January 31, 2027, and a narrowing draft is up for a vote September 30, 2026Revocation by any reasonable means, honored within 10 business days: in effect since April 11, 2025
Callers designating an exclusive revocation method: barred today, and the same draft would allow itOne-to-one written consent: vacated January 24, 2025 and removed from the rules August 29, 2025
An AI-call disclosure requirement: proposed August 2024, not adoptedAI voices are "artificial" under the TCPA: FCC 24-17, effective February 8, 2024; courts give it respect but decide for themselves

It depends on the call's purpose and the kind of line. Informational calls to cell phones need prior express consent. Telemarketing needs prior express written consent. Up to three informational calls in 30 days to a residential line need none, with an opt-out.

CallCell phoneResidential line
Informational, commercial (a collection call, an account alert)Prior express consentNone for up to 3 calls in any 30 days, with an opt-out; prior express consent beyond that
Telemarketing or advertisingPrior express written consentPrior express written consent
HIPAA health care message from a covered entityPrior express consent, apart from a narrow exemption for some care messages, never billing (64.1200(a)(9)(iv))None for 1 call a day, up to 3 a week, with an opt-out
Emergency purposesNoneNone

The cell-phone column comes from 227(b)(1)(A)(iii) and 64.1200(a)(1) and (a)(2); the residential column from 227(b)(1)(B) and 64.1200(a)(3). Health care calls get more depth in HIPAA and AI voice agents in patient access.

Prior express consent has no form requirement. For debt collection, the FCC's 2008 ACA International ruling set a simple rule. A consumer who gives a creditor a cell number during the transaction that created the debt has consented to calls about that debt at that number. The same ruling puts the burden of proving consent on the creditor and treats a third-party collector's calls as the creditor's own. After McLaughlin, a court reads that ruling for itself too.

Prior express written consent, per 47 CFR 64.1200(f)(9)
  • A written agreement bearing the signature of the person called
  • An electronic signature counts where federal law or state contract law recognizes it
  • It clearly authorizes the seller to deliver telemarketing calls using an autodialer or an artificial or prerecorded voice
  • It states the phone number those calls may go to
  • A clear and conspicuous disclosure that signing authorizes those calls, and that signing isn't a condition of any purchase

The rule AI agents break without anyone noticing is the trigger for written consent: a call that "includes or introduces an advertisement or constitutes telemarketing" (64.1200(a)(2)). A collection agent that improvises an offer for a new card turns an informational call into telemarketing that needed written consent. So does a claims agent that pitches an add-on policy. A transcript can check that.

What must an AI voice message say?

The business's registered name at the start and a callback number. Telemarketing, and exempt calls to residential lines, also need an automated opt-out. Every artificial or prerecorded voice message has to meet 64.1200(b), and FCC 24-17 repeats that these requirements reach AI calls.

What every AI voice message must include
  • At the beginning, the business's name as registered to do business with the state 64.1200(b)(1)
  • During or after the message, a phone number for that business, not the dialer's 64.1200(b)(2)
  • For telemarketing and exempt calls to residential lines, a number that takes do-not-call requests in regular business hours 64.1200(b)(2)
  • For telemarketing to a residential line, a cell phone or another line listed in 64.1200(a)(1), and for exempt calls to residential lines: an automated voice or key-press opt-out, with brief instructions, within two seconds of the identification 64.1200(b)(3)
  • Using the opt-out adds the number to the caller's do-not-call list and ends the call at once 64.1200(b)(3)
  • On a voicemail that needs the opt-out, a toll-free number that reaches it 64.1200(b)(3)

For an agent that improvises, the two-second window is the hard part: a pleasantry and a question before the opt-out already miss it. The opt-out applies on cell phones too. A collection call to a cell phone that turned into telemarketing when the agent pitched a new card needed one.

Collectors face one more collision. Regulation F's voicemail safe harbor wants a business name that doesn't reveal debt collection, and that can conflict with the registered-name rule (see the FDCPA and Regulation F checklist for AI collection calls).

No federal rule yet requires an agent to say it's an AI. The FCC proposed AI-call disclosure rules in August 2024 (FCC 24-84), and as of September 23, 2026 nothing from that proposal is in 64.1200. Check state law.

By any reasonable means that clearly expresses a wish to stop. That's the FCC's February 2024 revocation rule (FCC 24-24), codified at 64.1200(a)(10) and (11) and in effect since April 11, 2025. Three methods are reasonable per se:

  • Using the caller's automated opt-out on a call
  • Replying "stop," "quit," "end," "revoke," "opt out," "cancel" or "unsubscribe" to a text
  • Using a website or phone number the caller designated for opt-out requests

Other methods, such as a voicemail or an email, create a rebuttable presumption that the consumer revoked. Callers must honor a revocation within ten business days. Under the current rule, they may not designate an exclusive way to revoke. A consumer who tells your agent "stop calling me" has revoked, and the agent's job is to log it where the dialer will see it.

One piece isn't in force. Under the revoke-all requirement, a revocation in response to one type of message stops all of a caller's robocalls and robotexts on unrelated matters. DA 26-12 waived it to January 31, 2027.

The FCC's September 9, 2026 draft order would let callers apply a revocation only to the category of informational robocalls it was aimed at. It would also let them designate an exclusive revocation method from the three listed in the rule, provided it's disclosed on the call. A draft isn't a rule and can change before the vote. If it passes as written, an AI agent's in-call opt-out could become the one door consumers are told to use, so it must be announced and must work.

The Eleventh Circuit vacated it before it took effect, and the FCC took it out of its rules in August 2025. The December 2023 rule would have limited prior express written consent to one identified seller, for calls "logically and topically associated" with where consent was given. In Insurance Marketing Coalition v. FCC, the court held that it conflicted with the ordinary meaning of "prior express consent." The mandate issued April 30, 2025, and the FCC restored the earlier definition effective August 29, 2025.

That removes the one-seller and topic limits from the federal rule. It doesn't touch the written-consent requirement for telemarketing robocalls, which comes from a 2012 FCC order the court said was not at issue.

A consumer can sue under 227(b)(3), and the statute sets damages per violation:

$500

per violation, or the consumer's actual losses if greater

47 U.S.C. 227(b)(3)

$1,500

per violation, at most, when a court finds it willful or knowing and trebles the award

47 U.S.C. 227(b)(3)

No cap

on the total, so exposure scales with call volume

47 U.S.C. 227(b)(3)

Repeat telemarketing calls to numbers on the national do-not-call registry carry a separate right of action under 227(c)(5). State attorneys general can also sue on residents' behalf.

With records for each call, not each campaign, because the FCC puts the burden of showing consent on the caller's side.

Consent evidence for one outbound AI call, and where it lives
  • The number dialed, and whether it was wireless or residential when the call was made Dial log
  • The consent that covers that number: where and when it was given, by whom, to whom, and how it reached the caller Consent records
  • For telemarketing, the signed written agreement with the disclosure text the consumer saw Consent records
  • Every revocation on record for that number, from any channel, with the dates received and honored Consent records
  • A reassigned-numbers check, queried with the consent date Database query
  • For exempt calls to residential lines, the count of calls to that line in the prior 30 days Dial log
  • The opening identification, the callback number and the opt-out where required Transcript
  • Whether the agent introduced an advertisement, and whether a spoken revocation was logged Transcript

Only the last two live in the transcript and the agent's tool calls, so a transcript-only review can't tell you whether a call was lawful to place. The reassigned-numbers safe harbor in 64.1200(m) protects a caller who queried the database with the consent date and got an erroneous "no."

Graded against the example collections SOP, rev 7: 2 met, 1 not checked(Illustrative)

Agent: Hi, this is Maya, an automated assistant calling for Quillfeather Services on a recorded line. Am I speaking with Daniel Reyes?

1.1 met Opening: business named at the start and recording announced

Customer: Yes. Please stop calling me.

Agent: Understood, Daniel. We won't call you about this again, and I've recorded your request.

4.2 met Stop calling: acknowledged, collection talk stopped, request logged to the dialer at 00:19

6.2 not checked AI-voice consent: needs the consent records and dial log for this number

Rule 6.2 in the example collections SOP these guides share is that consent check. It needs your dial log and consent records, which Loops doesn't read, so Loops can't settle it; the in-call rules are still graded on every call. Our guide to auditing AI voice agent calls against your own procedures covers the in-call half. This is general information, not legal advice.

Next, take a sample of last month's outbound AI calls and assemble the checklist above for each. Where a call can't be backed, fix the record-keeping before the next release. Watch the FCC's September 30 vote, which may change how your agent's opt-out has to work. For collection calls, see how Loops audits collection calls, or start the free 30-day audit for a graded view of your own.

Questions

Does the TCPA apply to an AI agent that answers inbound calls?

The consent rules in 47 U.S.C. 227(b) attach to calls a business makes or initiates, and FCC 24-17 speaks of AI technology that initiates outbound calls, so a consumer who calls your agent doesn't need to have consented first. Callbacks, follow-ups and voicemails the agent places are outbound, though, and need consent like any other artificial-voice call.

Does an AI voice call need an autodialer to fall under the TCPA?

No. Section 227(b) covers calls made using an autodialer or an artificial or prerecorded voice, and the two triggers are separate. An AI voice call is covered even if the dialing system wouldn't meet the narrow autodialer definition in 47 CFR 64.1200(f)(2), because the synthetic voice alone brings it under the artificial-voice rules.

Can a caller require consumers to opt out only by pressing a key or saying stop?

Not under the rule in force on September 23, 2026. 47 CFR 64.1200(a)(10) lets consumers revoke by any reasonable means and bars callers from designating an exclusive method. A draft order up for an FCC vote on September 30, 2026 would let callers designate one of three methods, including an automated in-call opt-out, as exclusive if it's clearly disclosed on the call. Until it's adopted and effective, the any-reasonable-means rule applies.

How quickly must an opt-out made on an AI call be honored?

Within a reasonable time not exceeding ten business days of receipt, under 47 CFR 64.1200(a)(10), with the same ten-business-day ceiling for do-not-call requests under 64.1200(d)(3). Where the automated opt-out mechanism in 64.1200(b)(3) is required, using it must add the number to the do-not-call list and end the call immediately. The FCC encourages honoring requests sooner.

Who is liable when a collection agency's AI agent calls for a creditor?

Both. The agency that places the call is liable directly, since the TCPA reaches whoever makes it (47 U.S.C. 227(b)(1)(A); 47 CFR 64.1200(a)(1)). The FCC's 2008 ACA International ruling adds the creditor: one on whose behalf an autodialed or prerecorded call is made to a wireless number bears responsibility for any violation and the burden of proving consent. A voice platform can be liable too if so involved in placing the calls as to be deemed to have made them (FCC 15-72, paragraph 30). Allocate the risk by contract.

Sources

  1. Declaratory Ruling, Implications of Artificial Intelligence Technologies on Protecting Consumers from Unwanted Robocalls and Robotexts (FCC 24-17), Federal Communications Commission
  2. 47 CFR 64.1200, Delivery restrictions, eCFR
  3. 47 U.S.C. 227, Restrictions on use of telephone equipment, Legal Information Institute, Cornell Law School
  4. Report and Order, Rules and Regulations Implementing the TCPA, consent revocation (FCC 24-24), Federal Communications Commission
  5. Order extending the revoke-all effective date to January 31, 2027 (DA 26-12), Federal Communications Commission
  6. Fact sheet and draft Report and Order on consent revocation, September 9, 2026, Federal Communications Commission
  7. Insurance Marketing Coalition Ltd. v. FCC, No. 24-10277, U.S. Court of Appeals for the Eleventh Circuit
  8. Final rule conforming the prior express written consent definition to the court decision (90 FR 42137), Federal Register
  9. McLaughlin Chiropractic Associates, Inc. v. McKesson Corp., No. 23-1226, Supreme Court of the United States
  10. Declaratory Ruling on ACA International's petition (FCC 07-232), Federal Communications Commission
  11. Declaratory Ruling and Order on TCPA petitions, including who makes or initiates a call (FCC 15-72), Federal Communications Commission