"Hit ## to disconnect," creates another route to terminate a call; one that sends a signal to the phone company indicating that the active call should be marked as a robocall. Once this signal has been sent, no further action from the person who receives the robocall would be required. Once the ## signal has been sent by the phone, the user can then put their phone away as usual, because the line from the user's end would be disconnected. However, since the ## signal is sent before the connection has been disconnected, there remains some opportunity to keep the connection active for analysis. The call, for instance, can then be routed to a separate center for analysis.
An in-call signal to the phone company by the user is the smallest hurdle that we can hope to design for this problem and "## to disconnect" does just this. "## to disconnect" is a simple procedure that can be propagated among users without much expenditure, all the while giving us the most amount of time for data collection and analysis. Since "## to disconnect" is just another method for disconnecting the call, there is no chance of abuse. Since the call can still remain active on the offender's side, we don't have to rely on caller id received from the user in order to identify the offender.
Thanks for your time. Hope we get this problem solved. I myself received 6 calls in the past 2 months.
Log in or sign up for Devpost to join the conversation.