Solo Life Insurance Agent’s AI Outreach Compliance Checklist (2026)
A solo life insurance agent running AI outreach alone needs a compliance checklist that closes consent gaps fast, since there is no team to catch a bad text sent between appointments. It requires channel-specific written consent, an opt-out line, DNC scrubbing, and human review, because one unconsented campaign can trigger $500 to $1,500 in TCPA damages per message.
What consent do I need before AI marketing texts?
Prior express written consent is required before sending any AI-generated marketing text to a cell phone, and that consent must name your agency specifically, not just a lead-generation vendor. A generic opt-in captured by a third-party lead form does not satisfy this standard once you are the one texting.
This seller-specific requirement is the single biggest trap for a solo producer working purchased leads. If you buy leads from an aggregator, ask for the exact consent language and the date it was captured, because the vendor's opt-in usually authorizes the vendor to contact the consumer, not you. Per TCPA & AI Dialing Consent Rules for Insurance Agencies, consent also has to match the channel, since a lead who agreed to be called has not automatically agreed to be texted. Working alone, you do not have a compliance department to catch this after the fact, so the check has to happen before the first message goes out. Kadence is AI built to grow life insurance distribution, front to back office; its calling and texting layer checks a lead's consent status and Do Not Call flags automatically before dialing or texting, so a solo agent isn't relying on memory to know who opted out.
What happens if my solo AI outreach violates TCPA rules?
TCPA penalties run $500 to $1,500 per violation, and each unconsented call or text counts as a separate violation. There is no cap tied to how small your operation is, so a modest batch of messages sent without proper consent can generate a multiple of separate claims large enough to threaten a one-person book of business.
According to InsuraCentral's 2026 TCPA compliance guide for insurance agents, penalties can apply per call or per text, which is why volume without documented consent is the riskiest thing a solo agent can do on a tight lead budget. Here is the statutory exposure per message, by violation type:
| Violation Type | Statutory Damage (USD per message) |
|---|---|
| Standard violation | $500 |
| Willful or knowing violation | $1,500 |
Most solo agents never send hundreds of unconsented messages on purpose, but a shared or aged lead list bought cheap can quietly carry many numbers without proper channel consent. The exposure scales directly with your list size, not your revenue: a small list still multiplies the per-message figure above into real liability if consent was never properly captured.
Does my lead-form consent cover AI voice calls too?
Lead-form consent for calls does not automatically cover text messages, and consent for texting does not automatically cover voice calls; each channel needs its own authorization. A lead who typed their number into a rate-quote form to get a callback has not consented to receive an AI-voice sales call or a marketing text unless the form said so.
A text or call is only defensible if the recipient consented to that channel and the subject matter matches the scope of that consent. If your lead form only mentions "a licensed agent may call you," that language does not cover an AI voice dialer reaching out with a policy pitch, and it does not cover an SMS follow-up either. Read your own intake forms line by line; as a one-person operation you likely wrote or inherited that form without a lawyer checking it, so this is worth 20 minutes now instead of a complaint later.
Why does the FCC treat AI voices as artificial calls?
The FCC ruled in February 2024 that AI-generated, human-sounding voices qualify as "artificial or prerecorded voices" under the TCPA, which means they trigger the same prior-express-consent requirement as a traditional recorded robocall. This closed the argument that a natural-sounding AI voice dialer sits outside voice-call restrictions.
Per the FCC's ruling, "FCC Confirms that TCPA Applies to AI Technologies that Generate Human Voices," any outbound marketing call to a mobile number using an AI voice, however lifelike, needs prior express written consent before you dial. For a solo agent testing an AI dialer to cover leads while you're in an appointment, this means the tool's realism does not exempt you from the consent rule; it makes the rule more important to enforce on yourself, since one AI-voice campaign to an unconsented list carries the same per-message exposure covered in Voice AI Outbound Dialing Compliance Framework.
What hours can I legally call leads with AI voice?
Telemarketing calls, AI-voice or manual, are only permitted between 8 a.m. and 9 p.m. in the lead's local time zone, not your own. Calling a lead in a different time zone before 8 a.m. or after 9 p.m. their time violates the TCPA even if it's a reasonable hour where you're sitting.
Working solo often means squeezing outreach into odd hours, early morning before your first appointment or late evening after your last one, which makes time-zone math easy to get wrong on a multi-state book. A few related thresholds worth keeping on a sticky note:
| Compliance Rule | Required Threshold |
|---|---|
| Telemarketing calling window | 8 a.m. to 9 p.m., recipient's local time |
| Abandoned-call cap | 3% of connected calls per 30-day campaign |
| Minimum ring before abandonment | 4 rings or 15 seconds |
Also identify yourself and your business at the start of every call; skipping that on a rushed dial between appointments is a quick fix but an easy one to forget when you're the only person making the call.
How do I handle opt-outs on my own AI texts?
Every marketing text needs a clear opt-out instruction, such as "Reply STOP to unsubscribe," and that request must be honored immediately, with the number suppressed from future campaigns right away. There is no grace period and no batch-processing delay allowed once a lead asks to stop.
For a one-person shop, "immediately" has to mean the same day, not whenever you next open your laptop between appointments. Consumers can revoke consent by any reasonable means, not only by replying STOP, so a verbal "stop texting me" during a call counts too and has to be logged the same way. Registering under the A2P 10DLC framework also reduces the odds carriers flag or block your texts outright, which matters more for a solo sender than for a large shared number pool, since a single flagged line is your entire texting operation.
Do I still need to scrub the Do Not Call list?
Yes, every calling list has to be scrubbed against the National Do Not Call Registry and your own internal suppression list before you dial, regardless of how small your personal lead list is. A common industry benchmark is re-scrubbing every 31 days, even for lists you've already worked once.
A solo agent recycling an aged lead list from three months ago is exactly the scenario this catches: someone on that list may have registered on the National DNC Registry or asked you directly to stop contacting them since the last time you called. Build the 31-day re-scrub into your calendar the same way you'd block time for appointments, because there is no assistant to run it for you if you forget.
What consent records must I keep as a solo agent?
Keep the date, method, and exact consent language for every lead as your proof of opt-in, since a verbal memory of "they said yes" won't hold up against a complaint. This record has to exist before you make the first AI call or send the first text, not be reconstructed afterward.
A simple three-field log works for a one-person operation: when consent was given, how it was given (web form, verbal, text reply), and the precise wording the lead agreed to. If you're managing this in spreadsheets and sticky notes while also selling every policy yourself, the record-keeping is the first thing to slip during a busy week. This is the kind of gap that shows up when your outbound calling and texting run through a single system that timestamps consent the moment a lead comes in, rather than relying on you to remember it hours later between calls.
How does the one-to-one consent rule affect me?
The one-to-one consent standard requires that consent for marketing contact be given specifically to the business making contact, so a solo agent buying leads through a shared vendor cannot rely on that vendor's blanket opt-in as cover. A related cross-campaign opt-out propagation requirement was delayed until January 31, 2027, per Entrovox's 2026 coverage of the rule.
In practice, this means the burden sits on you, not the lead vendor, to confirm the consent you're relying on actually names your agency. Two-thirds of independent agencies plan to increase AI use this year, according to a survey covered by Insurance News Net, and every one of those agents is buying leads into the same seller-specific consent standard. As a solo producer with no compliance staff, treat every purchased lead as unverified until you've seen the actual opt-in language, not just a vendor's assurance that "it's compliant."
Why review every AI-drafted message before I send it?
A human has to review every AI-generated text or call script before it reaches a lead, checking that coverage claims, cost mentions, and required disclosures are accurate. AI-drafted copy can overstate a benefit or drop a disclosure without meaning to, and you are the only line of defense catching it before it goes out.
With no compliance team and no second set of eyes, this review step is the one most likely to get skipped on a busy day, and it's the one most likely to create a real problem if it does. Build it into your routine the same way you'd proofread a quote before sending it to a client. Here's a snapshot of what to check against, by channel, before anything goes out:
| Outreach Channel | Consent Standard Required | Proof to Keep on File |
|---|---|---|
| AI voice call to mobile | Prior express written consent | Date, method, exact opt-in language |
| Marketing text (SMS) | Prior express written consent, channel-specific | Date, opt-in language, A2P 10DLC status |
| Informational call or text | Prior express consent (lower standard) | Date and context of the request |
If checking this list every week on top of selling, prospecting, and everything else feels like a second job, to see how Kadence answers, texts back, and gets a qualified lead on your calendar in under 10 seconds while keeping consent and Do Not Call status attached to every one of those touches automatically.
Sources
- FCC Confirms that TCPA Applies to AI Technologies that Generate Human Voices
- TCPA & AI Dialing Consent Rules for Insurance Agencies (2026) | Kadence
- TCPA Compliance for Insurance Agents in 2026: The Complete ...
- Texting Insurance Leads Compliance: The 2026 Agent Guide
- TCPA Compliance for Insurance Agents: The Definitive Guide
- Insurance sales TCPA compliance: specific requirements...
- AI insurance sales calls: TCPA and NAIC compliance explained
- TCPA Compliance for AI SMS & Callbacks - Aira
The steps
- Confirm channel-specific written consent before you reach out. Before texting or calling a new lead, verify you have prior express written consent naming your agency for that specific channel; if a purchased lead only carries a vendor's opt-in, get the consent language and date in writing before contacting the number.
- Add opt-out language and honor it immediately. Every marketing text needs a visible opt-out line such as 'Reply STOP to unsubscribe,' and the moment a lead opts out, remove that number from every active and future campaign the same day, not the same week.
- Scrub your list against DNC registries on a set schedule. Run your calling and texting list against the National Do Not Call Registry and your own internal suppression list on a recurring cycle, no less often than every 31 days, before launching any new outreach batch.
- Log the date, method, and exact consent language. For every lead, record in your CRM the date consent was given, the method (web form, verbal, text reply), and the exact language they agreed to, so you have a defensible record if a complaint or audit surfaces.
- Have a human review every AI-drafted message before it sends. Read every AI-generated text or call script yourself before it reaches a lead, checking that claims about coverage or cost are accurate and that disclosures and opt-out language are intact, since you have no compliance team to catch a bad draft after the fact.
Frequently asked questions
Can I use a free AI texting app and still stay TCPA compliant as a solo agent?
Yes, but the app does not grant compliance automatically. You still need documented channel-specific consent, visible opt-out language, National and internal DNC suppression, and human review of every message; a free or low-cost tool is only compliant if you operate it under these same rules yourself.
Is a verbal yes enough before an AI voice call to a lead's cell phone?
No, marketing or solicitation calls using an AI or artificial voice dialer require prior express written consent, not just a verbal yes. Purely informational calls can rely on the lower prior express consent standard, but any call pitching a life insurance product needs the written standard.
How fast do I have to honor an opt-out from a lead?
Immediately, with no grace period. Once a lead texts STOP or verbally revokes consent, suppress that number from every active and future campaign the same day, since consumers can revoke consent through any reasonable method and a solo agent has no second person to catch a missed opt-out later.
Written by
Kadence Team
Kadence is AI built to grow life insurance distribution, front to back office, purpose-built for producers, agencies, and IMO networks. We write about speed to lead, AI search, back-office tracking, and the systems that help producers and agencies win more policies.
Reviewed by the Kadence Team.
Book a demo
