MEMORANDUM OPINION AND ORDER

VALERIE CAPRONI, District Judge.

Plaintiffs Christina Melito, Christopher Legg, Alison Pierce, and Walter Wood (collectively, "Plaintiffs") bring this putative class action against American Eagle Outfitters and AEO Management Co. (collectively, "AEO") and Experian Marketing Solutions, Inc. ("Experian") (collectively, "Defendants"), for violations of the Telephone Consumer Protection Act, 47 U.S.C. § 227 et seq. ("TCPA"). In the Consolidated Third Amended Complaint ("TAC"), Plaintiffs, individually and on behalf of four potential classes, allege Defendants violated the TCPA by sending them unsolicited commercial text messages ("Spam Texts"). Defendant Experian moves to dismiss the TAC in its entirety under Fed. R. Civ. P. 12(b)(6) for failure to state a claim. For the following reasons, Experian's Motion to Dismiss is GRANTED.1

BACKGROUND2

Plaintiffs' claims arise from a marketing campaign that involved using text messages or "Short Message Services" ("SMS") to advertise. TAC ¶¶ 20, 27. AEO sells clothing, accessories, and personal care products under the American Eagle Outfitters and Aerie brands. Id. ¶¶ 25-26.3 Experian provides marketing services, including mass text message advertising, to clients such as AEO. Id. ¶ 31. According to Plaintiffs, AEO "makes, either directly or through Experian, SMS calls using ATDS [Automatic Telephone Dialing System] equipment and software" to cellular telephones whose owners have not provided express consent to receive such messages. Id. ¶ 28 (defining these SMS as "Spam Texts"). Plaintiffs allege that AEO hired Experian "to send Spam Texts on its behalf in November 2013," id. ¶ 32, and that starting around November 21, 2013, Experian "caused the transmission of Spam Texts on behalf of AEO." Id. ¶ 38. In explaining how Experian "caused texts to be sent on behalf of AEO," id. ¶ 33, the TAC presents the following chart, which illustrates, in relevant part, the program flow for transmitting Spam Texts to consumers:

Id. ¶ 33. According to the TAC:

Id. ¶ 34. Plaintiffs contend that "there is no human intervention in the actual dialing of the texts" and "the texts are sent out from a database list en masse by the thousands without human intervention." Id. ¶ 37. AEO approves the content prior to Experian causing the Spam Texts to be sent, id. ¶ 39, and Experian provides AEO with reports on the Spam Texts sent, id. ¶¶ 40.

The TAC asserts that "Experian had control over the texts sent" insofar as Experian contracted with AEO to send the texts, received the campaign request form and the campaign ready file from AEO, sent the information to Archer4 to use Archer's platform, scheduled the text messages to be sent, and sent AEO reports on the results of the text messaging campaigns. Id. ¶¶ 42, 44. The TAC contends that "to the extent that Experian is not directly liable, it is vicariously liable for the actions of Archer to the extent that Archer is deemed to have sent the texts. Archer is Experian's agent because Experian used Archer's texting platform to send the texts." Id. ¶ 43.

The TAC alleges facts specific to each individual plaintiff. Plaintiffs Melito and Woods never provided "prior express consent, either written or oral, to receive Spam Texts on [their] cellular telephone[s] from, or on behalf of, AEO." Id. ¶¶ 49, 81. Plaintiffs Legg and Pierce5 both texted STOP in response to several text messages sent on behalf of AEO. Id. ¶¶ 55-61, 67-68. Notwithstanding their requests not to receive texts, both continued to receive messages from AEO. Id. ¶¶ 62, 69.6

