AI Voice Agents and Purchased Lead Lists: The Consent Chain That Decides Your TCPA Exposure - Zian AI

AI Voice Agents and Purchased Lead Lists: The Consent Chain That Decides Your TCPA Exposure

A lead vendor sends you 40,000 records with a badge on the invoice: “100% TCPA-compliant, fully consented leads.” You load them into an AI voice agent and start dialling. Under the Telephone Consumer Protection Act, that badge is worth close to nothing. You are the caller. If a called party sues, the question is not what your supplier promised — it is what you can produce, per record, to show that person agreed to receive that call.

AI voice makes the gap worse, because an AI or cloned voice is an “artificial” voice under the TCPA, which turns a normally contested element into a documented one. Everything below is current as at 18 August 2026, checked against the statute, the FCC’s rules and the court record rather than vendor marketing.

Quick answer: Under the TCPA (47 U.S.C. §227) and FCC rules (47 C.F.R. §64.1200), the caller — not the list seller — must prove consent. The FCC confirmed in 2024 that AI-generated and cloned voices are “artificial” voices, so they need prior express consent, and prior express written consent for telemarketing. The Eleventh Circuit vacated the FCC’s one-to-one consent rule in 2025, but that removed a narrowing rule — it did not make purchased-list calling safe.

Zian AI builds autonomous outbound agents, so we have a commercial interest in you dialling more. We would still rather you dialled a smaller list you can defend. Our agents are designed to log every call against its source record, script version and outcome, so the consent artefact and the call artefact stay joined up — the only configuration that survives a discovery request. If that is how you want to run outbound, Apply For Partnership.

What the rules actually say

47 U.S.C. §227(b)(1) makes it unlawful to call a mobile number using an autodialler or “an artificial or prerecorded voice” without the prior express consent of the called party, and separately bars artificial-voice calls to residential lines. Section 227(b)(3) gives the called party a private right of action for actual loss or $500 for each such violation, trebled at the court’s discretion for wilful or knowing conduct. Per call. The statute never uses the phrase “prior express written consent” — that tier comes from the FCC.

In its Declaratory Ruling of 8 February 2024 (FCC 24-17), the Commission confirmed that “the TCPA’s restrictions on the use of ‘artificial or prerecorded voice’ encompass current AI technologies that resemble human voices,” so callers “must obtain prior express consent from the called party before making a call that utilizes artificial or prerecorded voice simulated or generated through AI technology” (para. 5). Footnote 13 adds: “If these robocalls introduce an advertisement or contain telemarketing, the Commission’s rules require that the caller obtain the prior express written consent of the called party.” Voice cloning is named explicitly.

The tiers live in 47 C.F.R. §64.1200. Paragraph (f)(9) defines prior express written consent as a signed agreement clearly authorising the seller to deliver telemarketing using an autodialler or artificial voice, naming the number the signatory designates, with a clear and conspicuous disclosure and a statement that signing is not a condition of purchase.

Consent tiers and what each buys an AI voice agent

Consent tier Informational AI-voice call to a mobile Telemarketing AI-voice call Autodialled text Evidence you must produce
No consent No — barred by §64.1200(a)(1) absent an emergency purpose No No Nothing helps. A purchased list with no per-record artefact sits here, whatever the invoice says.
Prior express consent Yes — §64.1200(a)(1) No — (a)(2) and (a)(3) require written consent for advertising or telemarketing Informational only Proof the consumer gave you that number, and that the call is within the scope for which it was given.
Prior express written consent Yes Yes — the only tier that permits it Yes Signed agreement naming the seller and the designated number, the disclosure as displayed, and proof it was not a condition of purchase (§64.1200(f)(9)).
Established business relationship No — an EBR is not consent under §227(b) No No Purchase or transaction within 18 months, or inquiry or application within 3 months, not terminated by a do-not-call request (§64.1200(f)(5)).

The EBR row is where teams go wrong. An EBR removes a call from the definition of “telephone solicitation” in §64.1200(f)(15), which matters for the National Do Not Call Registry — it does not supply the consent §227(b) requires before you point an artificial voice at a mobile.

Registry mechanics add two more traps. The safe harbour in §64.1200(c)(2)(i)(D) requires scrubbing against a registry version obtained no more than 31 days before the call. And under (c)(2)(ii), permission to call a registered number “must be evidenced by a signed, written agreement between the consumer and seller which states that the consumer agrees to be contacted by this seller” and includes the number. A form promising “our marketing partners” does not name your company.

The one-to-one rule was vacated. That is not a green light.

