TCPA Consent Language for Lead Forms: What Insurance Agents Need on Their Own Forms

Every call you make to a lead is only as legal as the form that produced the lead. The dialer does not fix a bad form. The scrub does not fix a bad form. If the consent language on your landing page or your Facebook lead form is missing, buried, or vague, every dial and every text that follows is a dial you may have to defend with nothing behind it.

I learned this from the wrong direction. Years of buying leads taught me to interrogate other people's forms, and the first time I built my own I copied a disclaimer from a vendor page without reading it. It named a company that was not mine, promised calls from "partners," and sat below the fold in six-point gray. If a demand letter had come in during those months, I would have had a form that proved consent for someone else.

This is what the consent text on an agent's own form has to say, where it has to sit, how to get a real signature out of a checkbox, what changed and did not change with the one-to-one rule, and what to save so the form still means something a year later.

Why the form is the whole case

The TCPA treats a form-generated lead as a person who invited your call, but only if the invitation meets a specific standard. For marketing calls or texts to a cell phone using an autodialer or a prerecorded voice, the standard is prior express written consent. For calling a number on the federal Do Not Call registry, the standard is a signed written agreement giving you permission. In practice your lead form has to do both jobs at once, because you will not know which numbers are on the registry until you scrub them, and you will not want to keep two consent standards straight at dial 80.

A single-line power dialer generally is not an autodialer under the federal definition after the Supreme Court's 2021 Facebook v. Duguid decision. That helps. It does not get you out of the DNC rule, it does not cover texting, and it does not cover states such as Florida that define automated dialing more broadly than the federal courts do. The power dialer compliance guide goes into that split. The practical conclusion is that you should build every form to the written-consent standard and stop thinking about which standard applies to which call.

The five things the disclosure has to contain

The FCC rule defines prior express written consent in a few dense sentences. Stripped down, a compliant disclosure has five parts. Miss one and you have something weaker than consent.

The "not a condition of purchase" line looks like boilerplate, and it is the line that gets skipped when someone trims a disclaimer to fit a mobile screen. It is required. Leave it in.

A disclosure that covers all five

Here is the shape of a disclosure that hits every element, written for a solo agent. Swap in your own name and have a licensed attorney in your state review it before you run it. I am an agent, not a lawyer, and state law can add requirements on top of this.

Notice what it does not do. It does not say "partners." It does not say "up to four insurance professionals." It does not link to a separate page for the important part. It names one person, one topic, one number, and one action.

Where the text sits matters as much as what it says

The rule requires the disclosure to be clear and conspicuous. Courts read that phrase the way a reasonable consumer would experience the page, not the way a designer meant it. A perfectly worded disclosure that nobody could have seen is not consent.

• Next to the action, not below the fold. The text should be visible on the same screen as the checkbox or button that signals agreement, without scrolling, on the phone sizes your prospects actually use. Most of your final expense traffic is on a phone. Test on one.
• Readable. Same type size as the surrounding form, or close to it. Contrast a normal person can read. Light gray on white at a size that needs a pinch-zoom is the classic litigator screenshot.
• Tied to the signature. If you use a checkbox, the text should be the label of that checkbox. If you rely on the submit button, the text should sit directly above it and say "by clicking Submit" so the action and the agreement are the same thing.
• No hyperlink-only consent. A link that says "terms" with the consent language hidden behind it is not conspicuous. Links to a privacy policy are fine as an addition. They are not a substitute.
• Not buried in a wall of other text. If the consent is paragraph four of a privacy notice, it is not conspicuous. Set it apart.

Getting a signature out of a web form

"Signature" scares agents off, but the rule explicitly allows electronic signatures that comply with the federal E-SIGN Act. That covers a checkbox, a button click, a typed name, or a recorded voice agreement, as long as the action is clearly connected to the disclosure and you can show it happened.

The design choice that matters is affirmative versus passive. An unchecked box the prospect has to tick is affirmative. A pre-checked box they would have had to notice and untick is passive, and it is the first thing a plaintiff's attorney will ask about. A submit button with the disclosure directly above it is generally treated as affirmative, but a box is cleaner evidence because it produces a discrete, loggable event.

Whichever you use, the phone number has to be the one they typed. Consent attaches to the person and the number together. If your form lets someone submit a friend's number, or you later find a "better" number for them through a data append, the consent does not travel to that number. The reassigned numbers guide covers the version of that problem where the number changes hands after the form.

The one-to-one rule: what happened and what still matters

