Last updated 2026-07-10

TL;DR
Federal law (47 U.S.C. § 227) prohibits using an autodialer or prerecorded voice to call a cell phone for debt collection without prior express consent. Each illegal call exposes the caller to $500, $1,500 in statutory damages. A 2021 Supreme Court ruling narrowed what counts as an autodialer, but prerecorded message calls remain strictly regulated regardless of the equipment used.
Which federal laws govern debt collector robocalls on cell phones?
Two federal statutes do the heavy lifting. The Telephone Consumer Protection Act (47 U.S.C. § 227) is the main one: it restricts automated calls and prerecorded messages to cell phones. The Fair Debt Collection Practices Act (15 U.S.C. § 1692) layers on top with conduct rules specific to third-party debt collectors, covering call timing, harassment, and dispute rights. When a collector uses a robocall to reach a consumer's cell phone, both statutes can apply at once. That doubles the exposure.[1][2]
The TCPA was written in 1991, long before cell phones were everywhere, but the FCC has read it to cover cellular numbers since the early 2000s. The statute itself makes it unlawful to make any call using an automatic telephone dialing system (ATDS) or an artificial or prerecorded voice to any number assigned to a cellular telephone service, unless the caller has prior express consent or fits a narrow statutory exemption.[1]
The FDCPA has no robocall prohibition of its own. What it bans is conduct that harasses, oppresses, or abuses a consumer, and a run of automated calls can trip that standard on its own.[2]
What does 47 U.S.C. § 227 actually say about cell phone calls?
The operative sentence is worth quoting straight. 47 U.S.C. § 227(b)(1)(A) makes it unlawful "to make any call (other than a call made for emergency purposes or made with the prior express consent of the called party) using any automatic telephone dialing system or an artificial or prerecorded voice" to any number assigned to a cellular telephone service.[1]
A few words in that sentence carry enormous weight.
"Any call" means one call is enough. You do not need a pattern. One autodialed or prerecorded call to a cell phone without consent is one violation.
"Automatic telephone dialing system" is defined elsewhere in the statute as equipment with the capacity to store or produce telephone numbers using a random or sequential number generator, and to dial those numbers.[1] The Supreme Court's 2021 decision in Facebook, Inc. v. Duguid, 592 U.S. 395, narrowed that definition sharply. A system has to use a random or sequential number generator, not merely dial from a stored list, to count as an ATDS.[3] That matters enormously for debt collectors running a predictive dialer off a specific list of debtors, because those systems may not meet the ATDS definition after Duguid.
"Prerecorded voice" is a separate and independent path to liability. If your system plays a recorded message, the equipment classification is beside the point. The prerecorded voice prohibition applies no matter what dialing technology sits behind it.[1] Collectors who thought Duguid handed them a free pass on prerecorded voicemails were wrong.
Are there any exemptions that let debt collectors robocall cell phones legally?
Yes, one narrow exemption exists. Congress created a financial institution and debt collection carve-out in the Bipartisan Budget Act of 2015, which added 47 U.S.C. § 227(b)(1)(A)(iii). That provision allows autodialed or prerecorded calls to cell phones to collect a debt owed to or guaranteed by the United States without consent, subject to FCC rules.[4]
The FCC issued implementing rules for the exemption in 2016. The limits are real: no more than three calls per month to the consumer's cell phone, a mandatory opt-out mechanism, and calls that relate specifically to a federally backed debt such as a federally insured student loan or a government-backed mortgage.[4]
Private commercial debt, credit card debt, medical bills, auto loans, most consumer debt: none of it qualifies. The exemption is narrow by design. If a collector is calling about a Citibank card or a hospital bill, there is no federal statutory exemption to lean on. Consent is the only path.
Some states run their own mini-TCPA laws with different exemption structures, so cross-state operations have to check both layers. See our coverage of TCPA law for how federal and state rules interact.
What counts as prior express consent for debt collection calls?
Consent for debt collection calls is prior express consent, the informational-call standard, not the higher prior express written consent that governs marketing. The FCC's 2012 order and later guidance draw that line.[5]
Here is the practical version. The FCC has said a consumer who voluntarily gives a cell number to a creditor in connection with a debt has given prior express consent to be called at that number about the debt. The classic case: you put your cell number on a credit card application. The original creditor and, this part trips people up, a debt collector who later buys the debt can both rely on that consent.[5]
But consent has limits that catch collectors constantly.
Consent is revocable. The consumer can pull it at any time, by any reasonable means. A written request, a verbal statement mid-call, a text reply: any of them works. Once consent is revoked, the next autodialed or prerecorded call to that cell phone is a fresh violation.[6] There is no required format for revocation, so collectors need a system that captures and honors it the moment it lands.
Consent travels with the debt, but only the consent originally given. If the consumer hands a different cell number to somebody else, or the number gets reassigned to a new subscriber, the original consent does not stretch to the new holder. Reassigned-number liability is one of the most litigated corners of TCPA debt collection. The FCC has tried more than once to build a reassigned number database; as of 2025 that database exists and carriers contribute to it, though its coverage is still incomplete.[7]
How much does a TCPA violation cost per robocall on a cell phone?
Statutory damages under 47 U.S.C. § 227(b)(3) are $500 per violation, trebled to $1,500 if the court finds the violation was willful or knowing.[1] There is no cap per lawsuit. A collector who made 10,000 calls to cell phones without consent is looking at $5 million to $15 million in statutory exposure before any class certification.
TCPA class actions are what turn small per-call numbers into company-ending liability. A named plaintiff sues for everyone who got similar calls. Settlement figures swing widely. Capital One settled a TCPA class action in 2014 for $75.5 million, at the time one of the largest TCPA settlements on record.[8] More recent settlements have run from the low millions to north of $50 million depending on call volume and the quality of the consent record.
Here are the key penalty thresholds under federal law.
| Violation type | Statutory damages per call | Willful/knowing multiplier |
|---|---|---|
| TCPA: autodialed call to cell without consent | $500 | Up to $1,500 |
| TCPA: prerecorded call to cell without consent | $500 | Up to $1,500 |
| FDCPA: harassment or abuse | Up to $1,000 per action | N/A (actual damages also available) |
| FDCPA: class action cap | Lesser of $500,000 or 1% of net worth | N/A |
Sources: 47 U.S.C. § 227(b)(3)[1], 15 U.S.C. § 1692k[2].
FDCPA damages are separate and stack. One harassing robocall campaign can generate TCPA statutory damages plus FDCPA actual and statutory damages in the same suit.[2]
What did the Supreme Court's Facebook v. Duguid decision change for debt collectors?
Facebook, Inc. v. Duguid (2021) is the most significant TCPA ruling in a decade.[3] The Court held unanimously that to qualify as an ATDS, a device must use a random or sequential number generator to either store or produce the numbers it dials. A system that simply dials from a stored list of specific numbers, without generating them randomly or sequentially, does not meet the statutory definition.
For debt collectors, that was a real procedural win. Predictive dialers that work off a curated list of debtor phone numbers are the standard tool of the trade. Under Duguid, those dialers likely are not an ATDS, so the ATDS prong of 47 U.S.C. § 227(b)(1)(A) may not reach them.
Here is the catch collectors keep missing. Duguid never touched the prerecorded voice prong. If a collector uses any equipment to deliver a recorded message, including a human agent clicking play on a soundboard, the prerecorded voice prohibition still applies in full, ATDS status irrelevant.[1] Plenty of collectors run prerecorded messages or voicemail drops, which means Duguid gave them less relief than they assumed.
Lower courts after Duguid have also split on the edge cases. Some systems store numbers and layer in an algorithmic component, and courts are still sorting out where those land. If your dialer vendor calls itself "TCPA-safe" post-Duguid, make them show you exactly how it works and get it in writing.
Are robocalls allowed on cell phones under any law change after 2015?
The 2015 budget act created the federal-debt exemption described above, the biggest change since the original TCPA. Collectors sometimes call this the "robocalls allowed on cell phone law change" because it opened a window that did not exist before. That window is tiny: three calls per month max, federal debt only, mandatory opt-out.[4]
The FCC has issued several clarifying orders over the years that shape the law's practical reach. Its 2015 Omnibus Order addressed reassigned numbers, spelled out revocation rights, and answered some internet-to-phone text questions. A 2020 FCC order handled certain text-based exemptions. None of these expanded the core prohibition on autodialed or prerecorded calls to cell phones without consent.[6]
Congress has not otherwise loosened robocall restrictions on cell phones. If anything, the direction since 2019 has been the opposite: the TRACED Act of 2019 required carriers to build STIR/SHAKEN call authentication and gave the FCC new tools to chase illegal robocallers.[9] That law does not create new private rights of action against debt collectors specifically, but it added FCC enforcement resources and stiffer penalties for willful violations.
State law is its own story. Florida, through its Florida Telephone Solicitation Act (substantially amended in 2021), imposes stricter consent standards than federal law and creates its own private right of action.[10] The federal floor for robocalls on cell phones has not dropped; some states have raised the ceiling.
What rules does the FDCPA add on top of the TCPA for cell phone calls?
The FDCPA reaches only third-party debt collectors, not original creditors collecting their own debts. If Chase calls you about your Chase card, the FDCPA does not apply. If Chase sells the debt to a collection agency, the agency is covered.[2]
Under the FDCPA, calls can only happen between 8 a.m. and 9 p.m. local time at the consumer's location. That applies to every call, not only robocalls, and it stacks on top of any TCPA obligation.
The FDCPA also bars contacting a consumer who has told the collector in writing to stop. A written cease-and-desist under 15 U.S.C. § 1692c(c) is a different animal from a TCPA revocation of consent; the FDCPA cease-and-desist shuts down almost all communication, more than autodialed calls.[2]
The Consumer Financial Protection Bureau's 2021 Regulation F rules, which implement the FDCPA, added specific guidance on electronic communications including calls and texts. Under Regulation F, a debt collector may not call a consumer more than seven times within a seven-day period, and after a phone conversation with a consumer about a debt, the collector must wait at least seven days before calling again.[11] That frequency cap is independent of the TCPA consent analysis. Even with valid consent for TCPA purposes, blowing past Regulation F's cap creates FDCPA liability.
The short version: TCPA consent does not let you call as often as you like. FDCPA frequency and timing rules still apply, and you can violate them even with clean TCPA consent.
How does the CFPB's Regulation F affect robocalling practices?
Regulation F took effect November 30, 2021, the CFPB's first full rule implementing the FDCPA for modern communications.[11] Its call frequency limits are the change that bites hardest for collectors running automated dialers.
The seven-call-in-seven-days cap is a bright line. The CFPB built it as a rebuttable presumption: more than seven calls in seven days is presumed harassment. Fewer than seven does not automatically clear you; the broader FDCPA harassment standard still applies.
Regulation F also requires collectors to give a clear and conspicuous disclosure in certain electronic communications. For voicemails and prerecorded messages left on cell phones, a collector has to identify itself without revealing the call's debt-collection purpose to a third party who might overhear it. That is a genuine problem for prerecorded messages, because the script has to thread a very narrow needle.
If you use a compliance tool or dialer to manage attempts, it should track call frequency per consumer per week, more than total daily volume. Tools that count only at the daily-volume level will miss Regulation F violations even when the overall numbers look fine.
What should debt collectors actually do to stay compliant right now?
The cleanest path is a consent-first workflow that runs before any automated call or prerecorded message hits a cell number. That means documenting when and how consent was given, scrubbing for revocations ahead of every dial, and checking the reassigned number database for numbers that may have changed hands.[7]
The specific steps:
First, identify every cell number in your portfolio. Cell numbers carry specific area codes and prefixes, but number portability muddies that. Use a real-time number-type lookup, not a static list, before dialing.
Second, confirm consent for each cell number. If the original creditor's intake captured it, that consent should travel with the debt documentation. If you cannot document consent, do not autodial or drop a prerecorded message on that cell.
Third, scrub against the reassigned number database. The FCC's Reassigned Numbers Database launched in 2021.[7] Querying it before calling is not mandatory in every context, but it is strong evidence of good-faith effort when a lawsuit lands.
Fourth, build revocation capture into every call flow. If a consumer says "stop calling me" on a live agent call, or in reply to a text or prerecorded message, that revocation has to reach your dialer before the next cycle. Revocation-handling failures are one of the most common sources of post-consent TCPA liability.
Fifth, enforce FDCPA timing and frequency caps in your dialer logic. The seven-call-in-seven-day cap under Regulation F is a system configuration problem as much as a policy one.[11]
LeadCompliant offers a free TCPA compliance kit and number-checking tools that get teams through these steps without a full compliance staff. Worth running as a baseline even if outside counsel also reviews your program.
For multi-state operations, call recording consent is a separate layer that intersects with outbound collection, and the rules vary a lot by state. Our guide on TCPA law covers the federal framework, and if you operate in California, California call recording laws is worth reading before you record any collection calls.
What are the biggest mistakes debt collectors make that lead to TCPA lawsuits?
The mistakes that generate lawsuits are almost never exotic. They are operational failures that happen at scale.
Calling reassigned numbers. A consumer gave consent years ago, the number got reassigned to someone else, and the new subscriber gets fifty automated calls about a debt they know nothing about. That new subscriber has zero relationship with the creditor, gave no consent, and each call is a separate violation.[7] The damages pile up fast.
Ignoring verbal revocations. An agent takes a call, the consumer says "don't call me again," the agent drops a note in a comments field that never syncs to the dialer's suppression list, and the dialer calls again the next day. Courts have held consistently that a verbal revocation during a call is effective.[6]
Using prerecorded messages while assuming Duguid protects them. After Duguid, some collectors decided their systems were no longer regulated. If those systems leave any recorded message, that assumption is dead wrong.
Honoring opt-outs too slowly. Even with a process for capturing opt-outs, a lag in syncing that data to the dialer creates exposure. The FCC has not set a specific hours standard, but courts have found violations where opt-outs were processed in an overnight batch while more calls went out the same day.
Misreading a number as a landline when it is actually a cell. Wireless number portability means a number ported from a landline carrier is now a cell number. Static databases go stale. Real-time lookup before dialing is the only reliable method.
For teams recording their collection calls, state laws add another layer. Pennsylvania do-not-call list rules and Texas call recording laws are examples of state requirements that sit alongside the federal TCPA framework.
Frequently asked questions
Can a debt collector use a robocall on my cell phone at all?
Yes, but only with your prior express consent or if the debt is federally backed (like a government-guaranteed student loan), in which case they can call up to three times per month under FCC rules. For private debt such as credit cards, medical bills, or auto loans, a robocall or prerecorded message to your cell phone without consent violates 47 U.S.C. § 227 and exposes the collector to $500-$1,500 per call in statutory damages.
What is the law on how many times a debt collector can call my cell phone?
Under CFPB Regulation F (effective November 2021), a debt collector may not call any consumer more than seven times within a seven-consecutive-day period. After a live phone conversation with a consumer about a specific debt, the collector must wait at least seven days before calling again. This cap applies regardless of whether calls are manual or automated, and TCPA consent does not override it.
Did the Supreme Court change the law on debt collector robocalls?
The Supreme Court's 2021 Facebook v. Duguid ruling narrowed the ATDS definition, which may mean some predictive dialers calling from a stored list no longer qualify as autodialers under the TCPA. However, the prerecorded voice prohibition is entirely separate and unchanged. Any collector leaving recorded messages on cell phones is still subject to the full TCPA prohibition regardless of dialing equipment.
Can I sue a debt collector for robocalling my cell phone?
Yes. 47 U.S.C. § 227(b)(3) gives consumers a private right of action. You can sue in federal or state court and recover $500 per violation, or up to $1,500 if the violation was willful or knowing. No actual harm is required; statutory damages are available per call. Class actions are common when large numbers of consumers received similar calls.
Does giving my cell number to a creditor count as consent for robocalls?
Generally yes, under FCC guidance. If you voluntarily provide your cell phone number to a creditor when incurring or paying a debt, you have given prior express consent to be called at that number about the debt. That consent can transfer to a debt collector who later acquires the account. You can revoke consent at any time, by any reasonable means, and revocation takes effect immediately.
What is the difference between a robocall and a prerecorded voice message under TCPA?
The TCPA restricts two things: calls made with an ATDS (autodialer) and calls using an artificial or prerecorded voice. These are separate prongs. An ATDS must use a random or sequential number generator per the 2021 Duguid ruling. A prerecorded voice is any recorded message played during or instead of a live call. Either one, used without consent on a cell phone, is a violation.
Can a debt collector leave a prerecorded voicemail on my cell phone?
Only with your prior express consent. Voicemail drops and ringless voicemails have been debated at the FCC, but the dominant regulatory and court position is that they constitute calls under the TCPA. The FCC proposed in 2022 to confirm that ringless voicemails require TCPA consent. Without consent, even a prerecorded voicemail that never rings the phone is a potential TCPA violation.
What is the federal debt exemption for debt collector robocalls?
The Bipartisan Budget Act of 2015 added 47 U.S.C. § 227(b)(1)(A)(iii), allowing autodialed or prerecorded calls to cell phones to collect federally backed debt (such as government-guaranteed student loans or federally insured mortgages) without consent. FCC rules limit these calls to three per month per consumer, require an opt-out mechanism, and require calls to relate specifically to the federally backed debt.
How do I stop a debt collector from robocalling my cell phone?
Revoke consent verbally during any call, in writing by letter or email, or via text response if the contact was by text. Revocation is effective immediately under FCC guidance and the TCPA. You can also send a written cease-and-desist under the FDCPA (15 U.S.C. § 1692c(c)), which stops virtually all collector contact. If calls continue after clear revocation, document each one for a potential lawsuit.
Does the FDCPA also apply to robocalls, or only the TCPA?
Both apply to third-party debt collectors simultaneously. The TCPA governs the technology and consent. The FDCPA governs conduct including call timing (8 a.m. to 9 p.m. local time), frequency (Regulation F's seven-call cap), harassment, and cease-and-desist obligations. Violating either or both creates separate statutory damages. Original creditors collecting their own debt are covered by TCPA but not FDCPA.
What is a reassigned number and why does it matter for debt collector TCPA liability?
A reassigned number is a cell number that used to belong to the consenting consumer but has since been reassigned by the carrier to a new, different subscriber. Consent given by the original subscriber does not transfer to the new one. If a collector calls the reassigned number using an ATDS or prerecorded voice, the new subscriber can sue even though the collector believed it had valid consent. The FCC's Reassigned Numbers Database helps callers check before dialing.
Are state laws stricter than the TCPA for debt collector robocalls on cell phones?
Yes, in several states. Florida's 2021 amendments to the Florida Telephone Solicitation Act created state-level restrictions that in some ways go beyond federal TCPA requirements. California's consumer protection laws add additional layers. Collectors operating across multiple states need to meet the highest applicable standard, above the federal floor. State attorneys general can also bring enforcement actions separate from private TCPA lawsuits.
How does the TRACED Act affect debt collector robocalls?
The Telephone Robocall Abuse Criminal Enforcement and Deterrence Act of 2019 (TRACED Act) required carriers to implement STIR/SHAKEN call authentication, increased civil forfeiture penalties for willful TCPA violations, and extended the FCC's window to catch illegal robocallers. It did not change the substantive rules on consent or the per-call damages available to consumers, but it increased enforcement pressure and carrier-level blocking of suspicious call patterns.
What records should a debt collector keep to defend against a TCPA robocall lawsuit?
At minimum: the source and date of the cell number, documentation of how consent was obtained (original creditor intake form, signed agreement, or recorded verbal consent), timestamps of all call attempts and outcomes, revocation records with timestamps, reassigned number database query results, and dialer technology specifications. Courts have ruled against collectors who could not produce consent documentation. Treat consent records as you would financial records: keep them indefinitely.
Sources
- Cornell Law School, Legal Information Institute: 47 U.S.C. § 227: TCPA prohibits autodialed or prerecorded calls to cell phones without consent; statutory damages are $500 per violation, trebled to $1,500 for willful violations
- Cornell Law School, Legal Information Institute: 15 U.S.C. § 1692 (FDCPA): FDCPA prohibits harassment, abuse, and deceptive conduct by third-party debt collectors; statutory damages up to $1,000 per action plus class action caps
- U.S. Supreme Court: Facebook, Inc. v. Duguid, 592 U.S. 395 (2021): ATDS definition requires random or sequential number generation; systems dialing from stored specific lists may not qualify
- Cornell Law School, Legal Information Institute: 47 CFR § 64.1200 (TCPA consent rules): Consumer who provides cell number to creditor in connection with a debt gives prior express consent for informational calls about that debt
- FCC: Reassigned Numbers Database: FCC launched the Reassigned Numbers Database in 2021 to help callers identify numbers reassigned to new subscribers before dialing
- Federal Trade Commission: consumer resources on debt collection: Background on federal debt collection law framework and consumer rights
- Florida Legislature: Florida Telephone Solicitation Act, Section 501.059, Florida Statutes: Florida's 2021 amendments to the FTSA impose state-level consent requirements that in some applications exceed federal TCPA standards
- CFPB: Debt Collection Rule (Regulation F, 12 CFR Part 1006): Regulation F effective November 30, 2021 caps debt collector calls at seven per consumer per seven-day period; after live conversation, collector must wait seven days before calling again
- CFPB: Consumer Financial Protection Bureau homepage: CFPB examination findings on debt collector call practices and compliance failures