Phone numbers get recycled by carriers. A number you called with consent two years ago may now belong to someone who has never heard of your company and never agreed to be contacted. Standard DNC scrubbing doesn’t catch this — the number isn’t on any opt-out list. Here’s what reassigned number risk looks like and how to address it before it becomes a complaint.
## The Reassigned Number Problem
When a subscriber gives up a phone number — cancels service, moves, or simply lets a number lapse — that number eventually gets reassigned to a new subscriber by the carrier. The timeline varies, but reassignment can happen within weeks of a number being released.
Your lead list doesn’t know this happened. The number in your database was associated with a consenting contact. The consent was real. The problem is that consent doesn’t transfer to the new subscriber.
If your dialer calls that number and reaches the new subscriber — who has no relationship with your company and didn’t consent to contact — you’ve made a TCPA-regulated call without valid consent. The original subscriber’s consent is irrelevant to the new subscriber’s rights.
This exposure exists entirely outside the standard DNC compliance workflow. The number isn’t on the Federal DNC registry. It isn’t on state DNC lists. It isn’t in your internal opt-out database. It passes every standard DNC check and still represents liability.
## The Scale of the Problem
Carrier number recycling happens continuously. The older a lead list, the higher the probability that some of its numbers have been reassigned. A list that’s a year old may have a meaningful percentage of numbers that no longer belong to the original contacts.
The numbers most likely to have been reassigned are those associated with prepaid and mobile accounts, which have higher churn rates than landlines. These tend to be the same lead types that outbound contact centers rely on most heavily.
A list that passes full DNC scrubbing can still contain reassigned numbers. The two compliance checks are addressing different risks.
## How to Check for Reassigned Numbers
**The FCC’s Reassigned Numbers Database (RND)** is the authoritative source. The database contains numbers that have been reported by carriers as reassigned since the program launched. It’s updated monthly with new reassignments. Access is available directly from the FCC for a small per-query fee, or through third-party services that wrap the database with additional data.
The FCC’s safe harbor for callers who check the RND before dialing is meaningful from a liability standpoint — a good-faith check against the authoritative database before each call cycle is documented evidence of reasonable compliance effort.
**Third-party phone validation services** combine RND access with additional signal:
– Line type identification (wireless, landline, VOIP) — wireless numbers have higher reassignment rates
– Active subscriber confirmation — whether the number is currently active on a carrier
– Consent age matching — how long ago consent was captured versus when the number may have been reassigned
Services like IPQS (IPQualityScore) and similar providers wrap these checks into a single API call that can be integrated into the pre-import hygiene pipeline or run on demand before a campaign launches.
## The Complication: Standard DNC Scrubbing Doesn’t Cover This
The gap is architectural. DNC scrubbing checks whether a number has been opted out. Reassignment checking asks a different question: does this number still belong to the person who consented?
These are different databases with different update mechanisms. A number can be current on every DNC list and still have been reassigned. Running one check doesn’t run the other.
The compliance workflow that addresses reassigned numbers needs to be added as a separate layer — not as a replacement for DNC scrubbing, but alongside it. The correct pre-import sequence:
1. Federal DNC registry
2. State DNC lists
3. Litigator database (Blacklist Alliance, Contact Center Compliance, or equivalent)
4. Internal opt-out list
5. Reassigned number check (FCC RND or equivalent service)
6. Phone number validation (active subscriber, line type)
Steps 5 and 6 are where most operations have a gap.
**The second complication is list age.** Reassignment risk increases with list age — a number that was valid two years ago has had more time to be released and reassigned than one from last month. A compliance workflow that treats a two-year-old list the same as a recently acquired one underestimates the reassignment exposure in older inventory.
A practical approach: run reassignment checks at import time for new lists, and re-check older lists that have been sitting in inventory before they’re put back into active rotation after an extended pause.
## What Changes in Your Workflow
**At list import:** add reassignment checking to the pre-import hygiene pipeline. Numbers that return a confirmed reassignment are removed from the import set and logged with the reason. This keeps the contaminated numbers out of active campaigns rather than discovering them through complaints.
**Before recycling old lists:** run a reassignment check before reactivating a list that’s been dormant for an extended period. A list that was clean several months ago may have accumulated reassignments in the interim.
**Consent age tracking:** record when consent was captured for each lead. Use consent age as a factor in deciding whether to re-run reassignment checks before a list goes back into rotation. The older the consent, the higher the reassignment probability.
**Logging:** every reassignment check should produce a log entry — number, check timestamp, result, which campaign the number was excluded from. This is your documentation that the check ran before the campaign dialed.
## Frequently Asked Questions
**Does checking the FCC RND provide any legal protection?**
The FCC’s safe harbor for callers who check the RND before dialing is intended to provide protection against TCPA liability when a number has been reassigned. The safe harbor has specific conditions — consult compliance counsel for details on how it applies to your operation.
**How often do numbers get reassigned?**
Carrier reassignment rates vary and aren’t publicly published in detail. Reassignment timelines can range from weeks to months after a number is released. High-churn number types (prepaid mobile) tend to be reassigned faster than stable accounts.
**Is this the same as the DNC scrubbing we already do?**
No. DNC scrubbing checks whether a number is on an opt-out list. Reassignment checking asks whether the number still belongs to the person who provided consent. They’re different databases addressing different compliance risks.
**Does this add significant cost to the import process?**
Per-number check costs for reassignment services are small. The cost of a TCPA complaint or settlement is several orders of magnitude larger. The ROI calculation is straightforward.
## If You’d Rather Have This Built
I build pre-import hygiene pipelines for contact centers that include reassignment checking alongside standard DNC scrubbing. If you want the complete compliance layer — Federal DNC, state lists, litigator database, and reassignment checks — start here: rfditservices.com/intake.html
The first conversation is free.