What is an example of prior written notice?

Why One Badly Worded Consent Sentence Can Cost You $1,500 Per Call

A single poorly worded consent sentence can trigger TCPA penalties ranging from $500 to $1,500 per call, with lawsuits able to reach back four years — and liability falls squarely on the caller, not the lead generator. Industry research confirms this burden of proof rests entirely on the business making the call, meaning lead buyers like GrowthPros’ clients face direct financial exposure if consent language is deficient. This risk is amplified by the 2025 regulatory shake-up: the Eleventh Circuit vacated the FCC’s one-to-one consent rule, creating confusion rather than clarity, as state-level requirements in Florida, Oklahoma, and Maryland still mandate explicit seller disclosure. The FCC formally abandoned the rule, but failing to name sellers explicitly in consent disclosures remains a critical vulnerability in plaintiff-heavy jurisdictions.

Many businesses struggle to distinguish valid prior written notice from invalid versions, often overlooking structural details that invalidate consent despite seemingly clear language. For example, a disclosure that names "calls" but omits "text messages" fails to authorize SMS outreach, even if the intent seems obvious. TCPA attorney John H. Henson warns that such omissions do not authorize text messages, and capturing the phone number on a separate page from the consent language is another common failure mode that voids validity. To satisfy TCPA requirements, prior written notice must include an affirmative act (like an unchecked checkbox), disclose each channel separately (calls AND texts), name the technology used (ATDS, prerecorded/artificial/AI voice), state the marketing purpose clearly, and include the unambiguous statement that consent is not a condition of purchase — all presented in the same field of view with equal prominence.

A compliant example of prior written notice for a single-seller flow is: "By clicking 'Accept' below, I am providing my E-SIGN signature and expressly consent to {COMPANY}, directly or by third parties acting on its behalf, to send marketing and promotional messages — including text/SMS and/or calls made using an automatic telephone dialing system, pre-recorded or artificial voice messages, or AI-generated voice — related to the product or service I am inquiring about, to the number I provide above. Accepting this consent is not required to obtain any good or service." This template from Henson Legal includes every required element: named channels, explicit technology disclosure, topical scope, and the consent-not-required statement. For capped-shared leads — like those GrowthPros delivers to a maximum of two buyers — the multi-seller version is essential: "By clicking 'See My Quotes,' I expressly consent to each of the {#} {PRODUCT} providers listed at the link below — and {COMPANY} on their behalf — contacting me at the telephone number I provided, by call, pre-recorded or artificial voice, AI-generated voice, or text message, including with an automatic telephone dialing system, about {PRODUCT/SERVICE}. The full list of providers is shown here: [DIRECT LINK TO NAMED-SELLER LIST]. Accepting this consent is not required to obtain any good or service." This version satisfies both federal expectations and state-level named-seller rules by making seller identity transparent and directly accessible.

Ultimately, the consent sentence is only half the equation; the real protection lies in the consent record. Best practices require retaining the disclosure text, timestamp, signature, and telephone number for at least five years — the stricter of the TCPA’s 4+ year statute of limitations and the TSR 2024 amendments. GrowthPros builds this architecture into every lead: consent-recorded, time-stamped, and tied to a specific seller, ensuring clients receive not just a contact, but a defensible compliance trail that shifts risk away from the buyer and onto a verifiable process.

Two Copy-Ready Examples of Compliant Prior Written Notice

Many lead generators struggle to craft consent language that satisfies both federal and state TCPA requirements. Below are three copy-ready examples of prior written notice that meet current compliance standards, each designed for different lead-generation scenarios.

The first example is the standard single-seller template from TCPA attorney John H. Henson, ideal for exclusive lead flows: "By clicking 'Accept' below, I am providing my E-SIGN signature and expressly consent to {COMPANY}, directly or by third parties acting on its behalf, to send marketing and promotional messages — including text/SMS and/or calls made using an automatic telephone dialing system, pre-recorded or artificial voice messages, or AI-generated voice — related to the product or service I am inquiring about, to the number I provide above. Accepting this consent is not required to obtain any good or service." This language works because it names each communication channel separately (calls AND texts), specifies the technology (ATDS, prerecorded/artificial/AI voice), states the marketing purpose, identifies the named seller ({COMPANY}), and includes the critical "not required to obtain any good or service" statement. For GrowthPros’ exclusive leads by niche, this template ensures every consent record captures the required elements while supporting their AI Speed-to-Lead follow-up process.

