Online Checkbox Consent for Robocalls: TCPA Test

Quick answer: Yes, if the record proves all seven elements of 47 CFR 64.1200(f)(9). The FCC’s 2012 order (FCC 12-21) accepts E-SIGN-compliant website forms, so a checkbox works when the person ticks an unticked box beside a retained agreement naming the seller, the artificial-voice or autodialled calls, the number, and two disclosures. The one-to-one rule never took effect; it was vacated in 2025.

Does an online checkbox satisfy the prior express written consent requirement for robocalls?

It can. The Federal Communications Commission (FCC) defines “prior express written consent” in 47 CFR 64.1200(f)(9) as “an agreement, in writing, bearing the signature of the person called”, and the definition’s own paragraph (ii) says “signature” includes “an electronic or digital form of signature, to the extent that such form of signature is recognized as a valid signature under applicable federal law or state contract law.” Nothing in the rule text mentions paper, ink or a particular form control.

The FCC said so directly when it adopted the written-consent rule. In paragraph 34 of the 2012 Report and Order (FCC 12-21, summarised in the Federal Register at 77 FR 34233), the Commission wrote: “we now similarly conclude that consent obtained in compliance with the E-SIGN Act will satisfy the requirements of our revised rule, including permission obtained via an email, website form, text message, telephone keypress, or voice recording.” The E-SIGN Act it refers to is the Electronic Signatures in Global and National Commerce Act, 15 USC 7001. Those requirements took effect on 16 October 2013 (77 FR 63240).

So the real question is whether this particular checkbox, and the record behind it, proves every element of (f)(9). An online checkbox is a valid way to sign prior express written consent, and an invalid way to prove it if the page around it leaves out any of the seven elements.

For the sentence to put next to the box, see our guide to consent wording and records for AI calls.

When an AI voice call needs prior express written consent at all

Written consent is not the TCPA’s default. It is triggered by two paragraphs of 64.1200, and both apply to AI voice agents because the FCC’s Declaratory Ruling FCC 24-17 (adopted 2 February 2024, released 8 February 2024) confirmed “that the TCPA’s restrictions on the use of ‘artificial or prerecorded voice’ encompass current AI technologies that resemble human voices and/or generate call content using a prerecorded voice.” Its footnote 13 adds: “If these robocalls introduce an advertisement or contain telemarketing, the Commission’s rules require that the caller obtain the prior express written consent of the called party.”

Call made by an AI voice agent	Line called	Consent the rule requires	Where it says so
Telemarketing or advertisement	Mobile (cellular) number	Prior express written consent	64.1200(a)(2)
Telemarketing or advertisement	Residential line	Prior express written consent	64.1200(a)(3)
Telemarketing by or for a tax-exempt nonprofit	Mobile number	Prior express consent (not written)	64.1200(a)(2)
HIPAA “health care” message by a covered entity or business associate	Mobile number	Carved out of the written-consent requirement in (a)(2)	64.1200(a)(2)
Not telemarketing (for example an appointment reminder)	Mobile number	Prior express consent (not written), unless an emergency or another exemption applies	64.1200(a)(1)(iii)
Commercial but not telemarketing	Residential line	None, if no more than 3 calls in any consecutive 30-day period and opt-outs are honoured	64.1200(a)(3)(iii)

Two limits on that table. First, it covers the robocall consent rules only; do-not-call obligations in 64.1200(c) and (d) run separately and have their own consent wording, covered below. Second, an autodialled call with a live human voice to a residential line is outside (a)(3), which is written about artificial or prerecorded voice; an AI voice agent never falls into that gap, because its voice is artificial by the FCC’s own ruling.

The seven-element checkbox test

We call this the seven-element checkbox test: one row per element of 47 CFR 64.1200(f)(9) as it stands in the eCFR (up to date as of 30 September 2026), what the rule text says, what the checkbox form has to show, and how forms typically fail it. The definition has five elements in its opening sentence, two mandatory disclosures in paragraph (i), and the signature definition in paragraph (ii). “Clear and conspicuous” is itself defined at 64.1200(f)(3).

