Reassigned Numbers Database: When Good Leads Go Bad

Summary:

The Reassigned Numbers Database was launched by the FCC in late 2021, and anyone whose business depends on outbound calls needs to understand it. We put together a plain-English guide to the Reassigned Numbers Database: what it is, how phone numbers get reassigned, why it creates risk even for carefully-sourced leads, and what it means for list quality and responsible calling.

Most compliance missteps are things you can see coming: failing to get consent, ignoring a do-not-call request, dialing after hours. This one’s different.

Reassigned numbers are a unique risk because they show up after you’ve done things right.  Even teams using a purpose-built CRM for outbound phone sales had no way to catch them – for years the problem was invisible.

Picture a lead from six months ago. Mary filled out your form, gave you her number, and said yes, call me. The consent was valid. By every standard you’re held to, that contact was clean.

Then, sometime in the months that followed, Mary gave up the phone number and Tom became its proud new owner. Your CRM didn’t get the message.

When you later call the number intending to reach Mary, it lands with Tom instead. Tom's never heard of you, he's tired of getting calls for Mary, and depending on the consent requirements of your outreach, Tom may be within his rights to act.

This isn’t just a stale-list problem. It can happen with a lead from last year or a customer you spoke to two months ago. The number changes hands, and your records look exactly the same as the day they were right.

Why Reassigned Numbers Create Risk

The TCPA provides statutory damages at $500 per call, which a court may increase to $1,500 for violations a court finds willful or knowing. Those numbers can add up fast when calls are placed at scale.

In one case, a bank had consent to call a customer’s number, the number was later reassigned to someone else, and that new subscriber sued after receiving 189 calls. A jury awarded $500 for each of 189 calls, totaling $94,500, for calls the bank believed it had every right to make.The court confirmed what the TCPA makes clear: consent belongs to the person, not the phone number. Once a number changes hands, prior consent means nothing (N.L. v. Credit One Bank, 9th Cir. 2020).

When you consider that roughly 35 million U.S. phone numbers are disconnected and made available for reassignment every year, according to the FCC (that’s nearly 100,000 every day), you can imagine how often people receive calls intended for someone else.

That’s the gap the Reassigned Numbers Database was built to close, and understanding it is quickly becoming fundamental to responsible calling.

What Is the Reassigned Numbers Database (RND)?

In 2018, the FCC ordered the creation of a single, authoritative database to address a problem that cuts both ways: consumers have a right not to be bothered by calls meant for someone else, and businesses need a way to check whether the consent they were given is still good. The Reassigned Numbers Database went live in late 2021.

Here’s how it works. Every phone company has to report its permanently disconnected numbers, along with the date of each disconnection, into one central database. Before dialing, an organization can check a number against it, using the date you originally got permission to call. The database then tells you whether that number was disconnected at any point since then.

You get one of three answers:

•        Yes — the number was disconnected after your consent date. A red flag: it may now belong to someone new.

•        No — the database did not find a permanent disconnection after your consent date.

•        No data — there isn’t enough information to say.

A “yes” is the one that matters most. It’s the database telling you to stop and reconsider before you dial.

It’s worth being clear about what the database is and isn’t. It’s authoritative, built from the carriers’ own disconnection records, and comprehensive, growing to hundreds of millions of numbers since launch. But it isn’t a magic wand: it only knows about permanent disconnections reported by carriers, and its accuracy depends on having the right consent date to check against. It’s a powerful signal, not a guarantee, which is exactly how the FCC designed it.

What the RND Means for Callers

Here’s the shift worth paying attention to: checking the Reassigned Numbers Database has moved from a nice-to-have to something closer to standard practice, and in some places, the law.

Most calling teams already scrub their lists against the National Do Not Call Registry before they dial. The Reassigned Numbers Database is the same instinct applied to a different question.

•        DNC asks: “Am I allowed to call this person?”

•        The RND asks: “Is this still the right person to call?”

Together, they’re becoming the baseline of what responsible list hygiene looks like.

Learn More: A Comprehensive Guide to the Do-Not-Call Registry

And the expectation is starting to harden into rules. In 2024, Maine became the first state to require telephone solicitors to check the Reassigned Numbers Database before placing a sales call, layering it on top of the DNC scrubbing that was already expected.

Other states may follow. Between regulatory developments like this and the exposure that comes with calling the wrong person, the reasons to build Reassigned Numbers Database checks into your process keep stacking up.

The Benefits of Checking the RND

The practical upsides are real:

•        Cleaner lists. Reassigned numbers are dead weight. Clearing them means your list reflects people you can actually reach, not ghosts of leads past.

•        Fewer wasted dials. Every call to a reassigned number is time your team spends reaching the wrong person. That’s productivity you get back.

•        Better standing with carriers. Calls to disconnected numbers and complaints from wrong-person calls negatively impact your call reputation, increasing your risk of spam flags and blocks. Better list hygiene means healthier numbers.

Related: Strategies to Avoid Spam Labeling: Ensuring Your Sales Calls Stand Out

Potential Limitations

None of this means the Reassigned Numbers Database does the work on its own. It’s one signal among several, and using it well takes the right consent dates, regular checks, and a process that acts on what it finds. But it’s become a foundational part of how responsible callers operate, and understanding it is the first step.

