Quick answer: The FCC "one-to-one consent" rule — aimed at comparison-shopping websites that sold a single online form consent to many sellers — was adopted in December 2023 and would have added a requirement that a consumer's consent name one seller at a time. The Eleventh Circuit vacated it in IMC v. FCC (January 2025) before it ever took effect, holding that the agency exceeded its statutory authority given the statutory term "prior express consent" found in the TCPA. Nothing in the vacating weakened the base TCPA prior-express-written-consent requirements that have always applied to telemarketing with an autodialer or prerecorded voice, and neither state mini-TCPAs nor your lead providers' contractual consent requirements went away with it. What must still be captured — on every lead source, whatever the rule's status — is a consent record with the source, the timestamp, the scope, the exact disclosure language shown, and the identity of the seller the consumer agreed to hear from.
This is an industry-news explainer in the same family as the TCPA quiet-hours and state-window overlap post — external regulatory movement plus the tenant-owned posture for meeting it. Nothing described here is an Orbit product change; the hooks at the end point at shipped audience, dialer, and settings surfaces. None of this is legal advice — it is the state of the law as published, and the record-keeping pattern your counsel can audit.
What the rule was, and where IMC v. FCC left it
The Telephone Consumer Protection Act restricts telemarketing calls placed with an automatic telephone dialing system or an artificial or prerecorded voice to those made with the called party's prior express consent. The December 2023 FCC order targeted a specific industry practice: comparison-shopping and lead-generator websites that show a consumer one checkbox — buried under marketing partner lists — and sell that one "consent" to dozens or hundreds of sellers at once. The adopted rule would have required that a valid consent be "one-to-one": it had to identify a single seller and could not be transferred to others. The order also tightened the "topically related" scope test, requiring robocall and robotext content to be logically related to the transaction that prompted the consent.
The rule never took effect. The Eleventh Circuit vacated it in IMC v. FCC (Insurance Marketing Coalition v. FCC) in January 2025, ruling on the petition before the effective date arrived, on the grounds that imposing one-to-one consent exceeded the FCC's statutory authority over what "prior express consent" means in the TCPA. The result: the pre-vacating status quo — the FCC's long-standing consent doctrine and the Telemarketing Sales Rule's written-consent requirements — continued as before, and the comparison-shopping industry kept the framework it had operated under. The rule is vacated, not pending, and the FCC has not as of this writing re-adopted a successor.
The bottom line for outbound programs: the vacating restored the prior baseline, it did not remove one. Prior express written consent for autodialed or prerecorded-voice telemarketing, DNC registry and internal do-not-call rules, the federal quiet-hours window on voice dialing, and the seller-specific telemarketing disclosures under the TSR all still govern. States can and do layer their own statutes on top.
The vacating narrowed one thing: which consent scope a seller can rely on
Under the vacated one-to-one rule, a consent collected by a comparison site had to be seller-specific — a consumer's yes bound only to the seller that consumer affirmatively picked, not to the whole list. With the vacating, a seller that buys comparison-shopping leads is back to the pre-rule question: did the disclosure text this consumer saw name your company (or describe a partner list from which a consumer reasonably understood your company might call)? Courts and the FTC under the TSR still evaluate scope on the language actually presented. The narrow lesson the vacated rule formalized is still good hygiene: a consent record must capture the disclosure version as rendered, and downstream the seller's identity must be within the rendered scope. If the form named the seller, keep the lead. If it named an aggregated partner list, your counsel decides the reliance question — the platform records; it does not adjudicate.
Consent-record design: the four fields that decide discoverability
Whether you collect leads first-party, buy them from a comparison site, or import a legacy list, a consent record worth having answers four questions in litigation discovery:
- Source. Which form, campaign, web session, or provider generated the lead — captured at intake, not reconstructed later. On Orbit, contact imports and audience syncs record the source per record, so the lineage question is answered when the row lands, not when litigation arrives.
- Timestamp. The moment the consumer submitted the form — retained with its timezone — so a scope argument can be reconstructed: which form version, which partner list, was visible at that moment.
- Scope. What the consent covered: which sellers or categories were named, which channels (voice, SMS) the language authorized, and what topical relationship the offer had. Scope is language, and the language version matters.
- Language version. The exact disclosure text presented. "The checkbox said X" is only provable if the version is stored with the record. Where a list spans years of form edits, this is the field that decides a case.
Add a fifth field for seller identity: the one entity the consumer agreed to hear from. Binding the record to a named seller is the one-to-one instinct — and under the baseline rules it remains the cleanest scope fact a record can carry.
Orbit's consent surfaces — the workspace's audience consent tooling and the contact-record model (the same consent-receipt pattern the DPDP phase-II consent receipts post describes for India's DPDP regime) — store these fields per recipient so the association never depends on a parallel spreadsheet. For voice outbound specifically, the consent posture sits alongside the call recording consent rules and the known-litigator scrub the same programs run on list intake.
The surfaces on Orbit that carry the posture
The vacating changed the federal rule landscape; it changed nothing about which controls exist and who configures them. Consent and outbound configuration remain tenant-owned (Orbit is the conduit and platform; the platform does not own, mandate, or globally gate regulatory compliance):
- Audience and consent records. The audience consent tooling holds source, timestamp, scope, and language version per contact; list intake (CSV import, provider syncs, API writes) tags the consent metadata alongside the identity record so downstream sends and dials inherit the scope recorded at intake. The DPDP consent-receipts post shows the same record shape serving a different regime.
- Outbound flows and the power dialer. Outreach campaigns and the dialer operate against your inventory; the quiet-hours settings and (for US voice) the federal dialing-window guard document — shipped surfaces, not legal opinions — gate send timing per your policy and per federal statute, respectively. You configure the tenant-owned window; the federal guard is a separate, platform-wide layer that stands regardless of tenant toggles.
- Opt-outs and suppression. Opt-out lists and the message-suppression settings keep revocation recorded per channel; the TCPA quiet-hours and state-window overlap post covers the timing overlays.
The state-law overlay is untouched — and unaffected by the vacating
The federal vacating did not reach state law. Several states run their own mini-TCPAs — some tighter than the federal baseline on consent definition, others on calling windows, others on revocation language — and those statutes apply to outbound over their residents regardless of the Eleventh Circuit's reasoning. If your program treats the vacating as "consent doctrine settled" nationwide, the state overlay is the gap that surfaces. The TCPA quiet-hours vs state-window mapping posts how the federal window and stricter state windows intersect; the consent-scope mapping belongs in counsel's review of each state's enacted text.
Frequently asked questions
What was the FCC one-to-one consent rule?
Adopted in December 2023, it would have required that a consumer's telemarketing consent — collected via comparison-shopping or lead-generator websites — identify one seller at a time, rather than a transferable "marketing partners" list. It also tightened the topical-relation test for robocall and robotext content.
Is the rule in effect now?
No. The Eleventh Circuit vacated it in IMC v. FCC (Insurance Marketing Coalition v. FCC), January 2025, before the effective date, holding the FCC exceeded its statutory authority given the TCPA's "prior express consent" term. The vacating restored the pre-rule baseline.
What must we still capture for outbound consent?
A consent record per recipient with the lead source, the submission timestamp, the scope (which sellers/channels the language covered), the exact disclosure-language version, and the identity of the specific seller the consumer agreed to hear from. Prior-express-written-consent rules under the baseline TCPA and TSR still apply.
Does the vacating affect state mini-TCPAs?
No. The Eleventh Circuit's ruling concerns federal FCC authority; state statutes with their own consent definitions, calling windows, and revocation language continue to apply to outbound over their residents. Consult counsel per state.
Is any of this legal advice?
No. This is neutral industry context plus the shipped-consent-posture description; your counsel determines how the vacated rule, the baseline TCPA, TSR, and state overlays apply to your program.
The takeaway
The vacated one-to-one rule was a narrowing, not a liberation: comparison-shopping consent now sits under the same baseline doctrine it did before December 2023, which is the doctrine that always required prior express consent scoped to the language actually shown. Outbound teams that made records seller-specific during the rule's short life are in the strongest posture either way. For teams that did not, the program fix is the same fix this post prescribes: capture source, timestamp, scope, and language version per recipient, bind the consent to the specific seller the consumer picked, and let your counsel — not a platform — decide how the vacated-rule residual applies. The news is federal; the checklist is, and stays, tenant-owned.
Published 13 September 2026.