Plaintiffs assert four causes of action: two for violations of section 227(b)(1)(A) of the TCPA (counts 1 and 3), id. ¶¶ 94-98, 104-108, and two for "knowing and/or willful" violations of section 227(b)(1)(A) of the TCPA (counts 2 and 4), id. ¶¶ 99-103, 109-113. The first and second causes of action are "[b]rought on behalf of Plaintiffs Melito and Wood and members of the AEO Spam Text Class and Experian Spam Text Subclass." Id. ¶¶ 94-103. The third and fourth causes of action are "[b]rought on behalf of Plaintiffs Legg and Pierce and members of the AEO Revocation Class and Experian Revocation Subclass." Id. ¶¶ 104-113. Plaintiffs assert that each of the four causes of action is brought "against Experian as the sender of the Spam Texts" and AEO because it is liable for the actions of Experian as well as its own actions in causing the Spam Texts to be sent without consent. Id. ¶¶ 95, 100, 105, 110. Plaintiffs seek statutory damages and injunctive relief. Id. ¶¶ 97-98, 102-103, 107-108, 112-113.

DISCUSSION

To survive a motion to dismiss for failure to state a claim upon which relief can be granted, "a complaint must contain sufficient factual matter, accepted as true, to `state a claim to relief that is plausible on its face.'" Ashcroft v. Iqbal, 556 U.S. 662, 678 (2009) (quoting Bell Atl. Corp. v. Twombly, 550 U.S. 544, 570 (2007)). "A claim has facial plausibility when the plaintiff pleads factual content that allows the court to draw the reasonable inference that the defendant is liable for the misconduct alleged." Iqbal, 556 U.S. at 678 (citing Twombly, 550 U.S. at 556). "[T]o survive a motion under Rule 12(b)(6), a complaint does not need to contain detailed or elaborate factual allegations, but only allegations sufficient to raise an entitlement to relief above the speculative level." Keiler v. Harlequin Enters., Inc., 751 F.3d 64, 70 (2d Cir. 2014) (citation omitted). "Although for the purposes of a motion to dismiss we must take all of the factual allegations in the complaint as true, we `are not bound to accept as true a legal conclusion couched as a factual allegation.'" Iqbal, 556 U.S. at 678 (quoting Twombly, 550 U.S. at 555). Similarly, a complaint does not suffice "if it tenders `naked assertion[s]' devoid of `further factual enhancement.'" Iqbal, 556 U.S. at 678 (quoting Twombly, 550 U.S. at 557) (alteration in Iqbal). "While legal conclusions can provide the framework of a complaint, they must be supported by factual allegations. When there are well-pleaded factual allegations, a court should assume their veracity and then determine whether they plausibly give rise to an entitlement to relief." Iqbal, 556 U.S. at 679.

In relevant part, the TCPA makes it unlawful for anyone

47 U.S.C. § 227(b)(1)(A)(iii). The TCPA provides a private cause of action to persons who receive calls in violation of 47 U.S.C. § 227(b). Id. § 227(b)(3). The Federal Communication Commission ("FCC") was tasked with implementing the requirements of section 227(b). Id. § 227(b)(2).

I. Plaintiffs Fail To Plead Adequately That Experian Is Directly Liable Under Section 227(b)(1)(A)(iii) of the TCPA.

Experian argues that Plaintiffs fail to plead adequately that Experian has any direct liability because Plaintiffs fail to allege that Experian "ever actually sent them a single text message . . ." or "`made' or `physically placed' any text messages," as required under section 227(b)(1)(A)(iii) of the TCPA. Def. Mem. at 2, 9 (Dkt. 123) (emphasis in original). Experian further contends that Plaintiffs' allegations that Experian "caused" the texts to be sent are conclusory and fall short of pleading direct liability under the statute. Id. at 9. In response, Plaintiffs argue that: (1) as provided in the TCPA implementing regulations, 47 C.F.R. § 64.1200(a)(2), "liability flows to either someone who `initiates, or causes to initiate'" the text message, Pls. Opp'n, at 7 (Dkt. 130) (quoting 47 C.F.R. § 64.1200(a)(2)); (2) scheduling a text to be sent is the same as sending a text, id. at 8; and (3) Experian was "so involved in the placing of" the specific text messages at issue as to be directly liable for initiating them, id. at 8. As discussed below, Experian is correct that "none of plaintiffs' factual allegations, even if accepted as true, establishes direct liability on Experian's part under the TCPA because, put simply, none of those actions involves the making, or physical placement, of a text message." Def. Mem. at 9.