#	Element	What the rule text says	What the checkbox form must show	Common failure
1	Written agreement	“an agreement, in writing”	A retained record of the exact words the person agreed to, as displayed	Only a boolean consent=true survives; the text shown that day is gone
2	Signature of the person called	“bearing the signature of the person called”; (ii) electronic signature counts where federal law or state contract law recognises it	An unticked box the person ticked, with the click logged as their act (our reading of “signature”; the rule does not mention pre-ticked boxes)	Box pre-ticked by the page, or ticked by a call-centre agent with no signed or recorded agreement from the person
3	Clearly authorises the seller	“clearly authorizes the seller to deliver or cause to be delivered”	The calling seller named in the consent sentence or in a list visible beside the box	“Our partners” or a hyperlinked list the person never had to open
4	The calling technology	“advertisements or telemarketing messages using an automatic telephone dialing system or an artificial or prerecorded voice”	Words covering autodialled or artificial-voice calls; for AI voice, “artificial or prerecorded voice”	Consent to “be contacted” or “receive calls”, with no reference to the technology
5	The telephone number	“the telephone number to which the signatory authorizes such advertisements or telemarketing messages to be delivered”	The number the person typed, stored with the consent and matched to the number dialled	A number appended later from a data vendor, or a different number on the dial list
6	Disclosure (i)(A)	a “clear and conspicuous disclosure” that “by executing the agreement, such person authorizes the seller to deliver or cause to be delivered to the signatory telemarketing calls using an automatic telephone dialing system or an artificial or prerecorded voice”	The disclosure beside the box, “separate and distinguishable from the advertising copy or other disclosures” ((f)(3))	Consent clause buried in the terms of use, in grey micro-type, or below the submit button
7	Disclosure (i)(B)	the person “is not required to sign the agreement (directly or indirectly), or agree to enter into such an agreement as a condition of purchasing any property, goods, or services”	A sentence saying exactly that, as clear and conspicuous as disclosure (A), and a checkout that completes without the tick	No statement at all, or a purchase flow that will not submit unless the box is ticked

The word “prior” adds a timing condition across all seven rows: the agreement must exist before the first call.

A checkbox passes the seven-element checkbox test only when every row can be proved from your own records, without asking the lead source. If one row is missing, the agreement does not match the definition, and the call it supports was made without prior express written consent.

Why a pre-ticked box is weak evidence of a signature

Element 2 is where the checkbox mechanism itself succeeds or fails. The rule requires “the signature of the person called”. E-SIGN defines an electronic signature at 15 USC 7006(5) as “an electronic sound, symbol, or process, attached to or logically associated with a contract or other record and executed or adopted by a person with the intent to sign the record.” A tick that the person places is a process executed by that person. A tick the page’s code placed before the person arrived is not something the person executed.

The 2012 order points the same way: the consumer’s written consent must be “sufficient to show that the consumer” received the disclosure and, “having received this information, agrees unambiguously to receive such calls at a telephone number the consumer designates.” A default tick that the person merely failed to remove is hard to describe as unambiguous agreement.

To be precise about the source: neither 64.1200, the 2012 order, FCC 24-17 nor the Eleventh Circuit opinion we read uses the phrase “pre-checked” or “pre-ticked”. The conclusion above is the reading of the signature element and of E-SIGN’s “intent to sign”, not a quoted prohibition. It is also why your record should log the box’s default state and the click event separately – the default state is the only thing that distinguishes a signature from a default.

Consent buried in terms of use fails the clear and conspicuous test

The two disclosures in paragraph (i) must be “clear and conspicuous”, and 64.1200(f)(3) defines that as “a notice that would be apparent to the reasonable consumer, separate and distinguishable from the advertising copy or other disclosures.” A checkbox labelled “I agree to the Terms of Use”, where the calling authorisation lives in paragraph 14 of those terms, has a disclosure that is neither separate from other disclosures nor apparent on the page where the signature happens.

The same applies to a consent sentence below the submit button, in a colour close to the background, or behind a “details” toggle. None of these is named in the rule; each makes it harder to show the notice “would be apparent to the reasonable consumer”, and the 2012 order puts that risk on the caller.

The practical rule: the authorisation sentence and the “not a condition of purchase” sentence belong immediately beside the box, in body-size type, and nowhere else is a substitute.

Partner lists after the one-to-one consent rule was vacated

