Texting Compliance Checklist for Insurance Agents
Consent, opt-outs, and the one follow-up text you're allowed to send: a practical texting compliance checklist for insurance agencies, built around the FCC's current TCPA rules.
Under the TCPA, a client can revoke consent to be texted in almost any way that clearly says so — not just by typing the word STOP — and your agency has to honor it within ten business days. Getting texting compliance right means three things: collecting the right kind of consent before you send a marketing text, recognizing every reasonable form of opt-out the moment it arrives, and keeping your outbound cadence inside hours a regulator would call reasonable. None of it is complicated once it's written down, which is the point of this checklist.
Why this matters more for an insurance agency than most businesses
Every industry that texts customers deals with the TCPA. Insurance agencies deal with it under worse conditions than most: a large share of the numbers in your CRM came from a purchased lead list, not a client who filled out your own form, and the conversations you're having by text — plan changes, health questions, beneficiary updates — are exactly the kind that make a regulator or a plaintiff's attorney look twice. The TCPA is a strict-liability statute. A documented process that a vendor swore was compliant, or a lead list you were told was opted in, is not a defense once a text goes out.
The penalties are why agencies that otherwise ignore compliance paperwork pay attention to this one. Under the TCPA's private right of action, a consumer can recover $500 per violation, and up to $1,500 per violation if the violation was knowing or willful — per message, not per campaign (47 U.S.C. § 227(b)(3)). A single bad list sent to a few hundred numbers is not a rounding error.
The legal baseline: what the TCPA actually requires
Consent: informational text or marketing text?
The FCC's rules draw a real line between the two. An informational text — replying to a quote request, confirming an appointment, sending a policy document the client asked for — needs only the consent implied by the conversation you're already having. A marketing or promotional text sent with an autodialer or pre-set messaging platform needs prior express written consent: a signed agreement, physical or electronic, that names your agency, discloses that the client will get autodialed marketing messages, and states the number it will go to (47 CFR 64.1200(a)(2), (a)(9)). A checkbox buried in someone else's lead-gen form that says "our marketing partners" is not that agreement, and if a lead vendor can't produce the actual opt-in language naming your agency specifically, the list is not safe to text.
Opt-out: honoring "any reasonable method"
This is the part agencies most often get wrong, because the rule changed and most compliance checklists haven't caught up. Since April 11, 2025, the FCC's current rule is explicit: a client can revoke consent in any reasonable manner, and a business cannot designate one exclusive channel — like "text STOP only" — as the only way to opt out (FCC, Strengthening the Ability of Consumers To Stop Robocalls, 89 FR 82518). The current regulatory text lists the words that count automatically, and it is a longer list than most agencies train to:
| Treated as an automatic opt-out | Example |
|---|---|
| Any of: stop, quit, end, revoke, opt out, cancel, unsubscribe | A reply that is just "cancel" or "unsubscribe" |
| A clear plain-language request | "please stop texting me," "remove my number," "don't contact me again" |
| A request through any other channel the client can reach you on | A voicemail or email asking you to stop — this creates a rebuttable presumption of revocation the agency has to address, not ignore |
Whatever channel it arrives on, the request has to be honored within ten business days, and the only message allowed back is a single confirmation text with no marketing content in it — sent within five minutes, it's presumed reasonable; any later, the agency has to be able to show the delay was reasonable (47 CFR 64.1200(a)(10)–(12)). One more automated "are you sure?" text, or a "we'll miss you, here's 10% off" send, turns a compliant opt-out into a new violation.
What carriers add on top of the federal rules
Separately from the TCPA, the wireless carriers require every business number sending automated texts to be registered for application-to-person (A2P) messaging, and they throttle or block unregistered traffic on their own timeline, independent of whether you're otherwise compliant. That registration and its ongoing upkeep typically sits with whatever texting platform sends the message on your behalf, not with the agency directly — worth confirming with your platform rather than assuming, since "my texts aren't compliant" and "my texts are being filtered by the carrier" look identical from the client's side and need different fixes. The same consent-and-intent distinction matters on the calling side too — see what AI should automate around TCPA-covered outreach, and what it shouldn't.
A texting compliance checklist for insurance agencies
- Separate your lists by consent type. A client who called in or filled out your own form can get informational texts. A purchased or vendor-sourced lead needs documented prior express written consent before it goes into any automated marketing send — not "the vendor says it's opted in," the actual signed language naming your agency.
- Put an opt-out instruction on every marketing text, not just the first one in a sequence. It costs nothing and it's the easiest item on this list to get right.
- Train every person who reads client replies — not just your texting platform — to recognize opt-out language. "Stop" is the easy case. "Please quit contacting me" and a client who leaves a voicemail asking you to stop are opt-outs too, and if a human reads that reply before your system does, it still has to be honored within ten business days.
- Confirm, once, with no marketing content, and stop. Don't ask an opted-out client to reconsider, and don't let the next scheduled campaign catch their number before your suppression list updates.
- Re-verify consent before you text a number that's been dormant for a long stretch, particularly a purchased lead that sat unworked for months. Consent that was valid when the lead was generated can be stale enough by the time you actually reach out that a fresh, documented opt-in is the safer move — worth building into any lead follow-up sequence that leans on text as a channel.
- Keep the send window reasonable. Nothing in the TCPA sets a specific insurance-texting curfew, but a 6 a.m. or 11 p.m. marketing text is the kind of thing that turns a routine complaint into a willful one. Build your sends around normal daytime hours in the recipient's own time zone.
- Audit your suppression list against your CRM's own do-not-disturb flag periodically. A number can end up textable in one system and suppressed in the other after a manual edit, an import, or a platform change, and that gap is invisible until a client who opted out gets texted anyway.
Example: where this usually breaks down
Consider a five-agent Medicare agency running a weekly marketing text to a purchased lead list. One recipient replies "not interested, please stop" — not the word STOP, just that sentence. The platform's automation is tuned to catch the literal keyword and misses the phrase, so the number stays on the list. Three weeks later the same client gets another marketing text and files a complaint. Under the current rule, "please stop" is exactly as valid a revocation as "STOP" was under the old one — the agency's exposure here isn't that it lacked a suppression list, it's that the list only caught half of what counts as an opt-out.
How AgencyView handles this
AgencyView's texting tools are built around the assumption that an opt-out can arrive in more words than "STOP." Inbound replies are checked against the exact carrier keywords — stop, quit, end, revoke, opt out, cancel, unsubscribe — and against common plain-language phrasing like "stop texting me" or "remove my number," and a match suppresses that number immediately and writes the do-not-disturb flag back to the CRM contact record, so the opt-out shows up everywhere that record is opened, not just inside AgencyView. A backfill sweep catches anything a webhook delivery missed, so a suppression is never silently dropped. Every bulk text campaign checks that suppression list before each individual send and skips a number that's on it, campaigns can append an opt-out line to every message automatically, and each campaign runs inside a configurable send window in the recipient's own time zone instead of firing around the clock. When a client tells an agent by phone or in person that they want texts again, clearing the do-not-disturb flag updates both the CRM and AgencyView's own suppression list together, so the two never disagree about whether a number can be texted — and that action is logged to the contact's history. None of this replaces getting consent right in the first place, but it closes the gap between "our compliance policy says X" and what the system actually does on the next send. The same suppression list blocks a texted survey link from going out to an opted-out number, so a number that revoked consent through one AgencyView feature — texting, calling, or the rest of the CRM — doesn't stay reachable through another.
Learn more about texting and lead workflows in AgencyView at agencyview.net.
FAQ
Is "STOP" the only word that legally counts as an opt-out?
No. Current FCC rules treat stop, quit, end, revoke, opt out, cancel, and unsubscribe as automatically reasonable, and any other clearly-worded request — by text, call, voicemail, or email — can also count as a valid revocation depending on the circumstances (47 CFR 64.1200(a)(10)–(11)).
How fast do we have to honor an opt-out?
Within a reasonable time not to exceed ten business days from when the request is received (47 CFR 64.1200(a)(10)).
Can we send a confirmation text after someone opts out?
One, with no marketing or promotional content, and nothing further after that unless the client asks to resume. Sent within five minutes of the request it's presumed reasonable by rule; later than that, the agency needs to be able to justify the delay (47 CFR 64.1200(a)(12)).
Does an informational text need the same consent as a marketing text?
No. Informational texts tied to a conversation the client already started need a lower bar of consent than autodialed marketing texts, which require prior express written consent naming your agency (47 CFR 64.1200(a)(2)).
What's actually at risk if we get this wrong?
Statutory damages of $500 per violation, or up to $1,500 per violation if it's found knowing or willful, under the TCPA's private right of action — assessed per message, with no requirement that the client prove intent (47 U.S.C. § 227(b)(3)).
Where AgencyView fits
Keep reading
- AEP Text and Email Templates for Medicare Agents
- The FCC One-to-One Consent Rule and Insurance Leads
- A Role-Based Access Control Checklist for Insurance CRMs