{"id":3767,"date":"2021-03-19T11:26:03","date_gmt":"2021-03-19T16:26:03","guid":{"rendered":"http:\/\/blogs.luc.edu\/compliance\/?p=3767"},"modified":"2021-03-19T11:26:03","modified_gmt":"2021-03-19T16:26:03","slug":"let-it-ring","status":"publish","type":"post","link":"https:\/\/blogs.luc.edu\/compliance\/?p=3767","title":{"rendered":"Let It Ring"},"content":{"rendered":"<p><em>Patrick Lucas<\/em><\/p>\n<p><em>Associate Editor<\/em><\/p>\n<p><em>Loyola University Chicago School of Law, JD 2022<\/em><\/p>\n<p>A full year of quarantine, and a whole lot of spam. You wouldn\u2019t be alone in noticing that telemarketer and spam calls have proliferated in the past year of lockdown. The Federal Trade Commission (\u201cFTC\u201d) has noticed, too: the tail end of 2020 saw the agency file its first ever complaint against a VoIP service provider for enabling scammers to make robocalls. Just weeks later, they filed their second. The agency is making clear that this new method of enforcement will help combat the issue\u2014but is it?<!--more--><\/p>\n<p><strong>VoIP\u2014what is it?<\/strong><\/p>\n<p><a href=\"https:\/\/www.fcc.gov\/general\/voice-over-internet-protocol-voip\">VoIP<\/a>, or Voice over Internet Protocol, allows users to transmit voice and audio signals from a computer or phone across interest connections to another computer or phone. Essentially, one can make phone calls from a computer. These days, we think of Skype, FaceTime Audio, or WhatsApp, but it can still even be a traditional phone call. When computers, or other technologies, automate both the calling process and the message being delivered, you get the phenomenon known as \u201crobocalling\u201d.<\/p>\n<p>VoIP is not a new technology; nor is <a href=\"https:\/\/simpsons.fandom.com\/wiki\/AT-5000_Auto-dialer\">robocalling<\/a>: both were developed in the 1970s and 1980s, rising in popularity in the 1990s and 2000s. Today, apps utilizing VoIP are commonplace features on any new smartphone\u2014the tech is relatively low cost and simplified at this point.<\/p>\n<p><strong>Regulators\u2014mount up<\/strong><\/p>\n<p>The Federal Communications Commission (\u201cFCC\u201d) handles the majority of <a href=\"https:\/\/www.fcc.gov\/consumers\/guides\/voice-over-internet-protocol-voip\">VoIP regulation<\/a>. Much like traditional telephone service, FCC <a href=\"https:\/\/www.fcc.gov\/general\/voice-over-internet-protocol-voip\">dictates<\/a> how this technology is to be utilized for mass communications, including for specialized services like 911 and other emergencies, as well as accessibility to those with disabilities.<\/p>\n<p>The FTC gets involved, however, when VoIP is used as a means to advertise or otherwise conduct business with consumers in an unfair or deceptive way. This tracks with pretty much any action taken by the agency. FTC has targeted telemarketers since the 1990s, when Congress <a href=\"https:\/\/www.law.cornell.edu\/uscode\/text\/15\/6102\">directed<\/a> the agency to address the issue via the Telemarketing and Consumer Fraud and Abuse Prevention Act. The resulting regulation was the Telemarketing Sales Rule (\u201cTSR\u201d), 16 C.F.R. Part 310.<\/p>\n<p><strong>FTC in action<\/strong><\/p>\n<p>In September 2020, FTC announced a <a href=\"https:\/\/www.ftc.gov\/news-events\/press-releases\/2020\/09\/globex-telecom-associates-will-pay-21-million-settling-ftcs-first\">settlement agreement<\/a> for its first-ever Consumer Protection action against a VoIP service provider. The $2.1 million settlement arose out of an FTC action taken against Globex, Inc., a VoIP service provider, for facilitating and enabling a telemarketing scheme to be conducted by several of its clients. FTC used the TSR to bring the action, alleging that Globex knowingly allowed clients to conduct a fraudulent telemarketing scheme to sell a credit card interest reduction rate program. Not only was the program fraudulent; the means by which it was communicated violated the TSR by utilizing robocalling and accessing numbers on FTC\u2019s Do Not Call Registry. Globex, as the VoIP service provider, agreed to pay $1.9 million of the $2.1 million total settlement. FTC mandated that, moving forward, Globex properly screen clients who will use their VoIP service, and block any outgoing calls that appear to be suspicious or harassing.<\/p>\n<p><strong>Round two<\/strong><\/p>\n<p>FTC doubled down on VoIP-targeted enforcement just weeks later when it went after another company, <a href=\"https:\/\/www.ftc.gov\/news-events\/press-releases\/2020\/12\/ftc-takes-action-against-second-voip-service-provider\">Alcazar Networks, Inc.<\/a>, for very similar actions. The FTC used more charged language in describing the defendants\u2014labelling them the \u201cgatekeepers\u201d to illegal telemarketing conduct. Alcazar\u2019s clients used many familiar tactics: robocalling with pre-recorded messages, spoofing incoming call numbers to appear as \u201c911\u201d or other government services, and accessing people on the Do Not Call Registry. According to the FTC, Alcazar allowed tens of millions of illegal calls to be placed over its VoIP service. And for that, they would be punished.<\/p>\n<p>Here, FTC proposed a settlement agreement where Alcazar would pay $105,562 in the judgement. Additionally, they must severe all ties with any client violating the TSR and must authenticate and monitor the traffic on their service. It is unclear whether the significantly lower monetary penalty, when compared to the Globex settlement, stems from an inability to pay or perhaps because the violation wasn\u2019t as great.<\/p>\n<p><strong>The final message<\/strong><\/p>\n<p>The message from FTC is that compliance with TSR is not optional and is not to be taken lightly. However, in a <a href=\"https:\/\/www.ftc.gov\/system\/files\/documents\/public_statements\/1584050\/wilson-statement-alcazar.pdf\">statement<\/a> of concurrence on the Alcazar decision, Commissioner Christine S. Wilson clarified a point that these violations are not strict liability, and that VoIP providers must knowingly aid, or willfully ignore, violators to be subject to action.<\/p>\n<p>Perhaps this statement was meant to clear things up\u2014to show VoIP providers that FTC isn\u2019t just out to get everyone. But does this sort of hedging language effectively put providers on alert? And with such inconsistent monetary punishment, might non-compliance be more profitable than the punishment of getting caught?<\/p>\n<p>In the months since these decisions, spam calls have not slowed. It is likely we will see more action from FTC. Is it the answer we\u2019re looking for?<\/p>\n","protected":false},"excerpt":{"rendered":"<p>A full year of quarantine, and a whole lot of spam. You wouldn\u2019t be alone in noticing that telemarketer and spam calls have proliferated in the past year of lockdown. The Federal Trade Commission (\u201cFTC\u201d) has noticed, too: the tail end of 2020 saw the agency file its first ever complaint against a VoIP service provider for enabling scammers to make robocalls. Just weeks later, they filed their second. The agency is making clear that this new method of enforcement will help combat the issue\u2014but is it?<\/p>\n","protected":false},"author":62,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[29],"tags":[807,914,1736,1869,1960,2101],"class_list":["post-3767","post","type-post","status-publish","format-standard","hentry","category-fraud-abuse","tag-fcc","tag-ftc","tag-robocall","tag-spam","tag-telemarketer","tag-voip"],"_links":{"self":[{"href":"https:\/\/blogs.luc.edu\/compliance\/index.php?rest_route=\/wp\/v2\/posts\/3767","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/blogs.luc.edu\/compliance\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blogs.luc.edu\/compliance\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blogs.luc.edu\/compliance\/index.php?rest_route=\/wp\/v2\/users\/62"}],"replies":[{"embeddable":true,"href":"https:\/\/blogs.luc.edu\/compliance\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=3767"}],"version-history":[{"count":0,"href":"https:\/\/blogs.luc.edu\/compliance\/index.php?rest_route=\/wp\/v2\/posts\/3767\/revisions"}],"wp:attachment":[{"href":"https:\/\/blogs.luc.edu\/compliance\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=3767"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blogs.luc.edu\/compliance\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=3767"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blogs.luc.edu\/compliance\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=3767"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}