Link Leads Blog · November 19, 2026

The robocall mitigation database: why insurance agents' calls get blocked even after a clean DNC scrub

A DNC scrub checks consent. STIR/SHAKEN scores caller ID. Neither one is the reason calls can simply stop connecting — that's a third, earlier gate most agents have never heard of, and it sits upstream of the list entirely.

Three gates, not one

A DNC scrub answers one question: did this person ask not to be called. STIR/SHAKEN attestation answers a different one: how much does the terminating carrier trust this caller ID, which is why a clean scrub can still land on "spam likely" — covered in detail in our attestation-levels post. The Robocall Mitigation Database (RMD) answers a third question, earlier than both: is the provider carrying this call even allowed to put it on the network at all. If the answer is no, the call doesn't get a spam label and it doesn't get an attestation score. It just doesn't ring through, and nothing in your list, your scrub, or your script caused it.

What the database actually requires

The Robocall Mitigation Database was created under the TRACED Act (2019) and put into force by FCC rules that took effect in 2021. Every voice service provider that originates, carries, or terminates calls on the US telephone network has to file a certification in it — either confirming full STIR/SHAKEN implementation, or, for providers that haven't fully implemented it, a written robocall mitigation plan describing how they screen for illegal robocall traffic before it leaves their network. It's a provider-level filing. An insurance agency doesn't file anything, and most agents will never see the database directly — which is exactly why a problem there is so easy to misread as a list problem.

Why it reaches an agent who never heard of it

Intermediate and terminating carriers are required to reject traffic that arrives from an upstream voice provider that isn't listed in the RMD, or whose listing has been removed for an incomplete or false certification. Most agents don't contract with a carrier directly — they dial through a power dialer, CRM, or SMS/voice platform, which in turn routes calls through one or more underlying telephony providers. If one of those underlying providers gets pulled from the database, every call routed through it can stop completing, for every customer of that platform, with no notice to the agency that bought the leads and no error that points back to the real cause.

The symptom that tells you it's this, not your list

The three gates fail in different, recognizable ways:

What to check with your dialer or calling platform

You can't query the database for your own agency, because the filing isn't yours to make. What you can do is push the question to whoever you pay for outbound calling:

Texting runs on a different registration entirely

The Robocall Mitigation Database only covers voice calls on the public telephone network. SMS campaigns run through a separate system — 10DLC brand and campaign registration, covered in our 10DLC registration guide. A provider can be cleanly listed in the RMD for voice and still throttle texts under a poorly vetted 10DLC campaign, and the reverse holds too. If a mixed calling-and-texting push on an aged list stalls on one channel while the other keeps working, that's a sign to check the two registrations separately rather than assume one problem explains both.

Not legal advice

This is a practical overview of how the database affects call completion, not legal advice. Which provider you use, how to confirm its current filing status, and what obligations apply if you run your own SIP trunking rather than reselling a platform are questions for your communications provider and counsel, not a blog post.

Build the list once your calling path is confirmed

None of this changes what's in the file you're dialing — it changes whether the dial goes through at all. Link Leads sells SMS and email lead lists at a flat $0.012 per lead, minimum order 5,000 leads ($60), filterable by state and age band, deduped and delivered as an instant CSV — including a single-state pull like the Florida aged leads page, or one of the three clearance bundles at a steep discount off that rate while the sell-down runs. Build an order in the order builder, or pull a free 100-row sample before you commit to a batch.

These are aged data leads (not consented insurance-form leads) and are not DNC-scrubbed. Buyers are responsible for DNC scrubbing and dialing/texting compliance.