Putting the Reassigned Numbers Database to Work

Knowing about the Reassigned Numbers Database is one thing. Putting it to use is another.

The database isn’t something you can download and run your list against on a quiet afternoon. It lives on a government portal. To query it directly, you:

1.     Register as a “Caller.”

2.     Choose and prepay for a subscription tier based on how many numbers you expect to check (subscriptions start at $8 a month for up to 1,000 lookups).

3.     Submit each number paired with the consent date that goes with it — through a web form, a file upload, or an API.

That works well for larger operations with the volume to justify it. For everyone else, it’s another subscription and operational process to pay for and manage.

That’s the part we’re focused on. To reduce that growing operational burden for outbound teams — and in line with our Responsible Communications® initiative — PhoneBurner is exploring ways to bring Reassigned Numbers Database checks directly into the platform, alongside the DNC scrubbing already available. The goal: help customers reach the right people with cleaner, more reliable contact data, without managing their own RND account, subscription, uploads, or API access.

It’s one more way we’re working to make responsible outreach the easy, default path for our customers. More to come.

Frequently Asked Questions

What is the Reassigned Numbers Database?

The Reassigned Numbers Database (RND) is an official FCC database, launched November 1, 2021, that helps callers check whether a phone number may have been reassigned to a new person since the date they received permission to call it. Phone carriers are required to report permanently disconnected numbers to the RND every month, making it an authoritative source of carrier-reported data — not a third-party guess or generic phone-number lookup. 

How does the Reassigned Numbers Database work?

The Reassigned Numbers Database works by matching a phone number against carrier-reported disconnection records, based on the date you got consent to call.  When a caller submits a number and date, the database returns one of three responses: Yes, No, or No Data. A Yes means the number was permanently disconnected after the date provided — an indicator that it may have since been reassigned to someone new. A No means no permanent disconnection was found after that date. No Data means there isn’t enough information to answer.

How often is the Reassigned Numbers Database updated?

Carriers report permanent disconnections by the 15th of each month, and the database is updated by the 17th. Callers can check numbers individually or in batches through the official portal, by file upload, or via API.

How much does it cost to use the Reassigned Numbers Database?

The Reassigned Numbers Database is a paid service, not a free lookup. Access is sold through prepaid subscription tiers based on query volume, with one-month, three-month, six-month, and annual options. Current pricing starts at $8 per month for up to 1,000 queries, and the per-query cost generally drops as volume increases. Pricing is set by the RND administrator and can change, so callers should check the official portal for current rates.

Is registering for the Reassigned Numbers Database worth it for phone outreach teams?

For large organizations, the costs of registering for the RND may be a routine operating expense. For smaller teams, it can mean another process to manage: registering, estimating volume and prepaying for a tier, and managing queries alongside their other list-hygiene tools.

That's one reason calling platforms like PhoneBurner are working to bring RND checks directly into the calling workflow, so teams can use reassigned-number data without managing a separate RND account, upload process, or API connection.

Why do reassigned numbers create risk for outbound calling teams?

Reassigned numbers create risk because consent belongs to the person, not the number. When a phone number changes hands, your permission to call does not automatically transfer to whoever gets that number next. This can create TCPA exposure, where statutory damages may range from $500 to $1,500 per violation.

It also creates operational problems: wasted dials, wrong-party conversations, frustrated recipients, and complaints that may contribute to caller reputation issues over time. The risk is easy to miss because the number may still look valid in your CRM and connect normally — just to the wrong person.

Is checking the Reassigned Numbers Database required by law?

In most places, no. At the federal level, using the Reassigned Numbers Database is generally voluntary, but it can help callers identify numbers that may have been reassigned before they place a call. The FCC has also noted it can help callers demonstrate they took steps to avoid calling reassigned numbers.

Some states are going further. In 2024, Maine became the first state to require telephone solicitors to use the Reassigned Numbers Database before initiating a telephone sales call to verify that the consumer's number has not been reassigned. So in most jurisdictions, "required" is still too strong. But RND checking is increasingly becoming part of responsible list hygiene and outbound calling practices.

What’s the difference between the Reassigned Numbers Database and the National Do Not Call Registry?

They answer two different questions. The Do Not Call Registry tells you whether you need consent to call someone. A number being listed in the DNC is one of several reasons you might need consent. The Reassigned Numbers Database tells you whether the consent you already have is still valid, by flagging whether the number may have changed hands since you got it. In other words: one tells you whether you need to have consent to make the call, and the other tells you whether you're still reaching the person who agreed to hear from you. They're two sides of the same coin, and they catch different problems, which is why they're increasingly used together as part of standard list hygiene. Checking one doesn't cover you for the other.

Does using the Reassigned Numbers Database guarantee TCPA compliance?

No — the database is a signal, not a shield. A “No” response only tells you the number wasn’t reported as permanently disconnected after your consent date; it doesn’t confirm who currently holds the number, that your consent is otherwise valid, or that a call is legally safe to make. The database only knows about permanent disconnections that carriers have reported, and its accuracy depends on you supplying an accurate consent date. It’s a valuable input to a responsible calling program — not a substitute for sound consent practices, good recordkeeping, and other compliance obligations that come with outbound calling.