TCPA Consent and Revocation: What Insurance Agencies Must Document for Calls and Texts

Research question

What does the Telephone Consumer Protection Act and its implementing rule at 47 CFR 64.1200 require of an insurance agency that calls or texts policyholders, and what should an agency document when staff or a virtual assistant places those calls and texts?

The question is practical because routine service contacts, such as renewal reminders, claim status updates, payment notices, and appointment confirmations, are exactly the kinds of messages that the rule covers. This is a desk review of the primary rule text and related authority. It is not legal advice and does not resolve any agency's specific facts.

Method

This review reads the current rule text directly at Electronic Code of Federal Regulations (eCFR), 47 CFR 64.1200, which governs delivery restrictions on telemarketing, telephone solicitation, and related calls. The eCFR text used here is the version available as of September 2026. This review also considers the statutory basis at 47 U.S.C. 227 and the national do-not-call framework that the rule implements. One state law is noted as an illustration of the second layer of requirements that can apply. No agency records, call logs, consent forms, or carrier contracts were reviewed. No survey or empirical measurement was performed.

Evidence checked September 18, 2026.

Evidence

The rule distinguishes consent levels by call type

The rule separates calls that use an automatic telephone dialing system or an artificial or prerecorded voice from calls placed by a live person, and it separates marketing from non-marketing content. Under 47 CFR 64.1200(a)(1), a person may not initiate a non-emergency call using an automatic telephone dialing system or an artificial or prerecorded voice to a cellular telephone service, or to similar services where the called party is charged, without the prior express consent of the called party.

Under 47 CFR 64.1200(a)(2), a call that includes or introduces an advertisement or constitutes telemarketing and uses an automatic dialing system or a prerecorded voice generally requires prior express written consent. Under paragraph (a)(3), prerecorded telemarketing to a residential line requires prior express written consent, subject to narrow exceptions.

The rule text also treats text messages as calls for the exemption in paragraph (a)(9), stating that the term "call" includes a text message, including a short message service call. That drafting confirms what the enforcement framework already assumed: texting is covered, not a separate regulatory universe.

Source fact: The level of consent the rule demands depends on the technology used and whether the message is marketing. A live service call is treated differently from an automated marketing call or text.

Revocation is now an explicit, broad duty

Paragraph (a)(10) states that a called party may revoke prior express consent, including prior express written consent, by using any reasonable method to clearly express a desire not to receive further calls or text messages. The paragraph lists methods that are reasonable per se: an automated interactive voice or key press opt-out on a call; replying with the words "stop," "quit," "end," "revoke," "opt out," "cancel," or "unsubscribe" to a text; or using a website or telephone number the caller designated to process opt-outs.

The same paragraph states that the caller must honor a revocation within a reasonable time, not to exceed ten business days from receipt, and that a caller or sender may not designate an exclusive means to request revocation. Paragraph (a)(11) addresses other methods, such as a voicemail or email to a number or address intended to reach the caller, and creates a rebuttable presumption that the consumer revoked consent when the consumer produces evidence of the request, absent evidence to the contrary. Paragraph (a)(12) permits a one-time confirmation text that merely confirms the revocation and contains no marketing, with timing considerations described in the rule.

Source fact: An agency cannot funnel all opt-outs through a single channel. If a client tells any reasonable channel to stop, the rule treats that as a revocation and imposes a deadline to honor it.

Do-not-call and calling windows

Paragraph (c)(1) prohibits a telephone solicitation to a residential subscriber before 8 a.m. or after 9 p.m. local time at the called party's location. Paragraph (c)(2) prohibits solicitation to a residential subscriber who has registered on the national do-not-call registry. The same paragraph provides a safe harbor for a violation that results from error if the caller can show a routine business practice that includes written procedures, training of personnel, a recorded do-not-call list, and use of a version of the national registry obtained no more than 31 days before the call.

The rule also defines an established business relationship in paragraph (f)(5). As commonly summarized, that relationship is based on the consumer's purchase or transaction within the eighteen months immediately preceding the call, or the consumer's inquiry or application regarding a product or service within the three months immediately preceding the call, and it ends when either party terminates it. An established business relationship can matter for certain do-not-call obligations, but it does not override a company-specific request to stop calling.

Source fact: Recordkeeping is part of the safe harbor. The rule rewards agencies that can show written procedures, training, and a current do-not-call process.

State law adds a second layer

Federal law is a floor, not a ceiling. States have enacted their own telemarketing and text-message statutes, and some are stricter than the federal rule. Florida's Telephone Solicitation Act, for example, appears in Florida Statutes section 501.059 and has been amended in recent years to address automated calls and texts to consumers in the state. An agency that contacts clients across multiple states should assume that at least one of those states imposes its own consent, disclosure, or calling-window requirements.