The FCC tried to settle multi-seller forms in its December 2023 Second Report and Order, FCC 23-107. It amended (f)(9) so that consent would authorise “no more than one identified seller” and calls would have to be “logically and topically associated with the interaction that prompted the consent”, with that amendment due to take effect on 27 January 2025 (89 FR 5098).

It never took effect. On 24 January 2025 the US Court of Appeals for the Eleventh Circuit, in Insurance Marketing Coalition Ltd. v. FCC, No. 24-10277, held that the FCC “exceeded its statutory authority” and vacated Part III.D of the 2023 order. The FCC’s conforming order (90 FR 42137, effective 29 August 2025) records that the court’s mandate issued on 30 April 2025, that “prior to the court’s mandate, the Commission had postponed the effective date of the revised rule and the revised rule had not gone into effect”, and that the order “reinstates in the Commission’s rules the prior version of Sec. 64.1200(f)(9).” As at 2 October 2026, the eCFR text of (f)(9) (up to date as of 30 September 2026) is that reinstated pre-2023 wording, and a Federal Register search for FCC documents containing “prior express written consent” returns nothing later than that conforming order.

The court’s reasoning cuts against an easy reading of this page. It held that “consumers no doubt can give ‘prior express consent’ under the TCPA to receive robocalls from multiple parties without consenting to each caller separately.” A form naming several sellers is therefore not void just because it names several. Its footnote 14 makes the parallel point about topics rather than sellers: a consumer “presumably could give ‘prior express consent’ to receive calls about both auto loans and loan consolidation by checking both checkboxes.”

What the court did not touch is the 2012 written-consent rule: its footnote 1 says “The 2012 Order is not at issue in this case.” That rule still says, in force today:

• (f)(9): the agreement must “clearly” authorise “the seller”, and disclosure (A) must say the person “authorizes the seller”;
• the 2012 order: the disclosure must show “the consumer will receive future calls that deliver prerecorded messages by or on behalf of a specific seller”;
• 64.1200(c)(2)(ii), for numbers on the national do-not-call registry: a “signed, written agreement between the consumer and seller which states that the consumer agrees to be contacted by this seller and includes the telephone number to which the calls may be placed”;
• the FTC’s Telemarketing Sales Rule, 16 CFR 310.4(b)(1)(v)(A), for prerecorded-message calls under FTC jurisdiction: an express written agreement obtained after a clear and conspicuous disclosure that its purpose is to authorise the seller to place prerecorded calls, not as a condition of purchase, that “evidences the willingness of the recipient of the call to receive calls that deliver prerecorded messages by or on behalf of a specific seller” and includes the person’s telephone number and signature – four conditions.

After the vacatur, a multi-seller checkbox is lawful in principle, but each seller that dials still has to show it was clearly and specifically named to the person who ticked. A visible list of a few named sellers beside the box is the easiest version to prove; a hyperlink to hundreds of “marketing partners” that the person never had to open is the hardest. Where your leads come from someone else’s form, our page on purchased lead lists, AI voice agents and the TCPA covers the chain-of-custody questions to ask the vendor.

Who has to prove the box was ticked?

The caller does. In paragraph 33 of the 2012 order (77 FR 34237) the Commission concluded that “should any question about the consent arise, the seller will bear the burden of demonstrating that a clear and conspicuous disclosure was provided and that unambiguous consent was obtained.” The 2023 order repeated that “the TCPA and existing rules already place the burden of proof on the texter or caller” and that callers “may not … rely on comparison websites or other types of lead generators to retain proof of consent”; that restatement sits inside Part III.D, the part the court vacated, so the 2012 sentence is the one to rely on.

The stakes are set by the statute. Under 47 USC 227(b)(3), a person may sue to recover actual monetary loss or “$500 in damages for each such violation, whichever is greater”, and if the court finds the violation was wilful or knowing it may increase the award to “not more than 3 times” that amount – up to $1,500 per violation where the $500 figure is the greater. For what recent settlements actually paid, see our breakdown of TCPA settlements involving AI calling in 2026.

A checkbox you cannot reproduce is, for TCPA purposes, a checkbox nobody ticked.

What a consent log row needs to hold: a worked example

