For most claims, yes: a company can owe statutory damages under the Telephone Consumer Protection Act for a robocall or text it sent by mistake, and an honest error doesn’t shrink the $500 base award on a robocall claim. Good faith has a narrower job. It supports a statutory Do Not Call defense, a reassigned-number safe harbor, and the argument against increased damages. A business that kept its procedures on paper usually has more room to defend a claim than the strict-liability label suggests.
Does a TCPA violation require intent?
Intent isn’t an element of a robocall or autodialer claim under 47 U.S.C. § 227(b). The private claim for those calls lets a plaintiff “receive $500 in damages for each such violation,” under 47 U.S.C. § 227(b)(3). Intent shows up in only one place. “If the court finds that the defendant willfully or knowingly violated this subsection or the regulations prescribed under this subsection, the court may, in its discretion, increase the amount of the award,” the statute continues, up to three times the base amount.
In Alea London Ltd. v. American Home Services, Inc., the Eleventh Circuit wrote that “The TCPA is essentially a strict liability statute which imposes liability for erroneous unsolicited faxes,” and that “The TCPA does not require any intent for liability except when awarding treble damages.” That case was an insurance-coverage fight over junk-fax damages, but § 227(b)(3) is the same damages clause that governs robocall and autodialer claims.
The Fair Debt Collection Practices Act takes a different approach. It excuses a collector who “shows by a preponderance of evidence that the violation was not intentional and resulted from a bona fide error notwithstanding the maintenance of procedures reasonably adapted to avoid any such error,” under 15 U.S.C. § 1692k(c). The TCPA’s robocall section has no matching clause. Collection agencies used to the FDCPA defense shouldn’t assume it carries over to the calls themselves.
Can a good-faith belief in consent defeat a TCPA claim?
Usually not, at least under the Ninth Circuit’s 2020 ruling on a reassigned number. In N.L. v. Credit One Bank, N.A., the opinion describes 189 automated calls that the bank’s vendors placed to a number its customer had given, after the number was reassigned to a mother whose eleven-year-old son used the phone. The bank asked for a jury instruction excusing it if it had “a good-faith basis to believe that they had consent to call N.L.’s telephone number.” The district court refused, and the jury awarded $500 for each call, a total of $94,500.
The Ninth Circuit affirmed, holding that “Credit One’s intent to call a customer who had consented to its calls does not exempt Credit One from liability under the TCPA when it calls someone else who did not consent.” The same opinion added a point every caller should take seriously: “If a caller’s intent could defeat liability, the safe harbors would be unnecessary.” (The same opinion’s autodialer ruling followed a definition the Supreme Court later rejected in Facebook v. Duguid. The consent holding didn’t depend on it.)
The court assumed the customer’s 2014 consent was valid, but by 2017 the number belonged to someone else. Good faith about who held the number didn’t change the result.
In Van Patten v. Vertical Fitness Group, LLC, the Ninth Circuit said: “We think it plain from the statutory language that prior express consent is an affirmative defense, not an element of a TCPA claim.” The defendant has to prove consent. A lead seller’s assurance that every number “opted in” isn’t proof, and a company without the form and time stamp is defending on good faith alone. California businesses should know the other Ninth Circuit TCPA rulings that bind courts in California, because N.L. and Van Patten set the consent rules a California federal court applies.
Is there a safe harbor for reassigned numbers?
The FCC’s reassigned-number safe harbor in 47 C.F.R. § 64.1200(m) is narrower than most callers assume. It protects a caller who had consent from the prior subscriber only if “the person, bearing the burden of proof and persuasion, demonstrates” two things. The caller must have queried the FCC’s Reassigned Numbers Database and gotten a “no” answer, and the call must have been “the result of the database erroneously returning a response of ‘no’ to the person’s query,” in the words of the FCC’s rule. A company that never checked the database gets nothing from this rule. One that checked and got a correct “yes” answer gets nothing either, because the database did its job. Teams that call numbers collected years ago should query the database before each campaign and keep the logs, because those logs are the safe harbor.
Where does the TCPA reward good-faith compliance?
Section 227(c), the Do Not Call side of the statute, is the one place Congress wrote a compliance defense into the text. A person who received “more than one telephone call within any 12-month period by or on behalf of the same entity” in violation of the rules may sue for “up to $500 in damages for each such violation,” under 47 U.S.C. § 227(c)(5). The same paragraph adds the defense: “It shall be an affirmative defense in any action brought under this paragraph 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.”
The § 227(c)(5) defense covers only actions under that paragraph: calls to numbers on the National Do Not Call Registry (the federal list of numbers whose owners don’t want telemarketing calls) and calls to people on a company’s internal do-not-call list. Prerecorded and autodialed call claims fall outside it.
For Registry calls, 47 C.F.R. § 64.1200(c)(2)(i) spells out a more specific version. A seller “will not be liable for violating this requirement if” it “can demonstrate that the violation is the result of error and that as part of its routine business practice, it meets the following standards,” according to the rule. The standards are written procedures, trained personnel, a recorded list of numbers the seller may not call, and a process for buying and using the Registry data only for compliance. The scrub requirement is the one that trips people up: the seller must use “a version of the national do-not-call registry obtained from the administrator of the registry no more than 31 days prior to the date any call is made, and maintains records documenting this process.”
Each of the standards in § 64.1200(c)(2)(i) is a paperwork test, not a test of intentions. A careful sales team with no written policy or dated scrub files can’t meet it. The 31-day Registry scrub rule and the records to keep is where most of these defenses are won or lost. High-volume outbound programs, like season ticket and live event sales calls, are where a stale scrub file multiplies exposure fastest, since every call made with it can count.
The phrase “is the result of error” in the Registry safe harbor limits it too. A company that called Registry numbers on purpose, believing an exemption applied, is arguing about the exemption, not the safe harbor.
How do intent and good faith line up across TCPA claims?
| Claim | Intent needed for liability | Good-faith tool | What good faith can’t fix |
|---|---|---|---|
| Autodialed or prerecorded calls without consent, 47 U.S.C. § 227(b)(1) | None | Reassigned-number safe harbor in 47 C.F.R. § 64.1200(m), and the argument against increased damages | Missing consent records, or a reassigned number never checked against the database |
| Calls or texts to a Registry number, 47 U.S.C. § 227(c)(5) | None | Statutory reasonable-practices defense and the safe harbor in § 64.1200(c)(2)(i) | No written procedures, training records, or scrub files dated within 31 days |
| Calls or texts after an opt-out request, 47 U.S.C. § 227(b) or (c)(5) | None | Ten-business-day window in § 64.1200(a)(10) and (d)(3), plus the reasonable-practices defense for § 227(c)(5) claims | Requests ignored past the window |
| Any claim, increased damages up to three times the base award | Willful or knowing conduct | Evidence of honest error and working procedures | Ignored complaints or opt-outs |
Does good faith still matter if it isn’t a defense?
Good faith is still the main fight over money, because § 227(b)(3) makes any increase discretionary. The court “may, in its discretion” raise it, and only on a finding of willful or knowing conduct, under § 227(b)(3). In N.L., the district court denied the plaintiff’s post-trial motion for treble damages, according to the Ninth Circuit’s opinion, even though the bank lost on liability. The bar for “knowing” is lower than many businesses expect, though: the Eleventh Circuit in Alea London said the standard “does not require any malicious or wanton conduct.” Evidence of honest error still shapes how a judge exercises that discretion, and it shapes settlement talks well before any judge does.
Revocation timing under § 64.1200(a)(10) works the same way on a smaller scale. The rule says opt-out requests “must be honored within a reasonable time not to exceed ten business days from receipt of such request.” A text sent the morning after a STOP reply sits inside that window. One sent a month later doesn’t, however sincere the mistake.
In N.L., the bank’s vendors placed all 189 calls, and the bank still answered for them. When a texting platform or vendor sends the messages, the seller’s good-faith reliance on that vendor won’t excuse a violation by itself. Contracts that require the vendor to keep and hand over its logs are worth more than promises that it complies.
Steps that keep a good-faith defense alive
- Put a litigation hold on call and text logs, dialer and platform data, and the consent record for every number in the claim as soon as a demand letter or complaint arrives.
- Export the internal do-not-call list and every opt-out request for the numbers involved, with the date each was received and the date it took effect.
- Pull the Registry scrub files and the download date of each version used, along with any Reassigned Numbers Database query logs.
- Gather the written do-not-call policy, training records, vendor and lead-source contracts, call scripts, and any recorded messages.
- Talk to a lawyer before replying to the claimant, calling the number again, or offering a payment.
Records like scrub files dated within 31 days decide whether a company can prove the defense the statute gives it, or only describe its good intentions. The firm’s TCPA litigation defense page explains how demand letters and class actions move through state and federal court.
Questions businesses ask about TCPA intent and good faith
Can a company be liable for TCPA violations it didn’t know about?
Yes, because liability under § 227(b) and § 227(c)(5) doesn’t depend on what the company knew. Lack of knowledge can help against increased damages, which require willful or knowing conduct, and it fits the Do Not Call safe harbor if the company also meets the written-procedure and scrub requirements. Standing alone, it isn’t a defense to the base award.
Is relying on a lead vendor’s consent records a good-faith defense?
A vendor’s records help only if they are the consumer’s actual consent records, because the Ninth Circuit’s 2017 Van Patten decision treats consent as an affirmative defense. The business that made or benefited from the call must prove it. A vendor’s warranty may support an indemnity claim against the vendor, but it doesn’t prove the consumer agreed. Companies that buy leads should collect the underlying consent records, not just the vendor’s promise that they exist.
What makes a TCPA violation willful or knowing?
Section 227(b)(3) doesn’t define “willfully” or “knowingly.” The Eleventh Circuit has said the standard doesn’t require malicious conduct, so a company can’t count on a clean motive to avoid it. Ignored opt-outs and calls that continue after a complaint are the facts a plaintiff will point to first. Even when the standard is met, the decision to raise the award is left to the judge’s discretion.
If your company is defending a mistaken-call claim
If your company is accused under the Telephone Consumer Protection Act of calling a reassigned number or a Registry number by mistake, the scrub files and consent records it kept before the calls usually decide how much the mistake costs. Rosenberger + Kawabata represents businesses defending TCPA lawsuits and class actions through its business litigation practice, including claims involving reassigned-number calls and Do Not Call compliance. Contact Rosenberger + Kawabata online for a confidential consultation, or call (310) 894-6921.
Sources
The statute is the Telephone Consumer Protection Act at 47 U.S.C. § 227. The FCC’s rules are at 47 C.F.R. § 64.1200. The Fair Debt Collection Practices Act’s bona fide error defense is at 15 U.S.C. § 1692k(c).
The court decisions are N.L. v. Credit One Bank, N.A., 960 F.3d 1164 (9th Cir. 2020); Van Patten v. Vertical Fitness Group, LLC, 847 F.3d 1037 (9th Cir. 2017); and Alea London Ltd. v. American Home Services, Inc., 638 F.3d 768 (11th Cir. 2011).
This post is general information about the Telephone Consumer Protection Act and related laws as of February 12, 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.