TCPA & Reassigned Numbers
In a number of scenarios the TCPA (Telephone Consumer Protection Act) requires businesses to have consent before calling consumers. When a phone number is reassigned to a new person, your previous consent is no longer valid as consent is tied to an individual, not a specific phone number. Our Reassigned Authority APIs help you identify reassigned phone numbers to maintain compliance.Why Reassigned Number Detection Matters
When a consumer gives you consent to call them, that consent is tied to:- That specific person
- That specific phone number
Available APIs
Reassigned Authority Plus
Enhanced reassigned number detection with additional data points. Uses both
the FCC Reassigned Number Database plus more frequently updated carrier
deactivation data. Goes further back than the FCC Reassigned Number
Database.
RND Basic API
Basic reassigned number detection for high-volume screening.
Reassigned Authority
Reassigned number detection based on carrier deactivation data.
Basic RND
Basic reassigned number data using only the FCC’s Reassigned Number
database.
File Formats for SFTP or Web Portal
File Formats
Batch file processing formats for bulk reassignment checking doing via SFTP or
Web Portal
How It Works
- Store the consent date when a consumer gives you permission to call
- Before calling, check if the number has been reassigned since that date
- If reassigned, do not call - the number now belongs to someone else
Example Workflow
Key Response Values
| IsReassigned | Meaning | Action |
|---|---|---|
true | Number was reassigned after the consent date | Do not call |
false | Number has not been reassigned | Safe to call |
null | Insufficient data to determine | Use caution |
Additional Information Returned
The TCPA Authority API also returns useful phone number information:- Line Type - Wireless, VoIP, Landline, or Paging
- Carrier - Original carrier assignment
- Location - City, region, country
- Timezone - For calling time compliance