In its brief opposing Experian's Motion to Dismiss, Plaintiffs rely on 47 C.F.R. § 64.1200(a)(2), one of the implementing regulations of the TCPA. That reliance is misplaced. Section 64.1200(a)(2) provides:

47 C.F.R. § 64.1200(a)(2). As Defendant notes, the TCPA in section 227(b)(3) contemplates a private right of action based on "a violation of this subsection or the regulations prescribed under this subsection to enjoin such violation . . ." or both. 47 U.S.C. § 227(b)(3). But the TAC claims violations only of TCPA section 227(b)(1)(A)(iii); it does not assert claims under the implementing regulations.7 Moreover, section 64.1200(a)(2) does not purport to define "make" as used in section 227(b)(1)(A)(iii), and Plaintiffs have not cited any authority to support its argument that section 64.1200(a)(2) should guide the Court's interpretation of the word. Thus, contrary to Plaintiffs' argument that the Court should focus on whether the TAC adequately alleges that Experian caused the texts to be "initiated" under section 64.1200(a)(2), the language of section 227(b)(1)(A)(iii) controls whether Experian is directly liable.

The plain language of section 227(b)(1)(A)(iii) imposes liability upon persons that "make" a telephone call or text. 47 U.S.C. § 227(b)(1)(A)(iii). Although the Second Circuit has not weighed in, many of the courts that have considered this provision have held that the verb "make" imposes civil liability only on the party that places the call or text. Jackson v. Caribbean Cruise Line, Inc., 88 F.Supp.3d 129, 135 (E.D.N.Y. 2015) ("By its terms, 47 U.S.C. § 227(b)(1)(A)(iii), assigns civil liability only to the party who `makes' a call."); Kristensen v. Credit Payment Servs., 12 F.Supp.3d 1292, 1301-02 (D. Nev. 2014) (associating the party who "made" the call with "the party who actually sent the text message to [Plaintiff]"); Thomas v. Taco Bell Corp., 879 F.Supp.2d 1079, 1084 (C.D. Cal. 2012), aff'd, 582 F. App'x 678 (9th Cir. 2014) ("The plain language of the TCPA assigns civil liability to the party who `makes' a call" and "[d]irect liability is inapplicable here as the parties do not dispute that the actual sender of the text was . . . a separate provider of text-message based services . . . .").8

In the TAC, Plaintiffs fail to allege adequately that Experian actually sent any texts. Instead, Plaintiffs assert in an entirely conclusory fashion that Experian "caused texts to be sent on behalf of AEO," TAC ¶ 33, and that, as to each of the individually-named Plaintiffs, "AEO and Experian are responsible for sending" the Spam Texts and have sent a large number of Spam Texts to persons in New York, Florida, California and throughout the United States. Id. ¶¶ 50-51, 63-64, 70-71, 82-83. Plaintiffs' class action allegations are similarly conclusory, alleging that there is a class comprised of: "All persons in the United States who: (a) received a text message sent by Experian and/or a third party acting on Experian's behalf." See id. ¶ 86 (defining the purported "Experian Spam Text Subclass" and the "Experian Revocation Subclass").

The factual allegations culminating in those conclusory assertions are an interesting mix of active and passive voice allegations; the TAC uses the active voice to allege who took each step up to the critical allegation regarding who sent the offending text messages:

