TL;DR: TCPA violations do not all cost the same thing and they do not all require the same proof, because the statute carries two separate private rights of action. Under 47 USC 227(b)(3) a plaintiff can sue over a single call or text, and recovers actual monetary loss or $500 per violation, whichever is greater, with no affirmative defense written into that paragraph. Under 47 USC 227(c)(5), the do-not-call track, the plaintiff must have received more than one telephone call within any 12-month period by or on behalf of the same entity, damages are worded as up to $500 per violation, and the defendant does get an affirmative defense for reasonable practices and procedures implemented with due care. Treble damages are discretionary in both tracks and capped at not more than three times the base award, so $1,500 is a ceiling a court may reach and not an automatic multiplier. The FCC runs a separate civil forfeiture track under 227(b)(4) where intent adds a penalty not to exceed $10,000, the limitations period is one year for ordinary violations and four years for intentional ones, and the Commission may not penalize under both subparagraphs for the same conduct. The Supreme Court shifted the posture on June 20, 2025 in McLaughlin Chiropractic Associates, Inc. v. McKesson Corp., 606 US 146, holding that the Hobbs Act does not bind district courts to the FCC reading of the statute. Calling outside 8 a.m. to 9 p.m. local time and calling a registered do-not-call number are both (c)-track problems under 47 CFR 64.1200(c), which makes them the violations your documented process can actually defend.
A rep works a list. Someone on that list sues. Now what?
Most teams answer that with one number they half remember, usually $1,500 a call, and build their entire posture around it. The number is real. It is not the rule. TCPA violations split into two different lawsuits with different entry requirements, different damages language, and only one of them hands you a defense you can earn through process.
That split decides what you fix first. So let’s break it down. This is general information about how the statute is written, not legal advice about your program.
What Counts as a TCPA Violation
A TCPA violation is conduct that breaks the Telephone Consumer Protection Act or the FCC rules written under it. Fine. That definition does not help you prioritize a single thing, because TCPA violations come in two kinds and the two behave nothing alike.
The useful frame is procedural. The statute gives private plaintiffs two separate rights of action and they live in different subsections. Subsection (b) is the technology side: prerecorded and artificial voice messages, automatic telephone dialing systems, and unsolicited fax advertisements. Subsection (c) is the solicitation side: the national do-not-call registry, company-specific suppression, and the hours you are allowed to dial.
Same statute. Different predicates. Different money.
One more thing before the details, because it closes an argument people try to make. 47 USC 227(c)(6) says the do-not-call subsection “shall not be construed to permit a communication prohibited by subsection (b).” Clearing the do-not-call rules does not clear the technology rules. They stack. A number that is absent from every registry and gave you written permission to call can still produce a (b)-track claim if the message that goes out is automated in a way the consent never covered.
TCPA Violations on the Automated Call Track Need Only One Call
Here is the part that surprises people. Under 47 USC 227(b)(3) there is no minimum call count. One prerecorded message to one wireless number, without the consent the rule requires, is already a complete claim. Nobody has to call twice. Nobody has to be annoyed twice.
The damages language is worth reading slowly. A plaintiff may bring an action “to recover for actual monetary loss from such a violation, or to receive $500 in damages for each such violation, whichever is greater.” That is not $500 instead of actual loss. It is whichever number is bigger. For most single-call claims actual loss is close to nothing, so $500 is the operative figure, and it attaches per violation rather than per plaintiff.
And there is no affirmative defense in that paragraph. None. The due-care defense people talk about sits in a different subsection and does not reach here.
So what does that change on the floor? Everything automated becomes a one-shot exposure. A campaign that is misconfigured for ten minutes and fires once is actionable on that one send. There is no “we caught it quickly” argument built into the statute for this track, and no process narrative that converts into a defense after the fact. Your controls on the (b) side have to be preventive, because the statute gives you nothing to say afterward.
That is also why this track is the one that scales badly. TCPA violations here are counted per message rather than per complaint. Per violation, times a campaign list, with no second-call requirement filtering the class down. The arithmetic is linear and it starts at the first send.
The Do-Not-Call Track Needs a Second Call Within 12 Months
The do-not-call track works differently and the difference is in the opening words of 47 USC 227(c)(5). The plaintiff has to be “A person who has received more than one telephone call within any 12-month period by or on behalf of the same entity.”
More than one. Within 12 months. Same entity. All three, together. TCPA violations on this track do not exist until the second call lands.
A single call to a registered do-not-call number does not open a private suit on this track. The second one does. And “by or on behalf of” is the clause that quietly pulls your vendors, lead partners and outsourced dialing into your own count. If two different partners each call the same person once for you inside a year, the statute is looking at the entity they called for, not at the two companies separately.
The damages wording shifts too, by exactly one word. Subsection (b) says “to receive $500 in damages for each such violation.” Subsection (c) says “to receive up to $500 in damages for each such violation.” One is a fixed figure, the other is a ceiling the court works under. Most summaries flatten both into “$500 per violation” and lose the distinction.
Then the defense, which is the whole reason documented process matters. 227(c)(5) states that it is an affirmative defense that the defendant “has established and implemented, with due care, reasonable practices and procedures to effectively prevent telephone solicitations in violation of the regulations prescribed under this subsection.”
Read what that asks for. Established and implemented. With due care. Practices and procedures, plural. Effective at preventing, not merely present in a policy document. This is an organizational test, and it only exists on this track. Teams that run disciplined do-not-call scrubbing on their calling lists are building the record this paragraph asks about, which is a different exercise from buying a tool and assuming the tool is the answer.
Willful Violations and the Treble Damages Ceiling
$1,500 is the number everyone quotes when TCPA violations come up. It is a ceiling, it is discretionary, and it is not where you should start your planning.

