Smith v. Microsoft Corp.

297 F.R.D. 464, 2014 WL 323683, 2014 U.S. Dist. LEXIS 12799
CourtDistrict Court, S.D. California
DecidedJanuary 28, 2014
DocketNo. 11-CV-1958 JLS (BGS)
StatusPublished
Cited by8 cases

This text of 297 F.R.D. 464 (Smith v. Microsoft Corp.) is published on Counsel Stack Legal Research, covering District Court, S.D. California primary law. Counsel Stack provides free access to over 12 million legal documents including statutes, case law, regulations, and constitutions.

Bluebook
Smith v. Microsoft Corp., 297 F.R.D. 464, 2014 WL 323683, 2014 U.S. Dist. LEXIS 12799 (S.D. Cal. 2014).

Opinion

ORDER DENYING PLAINTIFF’S MOTION FOR CLASS CERTIFICATION

JANIS L. SAMMARTINO, District Judge.

Presently before the Court is Plaintiff Neil Smith’s (“Plaintiff” or “Smith”) Motion for Class Certification. (ECF No. 38.) Also before the Court are Defendant Microsoft Corp.’s (“Defendant” or “Microsoft”) Response in Opposition (ECF No. 48 (sealed)), Defendant’s Supplemental Document to its Response in Opposition (ECF No. 55), Plaintiffs Reply in Support (ECF Nos. 63-65 (sealed)), Plaintiffs Evidentiary Objections to the Evidence Submitted in Support of Defendant’s Opposition (ECF No. 66 (sealed)), Defendant’s Response in Opposition to Plaintiffs Evidentiary Objections (ECF No. 69), and Plaintiffs Reply in Further Support of his Evidentiary Objections (ECF No. 77). Also before the Court are Microsoft’s Notice of Supplemental Authority (ECF No. 76) and Plaintiffs Response to Microsoft’s Notice (ECF No. 79.) Oral argument was heard on this matter on December 19, 2013. Having considered the parties’ arguments and the law, the Court DENIES Plaintiffs Motion.

BACKGROUND

Smith, a resident of Illinois, brings this putative class action against Microsoft, a Washington corporation, for sending unauthorized text messages promoting Microsoft’s Xbox to cellular telephones in violation of the Telephone Consumer Protection Act of 1991 (“TCPA” or “Act”), 47 U.S.C. § 227.1 (See generally Compl., ECF No. 1.)

In September 2008, Microsoft’s advertising agencies used text-message advertising company Come & Stay, Inc. (“C & S”) to send two versions of a text message advertising Microsoft’s new Xbox website (“the Xbox Texts”). (Mot. for Class Cert. 13, ECF No. 34-1.) On September 12, 2008, SMS aggregator m-Qube sent 92,927 of these messages to 91,708 unique phone numbers (“the mQube List”). (Id.) Smith received one such message. (Compl. ¶ 16, ECF No. 1.) The [467]*467“from” field of the message identified SMS short code “88202.” (Id. ¶ 17.) The body of the text message read:

FREE XBOX GAMES CONTENT!
HTTP://XBOX.MOBI/SMl.
PERSONALIZE YOUR PHONE WITH RINGTONES,
WALLPAPER TRAILERS AND GAME UPDATES.
TO OPT-OUT REPLY END.

Smith claims to have neither requested nor consented to receive the message. (Mot. for Class Cert. 14, ECF No. 34-1.)

Smith brings this claim on behalf of himself and a class of others similarly situated, defining the class as “[a]ll individuals that [sic] received a text message from short code 88202 containing the term ‘Xbox’ on September 12 or September 13, 2008.” (Id. at 15.) Allegedly, some members of the class suffered actual damages by having to pay their respective wireless carriers a fee for receipt of the text message. (Compl. ¶31, ECF No. 1.) Although omitting information about his own wireless plan, Smith states that “consumers frequently have to pay their cell phone service providers for the receipt of such wireless spam.” (Id. ¶ 3.) Further, Microsoft has caused all members of the class to suffer actual “harm and damages” by subjecting them to “the aggravation that necessarily accompanies wireless spam.” (Id.) Consequently, Smith seeks an injunction requiring Microsoft to cease “all wireless spam activities” and an award of actual and statutory damages to the class members, together with costs and attorneys’ fees. (Id. at 7.) Smith requests a minimum of $500.00 for each violation of the Act, and up to treble damages. (Id. ¶ 32.)

