The One Legal Requirement in Written Consent

You likely assume that getting a consumer to sign a form is the hardest part of compliance. It isn’t. The specific wording inside that form determines whether you hold a valid defense or a liability.

Under 47 C.F.R. § 64.1200(f)(9), written consent has one non-negotiable statutory element. You must include a disclosure stating that signing the agreement is not a condition of purchase. This specific phrase protects consumers from being forced to consent to marketing calls just to buy a product. If your consent form lacks this exact language, the agreement may be legally void, regardless of how clearly the consumer expressed intent to opt in.

This requirement creates immediate litigation risk when paired with vague, broadly worded consent language. In Satterfield v. Simon & Schuster, a district court flagged a checkbox labeled "Yes! I would like to receive promotions from Nextones affiliates and brands...." as a "broadly worded consent provision." The case resulted in a settlement of $175 per class member, with potential liability reaching $90 million. That financial exposure stems from consent language that didn't specify the exact business or call purpose.

To avoid this trap, your consent records must be granular and verifiable. Legal analysts recommend that consent documentation capture the exact wording agreed to, the timestamp, the source, and the specific business named. This documentation standard ensures that if a dispute arises, you can prove the consent was "clear, direct, and unequivocal."

Here is what valid written consent documentation must include to withstand scrutiny:

• The explicit statement that signing is not a condition of purchase
• The specific name of the business making the call
• The precise nature of the messages authorized (e.g., appointment reminders vs. sales pitches)
• A verifiable timestamp and source of the consent capture

My AI Call Center reviews these consent records before any campaign launches. We check for the no-purchase-condition disclosure and verify that the language names the specific entity and purpose. If the list lacks clear permission records or uses broad, ambiguous phrasing, we flag it. In most cases, we decline to run the campaign. We tell you plainly if the list will not support the goal, before you spend anything.

This rigor matters because statutory damages for TCPA violations start at $500 per call, and can triple to $1,500 for willful violations. Recent FCC enforcement actions show that regulators are actively pursuing these violations. Since 2015, the FCC has ordered violators to pay over $208 million in fines. While the legal landscape is shifting, with some circuits now accepting documented oral consent, the safest path remains strict written documentation.

Vague consent isn't just a legal technicality; it's a financial risk. By ensuring your consent forms contain the specific statutory disclosure and precise business details, you protect your organization from class action exposure. We build our campaigns on this foundation, ensuring every call runs against approved, permissioned lists that meet these documentation standards.

The Five Elements of In-Call Disclosure

Consent gets a lot of attention, but it's only half the compliance picture. Once a consumer has agreed to receive your calls, a separate obligation kicks in: telling them, at the start of each call, who you are and why you're calling.

Under the TCPA, prerecorded telemarketing messages must identify the business on whose behalf the call is made, provide a callable number for do-not-call requests, and offer an automated opt-out mechanism, generally within two seconds of the required identification, per FCC rules at 47 C.F.R. § 64.1200(b). Meeting the consent obligation doesn't satisfy the disclosure obligation. They're distinct requirements, and a campaign can pass one check and fail the other.

For AI-assisted calls specifically, vendor guidance from Plura AI describes a five-element opening disclosure that has become the practical standard. Every call should open with:

• AI identity, the listener knows an AI assistant is on the line
• The company name making the call
• The purpose of the call, stated plainly
• An option to speak with a human at any time
• A callback number for DNC requests and follow-up

A sample opening sounds like this: "Hi, this is an AI assistant calling from [Company Name]. I'm reaching out about [purpose]. If you'd like to speak with a person at any time, just let me know." It's worth noting the source frames these five elements as best practice rather than a settled legal mandate in every jurisdiction. The FTC's Telemarketing Sales Rule reinforces the timing, though, requiring disclosure of the seller's identity, the call's purpose, and what's being sold promptly at the beginning of the call.

Why lead with all of this? Because AI-generated voices are treated as artificial voices under the TCPA, per the FCC's final rule FCC-24-17, which means prior express consent applies and disclosure expectations keep tightening. Proposed rulemaking (FCC-24-84) would go further, requiring explicit in-call AI disclosure and AI-specific language in consent forms, though it hasn't been finalized.

This is why the disclosure script is a required approval step before any campaign launches. At My AI Call Center, nothing goes live until you've reviewed and approved the script, the disclosure, the opt-out handling, and the escalation path. The five elements get built into every approved script by default, so the first seconds of every call do the compliance work for you.

One caution: requirements vary by jurisdiction, industry, and consent status, so it's worth getting legal guidance specific to your campaigns before launch.

Documenting Consent for Verification

The legal standard for proving consent is shifting, and the paper trail is what decides who wins the argument. Under the FCC's rules, written consent must be a signed agreement authorizing the seller to deliver telemarketing messages to a stated number, and it must include the disclosure that signing is not a condition of purchase. That single element is the one definitive content requirement spelled out in the definition at 47 C.F.R. § 64.1200(f)(9).

Beyond that, regulators and courts converge on documentation rather than a fixed checklist. A vendor analysis of AI voice disclosure requirements recommends consent records capture the exact wording agreed to, the timestamp, the source, and the specific business named. That last point matters because broadly worded consent language has drawn litigation, as in the Satterfield case where a checkbox promising promotions from "affiliates and brands" was challenged as overbroad.

The bigger change is oral consent. In February 2026, the Fifth Circuit held the TCPA does not require prior express written consent for automated telemarketing calls to cellphones, provided consent is "clear, direct and unequivocal" and carefully documented. According to Holland & Knight's analysis of the Bradford decision, that ruling applies only in the Fifth Circuit, so interstate callers should still default to the stricter written standard. Courts can award $500 per violation, trebled to $1,500 for willful conduct.

For My AI Call Center, this shapes the list and consent review that runs before any campaign launches. A consent file that survives scrutiny typically shows:

• The exact consent wording the consumer agreed to, quoted verbatim
• A timestamp and the source of the consent, such as a web form or signed agreement
• The specific business named in the consent, not a generic affiliate reference
• Confirmation that the no-purchase-condition disclosure appeared in the written consent
• A record of any later revocation, honored within 10 business days

If your records cannot answer those questions, the consent is hard to prove no matter which standard applies.