Both tracks use the same construction. If the court finds the defendant “willfully or knowingly” violated the statute or its regulations, the court “may, in its discretion, increase the amount of the award to an amount equal to not more than 3 times the amount available” under the damages subparagraph.
Count the moving parts. The court has to find willful or knowing conduct. The court may increase the award. The increase is capped at not more than three times. Three separate gates, and a court that clears all three still has discretion to land anywhere underneath the cap.
So $1,500 is the top of the (b) track rather than its default. Plan around $500 per violation and treat the multiplier as a risk premium attached to how your conduct looks, not as a line item. The practical read is that willfulness is usually argued from your own records: what you knew, when a suppression request arrived, and how long the dialing continued after it.
What a TCPA Violation Costs When the FCC Brings It
Private suits are not the only way TCPA violations get punished. 47 USC 227(b)(4) gives the FCC a civil forfeiture route and it runs on its own rules. Three details matter for planning.
Intent adds money. Under 227(b)(4)(B), a violation committed “with the intent to cause such violation” carries the ordinary forfeiture plus an additional penalty “not to exceed $10,000.”
The clock is short, then long. Under 227(b)(4)(E), no forfeiture penalty may be imposed for an ordinary violation that occurred more than one year before the required notice, or more than four years before it for an intentional one. Intent quadruples the lookback window. That is a records-retention question as much as a legal one, because the exposure period you have to be able to reconstruct is four times longer in the case where someone alleges you meant it.
The agency picks one, not both. 227(b)(4)(F) says the Commission may not determine or impose a forfeiture penalty under both the ordinary and the intentional subparagraphs “based on the same conduct.”
Forfeiture is additive against everything else, though. The statute says a forfeiture penalty under this subparagraph “shall be in addition to any other penalty provided for by this chapter.” An FCC action does not consume or settle the private claims sitting next to it.
Why Courts Stopped Deferring to the FCC on TCPA Questions
For years the practical answer to a hard TCPA question was to find the FCC ruling and stop reading. That stopped being right on June 20, 2025.
In McLaughlin Chiropractic Associates, Inc. v. McKesson Corp., 606 US 146 (2025), the Supreme Court held that “The Hobbs Act does not bind district courts in civil enforcement proceedings to an agency’s interpretation of a statute.” District courts “must independently determine the law’s meaning under ordinary principles of statutory interpretation while affording appropriate respect to the agency’s interpretation.”
The facts underneath show the stakes better than the holding does. McKesson sent unsolicited fax advertisements through a subsidiary in 2009 and 2010. The district court treated an FCC order as binding, granted summary judgment against the claims involving online fax services, and then decertified the class. What survived was 12 faxes received on a traditional machine and damages of $6,000.
Twelve violations. $500 each. $6,000. That is the statute doing exactly what the text says, and it is a cleaner illustration of per-violation arithmetic than any hypothetical.
What it means for your program is narrower than the headlines suggested. The prohibitions did not change. Who gets the last word on what they mean did. An FCC interpretation you have been relying on is now persuasive in district court rather than controlling. If your program’s entire defensibility rests on one favorable Commission reading of an ambiguous term, that position is thinner than it was before that date, and it is worth knowing which of your assumptions are statutory text and which are agency gloss.
How One Campaign Becomes Thousands of TCPA Violations
Per violation is the phrase that does the damage once TCPA violations start being counted. Not per plaintiff, not per campaign. Every message that breaks the rule is its own count, so the exposure scales with list size rather than with how many people bother to complain.

