Reassigned Numbers and Do Not Call Claims: The Safe Harbor Gap
Checking the FCC’s Reassigned Numbers Database before a call is a real defense, but only against one kind of TCPA claim. The database safe harbor answers the robocall rule. It does nothing for a Do Not Call claim, which is exactly what a reassigned number can set off when the new holder is on the national registry or asks the caller to stop. A company that queried the database and stopped there can still lose a Do Not Call case. The records that answer that claim are different ones.
What does the reassigned numbers safe harbor actually cover?
It covers the robocall rule, and only the robocall rule. The protection lives at 47 C.F.R. § 64.1200(m), and the text is specific about its reach. A person “will not be liable for violating the prohibitions in paragraph (a)(1), (2), or (3) of this section by making a call to a number for which the person previously had obtained prior express consent of the called party.” Paragraphs (a)(1), (2), and (3) are the parts of the rule that bar autodialed and prerecorded calls. An autodialer, after the Supreme Court’s reading, is equipment that generates numbers randomly or sequentially. A prerecorded call plays a recorded message instead of a live voice.
So the safe harbor’s job is narrow. It protects a caller whose database query came back clean but was wrong, against a claim that the caller robodialed a number after the consent for it had moved to a stranger. The FCC built the tool for that exact problem. Its 2018 order setting up the database said the database “will enable any caller to verify whether a telephone number has been reassigned before calling that number,” in the Second Report and Order that created it.
Read the safe harbor again and notice what it leaves out. It names paragraphs (a)(1), (2), and (3). It never mentions paragraphs (c) or (d). Those are the Do Not Call rules, and a reassigned number can land a company in both kinds of trouble at once.
Why does a reassigned number create a Do Not Call claim at all?
Because the Do Not Call rules protect whoever holds the number now, not the customer who used to. When a carrier ages a disconnected number and hands it to someone new, that person brings their own registry listing and their own right to be left alone. The robocall provision already works this way: it bars automated and prerecorded calls to a cell phone without “the prior express consent of the called party,” under 47 U.S.C. § 227(b)(1)(A), and courts read “called party” as the current subscriber. The earlier post on wrong-number exposure for businesses walks through that case law.
The Do Not Call side runs on the same logic. The national registry rule protects “a residential telephone subscriber who has registered his or her telephone number on the national do-not-call registry,” under § 64.1200(c)(2). The Do Not Call Registry is the federal list consumers join to block telemarketing. If the new holder of a reassigned number is on that list, a telemarketing call or text to the number is a potential violation, and the caller’s old consent from the prior holder is beside the point.
These rules reach cell numbers and texts, not just landlines. The FCC’s rule says “the rules set forth in paragraph (c) and (d) of this section are applicable to any person or entity making telephone solicitations or telemarketing calls or text messages to wireless telephone numbers,” under § 64.1200(e). A reassigned wireless number carries the Do Not Call rules with it.
One feature of the Do Not Call claim cuts in a business’s favor. The private right of action belongs only to someone who “has received more than one telephone call within any 12-month period by or on behalf of the same entity,” under § 227(c)(5). A single call or text to a reassigned number isn’t a Do Not Call case on its own. A pattern is.
How is the robocall claim different from the Do Not Call claim?
They come from different paragraphs, carry different defenses, and the database answers only one of them. Treating a clean query as full TCPA compliance is the most common mistake in this area, and it’s an expensive one, because the number that passes a reassignment check can still be sitting on the Do Not Call registry. Those are two separate lists, kept for two separate purposes.
| Claim | Where it comes from | Exposure per violation | What answers it |
|---|---|---|---|
| Robocall to a reassigned cell number | 47 C.F.R. § 64.1200(a)(1); 47 U.S.C. § 227(b)(3) | $500, or up to $1,500 if willful or knowing | The database safe harbor with query records, or consent from the current subscriber |
| Call or text to a number on the national registry | 47 C.F.R. § 64.1200(c)(2); 47 U.S.C. § 227(c)(5) | Up to $500, or up to $1,500 if willful or knowing | Registry scrub records, an established business relationship, the single-call rule |
| Call or text after a stop request | 47 C.F.R. § 64.1200(d); 47 U.S.C. § 227(c)(5) | Up to $500, or up to $1,500 if willful or knowing | Internal do-not-call list, suppression within the deadline, the request never reached the caller |
The database safe harbor appears in exactly one row. The two Do Not Call rows don’t touch it.
What defends the Do Not Call claim when the safe harbor doesn’t?
A written internal Do Not Call program is the backbone, and it’s a rule most callers already have to follow. The regulation bars telemarketing to a residential subscriber unless the caller “has instituted procedures for maintaining a list of persons who request not to receive such calls made by or on behalf of that person or entity,” under § 64.1200(d). When a reassigned number’s new holder says stop, that request has to be logged and honored, and the rule gives a deadline: “This period may not exceed ten (10) business days from the receipt of such request.” Suppress the number inside that window and keep the dated record, and a company has a real answer to the stop-request claim.
The content of the message matters too. The Do Not Call rules apply to a “telephone solicitation,” defined as “the initiation of a telephone call or message for the purpose of encouraging the purchase or rental of, or investment in, property, goods, or services, which is transmitted to any person,” under § 64.1200(f)(15). A purely informational message to a reassigned number, with no sales pitch, isn’t a solicitation at all, so the registry rule doesn’t reach it. Don’t push that line too hard, though. A friendly check-in that exists to feed a sales funnel can still be a solicitation.
An established business relationship can also take a call outside the registry rule, but reassignment is usually what kills it. The relationship is defined as one “formed by a voluntary two-way communication between a person or entity and a residential subscriber,” under § 64.1200(f)(5). The business had that with the old holder. It has nothing with the stranger who got the number next, so the exception that covered the first customer doesn’t cover the second.
The firm’s work defending TCPA class actions in California depends on records like these more often than on any single legal argument. The post on how the reassigned numbers database safe harbor works covers the robocall side in detail.
What to pull when a Do Not Call demand lands on a reassigned number
When a letter or complaint arrives, the goal is to show which rule the caller is accused of breaking and which records answer it. Pull these together before anyone responds.
- Put a litigation hold on the call and text logs for the number, the dialer or platform data, and the consent record from the original subscriber.
- Pull the national Do Not Call Registry scrub records for the number, with the version dates used for each campaign that reached it.
- Pull the internal do-not-call log: every stop request tied to the number, how the system read it, and the date the number was suppressed.
- Pull the Reassigned Numbers Database query records and timestamps, which answer the robocall claim even though they do nothing for the Do Not Call claim.
- Talk to a lawyer before responding to the demand, contacting the number’s holder, or offering anything to settle.
Questions businesses ask about reassigned numbers and Do Not Call claims
If we queried the reassigned numbers database, are we protected from a Do Not Call lawsuit?
No. The database safe harbor at § 64.1200(m) protects only against the robocall rule in paragraphs (a)(1), (2), and (3). A Do Not Call claim arises under paragraphs (c) and (d), which the safe harbor never mentions. A clean query shows the caller did its homework on the robocall side, but it isn’t a defense to a claim that the number was on the national registry or that the new holder asked the caller to stop.
Does the Do Not Call rule apply to a reassigned cell phone?
Yes. Section 64.1200(e) extends the Do Not Call rules in paragraphs (c) and (d) to telephone solicitations, telemarketing calls, and text messages sent to wireless numbers. When a wireless number is reassigned, the new subscriber’s registry listing and stop requests travel with the number, so a marketing text to a reassigned cell can support a Do Not Call claim the same way a call can.
Can a single text to a reassigned number be a Do Not Call case?
Usually not by itself. The private right of action under § 227(c)(5) requires more than one call within a 12-month period by or on behalf of the same entity. One message to a reassigned number rarely clears that bar. The exposure builds when a caller keeps messaging a number after the new holder is already on the registry or has asked it to stop, which is why prompt suppression matters so much.
Is an informational text to a reassigned number a Do Not Call violation?
Often not. The registry and solicitation rules reach messages sent to encourage a purchase, rental, or investment. A message with no sales content falls outside the definition of a telephone solicitation. The catch is that courts look at purpose, not labels, so a message dressed up as informational that really exists to drive sales can still count.
Defending a Do Not Call claim over a reassigned number?
If your company is being sued or has received a demand letter because a marketing call or text reached a reassigned number, the database query records answer one claim and the registry and opt-out records answer another, so the first job is sorting out which rule is actually at issue. Rosenberger + Kawabata represents businesses defending TCPA lawsuits and class actions through its business litigation practice, including claims involving reassigned numbers and Do Not Call compliance. Contact Rosenberger + Kawabata online for a confidential consultation, or call (310) 894-6921.
Sources
The statute is the Telephone Consumer Protection Act at 47 U.S.C. § 227. The FCC’s rules are at 47 C.F.R. § 64.1200. The reassigned numbers database was established in the FCC’s 2018 Second Report and Order, FCC 18-177.
This post is general information about the Telephone Consumer Protection Act and related laws as of August 27, 2026. It is not legal advice, and reading it does not create an attorney-client relationship. Courts and the FCC change the rules in this area often, and the outcome of any claim depends on its facts. Past results do not guarantee future outcomes.