Last updated 2026-07-11
TL;DR
The FCC's January 2024 declaratory ruling (FCC 24-17) tried to kill the practice of getting one blanket consent to reach a consumer for many sellers. Each seller would have needed its own clear, written, one-to-one consent before calling or texting. Violations carry TCPA penalties of $500 to $1,500 per call or text. A federal appeals court vacated the one-to-one provision in January 2025.
What is the FCC declaratory ruling on consent?
The FCC's consent ruling, formally titled FCC 24-17 and adopted January 26, 2024, is the agency's reading of what "prior express written consent" actually requires under the Telephone Consumer Protection Act [1]. The order was published in the Federal Register and set January 27, 2025 as the effective date for the one-to-one consent provisions. Companies got about a year to adjust.
Here's the short version. A lead form that lists ten partner companies and asks a consumer to check one box to contact all of them does not satisfy TCPA consent for any of those companies. The FCC called this the "lead generator loophole" and moved to close it [1].
The order also hit artificial intelligence voice calls. It clarified that AI-generated voices count as "artificial or prerecorded" voices under 47 U.S.C. § 227(b)(1)(A), which means robocall restrictions apply even when no traditional pre-recorded audio file exists [2]. That reading matters a lot for teams running AI dialers or voice-cloned agents.
One wrinkle you have to know before you build anything: the Eleventh Circuit vacated the one-to-one consent requirement in January 2025, right before it was set to take effect, in Insurance Marketing Coalition v. FCC. So the AI voice piece is live. The one-to-one piece is not, at least not right now. More on that below.
What changed with the one-to-one consent requirement?
Before FCC 24-17, the lead generation business ran on what practitioners called "comparison shopping" consent. A consumer visits a mortgage comparison site, fills out a form, checks a box agreeing to hear from "our partners," and 30 seconds later their phone rings from a dozen lenders. Courts had split on whether that met TCPA consent, and lead buyers argued it did.
The FCC landed hard on the other side. The order said prior express written consent must come from the specific seller who will make the call or send the text [1]. The consent also had to be logically and topically related to the website where it was collected. Fill out a form on a solar comparison site, and that consent could not be used to call you about life insurance.
The intended hit was enormous. A lead company that sold one lead to 20 buyers could no longer claim a single consent covered all 20. Each buyer had to be named in the consent language, and the consumer had to take a separate, distinct action for each named seller.
Here is the catch. The Eleventh Circuit struck this down before it took effect. In Insurance Marketing Coalition Ltd. v. FCC (decided January 24, 2025), the court held the FCC exceeded its statutory authority by adding the one-to-one and "logically and topically related" requirements to the definition of prior express consent [11]. The court's language: the FCC's rule "impermissibly conflicts with the ordinary statutory meaning of 'prior express consent.'"
So the bundled-consent world the FCC tried to end is legally back in place at the federal level. That does not mean bundled consent is safe. Read the next sections carefully before you assume you can go back to old forms.
How does the ruling define prior express written consent?
The TCPA's prior express written consent standard predates FCC 24-17. The FCC set it by rule in 2012, and it lives at 47 C.F.R. § 64.1200(f)(9) [3]. That base definition is still good law. It's the extra specificity the 2024 order tried to layer on top that got vacated.
Under the surviving 2012 standard, valid prior express written consent for autodialed or prerecorded calls and texts to a cell phone needs:
1. A written agreement (electronic signatures count under the E-SIGN Act). 2. Clear authorization from the consumer to receive the calls or texts. 3. The telephone number to which calls may be directed. 4. A disclosure that consent is not a condition of purchase.
What FCC 24-17 tried to add, and what the Eleventh Circuit vacated, was the one-seller-per-consent rule and the requirement that consent be logically related to the website's subject matter [11]. Those extra requirements are not currently enforceable at the federal level.
Pre-checked boxes still do not satisfy the base standard. The consumer has to take an affirmative action.
One thing teams miss even under the surviving rule: the "not a condition of purchase" disclosure has to appear in the consent language itself. Burying it in a privacy policy or terms of service does not meet the standard. Courts have found TCPA liability where consent existed but that disclosure was missing or hard to find.
Residential landline prerecorded calls follow a somewhat simpler express consent standard. The tighter rules apply to automated calls and texts to cell phones, which is where most outbound sales lives anyway.
Does the FCC ruling apply to text messages as well as calls?
Yes. The TCPA and the FCC's rules treat SMS and MMS sent with an autodialer the same as autodialed calls to cell phones [3][4]. Nothing in FCC 24-17 carved out texting, and the AI voice provisions that survived apply across the board.
If your team sends bulk promotional texts, or appointment reminders through an automated platform, or any message where a system selects and dials the number instead of a human typing it, you still need prior express written consent under the base 2012 standard [3].
For text message marketing, the vacated one-to-one piece would have hit especially hard, because SMS lead generation leaned on co-registration forms even more than voice lead gen did. A consumer signing up for a coupon site and then getting texts from 15 affiliated brands was exactly the scenario the FCC targeted. That scenario is back in the legal gray zone after the Eleventh Circuit ruling, but plaintiff's lawyers still challenge bundled SMS consent under the general TCPA specificity case law.
The order also touched the definition of an autodialer (ATDS), pointing to the Supreme Court's 2021 decision in Facebook v. Duguid, which narrowed ATDS to systems that use a random or sequential number generator [5]. The FCC did not try to expand that definition back out. Teams using systems that only dial from a pre-loaded list with no random number generation stay in the post-Duguid gray zone on that specific point. Consent requirements apply regardless of ATDS status for prerecorded or AI-generated voice calls.
When did the FCC consent ruling take effect?
FCC 24-17 was adopted January 26, 2024, and published in the Federal Register [1]. The AI voice provisions took effect and are live now. The one-to-one consent provision was set for January 27, 2025, but never took effect, because the Eleventh Circuit vacated it on January 24, 2025, three days before the deadline [11].
The FCC built in a one-year runway on purpose. The agency knew the lead generation industry needed time to rebuild consent flows, renegotiate contracts, and audit lead databases. That work turned out to be moot for the one-to-one piece once the court struck it.
Here's the practical picture as of mid-2025. The one-to-one requirement is off the table at the federal level. The base 2012 prior-express-written-consent standard still governs. The AI voice clarification is in force.
Do not read the court win as permission to get sloppy. Plaintiff's firms still sue over vague or bundled consent under existing TCPA specificity doctrine, and some states have their own mini-TCPA statutes with stricter consent rules. Florida and Oklahoma both passed telemarketing laws with tighter consent language.
Compliance teams should still audit lead inventory by consent collection date and form language. Leads with ambiguous consent are litigation bait whether or not the FCC's one-to-one rule is enforceable this quarter.
What are the penalties for violating the consent rules after this ruling?
The TCPA penalty structure has not changed, and it is brutal by design. Under 47 U.S.C. § 227(b)(3), a consumer can recover the greater of actual monetary loss or $500 per violation [6]. If the court finds the violation was willful or knowing, that triples to $1,500 per call or text [6].
TCPA cases are almost always class actions, because the per-violation math turns even modest outreach into eight-figure exposure. A campaign that sends 100,000 texts without valid consent carries $50 million in statutory damages at $500 per text, or $150 million if the court finds willfulness.
This is not theoretical. Large companies have settled TCPA class actions for tens of millions of dollars. The cash app tcpa class action settlement and the credit one tcpa settlement show what consent failures cost at scale.
For a small outbound team, one plaintiff suing over 50 calls at $1,500 each is $75,000 in exposure before legal fees. The math is ugly at any company size.
The FCC can also issue its own forfeiture orders separate from private lawsuits. Under the agency's enforcement authority, forfeitures for TCPA robocall violations run into the tens of thousands of dollars per violation, and the FCC has issued proposed fines in the hundreds of millions against high-volume robocallers [7].
How does the ruling affect lead generators and lead buyers differently?
Lead generators (the companies running intake forms and collecting consumer data) would have carried the primary obligation to fix consent language under the vacated one-to-one rule. New forms would have needed to name each specific seller, with a distinct affirmative action per seller. That obligation is not federally enforceable right now.
Lead buyers still carry the practical burden of proving the consent they bought actually covers them. Buying a lead from a generator does not transfer the generator's liability to the buyer, and it does not shield the buyer if the underlying consent was defective. Both parties can face liability under the surviving TCPA standard.
The safest posture for lead buyers has not changed with the court ruling. Require sellers to hand over the actual consent record: timestamp, IP address, the exact form language the consumer saw, and proof that your company name appeared in that language. Put a representation and warranty in every contract that consent was collected in compliance with the TCPA and applicable state law.
LeadCompliant's free consent checker helps teams validate whether a form's language holds up before they start buying from it, which beats reading every vendor's terms line by line.
Even with the one-to-one rule vacated, the aggregator model is under pressure. State mini-TCPA laws, plaintiff's-bar litigation, and the risk of the FCC re-issuing a narrower rule all push toward tighter buyer-seller relationships. Expect the market to keep consolidating around named, documented consent rather than sprawling partner lists.
Does the ruling change anything for the Do Not Call registry?
No. FCC 24-17 did not modify Do Not Call rules, and neither did the Eleventh Circuit's decision. The National DNC Registry runs under a parallel set of regulations: 16 C.F.R. Part 310 (the FTC's Telemarketing Sales Rule) and 47 C.F.R. § 64.1200(c) (the FCC's TCPA rules) [3][8].
The two regimes interact. A consumer on the do not call list who also never gave valid consent is protected on two independent grounds. A caller without valid consent cannot use the "established business relationship" exception to the DNC rules to justify autodialed calls to cell phones, because the TCPA consent requirement is separate from the DNC exemption.
If you keep an internal suppression list and scrub against the DNC registry, keep doing it. The consent rules sit on top of DNC compliance, not instead of it.
For teams asking how to get the do not call list or how to handle mobile phone do not call list rules, those duties run alongside consent duties. Satisfying one does not satisfy the other.
What should outbound sales teams actually do right now?
The steps are not complicated, but they force real decisions about where your leads come from and how you document consent.
Audit every lead source in your current flow. For each source, get the actual form the consumer saw, including the exact consent language. Check whether your company is named and whether the consent is specific. Vague or bundled consent is litigation risk for automated outreach even after the one-to-one rule was vacated, because courts still test consent specificity under general TCPA doctrine. You can often make manual calls from those lists, but autodialed calls and prerecorded or AI voice messages need documented consent.
If you run your own intake forms, tighten the consent language. Name the seller. Get a clear affirmative action. Keep the "not a condition of purchase" disclosure inside the consent text, not buried in a policy.
Document everything. Consent records should capture the exact form text, timestamp, IP address, and the fields the consumer filled in. You want to be able to produce this in litigation or a regulatory inquiry within days.
Train your dialing team on the AI voice provisions, because those survived the court challenge and are enforceable now. If your autodialer uses AI-generated voice in any form, those calls need the same prior express written consent as prerecorded calls to cell phones.
Revisit vendor contracts. If you buy leads, add consent-compliance representations. If you sell leads, expect buyers to demand tighter consent collection anyway. Watch state mini-TCPA laws in Florida, Oklahoma, and elsewhere, which impose consent rules the federal court ruling did not touch.
For teams doing cold calling without automation, TCPA consent requirements are lighter, but DNC obligations still apply. A human manually dialing has more flexibility than an autodialer. DNC scrubbing is not optional either way.
How have courts responded to the FCC's consent interpretation?
The headline is that a federal appeals court rejected the FCC's one-to-one rule. In Insurance Marketing Coalition Ltd. v. FCC, decided January 24, 2025, the Eleventh Circuit vacated the one-to-one consent and "logically and topically related" requirements, holding the FCC exceeded its authority under the TCPA [11]. That decision is why the rule never took effect.
Step back to before the ruling, though, and courts were already reading consent strictly. The Ninth Circuit in Van Patten v. Vertical Fitness Group (2017) held that consent must be clearly given for the specific type of contact at issue [9]. The Eleventh Circuit itself had reached similar conclusions on specificity. So bundled or vague consent was risky well before the FCC acted, and it stays risky now.
The Loper Bright backdrop matters here. In Loper Bright Enterprises v. Raimondo (2024), the Supreme Court overruled Chevron deference, so courts no longer defer to an agency's reasonable reading of an ambiguous statute [10]. That shift is part of why the Eleventh Circuit felt free to strike the FCC's rule. Agency interpretations now get Skidmore-level persuasive weight at most.
Plaintiff's firms still send demand letters over weak consent, and they will keep pressing consent-specificity theories that do not depend on the vacated FCC rule. The litigation pressure is real and growing regardless of what happened to one-to-one.
Build your program on the assumption that a judge will scrutinize whether the consumer clearly agreed to be contacted by you. That assumption survives the court fight.
Does the ruling cover ringless voicemails and AI-generated calls?
Yes on AI-generated calls, and yes with some history on ringless voicemails. This is the part of FCC 24-17 that is fully alive after the Eleventh Circuit ruling, because the court struck the one-to-one consent provision, not the AI voice clarification.
On AI voice: the FCC declared that AI-generated voices, including voice cloning, qualify as "artificial or prerecorded" voices under 47 U.S.C. § 227(b)(1)(A) [2]. A call using an AI voice agent to a cell phone without prior express written consent is a TCPA violation on the same footing as a traditional robocall. This closed a gap some vendors tried to exploit by arguing AI voices were neither "artificial" nor "prerecorded" in the old sense.
On ringless voicemails (RVMs): the FCC has long treated these as "calls" under the TCPA because they use the phone network to deliver audio [2]. Vendors who marketed RVM as consent-free because "there's no ring" have been on shaky legal ground for years, and this order did not help their case.
Practically: if you use any automated or AI-assisted method to leave voice messages, send texts, or make calls to cell phones, treat it as subject to TCPA's prior express written consent standard. The label your vendor slaps on the product does not change the legal analysis.
Where can I read the actual FCC declaratory ruling?
The full text of FCC 24-17 is on the FCC's website [1]. The order runs about 100 pages including the commissioners' statements, and the operative legal interpretations sit in roughly the first 40 pages.
The Federal Register publication (February 2024) is the definitive version for effective-date purposes. The FCC's Consumer & Governmental Affairs Bureau also publishes plain-language TCPA guidance that reads easier than the full order [7].
For the statute, 47 U.S.C. § 227 is the TCPA itself, available at the Cornell Legal Information Institute [6]. The FCC's implementing regulations are at 47 C.F.R. § 64.1200, available through the eCFR [3]. For the court decision that vacated the one-to-one rule, look up Insurance Marketing Coalition Ltd. v. FCC in the Eleventh Circuit [11].
A note on reading order documents: the parts labeled "declaratory ruling" are the FCC's legal interpretations. Parts labeled "order" or "rulemaking" are binding rule changes. FCC 24-17 contained both. That is why it had teeth, and it is also why the vacated piece and the surviving piece have to be read separately.
At LeadCompliant, we track every FCC TCPA order and the court cases that reshape them, then translate the operative changes into plain-language checklists. The TCPA compliance kit includes a consent audit template you can run against your current lead sources without hiring outside counsel for a first pass.
If you want the broader TCPA framework this ruling sits inside, start with the tcpa overview before you open the order itself.
Frequently asked questions
What is the effective date of the FCC's one-to-one consent rule?
The one-to-one consent requirement in FCC 24-17 was set to take effect January 27, 2025. It never did. The Eleventh Circuit vacated it on January 24, 2025 in Insurance Marketing Coalition v. FCC, three days before the deadline. The AI voice provisions of the same order did take effect and remain enforceable.
Does the FCC consent ruling apply to B2B calls?
Mostly not directly. The TCPA's autodialer and prerecorded voice rules focus on calls to cell phones regardless of whether the recipient is a consumer or a businessperson. Prior express written consent requirements are applied most strictly to consumer solicitations. B2B calls to business landlines have more flexibility, but calling a salesperson's personal cell still triggers TCPA protections.
Can I still use a lead aggregator after the ruling?
Yes. With the one-to-one rule vacated, bundled partner consent is not automatically invalid at the federal level. But you still need consent that clearly names your company and shows an affirmative action, because courts test consent specificity under general TCPA doctrine and some states have stricter laws. Ask every aggregator for the actual form language and a sample consent record.
What counts as "one-to-one" consent under FCC 24-17?
One-to-one meant a single consumer taking a single affirmative action to authorize a single, named seller, with no bundling of multiple sellers into one checkbox, plus a subject-matter relationship to the website. The Eleventh Circuit vacated this requirement in January 2025, so it is not currently enforceable federally. The base 2012 prior-express-written-consent standard still applies.
Does the ruling affect text message marketing specifically?
The AI voice and general consent rules apply to texts, since the FCC treats SMS and MMS sent via autodialer the same as autodialed calls to cell phones. The vacated one-to-one requirement would have hit SMS co-registration hard. With it vacated, bundled text consent is back in a legal gray zone, but plaintiff's lawyers still challenge vague SMS consent under existing TCPA specificity case law.
How does the FCC's AI voice ruling change things for sales teams using AI dialers?
FCC 24-17 declared that AI-generated voices are 'artificial or prerecorded' voices under 47 U.S.C. § 227(b)(1)(A), and this provision is enforceable. Outbound calls using AI voice agents to cell phones require prior express written consent, the same as traditional robocalls. Teams that switched to AI voice thinking it created a gray zone are clearly inside TCPA's requirements.
What documentation do I need to prove valid consent after the ruling?
The exact form language the consumer saw, the specific affirmative action they took, your company name in that language, the consumer's phone number as entered, a timestamp, and the IP address. Courts and the FCC expect this specificity, and it is your best defense in litigation. Screenshots or PDF captures of the live form at the time of consent are worth preserving.
Does FCC 24-17 change the Do Not Call registry rules?
No. The DNC registry runs under separate FTC and FCC regulations and was not modified by FCC 24-17 or by the Eleventh Circuit's decision. The two regimes work together. A consumer on the DNC list who also never gave valid consent is protected on two independent grounds. DNC scrubbing stays mandatory regardless of your consent status.
What happens if I already have a large database of leads with old bundled consent?
With the one-to-one rule vacated, those leads are less risky federally than they would have been, but bundled consent is still litigation bait under general TCPA specificity doctrine and state mini-TCPA laws. Safest options: get fresh, specific consent before autodialing, use manual dialing while checking DNC status, or document that the original consent clearly named you. Do not assume the court win makes old forms bulletproof.
Can consumers revoke consent after giving it under the new rules?
Yes, and this was not affected by the court ruling. Consumers have always had the right to revoke consent at any time through any reasonable means under FCC guidance. A consumer who texts STOP, emails a request, or tells a caller verbally to stop must be removed from automated contact promptly. Companies may designate opt-out channels but cannot make revocation unreasonably burdensome.
Is the FCC's declaratory ruling legally binding or just guidance?
It was binding agency interpretation, but a federal appeals court vacated the one-to-one consent portion in January 2025, so that part is not enforceable. The AI voice clarification stands. Post-Loper Bright, courts no longer give FCC readings Chevron deference; they treat them as persuasive at most, which is part of why the Eleventh Circuit struck the one-to-one rule.
What is the TCPA penalty per text message for violating the consent rules?
The TCPA provides $500 per violation, which courts read as $500 per text or call. If the violation is willful or knowing, courts may award up to $1,500 per message. Because TCPA cases are class actions, 100,000 texts without valid consent means $50 million in potential statutory damages at the base rate, before any trebling.
Do cold calls made by a live human require prior express written consent?
Not for TCPA autodialer purposes, if the call is truly manual with no automated dialing technology. A human agent manually dialing does not trigger the TCPA's autodialer consent requirements. But that caller still must follow DNC registry rules, internal suppression lists, and calling-hour limits. FCC 24-17's consent provisions targeted automated calls and texts, not manual dialing.
Where can I find the actual text of FCC 24-17?
The full order is on the FCC's website at fcc.gov; search for 'FCC 24-17' in the document search. The Federal Register publication from February 2024 is the official version for effective-date purposes. For the case that vacated the one-to-one rule, look up Insurance Marketing Coalition Ltd. v. FCC in the Eleventh Circuit.
Sources
- FCC, Report and Order and Further Notice of Proposed Rulemaking, FCC 24-17 (Jan. 26, 2024), available via the Federal Register: FCC 24-17 adopted January 26, 2024, aimed to close the lead generator loophole and require one-to-one prior express written consent per named seller, with an intended effective date of January 27, 2025.
- Electronic Code of Federal Regulations, 47 C.F.R. § 64.1200: FCC implementing regulations for the TCPA, including the prior express written consent definition at § 64.1200(f)(9) and DNC rules at § 64.1200(c).
- FCC, Consumer Help Center guidance on unwanted texts and calls: FCC treats SMS and MMS sent via autodialer the same as autodialed calls to cell phones under the TCPA.
- Supreme Court of the United States, Facebook Inc. v. Duguid, 592 U.S. 395 (2021): Supreme Court narrowed the ATDS definition to systems that use a random or sequential number generator, limiting TCPA autodialer claims.
- Cornell Legal Information Institute, 47 U.S.C. § 227 (Telephone Consumer Protection Act): TCPA provides $500 per violation in statutory damages, trebled to $1,500 for willful or knowing violations, under 47 U.S.C. § 227(b)(3).
- FTC, Telemarketing Sales Rule, 16 C.F.R. Part 310: National DNC Registry operates under the FTC's Telemarketing Sales Rule at 16 C.F.R. Part 310, parallel to the FCC's TCPA rules.
- Ninth Circuit Court of Appeals, Van Patten v. Vertical Fitness Group LLC, 847 F.3d 1037 (9th Cir. 2017): Ninth Circuit held consent must be clearly given for the specific type of contact at issue, supporting stricter consent specificity readings.
- Supreme Court of the United States, Loper Bright Enterprises v. Raimondo, 603 U.S. 369 (2024): Supreme Court overruled Chevron deference in 2024; agency rulings now receive Skidmore-level persuasive weight rather than binding deference in federal courts.
- Eleventh Circuit Court of Appeals, Insurance Marketing Coalition Ltd. v. FCC (decided Jan. 24, 2025): Eleventh Circuit vacated the FCC's one-to-one consent and 'logically and topically related' requirements, holding the FCC exceeded its statutory authority; the requirements never took effect.