PERRONG v. CHASE DATA CORP.

CourtDistrict Court, E.D. Pennsylvania
DecidedJanuary 26, 2024
Docket2:22-cv-02628
StatusUnknown

This text of PERRONG v. CHASE DATA CORP. (PERRONG v. CHASE DATA CORP.) is published on Counsel Stack Legal Research, covering District Court, E.D. Pennsylvania primary law. Counsel Stack provides free access to over 12 million legal documents including statutes, case law, regulations, and constitutions.

Bluebook
PERRONG v. CHASE DATA CORP., (E.D. Pa. 2024).

Opinion

IN THE UNITED STATES DISTRICT COURT FOR THE EASTERN DISTRICT OF PENNSYLVANIA ANDREW R. PERRONG, Plaintiff, CIVIL ACTION v. NO. 22-2628 CHASE DATA CORP., et al., Defendants.

PAPPERT, J. January 26, 2024 MEMORANDUM Chase Data Corp., Dialed In Inc. and their owner Ahmed Macklai sell “turnkey” calling and texting services. Andrew Perrong received three text messages from Chase Data, each one asking him to call a specific phone number and discuss injuries he suffered—purportedly to generate “leads” that can be sold to personal injury attorneys. Perrong asserts these messages constitute violations of the Telephone Consumer Protection Act and brings three TCPA claims against Chase Data, Dialed In and Macklai, respectively. Defendants filed multiple motions to dismiss, which collectively seek to dismiss all claims against them. The Court grants the motions in part and denies them in part, allowing Perrong to amend his pleading as to certain claims. I In March 2022, Perrong received three text messages—each from a different caller ID owned and operated by Chase Data—asking him to call a different “855” to talk about his potential injuries and possible compensation. (Id. at ¶¶ 30–33; 35). Perrong claims that when he called the 855 numbers, he heard an identical pre- recorded message “asking to confirm an injury and whether the caller would like to speak with a personal injury lawyer.” (Id. at ¶ 33). Perrong alleges Chase Data’s customers use these messages to generate leads that can be sold to personal injury

attorneys. (Id. at ¶¶ 19–21). Perrong, a Pennsylvania resident, has a telephone number that is on the “Do Not Call Registry.” (Id. at ¶¶ 4, 23). Perrong’s number is assigned to a Voice over Internet Protocol service that charges a ring charge of $0.01 for each block of 160-character text messages sent. (Id. at ¶¶ 26, 28). Perrong filed an Amended Complaint asserting three counts against Chase Data, Dialed In and Macklai for alleged violations of specific provisions of the TCPA: (a) 47 U.S.C. § 227(b) which prohibits automated calling by using a pre-recorded message; (b) a separate provision of Section 227(b) which proscribes use of an automatic telephone dialing system (ATDS); and (c) Section 227(c) and three of its implementing

regulations. II To avoid dismissal under Federal Rule of Civil Procedure 12(b)(6), a complaint must “state a claim to relief that is plausible on its face.” Bell Atl. Corp. v. Twombly, 550 U.S. 544, 570 (2007). A claim is facially plausible if the plaintiff pleads facts from which the Court can infer “that the defendant is liable for the misconduct alleged.” Ashcroft v. Iqbal, 556 U.S. 662, 678 (2009). Though this “plausibility standard is not akin to a ‘probability requirement,’” it demands “more than a sheer possibility that a defendant has acted unlawfully.” Id. (quoting Twombly, 550 U.S. at 556). Assessing plausibility under Twombly and Iqbal is a three-step process. See Connelly v. Lane Const. Corp., 809 F.3d 780, 787 (3d Cir. 2016). Step one is to “take

note of the elements the plaintiff must plead to state a claim.” Id. (alterations omitted) (quoting Iqbal, 556 U.S. at 675). Next, the Court “should identify allegations that, ‘because they are no more than conclusions, are not entitled to the assumption of truth.’” Id. (quoting Iqbal, 556 U.S. at 679). Finally, for all “well-pleaded factual allegations, the court should assume their veracity,” draw all reasonable inferences from them “and then determine whether they plausibly give rise to an entitlement to relief.” Id. (alterations omitted) (quoting Iqbal, 556 U.S. at 679). If the well-pleaded facts do not nudge the “claims across the line from conceivable to plausible,” the Court must dismiss the complaint. Twombly, 550 U.S. at 570. III

