TCPA Preemption: Does Federal Law Override State Calling Laws?

Mostly, no. The TCPA’s savings clause says that “nothing in this section or in the regulations prescribed under this section shall preempt” state laws that impose more restrictive intrastate requirements on, or that prohibit, autodialers, prerecorded messages, unsolicited fax ads, and telephone solicitations. Federal appeals courts have read that clause to leave state laws standing even when the calls cross state lines. A business sued under a state mini-TCPA shouldn’t expect preemption to end the case, but the clause has limits that still matter.

What does the TCPA’s savings clause say?

It protects two kinds of state laws from preemption, and it carves out one federal subject the states can’t touch.

The clause is 47 U.S.C. § 227(f)(1). It provides that “Except for the standards prescribed under subsection (d) and subject to paragraph (2) of this subsection, nothing in this section or in the regulations prescribed under this section shall preempt any State law that imposes more restrictive intrastate requirements or regulations on, or which prohibits” four things, per the statute: fax advertisements, “the use of automatic telephone dialing systems,” “the use of artificial or prerecorded voice messages,” and “the making of telephone solicitations.”

Three pieces of that sentence shape every preemption argument. The words “more restrictive intrastate requirements” save state rules that are tougher than federal law for calls within the state. The words “or which prohibits” save state laws that ban a practice outright, with no “intrastate” limit attached. And the opening exception, for “the standards prescribed under subsection (d),” keeps the federal technical and identification standards for faxes and prerecorded messages out of the states’ reach.

A second paragraph, § 227(f)(2), adds that if the FCC requires a single national do-not-call database, a state “may not, in its regulation of telephone solicitations, require the use of any database, list, or listing system that does not include the part of such single national database that relates to such State.”

Do state laws apply to calls made from another state?

Courts have generally said yes. The leading appellate decisions rejected the argument that “intrastate” limits the whole clause.

In Patriotic Veterans, Inc. v. State of Indiana, 736 F.3d 1041 (7th Cir. 2013), a political group argued that Indiana’s autodialer law was preempted as applied to interstate calls. The Seventh Circuit disagreed. It held that “the plain language of the statute decrees that state laws that prohibit autodialers are not preempted by the statute,” and that “The TCPA does not expressly preempt the Indiana statute.” The court went further, reasoning that even if Indiana’s law were treated as a regulation rather than a prohibition, “the TCPA says nothing about preempting laws that regulate the interstate use of automatic dialing systems. Therefore, we must conclude that they are not preempted.”

The North Dakota Supreme Court reached the same result in State ex rel. Stenehjem v. FreeEats.com, Inc., 2006 ND 84, a case about automated political polling calls placed from Virginia. The court read the clause “to provide that the TCPA does not preempt any state law which prohibits interstate calls using automatic telephone dialing systems or using artificial or prerecorded voice messages.”

And in Van Bergen v. Minnesota, 59 F.3d 1541 (8th Cir. 1995), the Eighth Circuit rejected express, field, and conflict preemption arguments against Minnesota’s automatic dialing law. It concluded that “the TCPA does not expressly preempt state law, nor is it implied in the TCPA that Congress intended to preempt state law, nor does the Minnesota statute conflict with the TCPA.”

Does a stricter state rule “conflict” with the TCPA?

Not by itself. Being stricter isn’t the same as being impossible to follow.

The Seventh Circuit in Patriotic Veterans put it directly: “The fact that a state has more stringent regulations than a federal law does not constitute conflict preemption.” Conflict preemption requires that compliance with both laws be impossible, or that the state law stand as an obstacle to the federal scheme. A state 8 p.m. cutoff, a cap of three calls a day, or a written-consent rule for automated texts doesn’t make the federal rules impossible to follow. A company can satisfy both by meeting the stricter one.

That’s the practical lesson for multistate senders. Courts treat the state rules as an extra layer, not a replacement, and the safe design is to build campaigns to the strictest rule that applies to each recipient’s area code.

Where can a preemption argument still work?

At the edges, and mostly where a state rule reaches a subject Congress kept for itself.

The best opening is the carve-out for subsection (d). Under § 227(d)(3), the FCC sets the technical and procedural standards for prerecorded messages, including that they “state clearly the identity of the business, individual, or other entity initiating the call” at the beginning and give a telephone number or address. Because § 227(f)(1) excepts “the standards prescribed under subsection (d)” from the savings clause, a state rule that imposes different technical or identification standards on prerecorded messages is the strongest candidate for a preemption defense. It’s an argument to examine whenever a state claim rests on the content or mechanics of a recorded message and not on whether the message was allowed at all.

A second opening is the national database rule in § 227(f)(2), which limits states from requiring a do-not-call list that omits their part of the national Registry. That rarely decides a private damages case, but it can matter in a challenge to a state’s list requirements.