E-SIGN adds its own retention test. Under 15 USC 7001(e), where a rule requires a record to be in writing, the electronic record’s legal effect “may be denied if such electronic record is not in a form that is capable of being retained and accurately reproduced for later reference by all parties or persons who are entitled to retain the contract or other record.” For telemarketers within the FTC’s jurisdiction, 16 CFR 310.5(a)(8) lists six parts of a complete record of consent, including “a copy of the request for Consent in the same manner and format in which it was presented to the person providing Consent”, and 310.5(a) sets a retention period of 5 years from the date the record is produced unless specified otherwise.

Here is one row for a fictional seller, Example Solar LLC, with each field mapped to the test element it proves. The numbers use the 555-01xx range reserved for fiction.

Field	Example value	Proves
consent_id	c-001	Lets every call be traced to one signature
disclosure_text (verbatim, as displayed)	“By ticking this box, I agree that Example Solar LLC may call me at the number above with marketing calls, including calls using an artificial or prerecorded voice (such as an AI-generated voice) and an automatic telephone dialing system. I am not required to agree to this as a condition of purchasing any property, goods or services.”	Elements 1, 3, 4, 6 and 7
caller_seller	Example Solar LLC	Element 3: the dialling seller matches the named seller
checkbox_default / checkbox_event	unchecked / user_click	Element 2: the person executed the tick
disclosure_adjacent_to_box	true	Element 6: separate and distinguishable
number_consented / number_dialled	+1 512 555 0143 / +1 512 555 0143	Element 5: the number authorised is the number called
page_capture_sha256	hash of the stored HTML and screenshot of the form	Burden of proof; TSR 310.5(a)(8)(ii); E-SIGN 7001(e)
consented_at / first_call_at (UTC)	2026-09-14 02:11:09 / 2026-09-14 02:40:00	“Prior”: consent precedes the first call
ip, user_agent, session_id	captured at submit	Attribution to the person (evidence practice, not a rule element)
revoked_at / revocation_channel	empty until a revocation arrives	64.1200(a)(10): revocations honoured within a reasonable time, not exceeding 10 business days

The screen below runs that logic over a log. It is a first-pass filter, not a legal test: a regular expression can confirm that words are present, not that a reasonable consumer would notice them.

import json, re, sys

VOICE = re.compile(r"artificial or prerecorded voice|automatic telephone dialing system", re.I)
NOT_CONDITION = re.compile(r"\bnot\b.{0,80}\bcondition of (?:any )?purchas", re.I)

def check(row):
    fails = []
    text = row["disclosure_text"]
    if row["checkbox_default"] != "unchecked" or row["checkbox_event"] != "user_click":
        fails.append("2 signature: box not ticked by the person")
    if row["caller_seller"].lower() not in text.lower():
        fails.append("3 seller: calling seller not named in the disclosure")
    if not VOICE.search(text):
        fails.append("4/6A technology: no artificial/prerecorded voice or autodialler wording")
    if row["number_consented"] != row["number_dialled"]:
        fails.append("5 number: dialled number is not the consented number")
    if not row["disclosure_adjacent_to_box"]:
        fails.append("6 conspicuous: disclosure not beside the box")
    if not NOT_CONDITION.search(text):
        fails.append("7B condition: no 'not a condition of purchase' statement")
    if not row.get("page_capture_sha256"):
        fails.append("burden: no copy of the form as presented")
    if row["consented_at"] >= row["first_call_at"]:
        fails.append("prior: consent not before the first call")
    return fails

rows = json.load(open(sys.argv[1]))
for r in rows:
    f = check(r)
    print(r["consent_id"], "PASS" if not f else "FAIL: " + "; ".join(f))

We ran it against a four-row fixture: the row above, the same row with a pre-ticked box, a “Terms of Use and marketing partners” consent with no page capture, and a row whose dialled number differs from the consented one and whose consent post-dates the first call. Timestamps are ISO 8601 UTC strings in one format, which is what makes the string comparison safe. Output:

c-001 PASS
c-002 FAIL: 2 signature: box not ticked by the person
c-003 FAIL: 3 seller: calling seller not named in the disclosure; 4/6A technology: no artificial/prerecorded voice or autodialler wording; 6 conspicuous: disclosure not beside the box; 7B condition: no 'not a condition of purchase' statement; burden: no copy of the form as presented
c-004 FAIL: 5 number: dialled number is not the consented number; prior: consent not before the first call