In December 2023 the FCC adopted a rule requiring written consent to name one identified seller at a time, with resulting calls “logically and topically associated” with the interaction that produced the consent, due to take effect in January 2025. It never took effect — the FCC postponed the effective date, and the rule was vacated before it began operating. On 24 January 2025 the Eleventh Circuit decided Insurance Marketing Coalition Ltd. v. FCC, No. 24-10277, holding that “the FCC exceeded its statutory authority under the TCPA because the 2023 Order’s new consent restrictions impermissibly conflict with the ordinary statutory meaning of ‘prior express consent’.” Disposition: “PETITION GRANTED; ORDER VACATED IN PART AND REMANDED.”

Following the court’s mandate of 30 April 2025, the FCC issued a ministerial order reinstating the earlier text of §64.1200(f)(9), published on 29 August 2025, noting the revised rule “had not gone into effect.”

Read that precisely. The vacatur means the FCC’s additional narrowing — one seller at a time, topical relatedness — is not law, so a consumer may lawfully consent to more than one named seller in a single interaction. It does not touch the written-consent requirement, the requirement that the agreement authorise a named seller, the caller’s burden of proof, or the registry rules. If your list’s disclosure named a hundred unnamed “partners,” the vacatur does not save it.

Chain of custody: what you need per record

The burden question is settled. In the 2012 TCPA Order (FCC 12-21, para. 33) the FCC concluded that “should any question about the consent arise, the seller will bear the burden of demonstrating that a clear and conspicuous disclosure was provided and that unambiguous consent was obtained.” Not the broker. The seller on whose behalf the call is made.

For every record you dial, you should be able to retrieve, without ringing the vendor:

  • The capture point — the exact URL or channel, plus a rendered copy of that page as it appeared on the capture date.
  • The disclosure language as displayed — verbatim, including which sellers were named and whether consent was affirmative or pre-ticked.
  • Timestamp and IP address of the submission, with user agent and form-session identifier.
  • The number the consumer designated, matched to the number in your dialling list.
  • Revocation and suppression history since capture.
  • Retention. The FTC’s Telemarketing Sales Rule, 16 C.F.R. §310.5, requires five-year retention and defines a complete consent record as including the person’s name and number, “a copy of the request for Consent in the same manner and format in which it was presented,” the purpose, a copy of the consent, and the date given.

A list you cannot audit to that level is a list you cannot defend. The honest test: pick ten rows at random and ask the vendor for the artefacts. If they cannot produce them inside a working week, you bought data, not consent — and that belongs in your outreach compliance posture before it goes anywhere near a dialler.

Why AI voice raises the exposure

The artificial-voice element becomes trivially provable. In autodialler cases, plaintiffs fight for years over whether the equipment qualifies as an ATDS. With a synthetic or cloned voice there is nothing to argue: FCC 24-17 already says AI voices are artificial voices, the vendor invoice says text-to-speech, and the recording says the rest.

Damages scale with call volume. At $500 per violation, which a court may in its discretion increase up to $1,500 for wilful or knowing conduct, a mid-sized campaign against an unprovable list is arithmetic, not risk. AI agents are bought to multiply attempts, which multiplies the multiplicand.

Artificial-voice calls carry extra duties. Section 64.1200(b) requires every artificial or prerecorded-voice message to identify the responsible business at the start and to state a callback number. Where the message includes or introduces an advertisement or constitutes telemarketing — or runs under an exemption in (a)(3)(ii) to (v) — paragraph (b)(3) also requires an automated, interactive opt-out mechanism within two seconds of that identification. See our AI disclosure scripts for wording that satisfies this without killing the call.

Revocation is the fourth pressure point. Section 64.1200(a)(10) lets a called party revoke “by using any reasonable method,” bars an exclusive revocation channel, and requires requests be “honored within a reasonable time not to exceed ten business days from receipt.” One carve-out is on hold: in Order DA 26-12 (6 January 2026) the FCC extended its waiver of the portion treating revocation of one type of informational message as covering all future robocalls on unrelated matters, now effective 31 January 2027. The ten-day and “any reasonable method” rules are in force today. Meanwhile the FCC’s proposed AI-call disclosure rules in NPRM FCC 24-84 remain proposals as at this check date — we cover them in our breakdown of what NPRM 24-84 means for AI voice vendors. Build to them anyway.

Australia does not run the same consent model

If you dial +61 numbers, one global consent policy will break. The ACMA’s Statement of Expectations on consent (1 July 2024) recognises express consent and the “less common” inferred consent, with no written-consent tier, and states that “commercial calls made using an auto-dialler (robocalls) or that use pre-recorded or AI voices are all telemarketing calls.” Critically for bought lists, businesses “are responsible for their consent-related compliance obligations under the Rules, regardless of whether they outsource their telemarketing or e-marketing or consent gathering through third party or affiliate marketing arrangements.” Different statute, same answer on who carries the can.

This is general information, not legal advice. TCPA litigation is intensely fact-specific and nothing here substitutes for counsel reviewing your capture flows, contracts and call records.

If you want an agent platform that keeps the evidence trail intact from lead source to call disposition, Apply For Partnership — and if you are still comparing tools, our roundup of AI cold calling software covers what to ask each vendor about logging.

