State Telemarketing Registration for Insurance Agents

Most agents I talk to have their TCPA homework roughly in order. They know about the federal do-not-call registry, they know quiet hours exist, they have some version of a consent record. What almost nobody has looked at is whether the states they dial into require them to register before making the first call.

This is a separate body of law from the TCPA. It predates it in some states. It is enforced by different people, it carries different penalties, and your insurance license does not automatically clear it. If you got a nonresident license in eleven states because that is where your lead flow goes, you may have picked up eleven separate registration questions along with it.

This post is the map, not the answer. I am not a lawyer and I am not going to publish a state-by-state table that goes stale in a quarter and gets somebody fined. What I can do is show you the shape of these statutes, the exemptions that usually matter to insurance producers, and a process for working through your own list of states in an afternoon.

Two different rulebooks, both live at once

It helps to hold these apart in your head, because agents routinely assume compliance with one implies the other.

The last row is the one that bites people who did register. Registrations expire. Nothing in your dialer knows that. An agent who filed correctly in year one and forgot in year two is in worse shape than one who never filed, because the state has a record of them and a lapsed date sitting next to it.

What these statutes typically require

The wording varies a lot, but the machinery is similar enough across states that you can learn the pattern once. A telephone solicitation registration usually asks for some combination of:

• An application identifying who is calling. Legal name, any DBA, business address, owners or officers, and often the phone numbers you will be calling from.
• A description of what you are selling and how. Some states want the script, the offer, and the terms disclosed on the call.
• A fee. Typically annual, typically modest relative to the penalty for skipping it.
• A surety bond. Not universal, but common in the stricter states, and the single most annoying part of the process for a solo agent.
• Disclosure rules on the call itself. Identify yourself, name the entity you represent, and state the purpose of the call early — often within the first several seconds.
• Recordkeeping. Which calls were made, to whom, and what happened. If you already keep a defensible dial log for TCPA purposes, this part is usually already handled.

That last point is worth sitting with. A lot of what these statutes demand overlaps almost exactly with what a written do-not-call policy already forces you to build. The registration is the paperwork you file; the operating discipline behind it is the same discipline.

The exemptions that usually matter to producers

Here is the good news, with a caveat attached to every word of it. Most states that require registration also carve out categories of caller, and licensed insurance producers frequently land inside one of them. The exemptions I see most often take these forms.

The licensed-professional exemption

The statute exempts persons already licensed and regulated by another state agency — insurance producers, securities reps, real estate brokers. The logic is that you are supervised already. The catch is the word licensed: this generally means licensed in that state. Your resident license in Ohio does not make you a licensed professional in the eyes of a Florida statute. If you are dialing eleven states on nonresident licenses, that is eleven licenses that need to be current, not one.

The no-sale-on-the-call exemption

Some statutes only reach calls where the transaction is completed by phone. If the call exists to set an appointment and the sale happens face to face, the statute may not apply. This one is genuinely useful for field agents and genuinely dangerous for telesales agents, because the moment you start taking applications over the phone the analysis flips. If you moved from field to telesales in the last two years — and a lot of final expense agents did — this is the exemption most likely to have quietly stopped covering you.

The existing-relationship exemption

Calls to current customers, or to people who requested the contact, are frequently outside the definition of a solicitation. This is why working your own book and your own inbound-request leads sits on much safer ground than dialing a cold purchased list. Note that this is a different test from the TCPA's established business relationship concept, and the timeframes rarely line up. Do not assume one satisfies the other.

The prior-request exemption

Where the consumer asked to be called, many statutes step out of the way entirely. This is the same structural reason keeping a real consent record pays for itself twice — it is the evidence for the TCPA question and it is often the evidence for the registration question too.

How to work through your own states

This is a finite project. Most agents dial a handful of states seriously and a long tail of one-offs, and the work scales with the first group, not the second.

1. Pull the actual state list from your CRM, not from memory. Group your contacts by state and sort by volume. Agents are consistently wrong about this — there is almost always a state in the top five that you would not have named. If your states are stored inconsistently, normalize them first; this is part of a routine pipeline audit anyway.
2. Confirm your license status in each one. Current, correct lines of authority, not lapsed. If an exemption depends on being licensed there, this is the load-bearing fact.
3. Search the state for its solicitation statute.The Attorney General or Secretary of State site, terms like “telephone solicitation registration” or “telemarketing registration.” Read the definitions section and the exemptions section — in that order, because the definitions decide whether the exemptions even matter.
4. Write down the answer and the date. One row per state: registration required yes or no, exemption relied on, the statute cite, the date you checked, and who checked it. This file is the deliverable. It is also the first thing you would hand an attorney if a demand letter ever arrives.
5. Escalate the ambiguous ones. If you read a statute twice and still cannot tell whether a producer setting appointments is covered, that is not a sign to keep reading. Pay for an hour of advice from someone licensed in that state, or stop dialing there until you have it.
6. Calendar the renewals. Every registration you do file gets a renewal date on the calendar the same day you file it, plus a reminder a month ahead.
7. Re-run the whole thing annually, and on any change. New state, new nonresident license, moving from appointments to phone sales, adding a downline dialing under your entity.

What this has to do with your dialer

Registration is paperwork; no software files it for you and any vendor claiming otherwise is selling something. But the tooling does decide two things.

First, whether you can answer the question at all. “Which states do I actually call, and how often?” should take thirty seconds. If it takes an afternoon of spreadsheet work, you will not re-check it annually, and the drift is the risk.

Second, whether you can enforce a decision once you make it. If you conclude that you should not be dialing a particular state until the registration clears, that conclusion needs somewhere to live other than your memory at dial ninety on a Thursday. State-level rules, per-state calling windows, and the stricter mini-TCPA regimes are all the same category of problem: a rule that is true about a place, which the software either applies before the call connects or does not.

That is the honest test for any dialer on this topic. Not whether it handles registration — none of them do — but whether a state-level restriction you set is a block or a note.