On October 20, 2011, Microsoft moved to dismiss for lack of subject matter jurisdiction. (ECF No. 6.) The Court vacated the hearing on the motion scheduled for January 5, 2012. (ECF No. 12.) In a July 20, 2012 Order, the Court denied the motion, finding that Smith had standing to bring this action. (ECF No. 15.) On August 3, 2012, Microsoft answered the Complaint. (ECF No. 16.)

On December 14, 2012, Magistrate Judge Skomal granted the parties’ joint motion for entry of a stipulated protective order. (ECF No. 23.) On April 24, 2013, Smith filed the instant Motion for Class Certification.

LEGAL STANDARD

Class certification is governed by Federal Rule of Civil Procedure 23. Under Rule 23, the party seeking certification bears the burden of showing that each of the four requirements of Rule 23(a) and at least one of the three requirements of Rule 23(b) have been met. In addition to the Rule 23 requirements, the party seeking class certification must provide a workable class definition by showing that the members of the class are identifiable.

Rule 23(a) provides four requirements that must be met in any class action: (1) the class is so numerous that joinder of all members is impracticable; (2) there are questions of law or fact common to the class; (3) the claims or defenses of the representative parties are typical of the claims or defenses of the class; and (4) the representative parties will fairly and adequately protect the interests of the class.

As to Rule 23(b), a plaintiff need only show that any one of the three described scenarios is satisfied. Smith seeks certification of the proposed class pursuant to Rule 23(b)(3), and thus he must demonstrate that (1) “questions of law or fact common to class members predominate over any questions affecting only individual members,” and (2) “a class action is superior to other available methods for fairly and efficiently adjudicating the controversy.”

“Rule 23 does not set forth a mere pleading standard.” Wal-Mart Stores, Inc. v. Dukes, — U.S.-, 131 S.Ct. 2541, 2551, 180 L.Ed.2d 374 (2011). Rather, “[a] party seeking class certification must affirmatively demonstrate his compliance with the Rule— that is, he must be prepared to prove that there are in fact sufficiently numerous parties, common questions of law or fact, etc.” Id. The Court must engage in a “rigorous analysis,” often requiring some evaluation of the “merits of the plaintiffs underlying claim,” before finding that the prerequisites for certification have been satisfied. Id. “Although some inquiry into the substance of a [468]*468case may be neeessary[,]” however, “it is improper to advance a decision on the merits to the class certification stage.” Staton v. Boeing Co., 327 F.3d 938, 954 (9th Cir.2003) (citations and internal quotation marks omitted).

ANALYSIS

Microsoft opposes class certification on multiple grounds, arguing that Plaintiffs have failed to (1) set forth an objectively identifiable and ascertainable class; (2) satisfy Rule 23(a)’s commonality, typicality, and adequacy requirements; (3) satisfy Rule 23(b)(3)’s predominance and superiority requirements, or (4) establish standing to bring this action. As the Court finds that Rule 23(b)(3)’s superiority requirement is dispositive of Plaintiffs’ class certification motion, the Court does not address all of the parties’ arguments, but rather focuses its analysis on this key issue.

I. Rule 23(b)(3)’s Superiority Requirement

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

Related

Stokes v. Sensa Products
S.D. California, 2019
Reyes v. Educational Credit Management Corp.
322 F.R.D. 552 (S.D. California, 2017)
Ung v. Universal Acceptance Corp.
319 F.R.D. 537 (D. Minnesota, 2017)
Bee, Denning, Inc. v. Capital Alliance Group
310 F.R.D. 614 (S.D. California, 2015)
Ott v. Mortgage Investors Corp. of Ohio, Inc.
65 F. Supp. 3d 1046 (D. Oregon, 2014)
Balschmiter v. TD Auto Finance LLC
303 F.R.D. 508 (E.D. Wisconsin, 2014)

Cite This Page — Counsel Stack

Bluebook (online)
297 F.R.D. 464, 2014 WL 323683, 2014 U.S. Dist. LEXIS 12799, Counsel Stack Legal Research, https://law.counselstack.com/opinion/smith-v-microsoft-corp-casd-2014.