In December 2023 the FCC adopted a rule that would have required lead-form consent to name a single seller, with the calls logically related to the site where consent was given. It was set to take effect January 27, 2025. Three days before that date, the Eleventh Circuit vacated it in a case brought by the Insurance Marketing Coalition, holding that the FCC had gone beyond what the statute allowed. The federal one-to-one requirement is not in force.

Agents heard "vacated" and concluded the whole question went away. Three things did not go away.

• Clear and conspicuous still applies. A disclosure that consents to calls from a hyperlinked list of forty "marketing partners" was weak before the rule and is weak now. Litigators build cases on those forms every week, because a judge looking at one struggles to say a consumer knowingly agreed to hear from any specific company.
• Your own form has no reason to name anyone but you. The one-to-one design is the natural design for an agent running their own ads. The only forms that need a partner list are forms that sell the lead to several buyers. That is not what your form does.
• States can be stricter. Several state telemarketing laws have their own consent definitions, and the mini-TCPA guide walks through the ones that bite hardest. A form built to the single-seller standard clears most of them without changes.

Facebook lead forms and other hosted forms

Most agents who run their own ads collect leads on a Meta instant form rather than a landing page. That changes where the disclosure lives, not what it has to say.

Meta's form builder has a custom disclaimer section that appears on the review screen before the prospect taps submit, and it supports an optional checkbox with a required setting. Put the full consent language there, not in the ad copy and not in the intro text, and turn on the checkbox as required. The intro screen is not where the phone number is entered and it is not tied to the submit action, so consent text placed there is easy to argue away.

A few things to watch on hosted forms of any kind:

• Pre-filled phone numbers. Meta will pre-fill the number from the person's profile. That is convenient and it is also the number most likely to be stale. Pre-filled fields are still their submission, but the consent attaches to whatever was in the box when they tapped submit. Save that value, not a later correction.
• Disclaimer versions. When you edit the disclaimer, old leads were shown the old text. Keep a dated copy of every version. Naming the form with a version date is the low-tech way to do this.
• Export the proof, not just the lead. The lead download gives you the answers. It does not always give you what the disclaimer said. Screenshot each published form and file it with the date range it ran.
• Texting. If you intend to text, the disclaimer has to say so. The texting rules guide covers what happens after the first message, including the opt-out language you have to honor by any reasonable means.

What to save, and for how long

Consent you cannot produce is the same as no consent. The form is only useful if you can reproduce, for a specific lead on a specific date, what they saw and what they did. That is a record, not a checkbox in your CRM.

Third-party consent certification services exist that record the session and issue a certificate for each submission. They are common on lead-vendor forms and worth considering on a landing page you own if you run real volume. They do not work on Meta's hosted forms, which is why the versioned-screenshot habit matters there.

Keep the record for the life of the lead plus the longest statute of limitations that could apply, which for federal TCPA claims is four years. The consent records guide covers the retention and audit side in detail, and the consent duration guide covers the separate question of how long the consent itself stays fresh enough to dial on.

A ten-minute audit of your current form

Open your live form on your phone, as a prospect would, and check these in order. If any one fails, fix the form before the next ad runs, not after.

1. Is your name, or your agency's legal name, in the consent text? Not a vendor. Not "partners."
2. Does it say calls and texts, and does it say marketing or the subject matter?
3. Does it mention automated dialing technology and prerecorded or artificial voice?
4. Does it say consent is not a condition of purchase?
5. Can you read it on the same screen as the checkbox or submit button, without scrolling or zooming?
6. Is the checkbox unchecked by default, or is the disclosure directly tied to the submit button?
7. Do you have a dated copy of this exact text, and of every prior version?
8. Does your CRM store the form name, timestamp, and raw number on each lead, not just a consent flag?

Agents who pass all eight rarely get the kind of demand letter described in the litigator field guide, and when they do, the response is a screenshot and a timestamp rather than a settlement.

How FEXmagnet handles it

FEXmagnet is a CRM and single-line power dialer for life agents, and the consent record on each contact is built to hold the artifact, not just a flag. When a lead arrives through the webhook or a Meta form connection, the form identifier, the submission timestamp, and the raw phone number are stored on the contact as separate fields, and the consent source is visible on the dialer screen before the line connects.

The dialer will not place a call to a contact without a consent source on file, and the same gate applies to texts. That is a deliberate constraint rather than a convenience. A dialer that lets you call anything you can import is a dialer that will eventually call a number whose form you cannot produce.