Article summary:
Was one-to-one consent struck down? Yes. The Eleventh Circuit vacated the FCC’s one-to-one rule in Insurance Marketing Coalition v. FCC (Jan. 24, 2025). The FCC can still make changes if it decides to move forward with one-to-one consent in the future.
So why do people still care? Because proving you had permission is still the safest way to keep texting and calling programs running smoothly.
What should I do now? Run your program as if tighter rules could return in some form with brand-specific opt-ins, clean disclosures, and audit-ready records.
What helps operationally? A consent repository that stores who consented, what they consented to, and how you prove it.
What Happened in the Eleventh Circuit Court and Prior Express Written Consent?
Here’s the twist nobody expected: the FCC’s one-to-one consent rule didn’t survive court review. The Eleventh Circuit, on January 24, 2025, vacated the FCC’s one-to-one TCPA (Telephone Consumer Protection Act) consent rule in Insurance Marketing Coalition v. FCC.
And later, the FCC moved to clean up the rule text that had been nullified. So. . .are we done talking about one-to-one consent?
Not even close.
While the rule got struck down, the industry direction did not: carriers, platforms, compliance teams, and courts still err on the side of consumer protection, keeping the standard of clear permission + fast opt-outs + easy proof in full effect.
Law firms, including Perkins Coie, have advised businesses after the vacatur basically said: the one-to-one rules are “gone for now,” but you still need to meet the underlying consent requirements and be ready for what comes next. (We’re not lawyers and aren’t advising you on what you should specifically do, but we want to provide the pertinent information that’s out there.)
Why the One-to-One Consent Rule Still Matters Even After It Was Vacated
A rule can disappear from the Code of Federal Regulations, but the problem that created it doesn’t vanish.
The FCC tried to close what many called the lead-generator loophole, where one broad checkbox (“marketing partners”) could lead to a flood of calls and texts from multiple sellers. The FCC’s own one-to-one consent rule materials spelled out the idea: consent tied to a single seller, often with separate checkboxes per seller on comparison sites.
The court then held that the FCC overstepped its authority, and the rule was vacated. But here’s what didn’t change:
Consumers still expect “I gave you my number” to mean you, not the entire orbit of your partner network.
Businesses still need to respond quickly when a customer says “STOP.”
Compliance teams still need proof that holds up under the pressure of complaints, disputes, internal reviews, or audits.
Plus, there’s always a chance the FCC (or Congress, or state-level enforcement trends) pushes for stricter standards again. More than likely, in a revised form built to survive the next court test. Even legal commentary from Wiley Rein LLP on the vacatur noted paths like rehearing, Supreme Court review, or a refreshed rulemaking record.
So yes, the one-to-one rule got knocked down, but it’s unclear if it’s out for good. With that in mind, one-to-one discipline is still how mature organizations keep messaging programs healthy.
What Is One-to-One Consumer Consent in the Simplest Terms?
Forget the legal phrasing for a second. One-to-one consent means the customer’s “yes” is clearly tied to a specific sender (seller/brand) and a clear purpose.
Not:
“us and our partners”
“selected providers”
“marketing affiliates”
But:
Your brand name
Your use case (appointments, account updates, promos, whatever it is)
A clear way to opt out
That’s it. Straightforward and clear.
Can Consent Apply to Multiple Brands?
Yes, when the customer makes the choice to.
The one-to-one approach, when it was still alive, generally expected that if multiple sellers or brands want consent, the consumer should be able to choose them specifically, often through separate selections.
Practical rule of thumb
If you take a moment, step back, and evaluate your opt-in language, and there’s any question that it would make a reasonable customer say, “Wait. . .who is going to text me?”, get back to the drawing board because it’s too vague.
Unclear verbiage like “partners” gets you in trouble because it blurs responsibility.
Key Takeaways: What Actually Changed and What Didn’t
What changed
The Eleventh Circuit vacated the FCC’s one-to-one consent rule.
Later, the FCC formally eliminated the one-to-one requirement from its rules.
What didn’t
The TCPA still centers on prior express consent, and in many cases, prior express written consent for certain calls/texts.
The FCC continues to strengthen consumers’ ability to revoke consent and expects businesses to honor revocation quickly.
Unwanted robocalls and texts remain a major FCC consumer priority.
Translation: even without one-to-one as a formal rule, your operational standard still needs to prove it.
Take a moment to read our comprehensive TCPA Compliance Texting article
Operational Consequences for Businesses with Clear and Conspicuous Disclosure
When you run consent with purpose, it becomes specific and provable, then a few things get easier fast:
1) Your teams stop guessing
You quickly lose the fear of the unknown. There’s no more searching and hoping, trying to find exactly where they opted in and for what.
2) Your customer experience gets cleaner
There’s an added layer of trust with customers when they recognize the communication.
3) Your compliance team stops playing detective
You can pull proof quickly instead of hunting for screenshots.
4) You reduce reaching out to the wrong person
Phone numbers get reassigned. The FCC’s Reassigned Numbers Database exists to help prevent contacting someone who inherited a number that used to belong to your customer.
Shared Consent vs. Proof-Ready Consent
What you’re doing today | What it looks like in real life | Why it breaks | Proof-ready fix (what to store) |
“Partners” opt-in language | One checkbox covers many senders | The customer didn’t pick you | Brand name, disclosure text, timestamp, capture source |
Consent stored in 3 systems | Marketing has a list, support has a list, sales has a list | Opt-outs don’t sync | One consent repository with one suppression truth |
STOP handled manually | Agent sees STOP, forgets to log it | The customer keeps getting texts | Auto-enforce STOP across senders + time-stamped logs |
Proof = screenshots | “Here’s a screenshot of the form. . .I think” | Hard to defend and easy to fake | Exportable record pack: consent + messages + revocation |
Why a Consent Repository Matters
A consent repository is the boring hero your messaging program needs. It’s where you keep a living record of:
Who opted in
What they opted in to
Which brand(s) can contact them
When they opted out
How Permissions.com Helps You Stay Ahead of the Next Shift
Even though the one-to-one rule was vacated, many organizations are choosing to operate as if tighter consent standards could return because it’s operationally smarter to do so.
That’s where Permissions.com fits: it’s built to capture, prove, and share proof of consent at scale. So when someone asks, “Why did we text this person?” you have a confident answer you can back up.
And for teams that text inside Microsoft Teams, RingCentral, Zoom Phone, or Cisco Webex, the goal is simple: to make adoption as painless as possible. Permissions powered by Approved Contact’s approach is built around texting from the same business numbers that teams already use, inside the tools they already live in, so the user experience feels like normal mobile texting with basically zero training.
One important security note: SMS texting does not provide end-to-end encryption. That’s why a serious program focuses on policy, retention, and inspection, like DLP and eDiscovery-ready records, so you can see and control what’s being sent.
To dig into the compliance foundation and how to make it operational, start here:
A simple checklist to safeguard yourself even without the rule
Name the sender: Use brand-specific opt-ins whenever possible.
Store proof: Source URL, timestamp, disclosure text, and capture method.
Make STOP work everywhere: Not “eventually.” Not “in one system.” Everywhere.
Reduce reassigned-number mistakes: Use tools like the FCC’s RND where it fits.
Run a complaint drill: Can you produce a full record in under 10 minutes? If not, you don’t have a complete system yet.
Final Rule: One-to-one consent isn’t the law, but it’s the cleanest way to run messaging
Yes, the FCC’s one-to-one consent rule was vacated, and the FCC later removed the requirement from its rules. But the improved communication world it pointed to with specific permission + provable records + fast revocation is still where modern messaging is headed.
If you want to be ahead of the next shift (in whatever shape it takes), properly build your program now so proof is easy, opt-outs are automatic, and your teams don’t need a compliance manual taped to their monitors.
That’s exactly what Permissions.com is designed to support. Contact us to learn more or instantly book a demo to see what the system can do.
