Identifying recycled telephone numbers
View Patent ↗An automated method begins by receiving a list of numbers that have been de-activated by a carrier. Periodically, and for each number, a request is made to identify a current carrier for the number. If the current carrier matches the carrier that provided the de-activation information, the mobile number is considered to be in a first state, i.e., shut off and returned to a pool of numbers that are available to this same carrier. Upon a determination that the number is in the first state, the provider issues a request to any opt-in database to delete any express consent or other similar data associated with the number. If, however, the number does not match the carrier of deactivation, the number is considered to be in a second state, i.e., likely to have been ported by the same user to a new carrier. This state is logged in an audit trail.
1. An apparatus operative in association with one or more service provider opt-in databases, comprising:
one or more hardware processors;
computer memory holding computer program instructions executed by the one or more hardware processors to:
receive one or more de-activation lists from one or more carriers;
periodically, and for each telephone number identified on a given de-activation list, issue a request to determine a current carrier associated with that telephone number;
when the current carrier matches an identification of a carrier that had identified the telephone number as being de-activated, identify the telephone number as being recycled; and
for each recycled telephone number, issue to each of the one or more service provider opt-in databases an instruction to delete any opt-in data associated with the telephone number.
2. The apparatus as described in claim 1 wherein the telephone number is a mobile telephone number.
3. The apparatus as described in claim 1 wherein the opt-in data is associated with an express consent.
4. The apparatus as described in claim 1 wherein the instruction is issued programmatically.
5. The apparatus as described in claim 1 wherein the request is issued over an application programming interface (API).
6. The apparatus as described in claim 1 wherein the computer program instructions execute as software-as-a-service.
7. The apparatus as described in claim 1 wherein when the current carrier does not match an identification of a carrier that had identified the telephone number as being de-activated, the computer program instructions are further operative to identify the telephone number as being ported.
8. A method for managing one or more service provider opt-in databases, the method comprising:
receive, by a processor, one or more de-activation lists from one or more carriers;
periodically, and for each telephone number identified on a given de-activation list, issuing, by the processor, a request to deteimine a current carrier associated with that telephone number;
when the current carrier matches an identification of a carrier that had identified the telephone number as being de-activated, identifying, by the processor, the telephone number as being recycled; and
for each recycled telephone number, issuing, by the processor, to each of the one or more service provider opt-in databases an instruction to delete any opt-in data associated with the telephone number.
9. The method of claim 8 , wherein the telephone number is a mobile telephone number.
10. The method of claim 8 , wherein the opt-in data is associated with an express consent.
11. The method of claim 8 , wherein the instruction is issued programmatically.
12. The method of claim 8 , wherein the request is issued over an application programming interface (API).
13. The method of claim 8 , wherein when the current carrier does not match an identification of a carrier that had identified the telephone number as being de-activated, the method further comprises identifying, by the processor, the telephone number as being ported.