US

TCPA: Enforcement and Penalties

Enforcement and Penalties [47 USC 227(g)]

Citation: § 227(g) (state enforcement), § 227(c)(5) (private right of action), Section 227(g)

Q: What are the penalties for TCPA violations? A: $500 per violation, up to $1,500 for willful violations. Both private individuals and State Attorneys General can sue [§ 227(c)(5), § 227(g)].

Key rule (§ 227(g)): State attorneys general may bring civil actions to enjoin violations and recover damages on behalf of residents.

Rule: TCPA has real teeth — $500-$1,500 per call, private right of action, class actions allowed, and 48 state AGs have MOUs with FCC for enforcement.


Who Can Enforce

Private Right of Action [§ 227(c)(5)]

EnforcerAuthority
Individual consumersCan sue directly
Class actionsAllowed
No government involvement neededPrivate litigation

State Attorneys General [§ 227(g)]

EnforcerAuthority
State AGsCan sue on behalf of residents
Federal courtsExclusive jurisdiction
48 state MOUsWith FCC for enforcement

FCC

EnforcerAuthority
FCCAdministrative enforcement
ForfeituresCivil penalties
InjunctionsCan order compliance

Damages and Penalties

Private Lawsuits [§ 227(c)(5)]

Violation TypeDamages
Standard violation$500 per violation
Willful/knowing violationUp to $1,500 per violation
Actual damagesIf greater than statutory

State AG Actions [§ 227(g)]

RemedyAvailable
InjunctionYes
Actual damagesYes
Statutory damages ($500-$1,500)Yes
Attorney’s feesYes

Caller ID Spoofing [§ 227(e)]

ViolationPenalty
Per violationUp to $10,000
Criminal penaltiesPossible fines

Why TCPA Litigation Is Common

Math of TCPA Class Actions

FactorImpact
$500 per callHigh per-violation damages
Class certificationAggregates thousands of calls
No harm requiredStatutory damages apply
Willful = treble$1,500 per call
Attorney incentiveFee-shifting provisions

Example Exposure

ScenarioPotential Liability
1,000 robocalls$500,000 - $1,500,000
10,000 robocalls$5,000,000 - $15,000,000
National campaignTens of millions

Defenses

Common TCPA Defenses

DefenseArgument
Consent obtainedPrior express consent existed
Not an ATDSEquipment doesn’t meet definition
Emergency purposeCall was for emergency
Established business relationshipHad existing relationship
Wrong numberReasonable procedures to avoid

The most important defense is documented consent:

ElementImportance
Written consentBest evidence
TimestampWhen consent given
ScopeWhat was consented to
Revocation trackingWhen/if revoked

FCC Focus Areas

  • AI-generated voice scams
  • Political robocalls
  • Spoofed caller ID
  • Cross-border robocalls
  • Autodial definition litigation (post-Facebook v. Duguid)
  • Consent scope disputes
  • Revocation of consent claims
  • Wrong number / reassigned number cases

AI Agent Risk Mitigation

If your AI makes calls:

RiskMitigation
No consentDocument consent before calling
Ignoring opt-outImmediately honor “stop” requests
No caller IDAlways identify at start
Calling DNC numbersCheck registry before calling
Class action exposureRobust compliance program

Compliance Checklist

  • Document all consent (written preferred)
  • Track consent scope (what was consented to)
  • Honor revocation immediately
  • Maintain do-not-call lists
  • Check National DNC Registry
  • Identify caller at start of calls
  • Provide callback number
  • Train personnel on TCPA
  • Audit calling practices regularly

Contains public sector information licensed under the Open Government Licence v3.0 where applicable. This is not legal advice. Always refer to official sources for authoritative text.

llms.txt