Phone numbers get reassigned to new subscribers every day. One reassigned number on your contact list means a $500-$1,500 TCPA violation. Learn how phone validation APIs detect reassigned numbers and keep your FCC safe harbor intact.
When a consumer gives consent to receive calls or SMS from your business, that consent is tied to that specific person—not the phone number. If the consumer abandons their number and the carrier reassigns it to someone else, your consent becomes legally worthless. Continuing to call or text that reassigned number violates the Telephone Consumer Protection Act (TCPA), regardless of the original consent.
Carriers reassign approximately 35 million phone numbers annually in the United States alone. Disconnected numbers typically re-enter the carrier pool within 30-90 days, and high-demand area codes see faster recycling. For businesses with contact lists exceeding 100,000 numbers, a statistically significant portion (3-8%) will be reassigned within any given quarter—creating a ticking liability bomb.
A customer signs up, makes a purchase, or opts into your SMS program. You record their consent with the phone number, date, and purpose. At this point, everything is compliant.
The original customer switches carriers, lets their plan lapse, or moves. The carrier marks the number as disconnected after a grace period (typically 30-60 days of non-payment or port-out). You have no way of knowing this happened.
After the aging period (30-90 days depending on the carrier), the number enters the available pool and gets assigned to a new subscriber. This new person has never heard of your business and never gave consent to receive your communications.
Your next marketing campaign sends a promotional SMS or verification code to the reassigned number. The new subscriber receives an unsolicited message. If they complain or a plaintiff's attorney identifies the pattern, you face TCPA liability. Each message is a separate violation at $500-$1,500.
TCPA statutory damages are severe and uncapped in aggregate. Each individual call or text to a reassigned number counts as a separate violation. The math escalates quickly:
| Campaign Size | Reassigned Rate | Messages Sent | Max Exposure |
|---|---|---|---|
| 10,000 contacts | 5% | 500 | $750,000 |
| 50,000 contacts | 5% | 2,500 | $3,750,000 |
| 100,000 contacts | 5% | 5,000 | $7,500,000 |
| 500,000 contacts | 5% | 25,000 | $37,500,000 |
TCPA class action lawsuits averaged $68 million in settlements during 2025. Plaintiff attorneys actively solicit TCPA cases because the statutory framework makes them lucrative. They identify businesses sending messages to reassigned numbers by signing up for competitor lists with burner numbers, then tracking which messages they receive from businesses that never contacted them directly. Even small businesses face class action exposure—settlements under $5 million still represent existential financial risk for most SMBs.
Real Example: In 2025, a mid-sized e-commerce company settled a TCPA class action for $12.3 million after sending promotional SMS to 47,000 reassigned numbers. The original consent was valid—but the numbers had been reassigned within 18 months.
The FCC Reassigned Numbers Database is your primary safe harbor tool—it provides a legal defense when a number was permanently disconnected and reassigned after your consent date. But the RND has critical limitations that phone validation APIs fill:
| Detection Layer | What It Checks | Coverage |
|---|---|---|
| FCC RND Query | Permanent disconnection and reassignment records | ~95% of US reassignments |
| Carrier Status Check | Current subscriber active/disconnected status | Real-time carrier data |
| Line Type Detection | Mobile vs. VoIP vs. landline changes since consent | 232 countries, 99.6% accuracy |
| Carrier Change Detection | Number porting or carrier switch since last contact | Portability database queries |
| Number Status Validation | Active, inactive, disconnected, or unallocated status | Real-time, 50ms response |
async function checkReassignment(phoneNumber, consentDate) {
// Step 1: Validate number format and real-time status
const validation = await fetch(
'https://api.phone-check.app/v1/phone/validate',
{
method: 'POST',
headers: {
'Content-Type': 'application/json',
'Authorization': 'Bearer YOUR_API_KEY'
},
body: JSON.stringify({
phone_number: phoneNumber,
include_carrier: true,
include_line_type: true,
include_portability: true
})
}
);
const result = await validation.json();
// Step 2: Check if number is currently active
if (result.status === 'disconnected' || result.status === 'unallocated') {
return {
risk_level: 'high',
action: 'remove_from_list',
reason: 'Number is disconnected or unallocated'
};
}
// Step 3: Detect line type changes (reassignment signal)
if (result.line_type_history) {
const originalType = result.line_type_history.original;
const currentType = result.line_type.current;
if (originalType !== currentType) {
return {
risk_level: 'high',
action: 'flag_for_reconsent',
reason: `Line type changed from ${originalType} to ${currentType}`
};
}
}
// Step 4: Check carrier changes
if (result.portability && result.portability.recently_ported) {
return {
risk_level: 'medium',
action: 'flag_for_reconsent',
reason: 'Number was recently ported to new carrier'
};
}
// Step 5: Query FCC Reassigned Numbers Database
const rndResult = await queryFCCRND(phoneNumber, consentDate);
if (rndResult.is_reassigned) {
return {
risk_level: 'critical',
action: 'remove_from_list',
reason: 'FCC RND confirms reassignment'
};
}
return { risk_level: 'low', action: 'proceed' };
}{
"phone_number": "+14155551234",
"is_valid": true,
"status": "active",
"line_type": {
"current": "mobile",
"carrier": "T-Mobile US",
"mcc": "310",
"mnc": "260"
},
"portability": {
"is_ported": true,
"original_carrier": "AT&T Mobility",
"ported_date": "2025-11-15",
"recently_ported": true,
"porting_days_ago": 116
},
"carrier_info": {
"name": "T-Mobile US",
"country": "US",
"network_type": "mobile"
},
"validation_timestamp": "2026-03-11T14:30:00Z",
"response_time_ms": 47
}Phone-check.app's bulk CSV upload feature lets you screen entire contact lists against the phone validation API and FCC RND simultaneously. Upload multiple CSV files containing your subscriber lists, lead databases, or marketing contacts. The system validates every number in real-time, flags reassigned numbers, and exports a clean list with only verified, consented contacts.
The workflow eliminates reassigned numbers before they reach your SMS gateway: validate → detect line type → check carrier → cross-reference RND → flag/remove reassigned → export clean list. This prevents TCPA exposure at the source rather than reacting to complaints after the fact.
| Scenario | Before Screening | After Screening |
|---|---|---|
| Reassigned Numbers | Hidden in list | Detected and removed |
| Disconnected Numbers | Wasted SMS spend | Filtered out |
| Line Type Changes | Undetected | Flagged for re-consent |
| Carrier Porting | No visibility | Tracked and scored |
| TCPA Compliance Risk | High | Minimal |
Record the exact date and time of each consent. This date becomes your benchmark for FCC RND queries. If a number was reassigned after the consent date, you have safe harbor protection. Without accurate timestamps, you cannot prove when consent was given.
Run phone validation on your entire contact list before each SMS campaign. Numbers can be reassigned between campaigns. A quarterly screening catches 85% of reassignments, but monthly screening catches 97%. Real-time API calls before each send catch virtually all of them.
When a subscriber provides consent, validate and record their line type (mobile, landline, VoIP). If future validation shows the line type changed, it signals a likely reassignment—even if the RND hasn't updated yet. This gives you a secondary detection signal.
When your system detects a potential reassignment (line type change, carrier port, RND mismatch), pause communications and trigger a re-consent request. A simple double opt-in via SMS or email confirms whether the current subscriber wants to hear from you. If they don't respond, remove them.
| Metric | Without Detection | With Detection |
|---|---|---|
| TCPA Violation Risk | 3-8% of contacts | <0.1% of contacts |
| Annual Legal Exposure (100K list) | $3.75-15M | <$75K |
| API Cost (per validation) | $0 | $0.003-0.008 |
| Annual API Cost (100K list, monthly) | $0 | $3,600-9,600 |
| Wasted SMS on Reassigned Numbers | 3-8% of SMS budget | <0.1% of SMS budget |
Bottom Line: For a 100,000-contact list, spending $5,000-10,000 per year on phone validation and RND screening reduces TCPA exposure from millions of dollars to near zero. That's a 375:1 risk reduction ratio for an investment smaller than one TCPA violation fine.
The FCC Reassigned Numbers Database (RND) is a centralized database that tracks when phone numbers are permanently disconnected and later reassigned to new subscribers. Established under the FCC's 2021 TCPA rules, it allows businesses to verify whether consent was given by the current subscriber versus a previous owner. A single query to the RND before calling or texting provides a "safe harbor" defense against TCPA litigation if the number was reassigned after the consent date.
TCPA violations carry statutory damages of $500 per violation for negligent violations and $1,500 per violation for willful or knowing violations. Courts can also award actual damages and uncapped punitive damages. With class action lawsuits, total exposure can reach millions. A single batch of 10,000 SMS messages sent to reassigned numbers could theoretically expose a business to $5-15 million in statutory damages, even if the original contacts were consensual.
Phone validation APIs provide real-time intelligence about whether a number has been reassigned by checking: (1) carrier data to confirm current subscriber status, (2) line type changes indicating reassignment, (3) recent carrier porting or disconnection events, and (4) number status (active, disconnected, reassigned). When combined with FCC RND queries, phone validation creates a multi-layered defense that catches reassignments the RND alone might miss, such as temporary disconnections and same-carrier reassignments.
The TCPA safe harbor provision protects businesses from liability when they call or text a reassigned number, provided they checked the FCC Reassigned Numbers Database before contact. If the RND indicates the number was permanently disconnected and reassigned after the consent date, the caller has a complete defense against TCPA claims. The safe harbor applies to both calls and texts, and covers all industries. However, it only protects against reassignment claims—not other TCPA violations like lack of initial consent.
Protect your business from TCPA violations with real-time reassigned number detection. Phone-check.app validates every number against carrier databases and supports FCC RND integration—giving you complete compliance coverage before you send a single message.
Navigate GDPR and CCPA requirements for phone number verification with actionable compliance strategies.
Stay compliant with evolving SMS carrier regulations, A2P 10DLC requirements, and messaging policies.
Upload CSV files and validate thousands of phone numbers in minutes. Remove invalid, disconnected, and reassigned contacts.
Learn strategies to maintain clean phone databases, detect decay, and prevent wasted marketing spend.