Skip to main content
Menu Icon
Close

InfoBytes Blog

Financial Services Law Insights and Observations

Filter

Subscribe to our InfoBytes Blog weekly newsletter and other publications for news affecting the financial services industry.

  • New York expands definition of telemarketing to include text messages

    State Issues

    On July 13, the New York governor signed S.3941, which expands the state’s definition of telemarketing to include marketing by text message. A press release issued by the governor noted that expanding the definition closes a loophole in state law that previously limited the definition to phone calls, including unwanted robocalls. “Electronic text messages to [] mobile devices have become the newest unwelcomed invasive marketing technique. Consumers should not be burdened with excessive and predatory telemarketing in any form, including text messages,” the press release stated. The act takes effect 30 days after becoming law.

    State Issues State Legislation Privacy/Cyber Risk & Data Security Robocalls Consumer Protection Telemarketing

  • FCC signs robocall enforcement MOU with Australia

    Agency Rule-Making & Guidance

    On June 3, the FCC announced that it entered into a memorandum of understanding (MOU) with the Australian Communications and Media Authority (ACMA) on providing mutual assistance in the enforcement of laws on certain unlawful communications, such as robocall, robotexts, and “spoofing.” FCC Acting Chairwoman Rosenworcel noted that “[r]obocall scams are a global problem that require global commitment and cooperation” and that coordinating with ACMA can aid in removing scammers off of networks to protect consumers and businesses. ACMA Chair Nerida O’Loughlin noted that the agreement strengthens the existing relationship between the ACMA and the FCC in the regulation of unsolicited communications. According to the MOU, the FCC and ACMA understand that it is in their common public interest to, among other things: (i) “cooperate with respect to the enforcement against Covered Violations, including sharing complaints and other relevant information and providing investigative assistance”; (ii) enable “research and education related to unlawful robocalls and caller ID spoofing or overstamping”; (iii) “facilitate mutual exchange of knowledge and expertise through training programs and staff exchanges”: (iv) encourage awareness of economic and legal conditions and theories related to the enforcement of applicable laws as identified in Annex 1 to the MOU; and (v) update each other regarding developments related to the MOU in their respective countries in a timely manner.

    Agency Rule-Making & Guidance MOUs Robocalls FCC Federal Issues

  • 3rd Circuit: Alleging only a statutory violation of the TCPA does not establish standing to sue

    Courts

    On May 19, the U.S. Court of Appeals for the Third Circuit affirmed a district court’s dismissal of a proposed TCPA class action suit for lack of standing, finding that the named plaintiff did not claim anything other than a “bare procedural harm that resulted in no harm.” According to the opinion, the plaintiff—who worked as an investigator for an attorney who prepared TCPA lawsuits—received a prerecorded telemarketing call in 2005 from a marketing company on behalf of the defendant national bank. The plaintiff, using a false name and employer, then placed and recorded more than 20 investigative calls to the marketing company to determine the number and frequency of calls it made. He then provided the recordings to the bank and declined the marketing company’s offer to place him on their Do-Not-Call list. In 2011, the plaintiff sued the bank alleging a single count violation of the TCPA but did not allege that he suffered any annoyance or nuisance from the marketing company’s call. The bank moved for summary judgment, arguing that: (i) the plaintiff lacked Article III standing to sue; (ii) “the call was exempt from the TCPA under FCC rules because the parties had an established business relationship” because the plaintiff was a customer of the bank; and (iii) the recorded message’s content did not violate the TCPA. The district court agreed with the bank and granted summary judgment on all three grounds.

    On appeal, the Third Circuit disagreed with the plaintiff’s assertion that all he had to do was allege a statutory violation in order to have standing to sue, declining “to adopt such an absolute rule of standing with respect to the TCPA.” Because “the TCPA is intended to prevent harm stemming from nuisance, invasions of privacy, and other such injuries,” the plaintiff must allege at least one of those injuries to show concrete harm necessary to demonstrate an injury-in-fact and establish standing to sue, the appellate court wrote.

    Courts Appellate Third Circuit TCPA Robocalls Spokeo

  • FCC issues $4.1 million fine for deceptive robocalls

    Federal Issues

    On April 22, the FCC imposed a $4.1 million fine against a phone carrier for allegedly impersonating other carriers in telemarketing calls and deceiving consumers into changing carriers without consent. The FCC first proposed the fine in 2018 after the agency, state regulators, and the Better Business Bureau received many complaints about this conduct. According to the FCC, the company’s “actions specifically harmed elderly and infirm consumers who, in some cases, were left without telephone service for extended periods of time while the company refused to reinstate service until the unauthorized charges were paid in full.” FCC acting Chairwoman Jessica Rosenworcel issued a statement condemning the “ugly scam” as a violation of the Communications Act, and warned: “To anyone else using our nation’s phone systems to perpetuate this kind of scam, take note because our efforts won’t stop here.”

    Federal Issues FCC Robocalls Telemarketing Consumer Protection Enforcement

  • FCC pushes on robocall blocking

    Agency Rule-Making & Guidance

    On April 13, the FCC took several actions associated with blocking illegal and unsolicited robocalls, including sending cease and desist letters (see here and here) to two carriers that “appear to be transmitting multiple unlawful robocall campaigns” and seeking updated information from all carriers and developers of call-blocking tools to learn more about the tools available to consumers and their effectiveness. Key questions include:

    • Whether the companies are offering call blocking tools to consumers at no charge.
    • How the companies measure the effectiveness of blocking tools.
    • What protections the companies have put in place to ensure that call blocking does not interfere with emergency services.

    In addition to seeking input from the industry, the FCC sent cease and desist letters to two carriers regarding the transmission of illegal robocalls through their networks. The letters warn the carriers that downstream carriers will be authorized to block all of their traffic if they do not take steps within 48 hours to “effectively mitigate illegal traffic.”

     

    Agency Rule-Making & Guidance FCC Robocalls Privacy/Cyber Risk & Data Security

  • FCC issues record $225 million fine for spoofed robocalls

    Federal Issues

    On March 17, the FCC issued a record $225 million fine against two Texas-based telemarketers and their associated companies for allegedly transmitting roughly one billion illegally spoofed robocalls falsely claiming to offer plans issued by well known-health insurance companies. The Truth in Caller ID Act prohibits telemarketers from manipulating caller ID information with the intent to harm, defraud or wrongfully obtain anything of value. According to the FCC’s investigation, one of the companies’ allegedly spoofed robocalls “caused at least one company whose caller IDs were spoofed to become overwhelmed with angry call-backs from aggrieved consumers.” One of the telemarketers also apparently admitted that he placed millions of spoofed calls each day, including to numbers on the Do Not Call list. FCC acting Chairwoman Jessica Rosenworcel issued a statement commenting on the agency’s “largest fine ever,” in which she noted that the “individuals involved didn’t just lie about who they were when they made their calls—they said they were calling on behalf of well-known health insurance companies on more than a billion calls. That’s fraud on an enormous scale.”

    Federal Issues FCC Enforcement Robocalls Truth in Caller ID Act

  • FTC, multiple states halt charitable telefunding operation

    Federal Issues

    On March 4, the FTC, together with state attorneys general from 38 states and the District of Columbia, the secretaries of state from Colorado, Georgia, Maryland, North Carolina, and Tennessee, the Florida Department of Agriculture and Consumer Services, and the Utah Division of Consumer Protection (collectively, “plaintiffs”), announced settlements with a telefunding operation whose charitable fundraising calls allegedly collected over $110 million using deceptive solicitations. The plaintiffs’ complaint alleged, among other things, that the defendants engaged in deceptive fundraising by placing more than 1.3 billion prerecorded robocalls to convince consumers to donate to “practically nonexistent charitable programs.” The charitable organizations then paid the defendants typically 80 to 90 percent of every donation, the complaint states, noting that certain defendants knew that almost none of the donations would be spent supporting the charitable programs. The plaintiffs contended that these false or misleading actions violated the FTC Act. Moreover, in many instances, the plaintiffs alleged that the defendants knowingly violated the Telemarketing Sales Rule (TSR) by using soundboard technology to place the telemarketing calls. Using pre-recorded messages in calls to first-time donors is a violation of the TSR, the plaintiffs stated, as is using soundboard technology in calls to prior donors without first disclosing to recipients that they may opt-out of all future calls and providing them with a mechanism to do so.

    Proposed settlements (see here, here, and here) reached with one group of defendants will, among other things, permanently ban them from engaging in any fundraising activities, conducting telemarketing to sell goods or services, or using existing donor information. The defendants will also be required to pay $110,063,848 each, which is either partially or fully suspended due to the defendants’ inability to pay.

    Additionally, proposed settlements reached with the two fundraising company defendants and their senior managers (see here, here, and here) will permanently prohibit them from engaging in any fundraising activities or consulting on behalf of a charitable organization or nonprofit organization claiming to work on behalf of causes similar to those noted in the complaint. These defendants will also be banned from using robocalls connected to telemarketing, engaging in abusive calling practices, or making misrepresentations about a good, service, or contribution. The defendants will further be required to disclose when a donation is not tax deductible. The individual defendants also are required to pay $110,063,843 each, which is partially suspended due to the defendants’ inability to pay, while the two corporate defendants, along with two of the individual defendants, are subject to a partially suspended monetary judgment of $1.6 million.

    Federal Issues FTC Enforcement FTC Act Robocalls Telemarketing Sales Rule State Issues

  • Court cites 6th Circuit, rules TCPA covers autodialers using stored lists

    Courts

    On February 25, the U.S. District Court for the Northern District of West Virginia ruled that a satellite TV company cannot avoid class claims that it made unwanted calls to stored numbers using an automatic telephone dialing system (autodialer). The company filed a motion to dismiss plaintiff’s claims that it violated Section 227 of the TCPA when it made illegal automated and prerecorded telemarketing calls to her cellphone using an autodialer. The company argued, among other things, that the “statutory definition of an [autodialer] covers only equipment that can generate numbers randomly or sequentially,” and that “nothing in the complaint plausibly alleges that any of the calls were sent using that type of equipment.” According to the company, list-based dialing cannot be subject to liability under the TCPA. The court disagreed, stating that the TCPA makes it clear that it covers autodialers using stored lists. The court referenced a 6th Circuit decision in Allan v. Pennsylvania Higher Education Assistance Agency, which determined that “the plain text of [§ 227], read in its entirety, makes clear that devices that dial from a stored list of numbers are subject to the autodialer ban.” (Covered by InfoBytes here.) The court also referenced decisions issued by the 2nd, 6th, and 9th Circuits, which all said that the TCPA’s definition of an autodialer includes “autodialers which dial from a stored list of numbers.” However, these appellate decisions conflict with holdings issued by the 3rd, 7th, and 11th Circuits, which have concluded that autodialers require the use of randomly or sequentially generated phone numbers, consistent with the D.C. Circuit’s holding that struck down the FCC’s definition of autodialer in ACA International v. FCC (covered by a Buckley Special Alert). Currently, the specific definition of an autodialer is a question pending before the U.S. Supreme Court in Duguid v. Facebook, Inc. (covered by InfoBytes here). The court further ruled that three out-of-state consumers should be removed from the case as they failed to meet the threshold for personal jurisdiction, and also reiterated that the case could not be arbitrated as the company’s arbitration clause was “unconscionable.”

    Courts TCPA Autodialer Robocalls Appellate Sixth Circuit U.S. Supreme Court

  • FCC: Contractors must get consent to make robocalls under TCPA

    Federal Issues

    On December 14, the FCC released an order concluding that federal and state contractors are subject to the restrictions of the TCPA and must obtain prior express consent to call consumers. The order reverses a 2016 decision, which extended the presumption that “the word ‘person’ [in the TCPA] does not include the federal government absent a clear ‘affirmative showing of statutory intent to the contrary’” to calls made by contractors acting as agents of the federal government. The FCC acknowledges a number of requests to reconsider this conclusion, and in an effort to combat unwanted robocalls, the FCC now concludes that this presumption should not be extended to contractors. The FCC notes that there is “no longstanding presumption that a federal contractor is not a ‘person’” and the FCC did not “find any ‘context that otherwise requires’ [them] to ignore the express language of the Communications Act’s definition of the term ‘person’ in this situation.” While the presumption still applies to federal and state governments, the order clarifies that local governments are still considered a “person” under the TCPA and therefore, subject to the robocall restrictions without prior express consent.

    Federal Issues FCC TCPA Robocalls

  • Another district court dismisses TCPA action for lack of jurisdiction

    Courts

    On October 29, the U.S. District Court for the Northern District of Ohio dismissed a TCPA action against an energy service company and “ten John Doe corporations” (collectively, defendants), concluding that the court lacked jurisdiction over cases involving unconstitutional laws. According to the opinion, the plaintiff filed the putative class action against the defendants alleging the companies violated the TCPA by placing pre-recorded calls to the plaintiff’s cell phone without consent. While the action was pending, on July 6, the U.S. Supreme Court concluded in Barr v. American Association of Political Consultants Inc. (AAPC) that the government-debt exception in Section 227(b)(1)(A)(iii) of the TCPA is an unconstitutional content-based speech restriction (covered by InfoBytes here). The defendants moved to dismiss the action for lack of subject matter jurisdiction and the court agreed. Specifically, the court agreed with the defendants that the severance of Section 227(b)(1)(A)(iii) must be applied prospectively, thus, the statute can only be applied to robocalls made after July 6 and prior to 2015 (when the now unconstitutional government-debt exception in Section 227(b)(1)(A)(iii) was enacted). Because “the statute at issue was unconstitutional at the time of the alleged violations,” the court concluded it lacked subject-matter jurisdiction over the matter and dismissed the action.

    As previously covered by InfoBytes, the U.S. District Court for the Eastern District of Louisiana was the first known court to dismiss a TCPA action based on lack of jurisdiction over calls occurring after the exception’s enactment but prior to the Supreme Court’s decision on July 6.

    Courts TCPA U.S. Supreme Court Robocalls Class Action Subject Matter Jurisdiction

Pages

Upcoming Events