Caller ID rules are a separate matter. The federal provision on misleading caller ID, § 227(e), says that “subsection (f) shall not apply to this subsection or to the regulations under this subsection.” The savings clause doesn’t decide whether state caller ID laws survive, so ordinary preemption principles apply there instead.

Outside those areas, the stronger defenses to a state claim are usually in the state statute itself: its definitions, its exemptions, whether it covers texts, and how it counts violations. Preemption is worth pleading where it fits, but it’s rarely the argument that ends the case.

Type of state ruleSavings clause treatmentPreemption defense strength
Ban on autodialed or prerecorded calls without consentSaved as a prohibition, including for interstate calls under Patriotic Veterans and FreeEatsWeak
Stricter calling hours, daily call caps, written-consent rulesSaved as more restrictive intrastate rules; courts have also declined to preempt interstate applicationWeak
State rules on the technical or identification standards for prerecorded messagesOutside the savings clause because of the subsection (d) exceptionStrongest available
State do-not-call list that omits the national RegistryLimited by § 227(f)(2)Possible in a challenge to the list rules
State caller ID spoofing lawsSavings clause doesn’t apply under § 227(e)(9)Depends on general preemption principles

What changed after McLaughlin?

Less than the headlines suggest, for preemption purposes.

In McLaughlin Chiropractic Associates, Inc. v. McKesson Corp. (2025), the Supreme Court held that district courts in TCPA enforcement proceedings must independently determine the meaning of the statute rather than defer to the FCC. That shift matters when a defendant argues that an FCC order displaces a state rule. Courts deciding preemption have always worked from the statutory text of § 227(f), and the appellate decisions above did exactly that. An FCC statement about preemption, standing alone, now carries even less weight than it did before.

When a state calling claim arrives

  1. Preserve the call and text logs, platform data, and consent records for every number in that state, under a litigation hold.
  2. Pull the opt-out and internal do-not-call logs for those numbers, with dates.
  3. Gather the national Registry and any state list downloads used for scrubbing, with version dates.
  4. Collect the recorded message files, scripts, vendor contracts, and caller ID settings, since a claim about message content may raise a subsection (d) issue.
  5. Have a lawyer review the claim before responding to a demand letter, contacting the claimant, or offering money.

A preemption defense should be evaluated early, alongside the state statute’s own definitions and exemptions. Businesses facing these claims can read more about defending TCPA and state calling claims, and the firm’s earlier post on Washington’s CEMA text claims shows how one state statute works in practice.

Questions about TCPA preemption

Does complying with the TCPA protect a company from state claims?

No. Federal compliance is a floor, not a shield. The savings clause in § 227(f)(1) preserves state laws that are stricter or that prohibit certain calls outright, and appellate courts have applied those laws to interstate calls. A campaign that meets every federal rule can still violate a state’s calling hours, daily call limits, or written-consent requirement for automated messages.

Is the word “intrastate” a defense for out-of-state callers?

Usually not. The Seventh Circuit called the reading that “intrastate” limits the whole clause irrational, and the North Dakota Supreme Court held that “intrastate” modifies only the first phrase, not the phrase saving state prohibitions. A caller located outside the state shouldn’t count on that argument to defeat a state claim.

Which state rules are most open to a preemption challenge?

Rules that regulate the technical or identification standards of prerecorded messages, because § 227(f)(1) excepts the federal subsection (d) standards from the savings clause. A state requirement about what a recorded message must say, or how the system must release the line, is the most promising target. Rules about whether a call may be made at all are much harder to attack.

Should a defendant raise preemption anyway?

Where it fits the claim, yes, because it’s waived if it isn’t raised and it can narrow a case even when it doesn’t end it. But it belongs alongside the stronger defenses in the state statute itself, such as its definitions, exemptions, and the count of separate violations, not in place of them.

Facing a state mini-TCPA claim

If your company has been sued or received a demand letter under a state calling or texting law, how that statute fits with the TCPA can shape which defenses are available from the start. Rosenberger + Kawabata represents businesses defending TCPA lawsuits and class actions through its business litigation practice, including claims involving state telemarketing statutes. Contact Rosenberger + Kawabata online for a confidential consultation, or call (310) 894-6921.

Sources

47 U.S.C. § 227; Patriotic Veterans, Inc. v. State of Indiana, 736 F.3d 1041 (7th Cir. 2013); State ex rel. Stenehjem v. FreeEats.com, Inc., 2006 ND 84; Van Bergen v. Minnesota, 59 F.3d 1541 (8th Cir. 1995); McLaughlin Chiropractic Associates, Inc. v. McKesson Corp. (2025).

This post is general information about the Telephone Consumer Protection Act and related laws as of May 3, 2026. It is not legal advice, and reading it does not create an attorney-client relationship. Courts and the FCC change the rules in this area often, and the outcome of any claim depends on its facts. Past results do not guarantee future outcomes.

← Back to Blog

Let’s Talk.