For capped-shared or comparison-shopping leads, Henson’s multi-seller template provides compliance when multiple sellers are involved: "By clicking 'See My Quotes,' I expressly consent to each of the {#} {PRODUCT} providers listed at the link below — and {COMPANY} on their behalf — contacting me at the telephone number I provided, by call, pre-recorded or artificial voice, AI-generated voice, or text message, including with an automatic telephone dialing system, about {PRODUCT/SERVICE}. The full list of providers is shown here: [DIRECT LINK TO NAMED-SELLER LIST]. Accepting this consent is not required to obtain any good or service." This version satisfies TCPA requirements by naming sellers explicitly via a direct link, separately authorizing calls and texts, disclosing the use of automated technology (including AI-generated voice), tying consent to a logical product/service scope, and including the consent-not-required clause. It aligns with GrowthPros’ capped-shared lead model, where leads go to a hard maximum of two buyers, and supports their compliance stance that every lead carries a consent trail with timestamp, signature, and telephone number.

A simpler alternative appears in ActiveProspect’s guidance: "I consent to receive marketing calls and texts from [Company Name] using automated technology. Consent is not a condition of purchase." This checkbox-style language meets core TCPA standards by naming both calls and texts, disclosing automated technology, stating the marketing purpose, identifying the seller, and including the consent-not-required statement. While less detailed than the Henson templates, it remains valid for straightforward opt-in flows where brevity is preferred, provided it is presented as an unchecked checkbox tied to an affirmative action and captured with a full consent record. Regardless of template choice, retaining the consent record — including disclosure text, timestamp, signature, and phone number — for at least five years is essential, as this exceeds both the TCPA’s 4+ year recommendation and the TSR 2024 recordkeeping amendment.

The Five Structural Elements That Make or Break the Notice