Sources and who owns each figure

Figure/claim Owner (organisation) Where it’s published Date checked
Ban on artificial or prerecorded voice calls without prior express consent; $500 per violation, which a court may in its discretion increase up to three times for wilful or knowing violations US Congress (47 U.S.C. §227) law.cornell.edu/uscode/text/47/227 18 Aug 2026
AI-generated and cloned voices are “artificial” voices; prior express consent required, written consent for telemarketing Federal Communications Commission (Declaratory Ruling FCC 24-17, para. 5) docs.fcc.gov — FCC-24-17A1.pdf 18 Aug 2026
Consent tiers, written-consent definition, EBR definition, 31-day registry scrub, signed agreement naming the seller, identification and opt-out duties, revocation within ten business days Federal Communications Commission (47 C.F.R. §64.1200) ecfr.gov/current/title-47/section-64.1200 18 Aug 2026
One-to-one consent rule vacated; restrictions “impermissibly conflict with the ordinary statutory meaning of ‘prior express consent'” US Court of Appeals for the Eleventh Circuit (Insurance Marketing Coalition Ltd. v. FCC, No. 24-10277, 24 Jan 2025) media.ca11.uscourts.gov — opinion PDF 18 Aug 2026
FCC reinstated the prior text of §64.1200(f)(9) after the mandate of 30 April 2025; revised rule never took effect Federal Communications Commission (Order DA 25-621), via the Federal Register federalregister.gov — 29 Aug 2025 final rule 18 Aug 2026
Seller bears the burden of demonstrating clear and conspicuous disclosure and unambiguous consent Federal Communications Commission (2012 TCPA Order, FCC 12-21, para. 33) docs.fcc.gov — FCC-12-21A1.pdf 18 Aug 2026
Five-year record retention; required contents of a complete consent record Federal Trade Commission (Telemarketing Sales Rule, 16 C.F.R. §310.5) ecfr.gov/current/title-16/section-310.5 18 Aug 2026
“Revoke-all” portion of §64.1200(a)(10) waived until 31 January 2027 Federal Communications Commission (Order DA 26-12, 6 Jan 2026) docs.fcc.gov — DA-26-12A1.pdf 18 Aug 2026
Proposed definition of “AI-generated call” and start-of-call disclosure (still a proposal) Federal Communications Commission (NPRM FCC 24-84, CG Docket 23-362) docs.fcc.gov — FCC-24-84A1.pdf 18 Aug 2026
Express vs inferred consent; AI-voice commercial calls are telemarketing; responsibility survives outsourced consent gathering Australian Communications and Media Authority (Statement of Expectations, 1 July 2024) acma.gov.au — Statement of Expectations (DOCX) 18 Aug 2026

Frequently asked questions

Does a vendor’s “TCPA-compliant leads” warranty protect us?

Contractually it may give you an indemnity claim. Legally it does not move the burden. The FCC’s 2012 TCPA Order states that “should any question about the consent arise, the seller will bear the burden of demonstrating that a clear and conspicuous disclosure was provided and that unambiguous consent was obtained” — and the seller is you, not the broker. An indemnity is a way to recover money after you have already been sued.

Since the one-to-one rule was vacated, can we call shared or co-registration leads?

Possibly, on far narrower ground than vendors suggest. Insurance Marketing Coalition v. FCC removed the FCC’s extra restrictions and left the underlying rule intact. You still need a signed agreement clearly authorising your named company for telemarketing artificial-voice calls, and for registry-listed numbers §64.1200(c)(2)(ii) requires a signed agreement naming that seller. A form disclosing unnamed “partners” fails either way.

Do informational AI-voice calls need written consent?

No — prior express consent suffices under §64.1200(a)(1). But classification follows content, not intent: if the call includes or introduces an advertisement, or constitutes telemarketing, (a)(2) and (a)(3) push it into the written-consent tier. An agent that improvises an upsell during a service call reclassifies the call in real time. Constrain the script.

How fast must we honour an opt-out?

Under 47 C.F.R. §64.1200(a)(10) a revocation made by any reasonable method must be honoured “within a reasonable time not to exceed ten business days from receipt,” and you may not designate an exclusive means of revoking. Ten business days is the legal ceiling, not a target — an agent that can suppress a number in seconds has no defensible reason to take days.

Does any of this apply to Australian numbers?

No — the TCPA is US law. Australia runs on the Spam Act 2003 and the Do Not Call Register Act 2006, where consent is express or inferred and there is no written-consent tier. The ACMA’s Statement of Expectations (1 July 2024) confirms pre-recorded and AI-voice commercial calls are telemarketing calls, and that responsibility for consent stays with your business even when consent gathering is outsourced. Run separate consent policies and separate suppression lists per jurisdiction.

Related Blogs

Related from Zian AI