dissenting:
The Supreme Court recently explained in Henderson ex rel. Henderson v. Shinseki that “Congress is free to attach the conditions that go with the jurisdictional label to a[n exhaustion] rule that we would prefer to call a claim-processing rule.” — U.S. —, 131 S.Ct. 1197, 1203, 179 L.Ed.2d 159 (2011) (emphasis added). Because Congress incorporated the exhaustion requirement of the Magnuson-Moss Warranty Act, 15 U.S.C. § 2301 et seq. (“MMWA”) into the statute’s jurisdiction-granting provisions, we must defer to Congress’s treatment of this provision as jurisdictional. See Henderson, 181 S.Ct. at 1203. Therefore, I must dissent from the majority’s conclusion that the MMWA’s exhaustion provision is merely procedural.
*1044Additionally, the majority errs in declining to address a critical question of law properly raised on appeal — whether courts (rather than the Federal Trade Commission) should decide challenges to a “Mechanism’s”1 compliance with federal regulations. Under the MMWA, courts no longer have authority to decide compliance issues, because Congress vested authority to decide those issues in the first instance with the FTC. On the other hand, even if the judiciary retained authority to address these issues, courts should defer to the FTC’s unique expertise in Mechanism compliance under the primary jurisdiction doctrine.
I. Mechanism exhaustion under the MMWA is a jurisdictional prerequisite to filing suit
Judicial interpretation of the MMWA “begins with the plain language of the statute. If the text of the statute is clear, this court looks no further in determining the statute’s meaning.” K & N Eng’g, Inc. v. Bulat, 510 F.3d 1079, 1081 (9th Cir.2007) (citation omitted). The key question in this case is “whether Congress mandated that the [exhaustion provision] be ‘jurisdictional.’ ” Henderson, 131 S.Ct. at 1203. (emphasis added). The Henderson Court reiterated the “readily administrable bright line” test from Arbaugh v. Y & H Corp. for deciding such questions: “we look to see if there is any ‘clear’ indication that Congress wanted the rule to be ‘jurisdictional.’ ” 131 S.Ct. at 1203 (quoting Arbaugh v. Y & H Corp., 546 U.S. 500, 515-16, 126 S.Ct. 1235, 163 L.Ed.2d 1097 (2006)). To indicate such a preference, Congress can “[1] speak in jurisdictional terms or [2] refer in any way to the jurisdiction of the [district court].” Id. at 1204 (quoting Zipes v. Trans World Airlines, Inc., 455 U.S. 385, 394, 102 S.Ct. 1127, 71 L.Ed.2d 234 (1982)); accord Arbaugh, 546 U.S. at 516, 126 S.Ct. 1235. “Congress, of course, need not use magic words in order to speak clearly on this point.” Henderson, 131 S.Ct. at 1203. The analysis might also turn on “the ‘legal character’ of the requirement, which we discern[ ] by looking to the condition’s text, context, and relevant historical treatment.” Reed Elsevier, Inc. v. Muchnick, — U.S. —, 130 S.Ct. 1237, 1246, 176 L.Ed.2d 18 (2010) (citations omitted); see Kontrick v. Ryan, 540 U.S. 443, 455, 124 S.Ct. 906, 157 L.Ed.2d 867 (2004) (“[L]itigants [should use] the label ‘jurisdictional’ not for claim-processing rules, but only for prescriptions delineating the classes of cases (subject-matter jurisdiction) and the persons (personal jurisdiction) falling within a court’s adjudicatory authority.” (emphasis added)).
Section 2310(d)(1) of the MMWA ties Mechanism exhaustion to the jurisdiction of the courts by expressly incorporating § 2310(a)(3):
(d) Civil action by consumer for damages, etc.; jurisdiction; recovery of costs and expenses; cognizable claims
(1) Subject to [the exhaustion requirement in] sub-section [](a) (3) ... of this section, a consumer who is damaged by the failure of a supplier, warrantor, or service contractor to comply with any obligation under this chapter, or under a written warranty, implied warranty, or service contract, may bring suit for damages and other legal and equitable relief—
(A) in any court of competent jurisdiction in any State or the District of Columbia; or
*1045(B) in an appropriate district court of the United States, subject to paragraph (3) of this subsection.
15 U.S.C. § 2310(d)(1) (emphasis added). There is no doubt that § 2310(d)(1) is a jurisdiction-granting provision, because: (1) the subsection heading includes the label “jurisdiction,” § 2310(d); (2) it speaks in jurisdictional terms by specifying which courts may hear MMWA claims, Arbaugh, 546 U.S. at 515, 126 S.Ct. 1235; and (3) it identifies the classes of cases that fall within courts’ adjudicatory authority under the MMWA, see Kontrick, 540 U.S. at 455, 124 S.Ct. 906. Therefore, because Congress incorporated § 2310(a)(3)’s exhaustion requirement into the jurisdictional provisions of § 2310(d)(1), the exhaustion provision must be treated as jurisdictional.2
The majority correctly notes that the MMWA’s exhaustion provision — providing that a “consumer may not commence a civil action ... unless he initially resorts to [an informal dispute settlement procedure],” § 2310(a)(3) — is not, standing alone, “jurisdictional in character.” Maj. Op. at 1041-42. However, the majority ignores the fact that Toyota never made this argument, and the district court, therefore, did not address it. Instead, Toyota argued that Congress imbued § 2810(a) with jurisdictional character by incorporating the exhaustion provision into a clearly jurisdiction-granting sub-section of the statute. The majority dismisses this argument as requiring “[n]o serious analysis,” because the incorporation is not sufficiently “sweeping and direct” to convey an intent to tie exhaustion to jurisdiction. Maj. Op. at 1042. One can reach this conclusion only by ignoring the Supreme Court’s most recently elucidated indicia of Congressional intent: (1) “speak[ing] in jurisdictional terms,” or (2) “refer[ring] in any way to the jurisdiction of the courts.” Henderson, 131 S.Ct. at 1204 (quoting Zipes, 455 U.S. at 394, 102 S.Ct. 1127). Nowhere in its opinion does the majority employ this “readily administrable bright line” rule.3 Id. at 1203 (quoting Arbaugh, 546 U.S. at 515-16, 126 S.Ct. 1235). When this standard is applied, it becomes clear that incorporating the exhaustion requirement into a subsection that both “speaks in jurisdictional terms” and “refer[s] in [some] way to the jurisdiction of the [courts],” id., conveys an intent to tie exhaustion to jurisdiction.
In sum, Congress is “free to attach the conditions that go with the jurisdictional label” at its discretion, even in cases where *1046“we would prefer to call [the provision] a claim-processing rule.” Id. This attachment need not be consistent with other statutes. Our inquiry simply turns on whether Congress has tied jurisdiction to the exhaustion requirement; in this case, it clearly has. I would therefore affirm on this issue and hold that the district court lacks jurisdiction to consider Maronyan’s claims until she exhausts Toyota’s Mechanism.
II. The Federal Trade Commission must decide challenges to a Mechanism’s regulatory compliance
Regardless whether Toyota’s dispute settlement program is a jurisdictional or procedural prerequisite to filing suit, Maronyan contends she was not required to exhaust the program. She argued to the district court that (1) Toyota’s program does not qualify as a Mechanism pursuant to certain MMWA and FTC regulations; and (2) courts, rather than the FTC, should determine a Mechanism’s regulatory compliance before making exhaustion a prerequisite to filing suit. Toyota argued to the district court that state and federal agencies have authority to assess Mechanism compliance, agency decisions should be conclusive, and litigating Mechanism compliance in every instance will produce inconsistent results. The district court granted Toyota summary judgment on the assumption that (1) courts have authority to review a Mechanism’s compliance with federal regulations and (2) Toyota’s program was, in fact, sufficiently compliant to require exhaustion. Although the issues of a court’s authority to decide Mechanism compliance and the propriety of making such decisions were properly raised on appeal, the majority’s opinion curiously declined to address them. Because I believe these questions of law should have been answered by our court, I address each in turn below.
A. Courts no longer have authority under the MMWA to review Mechanism compliance
The text and structure of the MMWA reveal that the FTC should determine a Mechanism’s compliance with federal law in the first instance. The statute assigns several clear responsibilities to the FTC: (1) establish the minimum requirements for Mechanisms, id. § 2310(a)(2); (2) on its own initiative, it may review Mechanism operations for compliance, id. § 2310(a)(4); (3) upon written complaint, it must review Mechanism operations for compliance, id.; and (4) it may take appropriate remedial action against non-compliant programs, id.4 The role of the courts (apparent from the text of the statute) is simply to invali*1047date any procedure that is “unfair” until the FTC adopts its own certification regulations. § 2310(a)(5). Maronyan argues that, because Mechanisms operate as “prerequisite[s] to pursuing a legal remedy” under § 2310(a)(3)(B), the MMWA impliedly authorizes courts to determine whether Mechanisms comply with FTC regulations when consumers bring claims under the statute. She supports this argument with an excerpt from a 1974 Senate Conference Report stating:
This is not intended to exclude the courts from reviewing the fairness, and compliance with FTC rules, of such procedures even where the FTC has not acted to disapprove them. In this connection the conferees recognize the limited resources of the Commission and the fact that its other responsibilities may preclude it from acting in some cases where private dispute settlement procedures may not comply with the legislation or the Commission’s rules thereunder. Accordingly, the courts would be free to determine that a given dispute settlement procedure need not be exhausted because it was not fair, had no provision for governmental or consumer participation, or did not comply with FTC rules.
S.Rep. No. 93-1408, at 5 (1974) (Conf. Rep.), reprinted in 1974 U.S.C.C.A.N. 7755, 7759.
This legislative history is not persuasive. As the Supreme Court observed in Puerto Rico Department of Consumer Affairs v. Isla Petroleum Corp., courts “never [search for] congressional intent in a vacuum, unrelated to the giving of meaning to an enacted statutory text---- [U]nenacted approvals, beliefs, and desires are not laws.” 485 U.S. 495, 501, 108 S.Ct. 1350, 99 L.Ed.2d 582 (1988). A legislative report may simply be “precatory” where the actual text of the statute does not support the language of the report. Sec’y of the Interior v. California, 464 U.S. 312, 322 n. 9, 104 S.Ct. 656, 78 L.Ed.2d 496 (1984). Thus, legislative history is only persuasive to the extent it finds textual support in the statute. Shannon v. United States, 512 U.S. 573, 583, 114 S.Ct. 2419, 129 L.Ed.2d 459 (1994) (the Court will not give “authoritative weight to a single passage of legislative history that is in no way anchored in the text of the statute”); Isla Petroleum, 485 U.S. at 501, 108 S.Ct. 1350.
Here, the statute identifies one instance in which courts should play a role in the Mechanism qualification process: “invalidating] any such procedure if it finds that such procedure is unfair,” but only “until [FTC rules] take effect.” § 2310(a)(5) (emphasis added). Because the FTC adopted rules in 1975, see Promulgation of Rule, 40 Fed.Reg. 60190-01 (Dec. 31, 1975), courts no longer have statutory authority to decide a procedure’s fairness or compliance with FTC rules. If Congress intended courts to continue playing this role, it should have (1) omitted the limiting qualification “until [FTC rules] take effect,” or (2) included similar authorizing language elsewhere in the statute, such as § 2310(a)(3) or (4). Thus, the intent of the Senate report authors (that courts continue playing a role in the review of Mechanism compliance) did not bear out in the statutory language ultimately approved by Congress.
Instead, Congress vested the FTC with authority to promulgate rules, monitor Mechanism compliance, and take remedial action against non-compliant programs. Id. § 2310(a)(2), (4). Significantly, Congress also established the process by which consumers should challenge the compliance of a Mechanism: “The Commission ... upon written complaint filed by any interested person shall[] review the bona fide operation of any [Mechanism]” for compliance with FTC rules. Id. § 2310(a)(4). As this provision suggests, *1048the proper way to challenge a Mechanism’s compliance with federal regulations is to lodge a written complaint with the FTC. See Wolf v. Ford Motor Co., 829 F.2d 1277, 1279 (4th Cir.1987) (“[T]he [MMWAJ’s ... mandate that the [FTC] prescribe minimum requirements for such mechanisms, evince a congressional intent to reserve to the federal regulatory body the authority to supervise whether the mechanisms are created and operated fairly.”); id. at 1279 n. 3 (“[A]ny attack on the fairness or legitimacy of a dispute settlement mechanism must be through administrative channels.”); see also Harrison v. Nissan Motor Corp., 111 F.3d 343, 346 n. 3 (3d Cir.1997) (stating in dicta that whether the “BBB Auto Line [Mechanism] is in compliance with the FTC regulations.... is for the FTC, and not this Court, to decide”).
Maronyan also claims the FTC renounced this role in an Action statement, suggesting Mechanism compliance is an “issue for litigation.” See Interpretations of Magnuson-Moss Warranty Act, 64 Fed. Reg. 19,700, 19,708 (Fed. Trade Comm’n Apr. 22,1999). This is inaccurate. In that Action, the FTC declined auto manufacturers’ request to establish a national “prior approval” certification program that would determine Mechanism compliance with Rule 703 before mechanisms became effective and preempt certain state certification standards. Id. at 19,707-08. The manufacturers suggested a federal certification program would (1) eliminate the uncertainty of conflicting state certification standards; (2) diminish the risk of litigation over a mechanism’s compliance with federal rules; and (3) encourage more warrantors to establish Mechanisms by diminishing the cost of compliance with unified standards for mechanism certification. Id. at 19,708. The Commission “reeognizefd] that a uniform certification program could possibly diminish uncertainty,” but declined the recommendation because, among other things, “FTC certification would not eliminate a [Mechanism]’s alleged non-compliance with Rule 703 as an issue for litigation.” Id. Thus, the FTC did not disavow compliance over-sight as an “issue for litigation.” It merely disputed one of the purported benefits of a national certification program by explaining that federal certification might create more litigation from auto manufacturers challenging the FTC’s denial of certification and consumers challenging the FTC’s approval of certification. Id. at 19,708 n. 65.
If there is any doubt, the FTC acknowledges its continuing role in the compliance verification process under Rule 703. Id. at 19,707; see 16 C.F.R. §§ 703.6, 703.7. The FTC’s existing regulations require Mechanisms to (1) maintain detailed records on each dispute referred to it, organize the records in categorical indices, generate semi-annual aggregated statistics based on the result of arbitration, and maintain such records for four years, id. § 703.6; (2) make these records available to independent auditors for evaluation based on criteria determined by the FTC, id. § 703.7(a), (b), (d); and (3) submit audits to the FTC on an annual basis, id. § 703.7(c). Thus, under both the statute and relevant FTC regulations, the FTC exclusively oversees warrantors’ Mechanism compliance.
B. Courts should defer to the FTC on issues of Mechanism compliance
Even if courts had authority under the MMWA to address Mechanism compliance with federal regulations, courts should defer to the FTC under the primary jurisdiction doctrine. The primary jurisdiction doctrine prescribes deference to an administrative agency where (1) the issue is not “within the conventional experiences of judges,” (2) the issue “involves technical or policy considerations within the agency’s *1049particular field of expertise,” (3) the issue “is particularly within the agency’s discretion,” or (4) “there exists a substantial danger of inconsistent rulings.” Brown v. MCI WorldCom Network Servs., Inc., 277 F.3d 1166, 1172-73 (9th Cir.2002) (citations omitted); accord Nat’l Commc’ns Ass’n, Inc. v. AT & T Co., 46 F.3d 220, 222-23 (2d Cir.1995). The issue of Mechanism compliance falls within each of these categories.
First, Mechanism compliance involves “technical [and] policy considerations within the [FTC]’s field of expertise,” which considerations fall outside the conventional experience of judges. The FTC has exclusive authority to promulgate minimum standards for Mechanisms, see § 2310(a)(2), and it alone monitors IDSM compliance nationally, see id. § 2310(a)(4). Thus, the FTC is in a unique position to determine the national implications of compliance orders determining, among other things, how strict compliance must be with certain provisions and whether the substantial compliance doctrine applies to the overall operation of the Mechanism. For example, the FTC declined to establish a national “prior approval” certification program in part because it might “exert a chilling effect on competition and on experimentation by Mechanisms, warrantors, and state governments in setting up and administering these programs.” 64 Fed. Reg. at 19,708. This was a policy judgment informed by the FTC’s expertise as the national overseer of Mechanism operations. The FTC processes data from annual audits submitted by every Mechanism in the country to evaluate Mechanisms’ overall performance in a broad range of categories. See 16 C.F.R. § 703.7. Because a court (utilizing the narrow facts in a single case) cannot evaluate the many policy considerations hanging in the balance of a compliance order, the FTC is better suited to decide compliance issues under the national Mechanism regulatory regime.
Second, Mechanism compliance is “particularly within the agency’s discretion.” Congress gave the FTC substantial leeway in reviewing Mechanism compliance and taking “appropriate remedial action” against non-compliant Mechanisms. See § 2310(a)(4). The FTC is in the best position to determine whether strict compliance with some provisions in Rule 703 (e.g., the four-year record keeping requirement, 16 C.F.R. § 703.6(f)) may be less important than strict compliance with other provisions (e.g., the requirement that manufacturers act in good faith in deciding whether to accept the outcome proposed by a Mechanism arbitrator, id. § 703.5(j)). Similarly, the FTC can better assess when the volume of a Mechanism’s irregularities rise to the level of non-compliance such that consumers need not exhaust the Mechanism before filing suit. The FTC has also expressed its desire to encourage “competition” and “experimentation” by warrantors in setting up and administering Mechanisms, and “would be loathe to take regulatory action likely to exert a chilling effect” on this process. 64 Fed.Reg. at 19,708. Strict enforcement by a court of any particular regulation could have the same chilling effect on warrantors’ Mechanism experimentation or even warrantors’ willingness to create Mechanisms. Thus, Mechanism compliance falls “particularly within the [FTC’s] discretion,” because the FTC is in the best position to balance consumers’ needs with Congress’s desire to encourage fair and expeditious settlement of consumer disputes. See § 2310(a)(1).
Finally, “there [is] a substantial danger of inconsistent rulings” that could compromise Congressional objectives underlying the MMWA. If warrantors must prove a Mechanism’s compliance to trial courts *1050anytime a consumer brings a claim under the MMWA, inconsistent rulings are virtually inevitable. Courts would create a national patchwork of Mechanism compliance decisions that companies would have to monitor and adapt to to ensure their own Mechanisms are deemed compliant when they assert § 2310(a)(3) exhaustion as a jurisdictional bar. This would raise the cost of compliance for warrantors and likely discourage companies from using Mechanisms to resolve consumer complaints. The FTC, by contrast, operates as the national clearinghouse for compliance standards. If all compliance decisions are rendered by the same agency, the standards will be more consistent and easy to identify. Congress explicitly declared its “policy to encourage warrantors to establish procedures whereby consumer disputes are fairly and expeditiously settled through informal dispute settlement Mechanisms.” § 2310(a)(1). Because creating an inconsistent regulatory patchwork through the courts could compromise this policy, the FTC should remain the primary judge of a Mechanism’s compliance with federal regulations.
In sum, given the statutory framework establishing the FTC as the principal authority on Mechanism compliance, the FTC is best suited to address challenges to Mechanism compliance in the first instance. Therefore, the FTC’s compliance decisions deserve judicial deference under the primary jurisdiction doctrine. Maronyan’s challenge to Toyota’s Mechanism compliance status should have been directed to the FTC rather than the courts. See § 2310(a)(3). Because Maronyan has not demonstrated that the FTC regards Toyota’s CDSP Mechanism as non-compliant with Rule 703 or applicable provisions of the MMWA, she must exhaust her warranty claims through Toyota’s Mechanism before filing suit. Her failure to do so deprives the federal courts of jurisdiction over her claims arising under the MMWA.
. The FTC refers to "informal dispute settlement procedures” authorized by the MMWA as "Informal Dispute Settlement Mechanisms” (IDSMs) or simply "Mechanisms.” See 16 C.F.R. § 703.1(e); 64 Fed.Reg. 19700, 19701 (Apr. 22, 1999).
. The majority points out that the Court warned lower courts not to find jurisdictional limits unless the "Legislature clearly states that a threshold limitation on a statute’s scope shall count as jurisdictional....” Reed Elsevier, 130 S.Ct. at 1244 (quoting Arbaugh, 546 U.S. at 515-16, 126 S.Ct. 1235). However, Reed Elsevier concluded that the numerosity provision at issue in Arbaugh, after examining the text of the provision, is not jurisdictional because "the employee numerosity provision is located in a provision 'separate' from” the jurisdiction section. Id. "Accordingly, the numerosity requirement could not fairly be read to ‘speak in jurisdictional terms or in any way refer to the jurisdiction of the district courts.’ ” Id. (quoting Arbaugh, 546 U.S. at 515, 126 S.Ct. 1235.). Here, unlike Arbaugh, the Mechanism exhaustion provision is incorporated into the jurisdictional provisions of the statute.
. The majority simply applies the "sweeping and direct language” standard from Weinberger v. Salfi, 422 U.S. 749, 95 S.Ct. 2457, 45 L.Ed.2d 522 (1975). This is not the standard employed by the Supreme Court in Henderson, Arbaugh, or Zipes. To the extent "sweeping and direct language” is still the applicable standard, it has been refined to encompass (1) "speak[ing] in jurisdictional terms,” (2) "refer[ing] in any way to the jurisdiction of the [courts],” or (3) conveying jurisdictional intent in the "context” of the statute. Henderson, 131 S.Ct. at 1204; Arbaugh, 546 U.S. at 516, 126 S.Ct. 1235; Zipes, 455 U.S. at 394, 102 S.Ct. 1127.
. The statute provides, in relevant part:
(2) The [FTC] shall prescribe rules setting forth minimum requirements for any informal dispute settlement procedure which is incorporated into the terms of a written warranty to which any provision of this chapter applies....
(4) The Commission on its own initiative may, or upon written complaint filed by any interested person shall, review the bona fide operation of any dispute settlement procedure resort to which is stated in a written warranty to be a prerequisite to pursuing a legal remedy under this section. If the Commission finds that such procedure or its implementation fails to comply with the requirements of the rules under paragraph (2), the Commission may take appropriate remedial action under any authority it may have under this chapter or any other provision of law.
(5) Until rules under paragraph (2) take effect, this subsection shall not affect the validity of any informal dispute settlement procedure respecting consumer warranties, but in any action under subsection (d) of this section, the court may invalidate any such procedure if it finds that such procedure is unfair.
§ 2310(a) (emphasis added).