The perfect consent sentence can still lose in court. TCPA attorney John H. Henson puts it bluntly: "Consent language is the sentence on the form. Consent architecture is the system that captures it, stores it, links it to a specific lead and a specific seller, retains it for at least five years, and produces it on demand" (Henson's consent-language guide).

1. An affirmative act, separate from Submit. Consent must come from an unchecked checkbox or button click tied directly to the disclosure — never a pre-checked box, and never bundled into the form submission itself (ActiveProspect's TCPA compliance breakdown). The disclosure text should also state expressly that clicking constitutes an authorized electronic signature under the E-SIGN Act.

2. Disclosure above the button, same size, same field of view. The notice must sit above the action element, in the same text size and the same field of view as the consent statement — including the "consent is not required to obtain any good or service" language. Small or hidden text invalidates the whole notice (per ActiveProspect).

3. Phone number captured on the same page. The number the consumer authorizes must be collected on the same page as the consent language. Splitting the two across pages is one of the two most common failure modes Henson identifies in insurance lead gen.

4. Sellers named in the disclosure itself. The seller must appear in the disclosure text — not buried in a linked privacy policy. Even after the Eleventh Circuit vacated the FCC's one-to-one consent rule in Insurance Marketing Coalition v. FCC, named-seller requirements persist in Florida, Oklahoma, and Maryland. Henson warns that a platform relaxing its practices after the vacatur "will pass federal scrutiny and fail state scrutiny in the most plaintiff-heavy jurisdictions in the country."

5. Every channel and technology named explicitly. A disclosure that names "calls" but not "text messages" does not authorize text messages (per Henson). The notice must separately name each channel and technology:

• Text/SMS/MMS and calls, each named separately
• ATDS, prerecorded or artificial voice, and AI-generated voice (per the FCC's February 2024 ruling)
• Marketing/promotional purpose, tied to "logically and topically related" products
• Any third parties acting on the seller's behalf, including dialing and AI voice vendors

The stakes explain why architecture matters: TCPA violations run $500 to $1,500 per call, with lawsuits reaching back four years. And the burden of proof falls on the caller, not the lead generator — the business making the call pays for someone else's sloppy form. That liability structure is why GrowthPros attaches a full consent record — disclosure text, timestamp, IP address, and named contacting party — to every lead it delivers, so buyers can prove the architecture, not just recite the sentence.

Get the sentence right and lose the audit trail, and you lose the case. Get both right, and the notice holds.

The 2025 Rule Change — and Why You Shouldn't Relax Anyway

If you heard the FCC's one-to-one consent rule died in 2025 and figured your consent language could loosen up, that instinct could cost you $500 to $1,500 per call. The federal rule is gone — but the risk isn't.

In Insurance Marketing Coalition Limited v. FCC, 127 F.4th 303 (11th Cir. 2025), the Eleventh Circuit vacated the FCC's one-to-one consent requirement, holding that "prior written consent" only demands "clear and unmistakable" information about receiving robocalls from various possible sellers — and that consent can be valid even on a website with no logical or topical relationship to the call. The FCC declined to challenge the decision and formally eliminated the rule shortly after.

That's the good news. Here's why you shouldn't relax anyway.

Three states still mandate named-seller consent at the state level. According to TCPA compliance analysis, Florida's FTSA, Oklahoma's OTSA (which explicitly requires the specific number authorized), and Maryland's Stop the Spam Calls Act all continue to require that consent name the seller. A platform that relaxes its practices after the Eleventh Circuit ruling, as attorney John Henson warns, "will pass federal scrutiny and fail state scrutiny in the most plaintiff-heavy jurisdictions in the country."

The practical math is brutal: TCPA lawsuits can reach back four years, and the burden of proving valid consent falls on the caller — the business making the call, not the lead generator. If you buy leads whose consent doesn't name you, you're the one holding the liability.

So what does best practice look like post-vacatur?

• Keep naming sellers explicitly in every disclosure — it satisfies Florida, Oklahoma, and Maryland, and future-proofs you if the FCC revisits the rule.
• Treat "logically and topically associated" scope as still alive. The vacatur lifted the federal requirement, but the concept survives as an interpretive principle — the FCC's own example warned that a car-loan comparison site doesn't consent consumers to loan consolidation calls.
• Capture the phone number on the same page as the consent language, and never bury the seller list in a linked privacy policy.
• Retain consent records for at least five years — the stricter standard under the TSR 2024 recordkeeping amendments, 16 C.F.R. § 310.5(a)(8).

This is exactly why GrowthPros built one-to-one consent discipline into its lead process from day one rather than waiting for the regulation to force it — every lead delivers with its disclosure text, timestamp, and named contacting party attached. As the FCC itself noted, nothing about the vacatur prohibits comparison-shopping websites from obtaining leads through valid, seller-specific consent.

The rule disappeared. The standard it set is still the safest one on the board.

Keep the Receipt: Consent Records Are the Real Product

Getting the consent sentence right is only half the battle. The other half — the part that actually wins or loses TCPA cases — is the record behind it.

TCPA attorney John H. Henson draws the line sharply: "Consent language is the sentence on the form. Consent architecture is the system that captures it, stores it, links it to a specific lead and a specific seller, retains it for at least five years, and produces it on demand. Get the sentence right and lose the audit trail and you lose the case" (Henson's compliance analysis). In other words, the sentence is cheap. The receipt is the product.

The retention stakes are concrete. Compliance guidance recommends keeping signed consent records — including date, signature, and telephone number — for the full TCPA statute of limitations period of four or more years, since TCPA lawsuits can reach back that far with penalties of $500 to $1,500 per call (ActiveProspect's TCPA guidance). The 2024 amendments to the Telemarketing Sales Rule go further, mandating retention of consent records for at least five years under 16 C.F.R. § 310.5(a)(8) (Henson's recordkeeping breakdown).

A defensible consent record typically includes:

• The exact disclosure text the consumer saw, with channels and technology named
• A timestamp and the consumer's electronic signature
• The telephone number, captured on the same page as the consent language
• The IP address and the named contacting party
• A storage and retrieval system that can produce all of it on demand

Here is the part most lead buyers miss: the burden of proof sits with the caller, not the lead generator. Under the TCPA, the business making the call or text is liable if the consent turns out to be invalid — not the website that sold the lead (per ActiveProspect). Buy a lead without its consent trail and you have bought the seller's compliance risk along with it.

This is why GrowthPros treats the consent record as part of the deliverable, not an afterthought. Every lead arrives with its full trail attached — disclosure text, timestamp, IP address, and the named contacting party — and DNC-scrubbed before any outbound contact, so buyers inherit defensible documentation instead of an evidentiary gap.

Bot-submitted leads carry no valid consent at all, which makes provenance checking part of the same equation (ActiveProspect notes). A lead you cannot trace is a lead you cannot defend.

If you want leads that arrive with their paperwork — exclusive or capped-shared by niche, consent-recorded, and followed up inside five minutes — book the 15-minute qualification call. It's free, honest about fit, and commits you to nothing.