DNC Scrubbing for Insurance Agents: What to Scrub, How Often, and What to Log

Most agents I talk to think “DNC scrubbing” is one thing you do once, at import, and then you are covered. It is not one thing. It is four separate jobs, they run on different schedules, and the one that gets agents in trouble is almost never the federal registry — it is the list you were supposed to be keeping yourself.

This is the practical version. Not a legal treatise, and not a scare piece. Just what each list is, who has to check it, how often, and what your file should look like if a demand letter ever lands in your inbox. I am an agent writing for agents; if you are facing an actual complaint, get a TCPA attorney, not a blog post.

The four lists, plainly

These get lumped together in conversation and they should not be. They come from different places, they update on different clocks, and missing one does not excuse you on the others.

1. Federal DNC: the one everybody knows

The National Do Not Call Registry is exactly what it sounds like: consumers put their number on it to stop telemarketing calls. For an insurance agent working a purchased or self-generated lead list, the question is not “is this number on the registry” so much as “do I have a documented basis to call it anyway.”

That basis is usually prior express written consent — the checkbox and disclosure language on the form the prospect filled out. If your lead vendor captured it properly and can hand you the record (form URL, timestamp, IP, the exact consent text shown), a registry hit is not automatically a violation. If they cannot, you are dialing a registry number with nothing to show for it, and the consent record is the whole ballgame under the 2026 TCPA rules.

The practical failure here is not agents deliberately calling registry numbers. It is agents who scrubbed a list in March, worked it in July, and never re-checked. Registrations are added continuously. A four-month-old scrub is a four-month-old guess.

2. State DNC lists: the quiet second layer

A handful of states run their own do-not-call registries and their own telemarketing rules on top of the federal framework. Some have stricter calling windows, stricter consent standards, or their own private right of action — which is what makes them dangerous for a solo agent dialing across state lines.

The rule of thumb I use: the prospect's state governs, not mine. If you are licensed in eight states and dialing all eight, you inherit the strictest rule in the set on any given call. I broke down the specific state regimes worth knowing in the mini-TCPA state law guide, and it is worth a read before you expand into a new territory rather than after.

3. Internal DNC: the list that actually gets agents sued

Here is the one nobody wants to hear. Your internal do-not-call list — your own record of everyone who has personally told you to stop calling — is the list most agents do not really keep, and it is the easiest one for a plaintiff to prove.

Think about the evidence. A federal registry claim requires establishing a registration and the absence of consent. An internal DNC claim requires one thing: your own call log showing you called someone after they asked you not to. That is a self-inflicted wound documented in your own system.

Three habits fix nearly all of it:

• Log the request the second it happens.Not at the end of the block, not at the end of the day. The revocation is effective when the prospect says it, and “I was going to enter it later” is not a defense when the redial happened two hours later.
• Catch the informal version.Nobody says “please add me to your internal do-not-call list.” They say “stop calling me,” “take me off your list,” or “I'm not interested, don't call again.” All of those count. Train yourself to treat any of them as a hard stop, not a soft objection to work around.
• Make it stick across every list you own. The number that opted out of your final expense list must also be blocked when you import a mortgage protection list six months later and the same person is on it. If your internal DNC lives in one spreadsheet tab, that will not happen.

That last point is the argument for enforcement at the dial rather than at import. A list-level scrub cleans the file you are looking at. A dial-level block covers every file you will ever own, including the one you have not bought yet.

4. Litigator scrubbing: cheap insurance

Serial TCPA plaintiffs are a real and organized thing. Some maintain multiple lines specifically to catch telemarketing calls, fill out lead forms to get onto lists, and document everything carefully because that is the business model. Their attorneys' office numbers show up too.

You cannot spot these people on a call. They sound like a normal prospect — often a very engaged one, asking clarifying questions and getting you to repeat things. By the time you know, the file is built.

Litigator scrubbing checks your numbers against maintained databases of known filers. It is not perfect, no database catches everyone, and it does not replace having real consent. But it is a screening step that costs you nothing per dial and removes the highest-risk contacts on your list before you ever hear a ring. There is no upside to skipping it.

Scrub at import or scrub at dial?

This is the real design question, and most tools only do the first one.

Import-time scrubbing is genuinely better than nothing, and if that is what your setup does today, keep doing it. But the honest framing is that it protects the list, and you get sued over calls, not lists. The check that matters is the one standing between you and the ring.

What your file should look like

If a demand letter arrives, the question is not whether you were a good-faith operator. It is what you can produce, quickly, in writing. A defensible file for any given call has four pieces:

• The consent record — where the lead came from, the exact disclosure language shown, a timestamp, and ideally the form URL and IP.
• The scrub record — that this number was checked against federal, applicable state, internal, and litigator lists, and when.
• The call record— date, time, duration, disposition, and the local time in the prospect's time zone so the calling-hours question answers itself.
• The opt-out record — if a request was ever made, when it was received and when it took effect.

Write those four down and you will notice something: none of them can be reconstructed after the fact. Either your system captured it at the time or it did not exist. That is the whole reason a spreadsheet stops being viable once you are dialing purchased lists at volume.

The five mistakes I see most

• Assuming the vendor scrubbed it. Many do. The liability for the call is still yours. Ask what they scrub, how often, and whether they will hand over the consent record on request — and treat a vague answer as an answer.
• Treating a scrub as permanent. A number clean in January can be registered in February. Aged lists are where this bites hardest, so re-scrub before any campaign to revive old leads.
• Keeping the internal DNC in your head. If it is not written down within seconds of the request, it is not a list.
• Scrubbing the imported list but not manual dials.The number a prospect gave you “to reach my husband on” is a dial like any other.
• No per-call log. Agents who have never had a complaint tend to keep the loosest records, which is exactly backwards — the record is cheap to keep and impossible to create later.

A ten-minute audit you can run today

Open whatever you dial from and answer these five questions honestly. Any “no” is your next project.

• Can I show, for a specific call last Tuesday, the consent basis for that number?
• When was my current working list last scrubbed against the federal registry?
• Where does an opt-out from three months ago live, and would it block a redial today?
• Does anything in my process screen for known litigators?
• If I got a demand letter this afternoon, how long would assembling the file take?

Most agents can answer one or two. That is not a character flaw — it is what happens when compliance is a set of habits rather than a property of the tool. The fix is not more discipline. It is moving the checks into the thing that places the call, so being compliant and being fast stop competing.