• Source fact: A single national consent process may not satisfy every state. The rule text reviewed here is federal.

Findings

Finding 1: Consent is layered, not binary. The rule imposes different consent standards for live calls, automated calls, and marketing content. An agency that treats all client contact the same way will either over-restrict routine service or under-protect marketing.

Finding 2: The revocation rules are broad and deadline-bound. Any reasonable method can revoke consent, the caller cannot force a single channel, and the rule states a deadline of ten business days at the outside. A system that only watches for one keyword in one inbox is exposed.

Finding 3: The safe harbor is operational. The national do-not-call safe harbor is available to callers that maintain written procedures, train staff, keep a recorded list, and refresh the registry data within 31 days. That is a documentation duty, not a technology purchase.

Finding 4: The rule expressly covers texts. The rule's own definitional language treats text messages as calls for its exemption structure, so text outreach is inside the framework.

Finding 5: State law can be stricter. Federal compliance does not guarantee state compliance.

Interpretation: what this means for an insurance agency using a virtual assistant

The following is the author's interpretation, not text from the sources.

• A virtual assistant who places service calls or sends texts is performing an activity the agency is responsible for. The consent and revocation duties attach to the calls and messages, and they do not disappear because a contractor or staff member performed them.
• The most common failure mode is not a deliberate marketing violation. It is an operational gap: an opt-out text that lands in a mailbox nobody monitors, a list that is not refreshed, or a script that does not capture consent.
• Written consent is more than a checkbox when the contact is marketing. It should be captured, stored, and retrievable with enough context to show what the client agreed to and when.
• Because any reasonable method can revoke, a single intake queue with a documented owner is safer than several disconnected channels.

Operational implications

These are proposed steps derived from the rule, not a legal checklist.

1. Classify each outbound contact by purpose (service or marketing) and by technology (live call, automated call, or text).
2. Capture consent at the source. Record what the client agreed to, the method, the date, and the scope, and store it where a service queue can find it.
3. Centralize revocation intake. Give every channel a path to one revocation log with a named owner and a deadline that builds in time before the ten-business-day outer limit.
4. Refresh do-not-call data on a schedule that is comfortably inside the 31-day safe harbor window, and keep proof of the refresh.
5. Train and document. Keep written procedures and training records, because the safe harbor asks for them.
6. Respect calling windows in each called party's local time, and build the check into the dialing or texting process rather than relying on memory.
7. Map state exposure. Identify the states where clients live and confirm whether those states impose additional requirements.
8. Confirm with counsel. Consent, revocation, and state-law questions are fact-specific and can change.

Limitations

• Not legal advice. This paper summarizes public primary and regulator-authored sources. It does not determine whether a particular contact, consent record, or calling practice complies with the law.
• Federal focus with one state illustration. One state statute is noted only to show that a second layer exists. No exhaustive state survey was performed.
• Rule text may change. The rule has been amended repeatedly. The eCFR text used here reflects the version available in September 2026; confirm the current text.
• Enforcement and litigation can shift the practical line even when the text is stable. This review does not analyze case law beyond the rule and statute.
• No facts. No agency calling campaign, consent form, or vendor contract was examined, so no conclusion about any specific practice can be drawn.

Practical conclusion

The rule reviewed here is built around three duties that an agency can design for: obtain the right level of consent for the contact, honor revocation quickly and through any reasonable channel, and keep the operational records that the safe harbor and enforcement defense require. For an agency delegating calls and texts to a virtual assistant, the practical response is to document consent at intake, centralize opt-outs with a deadline, refresh do-not-call data on schedule, and map state exposure before scaling outreach. Because these duties are fact-specific and layered with state law, an agency should confirm its process with qualified counsel rather than rely on a single national template.

Sources

1. Electronic Code of Federal Regulations, 47 CFR 64.1200, Delivery restrictions (Federal Communications Commission). https://www.ecfr.gov/current/title-47/part-64/section-64.1200
2. U.S. Code, 47 U.S.C. 227, Restrictions on use of telephone equipment. https://www.law.cornell.edu/uscode/text/47/227
3. Florida Statutes, section 501.059, Telephone solicitation (state-law illustration). https://www.leg.state.fl.us/statutes/index.cfm?App_mode=Display_Statute&URL=0500-0599/0501/Sections/0501.059.html
4. Federal Communications Commission, consumer guidance on unwanted calls and texts. https://www.fcc.gov/consumers/guides/stop-unwanted-robocalls-and-texts