Key takeaways
- A disconnected number can be handed to a stranger after as little as 45 days[2], and nobody tells the practice.
- Consent stays with the patient who gave it, so automated texts to the new holder of the number are a TCPA exposure[3][4].
- The FCC's Reassigned Numbers Database answers only yes, no or no data for a number and a date[1]; querying with the consent date is what earns the safe harbor[5].
- Wrong-number replies and carrier deactivation notices are the cheapest signals you have; act on them the same day[6].
How a patient's number ends up with a stranger
A patient switches to a new plan, lets an old prepaid line lapse or simply stops paying for a second phone. The carrier holds the number out of service for a while, then hands it to a new customer. For a number that belonged to a residential customer, that holding period can be as short as 45 days and no longer than 90[2]. Your practice management system still lists the old number as the patient's mobile, and your reminder tool still has her down as opted in. The next confirmation text goes to someone she has never met.
This is not a rare edge case. When the FCC built its national database of disconnected numbers, it estimated that about 35 million numbers are disconnected and made available for reassignment every year[1]. Patients are not careful about telling the front desk when a number dies. Most only mention it when they notice the reminders have stopped, if they notice at all.
Source: Electronic Code of Federal Regulations (National Archives), 2026[2]
Show the data
| Aging period | Days |
|---|---|
| Minimum, any number | 45 days |
| Maximum, residential number | 90 days |
| Maximum, business number | 365 days |
Two problems arrive with that misdirected text. One is the Telephone Consumer Protection Act, which cares about whether the person you reached agreed to automated messages. The other is privacy, because even a short reminder says something about a patient to a person with no right to know it.
Why the new owner of the number matters under the TCPA
Most practices text patients under the FCC's health care exemption for wireless numbers. One of its conditions is that the message goes only to the wireless number the patient provided[5]. Once that number belongs to someone else, the person receiving your reminders is not the patient, and the exemption's footing is gone. The FCC said in 2015 that callers are liable for robocalls to reassigned wireless numbers when the current subscriber or customary user has not consented[3]. In 2018 a federal appeals court set aside the FCC's earlier allowance of one call to discover a reassignment, along with its whole treatment of reassigned numbers[1]. The national database and its narrow safe harbor are what the FCC built next.
The money side is set by statute. The TCPA lets a person sue for actual losses or $500 per violation, whichever is greater, and a court can increase damages for willful or knowing violations[4]. Each automated text is counted separately.
Example: a patient's old mobile number is reassigned in March. In June your system sends the new owner a booking confirmation, a two-day reminder and a same-day reminder for her annual physical, then a recall text in December. That is four automated messages to someone who never consented, each one a potential $500 claim[4], before anyone at the desk hears about it.
Manual calls from a staff member's handset are a different matter from automated texts and prerecorded calls, but most reminder volume today runs through software. Treat every number your reminder platform touches as one that needs checking. The rules on what those messages may say are covered in TCPA rules for appointment reminders.
The privacy side: a reminder can be a disclosure
A reminder that says “Lakeview Oncology: Maria, your infusion is Tuesday at 9” tells a stranger the patient's first name, the specialty and the treatment. Under HIPAA, a disclosure the Privacy Rule does not permit is presumed to be a breach unless the practice shows a low probability that the information was compromised, using a risk assessment that looks at the information involved, who received it, whether it was actually viewed and how far the risk was reduced[7]. A wrong-number text that was read by its recipient usually fails the third factor.
The defense starts with the template. Keep reminders to the practice name, a date, a time and a callback number, and drop the provider's specialty where the clinic name alone gives away the condition. What a HIPAA-safe reminder can say has wording you can adapt, and breach notification steps for small practices covers what to do when a sensitive message has already gone to the wrong person.
What the Reassigned Numbers Database does
The FCC ordered a single national database of permanently disconnected numbers, and every provider that holds US geographic numbers must report its disconnects to it every month[8]. It now holds over 361 million geographic and toll-free numbers[8]. You do not get names or the new owner's details. You send a phone number and a date, and the database answers “yes”, “no” or “no data”: whether that number has been permanently disconnected since the date you gave[1].
The date is the part practices get wrong. The FCC's order says it can be any past date on which you were reasonably sure the person you mean to reach could be reached at that number, such as the day you last spoke to them there or the day they last updated their contact details[1]. The safe harbor in the FCC's rules is narrower: it protects a caller who queried with the date consent was obtained, got a “no”, and called because the database was wrong[5]. So the consent date has to be stored somewhere you can retrieve it, per number, not just a yes or no flag.
| Response | What it means | What the practice does |
|---|---|---|
| No | Not permanently disconnected since the date you entered | Keep the number active. Keep the query record: it is your safe harbor evidence if the database was wrong. |
| Yes | Permanently disconnected at some point after that date | Stop automated texts and calls to it today. Flag the record and confirm a new number with the patient through the portal, by mail or at the next visit. |
| No data | The database has nothing for that number in that window | Treat it as unconfirmed. Ask the patient to confirm the number at the next contact and record a fresh consent date. |
Some things are not disconnections. A patient who ports her number to a new carrier keeps it, and a line suspended for an unpaid bill is still hers; neither shows up as permanently disconnected[8]. Large and medium carriers started tracking disconnects on July 27, 2020[8], so a consent date older than that leaves part of the history uncovered. For long-standing patients, a recent date when they confirmed the number at the desk is the better anchor.
What checking costs and who runs the query
The database is a prepaid subscription. Since April 2025, a one-month plan with 1,000 queries costs $8 and 10,000 queries cost $60; a year of 1,000 queries a month costs $86[9]. The FCC describes using it as voluntary[1], but the safe harbor only exists for callers who use it. For a small or mid-size practice the cost is small next to a single $500 claim[4].
You may not need your own account. Agents can query on a caller's behalf, and many reminder and texting platforms either check numbers already or can tell you how they handle reassignment. Ask your vendor three questions in writing: do you query the Reassigned Numbers Database, which date do you send with each number, and how often do you re-check numbers that stay on our list?
Example: a four-provider family practice has about 6,000 patients with a mobile number on file and texts roughly 1,100 of them in a typical month. Querying only the numbers due to receive messages that month fits inside the 1,000 to 10,000 query plans[9]; a full-list check twice a year fits the 10,000 tier.
Clean the list at the desk, not only in the database
The database only knows about permanent disconnects. Your staff hear about wrong numbers sooner and more often: a reply that says “wrong number”, a stranger calling back to ask who you are, a text that bounces. CTIA's messaging guidance expects senders to process carrier deactivation files regularly, daily if possible, and drop deactivated numbers from opt-in lists[6]. Each of these signals should change the record the same day, not wait for the next audit.
- Caller
- SI Employee
- Your team
- System
01Caller
Stranger replies or calls
“Wrong number, stop texting me”, or a call asking who the practice is.
02SI Employee
Message taken
Nothing about the patient is confirmed; the caller's number and request are noted.
03Your team
Record flagged same day
Mark the number invalid with the date and source of the report.
04System
Automated messages stop
The reminder tool skips flagged numbers on every future run.
05Your team
New number confirmed
Ask the patient via portal, mail or at check-in; log a new consent date.
Example sequence. A STOP reply already revokes consent for that number; the flag makes sure every tool, not just the texting app, honors it.
The confirmation at check-in does most of the work. Reading the number back to the patient, rather than asking “has anything changed?”, catches more stale numbers; updating patient demographics at every visit has a confirm script that takes seconds. Store the date of that confirmation next to the number, because it doubles as the date you send to the database.
What to say when the wrong person calls
The person who now owns the number is often annoyed and sometimes curious. The goal is to stop the messages and give away nothing. Do not confirm the patient's name, do not say what the reminder was for and do not ask the caller whether they know the patient.
Script: “Thank you for letting us know. I can't share anything about who those messages were meant for, but I've taken this number off our list today and you won't receive more texts from us. Is this the number you're calling from? I'll make sure that's the one we remove.”
These calls often come in at lunch or after hours, when the person who maintains the reminder list is not at the desk. If an SI Employee answers your overflow or after-hours line, add a wrong-number answer to its approved script: it takes the caller's number, confirms nothing about any patient and the call summary lands in the inbox of the staff member you choose (see what it does). The record change is still a staff job. For how one practice in our examples splits phone work between people and an SI Employee, see the family practice morning rush example.
A quarterly check that keeps the list honest
Pull every mobile number marked for texts
Export number, consent date and last-confirmed date from the practice management system. Numbers with no consent date get a task for the desk.
Query the database
Run the list, or the numbers due for messages next quarter, through the Reassigned Numbers Database or your vendor, using the consent or last-confirmed date for each number.
Act on yes and no data
Suspend automated messages to every “yes”. Queue every “no data” for confirmation at the next contact.
Reconcile wrong-number reports
Check that every wrong-number reply, bounce and deactivation notice from the quarter is flagged in the main record, not only inside the texting tool.
Spot-check templates
Read three live reminder templates as if you were a stranger. Remove anything that hints at a diagnosis or specialty.
Keep the query results with your compliance records. If a claim ever arrives, the defense is a dated query showing the number checked out on the consent date you held. The consent date itself comes from how you capture permission in the first place, which is the subject of capturing text consent at registration, and the preferences side is in capturing patient contact preferences.
Frequently asked questions
Does the Reassigned Numbers Database tell us who has the number now?
No. It returns only “yes”, “no” or “no data” for whether the number was permanently disconnected since the date you enter[1]. It never identifies the new subscriber.
Are practices required to use it?
No. The FCC describes use of the database as voluntary[1]. The benefit is the safe harbor: a caller who queried with the consent date, got a “no” and reached a reassigned number because the database was wrong is protected[5].
Our patient ported her number to a new carrier. Will it show as disconnected?
No. A ported number stays with the same person, and a line suspended for nonpayment is not a permanent disconnection either[8]. Neither needs action.
What date should we enter for a patient who has been with us for ten years?
The most recent date you confirmed the number with the patient, if you record it. The FCC's order allows any date on which you were reasonably sure the person could be reached at that number[1]. Carrier tracking only began in July 2020[8], so an older consent date leaves a gap.
Someone replied STOP and said it is not the patient's number. Is the STOP enough?
The STOP ends texts to that number from that tool, and FCC rules treat it as a valid revocation[5]. You still need to flag the number in the patient record so phone calls, other platforms and the next import do not reuse it.
References
Federal Communications Commission (2018). Advanced Methods to Target and Eliminate Unlawful Robocalls, Second Report and Order (FCC 18-177) (opens in a new tab) ↑
Electronic Code of Federal Regulations (National Archives) (2026). 47 CFR 52.15(f)(1)(ii): Aging numbers (opens in a new tab) ↑
Federal Communications Commission (2015). Rules and Regulations Implementing the Telephone Consumer Protection Act of 1991, Declaratory Ruling and Order (FCC 15-72) (opens in a new tab) ↑
Legal Information Institute, Cornell Law School (current). 47 U.S. Code § 227 - Restrictions on use of telephone equipment (opens in a new tab) ↑
Electronic Code of Federal Regulations (National Archives) (2026). 47 CFR 64.1200: Delivery restrictions (opens in a new tab) ↑
CTIA (2023). Messaging Principles and Best Practices (May 2023) (opens in a new tab) ↑
Electronic Code of Federal Regulations (National Archives) (2026). 45 CFR 164.402: Definitions (breach) (opens in a new tab) ↑
Reassigned Numbers Database Administrator (2026). Frequently Asked Questions (Reassigned Numbers Database) (opens in a new tab) ↑
Reassigned Numbers Database Administrator (2025). Reassigned Numbers Database (RND) - Subscription Pricing (opens in a new tab) ↑