Section 227(b)(1)(A)(iii) prohibits, with exceptions, making “any call . . . using any automatic telephone dialing system or an artificial or prerecorded voice . . . to any telephone number assigned to . . . any service for which the called party is charged for the call[.]" 47 U.S.C. § 227(b)(1)(A)(iii). A text message is a call under § 227(b)(1)(A). Campbell-Ewald Co. v. Gomez, 577 U.S. 153, 156 (2016). Section 227(c)(5) provides a private right of action for violations of regulations that the Federal Communications Commission promulgates pursuant to the TCPA. These regulations, inter alia, prohibit soliciting those on the “national do-not-call registry,” and require both a policy to maintain, and the maintenance of, a do-not-call list. 47 C.F.R. § 64.1200 (c)(1); (d)(1), (6). IV A

Defendants argue Perrong does not plausibly allege Chase Data’s direct or vicarious liability under the TCPA. See (Chase Data and Dialed In’s Am. Motion to Dismiss, p. 16, ECF No. 17). 1 A common carrier can violate the TCPA if it “was so involved in placing the call as to be deemed to have initiated it.” In the Matter of Rules & Regulations Implementing the Tel. Consumer Prot. Act of 1991, 30 FCC Rcd. 7961, 7980 (2015). In determining whether entities that provide software applications or platforms that facilitate calling fall within the TCPA’s restrictions, the FCC explained that it “look[s] to the totality of the facts and circumstances surrounding the placing of a particular

call to determine: (1) who took the steps necessary to physically place the call; and (2) whether another person or entity was so involved in placing the call as to be deemed to have initiated it, considering the goals and purposes of the TCPA.” 2015 TCPA Declaratory Ruling, 30 FCC Rcd. at 7980. 2 Perrong alleges Chase Data owned and operated the accounts used to contact his phone. (Am. Compl. ¶ 35). Chase Data provides “intimate support for their customers’ campaigns” and “hold[s] their customers’ hands.” (Id. at ¶¶ 17-18). The totality of these factual allegations give rise to the inference that Chase Data was directly involved in the alleged TCPA violations.1 See Wick v. Twilio Inc., No. C16-00914RSL, 2017 U.S. Dist. LEXIS 107936, *14 (W.D. Wash. July 12, 2017) (denying motion to dismiss TCPA claim because plaintiff alleged Twilio was an active participant in developing the message, choosing the order and timing of messages and “allowing, if not

promoting, unsolicited text message campaigns on its platform.”); compare with Meeks v. Buffalo Wild Wings, Inc. No. 17-cv-07129-YGR, 2018 U.S. Dist. LEXIS 52328 (N.D. Cal., Mar. 28, 2018) (dismissing TCPA claim against Yelp where complaint alleged that texts were sent by user of Yelp platform, and did not allege that Yelp decided whether, when or to whom to send messages).

1 Perrong also states plausible claims against Chase Data under a vicarious liability theory. “[T]he Federal Communications Commission has ruled that, under federal common-law principles of agency, there is vicarious liability for TCPA violations.” Campbell-Ewald Co. v. Gomez, 577 U.S. 153, 168, 136 S. Ct. 663, 193 L. Ed. 2d 571 (2016) (citing In re Joint Petition Filed by DISH Network, LLC, 28 FCC Rcd. 6574 (F.C.C. 2013)).

Free access — add to your briefcase to read the full text and ask questions with AI

Related

Bell Atlantic Corp. v. Twombly
550 U.S. 544 (Supreme Court, 2007)
Ashcroft v. Iqbal
556 U.S. 662 (Supreme Court, 2009)
In Re Merck & Co. Securities & ERISA Litigation
493 F.3d 393 (Third Circuit, 2007)
Oran v. Stafford
226 F.3d 275 (Third Circuit, 2000)
Sandra Connelly v. Lane Construction Corp
809 F.3d 780 (Third Circuit, 2016)
Campbell-Ewald Co. v. Gomez
577 U.S. 153 (Supreme Court, 2016)
KHS Corp. v. Singer Fin. Corp.
376 F. Supp. 3d 524 (E.D. Pennsylvania, 2019)
Pennsylvania ex rel. Zimmerman v. Pepsico, Inc.
836 F.2d 173 (Third Circuit, 1988)

Cite This Page — Counsel Stack

Bluebook (online)
PERRONG v. CHASE DATA CORP., Counsel Stack Legal Research, https://law.counselstack.com/opinion/perrong-v-chase-data-corp-paed-2024.