How Insurance Agencies Can Work Their Whole Database Without Breaking TCPA
Published · Last updated
The general rules for AI voice calling are settled, and our guide to running a TCPA-compliant reactivation campaign in the United States covers them: AI-generated voices count as artificial or prerecorded voice under TCPA, prior express written consent is the standard for marketing calls, and suppression has to be live rather than a one-off export.
What a general guide cannot tell you is which parts of your book you can actually dial. An insurance agency's database is not one list — it is five or six different ones, each with a different consent position, and the work starts with telling them apart.
This is not legal advice, and it is not a substitute for your compliance lead. It is the operational map.
Start by splitting the book into consent positions
Before any campaign, sort every contact by how they arrived, because that is what determines what you can do with them:
Quotes you never converted. They came through your own site, form or phone. If your form named your agency and disclosed that automated or AI-generated calls may be placed, this is your strongest segment.
Lapsed policyholders. They were customers. An existing business relationship matters — but it is not the same as consent for an AI voice marketing call, and it does not last indefinitely.
Current policyholders. The best consent position you hold, and the natural place to start a conversation about the rest of the household.
Old internet and aggregator leads. Sourced through a third party. The disclosure at capture had to name your agency specifically; a reference to "trusted partners" or a rotating network list does not carry over to you.
Purchased or aged lead lists. The highest-risk segment in this industry, and usually the one to exclude.
Referrals. A referral is not consent. The person who passed the name on cannot give it on the contact's behalf.
If you cannot evidence consent for a segment, do not dial that segment. Work it another way.
An existing business relationship is not a blanket permission
An existing business relationship can matter for how the national Do Not Call rules treat your call, and it is why current customers and recently lapsed policyholders sit in a different position from cold leads. What it does not do is replace the consent standard for an outbound marketing call placed with an artificial voice.
For each segment, the questions your compliance lead will want answered are the same: what did this person actually agree to, when, in what words, and can we produce it? A policy record proves they were a customer. It does not prove they agreed to be called by an AI agent about anything else.
Who is allowed to say what
Insurance adds a boundary other verticals do not have: licensing. An AI agent can identify itself, confirm details, qualify and book — but it cannot give advice on coverage or recommend a product. Anything that crosses that line has to reach a licensed producer.
Design the agent around that boundary rather than discovering it in a recording. In practice that means a clear rule for what triggers a live transfer, a transfer path that actually works, and a qualification script that stops short of advice.
Calling under a national brand
If your agency operates under a national carrier's brand, the wording on the call is a compliance decision rather than a marketing one. How the agent identifies the agency, how it describes the relationship to the carrier, and what it says the call is about all need to be settled and reviewed before launch. Carriers also set their own expectations for outbound contact and marketing, and those sit alongside the federal and state rules rather than replacing them.
Reconcile the lists you actually have
Your suppression picture is not only the national registry. It is the national registry, your agency's own do-not-call list, any list the carrier or network maintains, and every opt-out a contact has given through any channel — a phone call, an email reply, a text, or a request to a producer who never logged it. A revocation sitting in someone's inbox is not suppressed.
What has to land on the record
A compliant campaign leaves a trail on the contact, not in a spreadsheet. For each call: which segment the contact belonged to and the consent basis for it, the suppression state at the moment of dial, the disclosure the agent gave, the outcome, and the agreed next step. When Aidan runs a campaign, that writes back to the contact in Ricochet 360 and a summary email follows every successful call, so the evidence and the follow-up are the same record.
Where to start
Work outward from the strongest consent position. Lapsed policyholders and unconverted quotes from your own forms come first, where the consent basis is documentable; leave third-party and purchased lists alone until someone can evidence them. Aidan's agents are built around the specifics of each agency's business and compliance requirements, and scoping is the right conversation to have with your compliance lead in the room.
Aidan is an independent software provider and is not affiliated with, or endorsed by, Farmers Insurance or Allstate Insurance.