How will this improve revenue or reduce our costs? Please provide a complete explanation!
Sometimes we try to port a phone number and fail to do so or debug why a phone number is not callable, when it turns out the number is not active with the losing carrier, wasting our time and energy.
Is your feature request related to a problem? Please describe.
Additional problems this helps with include:
Advising if a number is no longer textable due to deactivation
Helping our clients maintain TCPA compliance
Describe the solution you'd like
We should query this endpoint to build a table of all deactivated numbers and when they were deactivated. It would also be nice to blacklist blocks of phone numbers that have not been assigned yet.
It might also be useful to pull the ocnlist.csv from telcodata.us to help us true up which carriers own which OCNs. npa-nxx-state-company-etc-thousands.csv can also provide historical data on the original carrier of a number, when it was assigned to said carrier, and what ratecenter the number belongs to (since we have to keep a number in the same ratecenter when porting usually), and then we also know which North American Numbering Plan numbers are actually valid.
Additional context
There is also the Reassigned Numbers Database (managed by Somos, created by the FCC 2 years ago), but the pricing at scale is significantly more than a LRN query, and we get the same data from the deactivation reports for wireless carriers. The RND claims to have 305 million blacklisted numbers.
Querying the RND does offer a TCPA Safe Harbor to businesses that query it (the fact that you queried is not stored by Somos or the FCC though, unless you do a file upload to query, and even that only is stored for 45 days). I do not believe the RND dataset overlaps with the Do Not Call database, and Do Not Call makes it possible for us and our clients to get new database copies regularly.
Long term, it would be nice to give our clients a way to easily query these datasets (Disconnected Numbers, RND, Do Not Call, etc) from their softphone, via click to call, or on a deskphone if we could run an XML app before placing a call, that way they can establish safe harbor with ease. This would depend on us offering a billed API (@uncheckederror's department) and then making this easy to use for our end users (@thefinn93's department).
Looks like there are currently 335 area codes in the USA, with 7,919,000 possible numbers per area code (2.65 billion potential numbers) of which only a subset of which are actually assignable (eg: the NPA-NXX or thousands block from an NPA-NXX is assigned to a carrier),
danry25
commented
11 months ago
How will this improve revenue or reduce our costs? Please provide a complete explanation! Sometimes we try to port a phone number and fail to do so or debug why a phone number is not callable, when it turns out the number is not active with the losing carrier, wasting our time and energy.
Is your feature request related to a problem? Please describe. Additional problems this helps with include:
Describe the solution you'd like We should query this endpoint to build a table of all deactivated numbers and when they were deactivated. It would also be nice to blacklist blocks of phone numbers that have not been assigned yet.
It might also be useful to pull the ocnlist.csv from telcodata.us to help us true up which carriers own which OCNs. npa-nxx-state-company-etc-thousands.csv can also provide historical data on the original carrier of a number, when it was assigned to said carrier, and what ratecenter the number belongs to (since we have to keep a number in the same ratecenter when porting usually), and then we also know which North American Numbering Plan numbers are actually valid.
Additional context There is also the Reassigned Numbers Database (managed by Somos, created by the FCC 2 years ago), but the pricing at scale is significantly more than a LRN query, and we get the same data from the deactivation reports for wireless carriers. The RND claims to have 305 million blacklisted numbers.
Querying the RND does offer a TCPA Safe Harbor to businesses that query it (the fact that you queried is not stored by Somos or the FCC though, unless you do a file upload to query, and even that only is stored for 45 days). I do not believe the RND dataset overlaps with the Do Not Call database, and Do Not Call makes it possible for us and our clients to get new database copies regularly.
Long term, it would be nice to give our clients a way to easily query these datasets (Disconnected Numbers, RND, Do Not Call, etc) from their softphone, via click to call, or on a deskphone if we could run an XML app before placing a call, that way they can establish safe harbor with ease. This would depend on us offering a billed API (@uncheckederror's department) and then making this easy to use for our end users (@thefinn93's department).
Looks like there are currently 335 area codes in the USA, with 7,919,000 possible numbers per area code (2.65 billion potential numbers) of which only a subset of which are actually assignable (eg: the NPA-NXX or thousands block from an NPA-NXX is assigned to a carrier),