TAC ¶ 34. Similarly, in Plaintiffs' flow chart, Plaintiffs use the active voice for virtually every step seemingly related to Experian up to the final and critical step of sending the offending texts: "Experian routes campaign ready file to Archer," "Archer processes campaign ready file," "Automated process creates audience segments on Archer platform," "Experian team manually schedules messages for each segment," and "SMS messages deployed (internal tests + live broadcasts)." Id. ¶ 33. The absence of an allegation of who actually "made" or physically placed the text messages is not lost on the Court. Plaintiffs' conclusory assertions that Experian sent or caused the text message to be sent is simply a legal conclusion devoid of further factual enhancement. Because Plaintiffs do not plead that Experian "made," i.e., physically placed or actually sent, the text messages, the TAC fails to state a claim that is plausible on its face under section 227(b)(1)(A)(iii) of the TCPA.9

Finally, Plaintiffs argue that they have adequately stated a claim against Experian because "a defendant may be so involved in the placing of a specific telephone call as to be directly liable for initiating it—by giving the third party specific and comprehensive instructions as to timing and the manner of the call, for example." Pls. Opp'n at 8. For this argument, the Plaintiffs appear to rely on dicta from an FCC Ruling, In the Matter of the Joint Petition filed by Dish Network LLC, the United States of America, and the States of California, Illinois, North Carolina, and Ohio for Declaratory Ruling Concerning the Telephone Consumer Protection Act (TCPA) Rules, that discusses whether vicarious liability could be imposed under section 227(b) of the TCPA. 28 FCC Rcd. 6574, 6583 (2013) ("And one can imagine a circumstance in which a seller is so involved in the placing of a specific telephone call as to be directly liable for initiating it — by giving the third party specific and comprehensive instructions as to timing and the manner of the call, for example."). This dicta, however, is directed at the FCC's interpretation of the word "initiate" as used in a different provision of the TCPA, section 227(b)(1)(B) and implementing regulation section 64.1200(c)(2), in the context of the liability of "sellers," and is, therefore, not directly applicable to the instant case. As discussed previously, the specific provision at issue in this case is section 227(b)(1)(A)(iii), which does not use the verb "initiate" but instead uses the verb "make." Moreover, as Dish Network discusses, "seller" is defined in the implementing regulations section 64.1200(f)(9), 28 FCC Rcd. at 6583 n.80, as "the person or entity on whose behalf a telephone call or message is initiated for the purpose of encouraging the purchase . . . of . . . goods[] or services, which is transmitted to any person." 47 C.F.R. § 64.1200(f)(9). The relied-upon dicta is thus also inapplicable because the allegations in the TAC arguably qualify AEO, not Experian, as a "seller" under this definition, inasmuch as the alleged text messages advertised and encouraged the purchase of AEO-related products.10

In short, Plaintiffs fail to plead adequately that Experian is directly liable for violations of section 227(b)(1)(A)(iii) of the TCPA.

II. Plaintiffs Fail To Plead Adequately That Experian Is Vicariously Liable Under the TCPA

Defendant Experian also argues that Plaintiffs "have failed to plead facts sufficient to establish vicarious liability on Experian's part." Def. Mem. at 10; see also Def. Reply at 6. Plaintiffs argue that they properly alleged Archer is a sub-agent hired by Experian, Archer's role was minor, and Experian controlled every facet of the texting campaign. Pls. Opp'n at 13. Even assuming that there is vicarious liability for a violation of section 227(b) of the TCPA, Plaintiffs fail to plead facts establishing that Archer was Experian's agent.11

"Agency is the fiduciary relationship that arises when one person (a `principal') manifests assent to another person (an `agent') that the agent shall act on the principal's behalf and subject to the principal's control, and the agent manifests assent or otherwise consents so to act." Restatement (Third) of Agency, § 1.01 (2006); see also Cleveland v. Caplaw Enters., 448 F.3d 518, 522 (2d Cir. 2006) ("Agency is a legal concept that depends on the existence of three elements: (1) `the manifestation by the principal that the agent shall act for him'; (2) `the agent's acceptance of the undertaking'; and (3) `the understanding of the parties that the principal is to be in control of the undertaking.'" (quoting Cabrera v. Jakabovitz, 24 F.3d 372, 386 n.13 (2d Cir. 1994) (emphasis in original))). The Second Circuit in Cleveland noted that:

