The Reassigned Numbers Database and What It Means for Roofing Outreach

Why Reassigned Numbers Are a Real Compliance Risk

A phone number's consent history doesn't travel with it when the number is reassigned to a new person. If a homeowner gave consent, or opted out, on a number they later dropped, that history means nothing to whoever holds the number now. Dialing it as if the old relationship still applies is a real, avoidable risk, not a technicality. That is the same core TCPA consent principle behind every guide in this cluster: consent belongs to the person who gave it, not to the digits they gave it from, so a reassigned number resets that history to zero.

This is exactly the kind of gap that produces a complaint from someone who never had any relationship with your company at all, which is a worse look than a complaint from someone who simply asked to be removed and wasn't.

Maine LD 2234: Check Before You Dial

Maine LD 2234 requires checking the FCC Reassigned Numbers Database before dialing. The database itself is an FCC-run lookup tool telemarketers can query to see whether a number has been reported as reassigned since a given date, so it can be pulled from a dial list before a call is ever placed.

For a roofing company or vendor running outbound into Maine, that check is a compliance requirement, not optional due diligence. For everyone else, it's still the right practice, just not yet a specific statutory requirement outside Maine based on what this research confirms.

The 30 to 40 Percent Dead Number Problem

An estimated 30% to 40% of purchased lead-list numbers are dead or wrong. That's a striking number on its own, and it's a direct argument against relying on purchased or aged dial lists rather than pure inbound or owned-channel outreach: a third or more of what you paid for may not even reach a live, current owner of that number, let alone someone who consented to be called.

Reassigned Numbers Database checks catch part of that problem, the numbers that changed hands. They don't fix numbers that were simply never accurate to begin with. Both point to the same conclusion: list quality is a compliance issue, not just a cost-efficiency one.

It's Not Just a Maine Rule in Practice

Even if your outbound program isn't specifically targeting Maine, a broad national calling program will eventually touch Maine residents, and the underlying problem, a stale or reassigned number sitting on a dial list, exists in every state whether or not that state has passed its own version of LD 2234.

Treat the RND check as good practice everywhere your outbound reaches, not a box to tick only when calling into Maine specifically.

What to Ask a Vendor About List Hygiene

• Do they check the Reassigned Numbers Database before dialing, and not just when a Maine number is involved?
• What share of their dial list comes from purchased or aged sources versus a fresher, owned pipeline?
• How do they handle a call that reaches someone who says "wrong number, I just got this"? Is that number removed immediately and permanently?

A vendor with real answers here is protecting you from wasted dials and complaint risk at the same time, which is exactly the point of checking in the first place.

Sources

The external data in this guide draws on the sources below. Figures described in the text as estimates or industry triangulations are directional and are not attributed to a single dataset.

• Leads at Scale, cold calling compliance guide: TCPA, DNC, and state regulations
• Kixie, everything you need to know about the TCPA for cold calling

FAQ