Doing this yourself is mostly plumbing: capture the rendered form and the click at submit, write the row, carry consent_id onto the CRM contact, and gate the dialler on it. The cost is engineering time plus discipline every time marketing edits the form, because a new form version needs a new disclosure_text and a new capture. If your AI agents run on Zian, the HubSpot, Salesforce or HighLevel contact is the natural place for that field, and the check belongs before the number reaches the dial queue.

Where a checkbox is not enough on its own

Some situations sit outside what a checkbox test can settle, and they are where counsel earns the fee:

• Purchase flows. Disclosure (B) says consent is not a condition of purchasing. If your checkout will not complete without the tick, the disclosure contradicts the form. Quote-request forms where nothing is purchased are less clear-cut; ask counsel before making the box mandatory.
• Revocation. Under 64.1200(a)(10) a person may revoke prior express written consent “by using any reasonable method”, and revocations must be honoured “within a reasonable time not to exceed ten business days from receipt of such request”. A valid tick from last month does not survive a “stop” today.
• Reassigned numbers. The signature must be that of “the person called”. If the number has since been reassigned, the tick belongs to someone else; 64.1200(m) protects the caller only if it queried the reassigned numbers database and received a response of “no”, and the caller bears “the burden of proof and persuasion”.
• Do-not-call numbers. If the number is on the national registry and you rely on the person’s permission rather than, for example, an established business relationship, the (c)(2)(ii) agreement must state the consumer “agrees to be contacted by this seller” – check the wording covers that limb too.
• State law. This page covers the federal instruments only; state telemarketing laws are a separate check for counsel.
• Other countries. The TCPA is US law. Australian, Canadian and EU rules use different consent models; our AI outreach compliance guide to the Spam Act, TCPA and GDPR maps them.

This page describes what the instruments say as at 2 October 2026. It is not legal advice; for any form you plan to rely on at volume, have US counsel review the rendered page, not the wireframe.

Frequently asked questions

Where every figure on this page comes from

Figure	Who published it	Link	Date read
Seven elements of prior express written consent ((f)(9) opening sentence, (i)(A), (i)(B)); “clear and conspicuous” definition ((f)(3)); eCFR up to date as of 30 September 2026	FCC, 47 CFR 64.1200, via eCFR (Office of the Federal Register)	ecfr.gov 47 CFR 64.1200	2 October 2026
Written-consent triggers in (a)(2) and (a)(3); 3 calls in 30 days in (a)(3)(iii); 10 business days to honour revocation in (a)(10)	FCC, 47 CFR 64.1200	ecfr.gov 47 CFR 64.1200	2 October 2026
E-SIGN-compliant website forms satisfy the rule (para. 34); seller bears the burden of proof (para. 33)	FCC, FCC 12-21; summary in Federal Register 77 FR 34233 (11 June 2012), at 34237	FCC-12-21A1.pdf, federalregister.gov 2012-13862	2 October 2026
Written-consent rule effective 16 October 2013	FCC, Federal Register 77 FR 63240	federalregister.gov 2012-25316	2 October 2026
AI voices are “artificial or prerecorded voice”; FCC 24-17 adopted 2 February 2024, released 8 February 2024	FCC	FCC-24-17A1.pdf	2 October 2026
One-to-one amendment to (f)(9) due 27 January 2025 (FCC 23-107)	FCC, Federal Register 89 FR 5098	federalregister.gov 2023-28832	2 October 2026
Part III.D vacated, opinion dated 24 January 2025	US Court of Appeals for the Eleventh Circuit	No. 24-10277 opinion (PDF)	2 October 2026
Mandate 30 April 2025; prior (f)(9) reinstated effective 29 August 2025	FCC, Federal Register 90 FR 42137	federalregister.gov 2025-16641	2 October 2026
Electronic signature definition (7006(5)); retention test (7001(e))	US Code, via Cornell Legal Information Institute	15 USC 7006, 15 USC 7001	2 October 2026
$500 per violation; up to 3 times for wilful or knowing violations	US Code, via Cornell Legal Information Institute	47 USC 227	2 October 2026
Four conditions for prerecorded-message consent; six parts of a complete consent record; 5-year retention	FTC, 16 CFR 310.4 and 310.5, via eCFR	16 CFR 310.4, 16 CFR 310.5	2 October 2026