That is why class certification, not the per-call figure, is the real multiplier. McLaughlin shows both ends of it in one case. The district court first certified a class of fax recipients without distinguishing between traditional machines and online fax services. After the FCC order landed, the court granted summary judgment on the online-fax claims and decertified the class. The same conduct went from a certified class action to 12 faxes and $6,000.
Read the mechanism rather than the outcome. The class lived or died on whether one legal question applied the same way to everyone on the list. When the answer split the recipients into two groups, the class stopped holding together.
So the thing that concentrates risk is uniformity. A campaign that treats every record on a list identically, with the same technology and the same consent assumption, is a campaign where one adverse ruling applies to every record at once. Segmentation that follows the actual consent record is not only better targeting. It is the structural difference between a claim and a class.
Which Controls Reduce Which TCPA Violations
Now the operational part. Different TCPA violations call for different controls, so map each control to a track, because a control that helps on one side can do nothing at all on the other.
The do-not-call track is the one your process can defend, and two of its most common violations are flat rules in 47 CFR 64.1200(c). You may not make a telephone solicitation to a residential subscriber “before the hour of 8 a.m. or after 9 p.m. (local time at the called party’s location).” You may not call a number on the national do-not-call registry, and the rule says those registrations “must be honored indefinitely, or until the registration is cancelled by the consumer or the telephone number is removed by the database administrator.”
Both of those are list-and-clock problems. Both sit inside the affirmative defense. That is where documented process converts into something a court will look at.
Kixie’s National DNC compliance workflows support checks against the National Do Not Call Registry and against your internal suppression lists, and the product page states plainly that customers remain responsible for their own calling practices and legal review. That boundary is the honest one. A platform enforces a list and a clock. It cannot establish that your organization implemented reasonable practices with due care, because 227(c)(5) asks about the organization, not the software. Nothing you buy produces that finding for you.
The technology track is different in kind. Preventive only. Decide which campaigns can fire a prerecorded or artificial voice message, decide which consent record authorizes each one, and gate the campaign on the record rather than on the list. A list tells you who. A consent record tells you whether, and only the second one answers a (b)-track claim.
A reasonable place to start is your timing logic, because it fails quietly. Does your calling window follow the called party’s local time or your office’s? Area code is a weak proxy for where a mobile number actually is, and a window computed from the wrong zone produces violations nobody notices until the second call lands and a plaintiff has standing.
Here is the inspection list. Which campaigns can send an automated voice message, and what consent record gates each one? Does your calling window follow the recipient’s local time? When a suppression request arrives, how many minutes until it reaches every system that can dial? Could you produce the second call inside a 12-month window that a do-not-call plaintiff would have to prove? And who counts as acting on your behalf, and do their lists get scrubbed on your schedule or on theirs?
Answer those five and you know your real exposure to TCPA violations instead of your assumed one. Then layer the state rules on top, because mini-TCPA laws vary by state and are counted separately from the federal claims, and fold the result into whatever TCPA compliance program your team already runs.
TCPA Violations FAQ
Is one call a TCPA violation?
On the technology track, yes. 47 USC 227(b)(3) sets no minimum call count, so a single prerecorded or artificial voice message sent without the consent the rule requires can support a claim on its own. The do-not-call track is different. 227(c)(5) requires a plaintiff who received more than one telephone call within any 12-month period by or on behalf of the same entity.
How much does a TCPA violation cost?
Under 227(b)(3) it is actual monetary loss or $500 per violation, whichever is greater. Under 227(c)(5) it is actual loss or up to $500 per violation. A court that finds the conduct willful or knowing may increase either award to not more than three times that amount, and that increase is discretionary rather than automatic.
Does the TCPA have a safe harbor rule?
Not in the broad form most people mean. 227(c)(5) provides an affirmative defense for a defendant that established and implemented, with due care, reasonable practices and procedures to effectively prevent solicitations that break the do-not-call regulations. It applies to that track only. Subsection (b) contains no equivalent defense, so an automated-message claim cannot be answered this way.
Who enforces TCPA violations?
Private plaintiffs and the FCC, on separate tracks. Private plaintiffs sue under 227(b)(3) or 227(c)(5) in an appropriate state court where state law permits it. The FCC runs a civil forfeiture process under 227(b)(4), and because the statute says a forfeiture penalty is in addition to any other penalty in the chapter, both can proceed over the same campaign.
Did the Supreme Court change TCPA liability in 2025?
It changed who interprets the statute, not what the statute prohibits. McLaughlin Chiropractic Associates, Inc. v. McKesson Corp., 606 US 146 (2025), held that district courts are not bound by the FCC’s interpretation in civil enforcement proceedings and must determine the law’s meaning independently, while affording appropriate respect to the agency’s interpretation.
Do state laws add to federal TCPA violations?
Yes, and they are counted on their own terms. State telemarketing statutes carry their own consent standards, registration duties and damages, so a single campaign can face a federal claim and a state claim at once. Check the states your list actually dials into rather than assuming the federal window is the strictest one.
Sources
- United States Code, Title 47, Section 227, Restrictions on use of telephone equipment. Statutory text for the two private rights of action at 227(b)(3) and 227(c)(5), the discretionary treble construction, and the civil forfeiture provisions at 227(b)(4). govinfo.gov. Reviewed November 19, 2026.
- McLaughlin Chiropractic Associates, Inc. v. McKesson Corp., 606 US 146 (2025), No. 23-1226, argued January 21, 2025 and decided June 20, 2025. Slip opinion for the holding on Hobbs Act deference and for the 12-fax, $6,000 damages figure. supremecourt.gov. Reviewed November 19, 2026.
- Code of Federal Regulations, Title 47, Section 64.1200. FCC rules on telephone solicitation, including the 8 a.m. to 9 p.m. local-time window and the national do-not-call registry requirement. ecfr.gov. Reviewed November 19, 2026.
Sources verified by the Kixie Research Team on November 19, 2026.
Ready to close more deals with Kixie?
See how Kixie's AI-powered tools can transform your sales and support operations.
Start Free Trial