Experian is correct that Plaintiffs fail to allege adequately any agency relationship between Experian and an individual or entity, Archer or otherwise, upon which to base vicarious liability. Again, noting Plaintiffs' use of passive voice in their TAC, it is difficult to discern the exact individual or entity that Plaintiffs allege actually sent the text messages. With respect to Archer, the Plaintiffs' flow chart merely alleges that "Experian routes [the] campaign ready file to Archer," that "Archer processes [the] campaign ready file," and that an "Automated process creates audience segments on Archer platform." Id. ¶ 33. Plaintiffs further allege that "Experian sends the information to [Archer's] texting platform." Id. ¶ 34. Moreover, Plaintiffs assert that Experian:

Id. ¶ 42. Finally, Plaintiffs allege that to the extent Archer is deemed to have sent the texts, Experian is vicariously liable for the actions of Archer because "Archer is Experian's agent in that Experian used Archer's texting platform to send the texts." Id. ¶ 43.

Significantly absent from Plaintiffs' allegations, however, is any factual content regarding the relationship between Experian and Archer. Plaintiffs seem to suggest that the allegations that Experian "had the right to control the sending of the texts" and "in fact controlled and even scheduled the sending of each segment of the texts" are sufficient to plead Experian's vicarious liability for Archer's actions. Pls. Opp'n at 12. Indeed, Plaintiffs argue, without support, that "[w]hether Experian Marketing sent the texts via Archer's messaging platform or whether Archer sent the texts after Experian Marketing directed it to do so is irrelevant to the issue of vicarious liability." Id. But to plead vicarious liability under the TCPA in accordance with traditional tort principles, Plaintiffs must allege some facts regarding the relationship between an alleged principal and agent (or an alleged agent and sub-agent) and cannot simply allege general control in a vacuum. Cf. Gomez v. Campbell-Ewald Co., 768 F.3d 871, 878 n.6 (9th Cir. 2014), cert. granted, Campbell-Ewald Co. v. Gomez, 135 S.Ct. 2311 (2015) ("We need not determine whether [the defendant] constitutes a seller under this definition, as we conclude that vicarious liability turns on the satisfaction of relevant standards of agency, irrespective of a defendant's nominal designation" and "such a construction would contradict `ordinary' rules of vicarious liability, . . . which require courts to consider the interaction between the parties rather than their respective identities." (citation omitted)). Mere conclusory allegations that Archer was Experian's agent or that Experian had the right to control the sending of the texts, without more, fails to plead an agency relationship (between Experian and Archer or any other entity) sufficient to allege vicarious liability under section 227(b)(1)(A)(iii) of the TCPA. Jackson, 88 F. Supp. 3d at 138-39 ("[E]ven viewing the allegations in a light most favorable to the [p]laintiff . . ., the [c]ourt concludes that the [p]laintiff's non-conclusory allegations with regard the agency relationship between [defendant] and [a separate company that allegedly sent the text message on behalf of defendant] fail to `nudge' his claims against [defendant] `across the line from conceivable to plausible . . . .' Bell Atl. Corp. v. Twombly, 550 U.S. 544, 555 (2007). In this regard, absent from the second amended complaint is any allegations that [defendant] had the power to give `interim instructions' to [the separate company], or any non-conclusory suggestion of `direction' or `control' by [defendant] of [that company].").13

CONCLUSION

For the foregoing reasons, Experian's Motion to Dismiss (Dkt. 123) is GRANTED. Because Plaintiffs' claims against Experian are dismissed, Experian's Motion to Strike the Class Allegations in the Third Amended Consolidated Complaint (Dkt. 124) is hereby dismissed as moot. The Clerk of the Court is respectfully directed to terminate docket entries 123 and 124 under the lead case, 14-CV-02440.

SO ORDERED.