TL;DR
- The Stop Spam Calls Act is a legislative proposal, not a reason to announce that the FCC’s one-to-one consent restriction has returned to force.
- The sponsor’s released text would direct the FCC to restore a specified version of its prior express written consent definition. That version includes authorization of no more than one identified seller and a logical and topical connection between the consent interaction and subsequent covered calls or texts.
- The released text gives the FCC one year after enactment to revise the definition and makes the revised definition applicable 18 months after enactment. Neither period runs from the introduction announcement.
- Lead buyers can prepare by connecting the seller, disclosure, consumer action, telephone number, and source interaction in a retrievable record. Those are recommended readiness controls, not new duties created by an announcement.
- Seller-specific consent and lead exclusivity are different: permission to contact does not itself establish that a lead was sold only once.
Overview: Prepare the Evidence, Not an Imaginary Deadline
The latest one-to-one consent discussion gives lead buyers a familiar operational problem: how do you prepare for a possible rule change without misrepresenting what the law requires today?
On September 24, 2026, Representatives Suhas Subramanyam and Jefferson Shreve announced the Stop Spam Calls Act. The proposal drew renewed industry attention during the week of October 6–12. Its core mechanism is specific: direct the FCC to revise a regulatory definition by reference to language published in January 2024.
This guide analyzes the sponsor-released proposal, not an enacted statute or a final implementing order. The linked PDF is draft legislative text with an unfilled bill number; it should not be mistaken for proof of the latest congressional action. Check the legislative record for subsequent versions before making implementation decisions.
For operations teams, the useful response is neither an emergency form rewrite nor business as usual. It is a targeted readiness review: can your systems show which seller a consumer authorized, in what interaction, and before which contact? That question remains useful even if the proposal changes or never becomes law.
What the Proposal Actually Says
Section 2(a) of the sponsor’s released text would require the FCC, within one year of enactment, to revise 47 CFR § 64.1200(f)(9), or its successor, to the version published at 89 Federal Register 5098 on January 26, 2024.
That cross-reference matters. To understand the proposal, read the referenced regulatory text, not just the bill’s short title or a summary of its purpose.
The referenced definition describes a signed written agreement that clearly and conspicuously authorizes no more than one identified seller to deliver, or cause delivery of, advertising or telemarketing messages using an automatic telephone dialing system or an artificial or prerecorded voice. It also identifies the authorized telephone number and requires calls and texts to be logically and topically associated with the interaction that prompted consent.
The definition includes disclosures about the covered contact and that signing is not a condition of purchasing property, goods, or services. It recognizes electronic or digital signatures to the extent valid under applicable law.
This is not a proposal to require a handwritten signature before every sales conversation. Nor should “one-to-one” be translated into a blanket ban on comparison shopping. The referenced order discusses ways a comparison site could let consumers choose individual sellers or proceed to a seller’s own consent flow. The relevant unit is the authorization, not a prohibition on considering multiple businesses.
Why the 2025 Court Decision Still Matters
On January 24, 2025, the Eleventh Circuit decided Insurance Marketing Coalition Ltd. v. FCC, No. 24-10277. The court vacated Part III.D of the FCC’s 2023 order and remanded for further proceedings. It held that the one-to-one and logical-and-topical restrictions conflicted with the statutory meaning of “prior express consent” and exceeded the agency’s authority.
The opinion expressly says the FCC’s 2012 order was not at issue in that case. That distinction prevents two opposite mistakes: treating the vacated restrictions as an operative nationwide mandate, or treating the decision as eliminating every consent obligation.
The new proposal would have Congress direct a regulatory revision. Its section 2(c) also contains a rule of construction addressing the FCC’s pre-enactment authority to require written consent. A proposed legislative response and a judicial holding are different legal events. Announcing the former does not reverse the latter.
The practical lesson is narrow: do not label the January 2024 one-to-one language “current law” merely because it appears in a Federal Register final-rule document. Its litigation history is part of the source review. This guide does not attempt to resolve every later consent dispute or jurisdiction-specific issue; campaign decisions still require review of applicable law and current case law.
Which Dates Are Real, and Which Are Conditional?
The sponsor-released text has two separate clocks:
- Regulatory revision: no later than one year after enactment.
- Applicability: the revised definition takes effect beginning 18 months after enactment.
September 24, 2026 is the date of the introduction announcement. It is not the enactment trigger specified in the proposal. Do not add 18 months to that announcement and enter the result as a binding compliance deadline.
A useful change tracker separates the source date, legal status, triggering event, and responsible owner. An introduction announcement belongs in legislative monitoring. An enacted text, if one emerges, would require a new review of the actual language and deadlines. An FCC implementation document would then need its own review rather than being assumed to match an earlier draft.
This distinction also applies to agency notices. For example, the FCC’s September 4 public notice, DA 26-940, sets October 19, 2026 as the reply-comment date for petitions involving political artificial-voice calls and peer-to-peer texting. The notice seeks comment; it does not itself grant the requested relief or change the rules for commercial lead campaigns. A comment deadline is not an authorization to launch.
Build a Seller-Level Evidence Map
Start with a recent lead and follow it from the source interaction through the intended buyer. The goal is to see whether the record supports a concrete account of what happened, rather than a generic “consent captured” flag.
Seller identity. Record the consumer-facing seller name and the internal identifier used for routing. If a trading name differs from the contracting entity, preserve the mapping. A downstream buyer identifier added after submission does not, by itself, show that the consumer authorized that buyer.
Disclosure and presentation. Preserve the actual disclosure version and relevant page context. A screenshot of today’s form cannot establish yesterday’s dynamically rendered seller selection. Capture enough context to explain what the consumer was offered, without collecting unrelated personal information.
Consumer action and number. Connect the action relied upon as assent with the relevant disclosure, time, and telephone number. A completed form event is evidence to evaluate, not an automatic legal conclusion that the required consent exists.
Topic and intended contact. Preserve the source interaction’s subject and the campaign purpose. Treat a move from a home-repair inquiry into an unrelated product campaign as a separate review question. The proposal’s topical language should not be converted into an improvised universal taxonomy; the referenced order declined to define “logically and topically.”
Integrity and access. Retain a stable reference to the record, control access, and document material corrections. An evidentiary record that cannot be retrieved when a complaint arrives has limited operational value. Our lead consent documentation guide explains the broader capture-and-retention workflow.
These are recommended controls for understanding and testing a process. They do not guarantee valid consent, establish a statutory safe harbor, or replace campaign-specific legal analysis.
Keep Consent Separate From Exclusivity
A seller-specific authorization answers a permission question: did this consumer authorize the relevant contact from this seller?
Exclusivity answers a distribution question: under the applicable commercial arrangement, who else received or may receive this lead?
Those questions can have different answers. A consumer might separately choose two sellers through a comparison experience. Conversely, a lead sold exclusively to one buyer could still lack the authorization needed for that buyer’s planned contact. Neither a single-buyer delivery log nor a seller-named disclosure proves both concepts.
Keep the records separate but linked. Consent evidence should describe the interaction and authorization. Distribution evidence should describe transfers, recipients, contractual restrictions, and the limits of your visibility into resale. Avoid promising absolute non-resale based only on the transactions your own platform can observe. The guide to proving exclusivity and intent explores why evidence must match the claim being made.
A Practical Readiness Checklist for Buyers and Publishers
Use a small, representative sample from your highest-volume sources before expanding the review. These are internal readiness tasks, not a claim that the proposed bill has imposed them.
- Assign a source owner. Someone should monitor the official legislative record and distinguish sponsor materials from subsequent bill versions.
- Label policy accurately. Mark each control as existing legal advice, contractual requirement, proposed-change preparation, or voluntary practice.
- Reconstruct actual sessions. For sampled leads, retrieve the seller presentation, disclosure, consumer action, number, and timestamps together.
- Test routing changes. Review what happens when the buyer selected by an auction differs from the seller shown during the consent interaction. Do not assume that updating metadata repairs authorization.
- Review fallback paths. Include mobile layouts, failed scripts, duplicate submissions, and situations where the preferred buyer rejects a lead.
- Separate evidence gaps from legal conclusions. Missing source evidence calls for investigation; a complete file still requires evaluation of the actual disclosure and contact.
- Keep contact controls independent. A readiness project does not replace applicable suppression, revocation, calling-time, or other campaign controls.
- Plan access and retention. Determine who can retrieve records, how vendor termination affects access, and how retention fits legal requirements and data-minimization needs.
- Make changes reversible. Version consent language and routing policy so teams can evaluate proposed changes without silently rewriting the historical record.
Ask vendors to demonstrate these capabilities using a sample, not just a contractual assurance. The lead source tracking guide provides a complementary framework for following records across intermediaries.
Key Takeaways
The Stop Spam Calls Act proposal is a reason to prepare, not a basis for inventing an effective date. Its released text points to a particular consent definition and contains clocks tied to enactment. The earlier court vacatur must remain part of any accurate explanation of that definition.
For lead buyers, the durable work is concrete: make seller identity, disclosure, consumer action, source context, and downstream routing explainable together. Keep distribution promises separate from permission to contact, and distinguish internal risk controls from legal mandates.
Before the next supplier review, choose a handful of recent leads and ask one question: can we show why this seller was entitled to make this particular contact? Use the gaps in that demonstration to set the next improvement priority.