Robo Zap Protocol (RZP)

ROBO ZAP PROTOCOL (RZP) This method will utilize a combination of techniques to zap robo calls. The method is cost-effective and easy to rollout and would work in 95% of the cases.

Step 1: Identify/narrow down the problem:

a) Most of the robo-calls are made either from blocked/unknown numbers or numbers that are identified as landline/VoIP numbers. There are hardly any robocalls made from cellphones. b) The FTC already has a database of numbers that are identified as cell-phones. This is a part of the database thats used for Number Portability. All the numbers in the database whose ownership is listed with Mobile Operators can be identified as cellphones. c) So the problem set of numbers are the unknown/blocked numbers and the non-cellphone numbers.

Step 2: Validate if the calls from the problem numbers are real calls.

a) Any call from a blocked or non-cell phone caller should be validated by asking the user to enter some kind of captcha mechanism. It could be asking them to enter the answer to a simple math problem using the phone keypad.

b) White-list identified callers: Callers who can enter the captcha a set number of times (Say 5) should be whitelisted, so that their future calls can pass through to without being screened. Unknown or blocked callers can obviously never be whitelisted.

c) The white-listed number should be reset every time it changes ownership. This would prevent a previously whitelisted number to be used for robocalls.

Step 3: Eliminate "problem numbers" from the remaining pool.

a) If anyone tries to bypass this mechanism by either utilizing a cellphone number or a white-listed number for robocalls, this third step would tackle the problem. This step would create a user-reported blacklist, which can be used for further screening.

b) There should be an easy mechanism to automatically report a robocall. One way could be to input a set of keys like (*0#) during the call. When a user reports a call, the calling number would automatically be entered into a blacklist.

c) When a number is blacklisted the first time, the next 5 calls made from that number would be subject to screening as described in Step 2 (a). This would give a legitimate user a benefit of doubt and would address issues like improper/inadvertent spam reporting.

d) However, if 5 different users report a particular number for robocalls, then the number should be automatically reported to the concerned telephone company for generating spam calls. It should also be added to a blacklist where all future calls from that number would be screened by default.

e) A number should be automatically un-blacklisted in case the ownership of the number changes. This would prevent future owners of a problem number from being hassled unnecessarily. A mechanism should be present to un-blacklist culprit numbers by calling a toll-free number or via the web. This would help in cases where someone gets blacklisted in error or in cases where the automatic un-blacklisting for changed numbers doesn't work as intended.