Predictive dialer compliance: what outbound teams must know

Last updated 2026-07-09

What makes a predictive dialer an 'autodialer' under the TCPA?

Courts have fought over this question for a decade, and the answer still has rough edges. Under 47 U.S.C. § 227(a)(1), an automatic telephone dialing system (ATDS) is equipment with the capacity "to store or produce telephone numbers to be called, using a random or sequential number generator" and to dial those numbers automatically ^[1]. The problem is that modern predictive dialers do not always use random or sequential number generation. They work from a pre-loaded contact list and use an algorithm to predict when an agent will be free, then launch the next call before that agent finishes the current one.

The Supreme Court settled one piece of this in Facebook, Inc. v. Duguid (2021). The Court held that equipment must use a random or sequential number generator to qualify as an ATDS under the statute ^[2]. That ruling knocked out a wave of cases against systems that simply dial from a stored list in a fixed order. But it did not end all predictive dialer exposure. The FCC has historically read the ATDS definition broadly, and its 2015 Declaratory Ruling stated that a dialer's "capacity" includes potential or future capacity, more than present function ^[3]. That 2015 order was partly vacated by the D.C. Circuit in ACA International v. FCC (2018), which means the capacity question is still open at the FCC level.

Here is the practical upshot. If your predictive dialer generates numbers on the fly, randomizes any part of the dial sequence, or produces numbers outside your uploaded list, courts will treat it as an ATDS. If it exclusively dials numbers a human loaded into a CRM and does nothing more, Facebook v. Duguid gives you a real defense on the ATDS question. That defense does not make you immune. You still face the separate "artificial or prerecorded voice" prohibition if you use those call types, and state mini-TCPA statutes often define ATDS more broadly than the federal floor ^[4].

What consent does a predictive dialer call to a cell phone require?

Consent requirements depend on the purpose of the call. The FCC's 2012 rules drew a clear line ^[5]:

Call type	Required consent level
Telemarketing / advertising call to cell phone	Prior express written consent
Informational / non-telemarketing call to cell phone	Prior express consent (oral or written)
Telemarketing call to residential landline	Prior express written consent (since 2012 rules)
Debt collection / informational call to landline	No TCPA consent required (but state law may differ)

Prior express written consent for telemarketing means a signed, written agreement that clearly authorizes calls from the specific seller, includes the telephone number, and includes a clear and conspicuous disclosure that the person is not required to agree as a condition of purchase ^[5]. Electronic signatures count. A checkbox on a web form works if it meets those disclosure requirements.

Oral consent for informational calls is weaker. It satisfies the federal standard but is nearly impossible to prove in litigation unless you record it. If you are calling cell phones, getting written consent is almost always worth the extra friction.

One thing people miss: the called party can revoke consent at any time, by any reasonable means. The FCC's 2024 one-to-one consent rule, which took effect January 27, 2025, went further and required that each telemarketer obtain consent individually rather than relying on a blanket consent obtained by a lead generator for multiple companies ^[6]. That rule was vacated by the Eleventh Circuit in January 2025 before its effective date, so the one-to-one rule is currently not in effect, but the FCC may pursue it again. Watch TCPA news today for updates as this litigation unfolds.

How does the TCPA's abandoned call rule apply to predictive dialers?

Predictive dialers cause abandoned calls. The dialer places more calls than available agents, so when calls connect and no agent is free, the consumer picks up and hears silence or a dead line. That is an abandoned call, and it has its own rule.

The FCC allows a maximum abandoned call rate of 2% per campaign, measured over a 30-day period ^[3]. When a call is abandoned, you must play a prerecorded identification message within 2 seconds of the consumer's greeting. That message must state your name, phone number, and the fact that the call will not be delivered to an agent. You must also maintain a do-not-call list and honor requests made through the abandoned call message.

Most compliance officers focus on consent and forget the abandoned call rate. Do not. FCC enforcement actions and plaintiff class actions both cite abandoned call violations as standalone TCPA claims. Monitor your dialer's reporting dashboard weekly. If your abandon rate creeps above 2%, slow the pacing algorithm before the month closes, because the measurement is per campaign per 30 days, not per call.

A few dialers let you set the abandon rate target in the configuration. Set it to 1.5% as a buffer. That half-percent gives you room before you breach the FCC's ceiling during a spike in answer rates.

Do predictive dialer rules apply to debt collection calls under the FDCPA?

Yes, and collectors have two sets of rules to satisfy at once. The Fair Debt Collection Practices Act (15 U.S.C. § 1692 et seq.) governs collector conduct independently of the TCPA ^[7]. The TCPA governs the technology used to reach consumers. A debt collection call to a cell phone using a predictive dialer still needs prior express consent under the TCPA, unless a narrow exception applies.

The TCPA does have a healthcare and government-backed debt exemption, but it is narrow. Calls to collect debts owed to or guaranteed by the federal government (student loans, FHA mortgages) may qualify for reduced requirements under the 2015 FCC order, though that exemption has been contested and has strict conditions around frequency and timing ^[3].

For private debt collectors, the practical rule is simple: if you are calling a cell phone with a predictive dialer, you need prior express consent. Consent is typically established at account origination, when the consumer provides a cell phone number and agrees to be contacted. But if the number was reassigned to a different person since origination, you have a problem. The TCPA's reassigned number liability rule means a caller can be liable even if they had consent from the previous holder of that number.

The FCC's Reassigned Numbers Database (RND) went live in 2021 and provides a safe harbor if you check numbers against it before dialing ^[8]. Collectors using predictive dialers should scrub their lists against the RND on a regular cycle. The database charges per query; the exact rate is set by the FCC-designated database administrator, and you can find current pricing at the RND portal. Running a monthly scrub on active accounts is a reasonable floor. For high-volume operations, weekly is better.

The FDCPA adds its own restrictions on top of the TCPA: no calls before 8 a.m. or after 9 p.m. local time, no calls to a workplace if the collector knows the employer prohibits such calls, and mandatory cease-communication compliance ^[7]. Predictive dialers should be configured with time-zone-aware calling windows that respect both the TCPA's hours guidance and the FDCPA's hard limits.

What are the penalties for predictive dialer TCPA violations?

The TCPA provides for $500 per violation for negligent violations and up to $1,500 per violation for willful or knowing violations ^[1]. Each call or text is a separate violation. In a class action, even a modest campaign can generate eight-figure exposure.

A few real outcomes show the range. In 2015, Capital One and a group of affiliated debt collectors settled a TCPA class action for $75.5 million, one of the largest TCPA settlements at the time, relating to predictive dialer calls to reassigned cell phone numbers. Dish Network paid $280 million in 2017 to settle FTC and state AG claims involving telemarketing practices, including autodialer violations (though that case involved multiple statutes). Individual plaintiff claims regularly settle for $500 to $2,000 per affected consumer, which sounds modest until you multiply by a list of 100,000 numbers.

The FCC can also issue its own forfeitures. Under 47 U.S.C. § 503(b), the FCC can impose fines up to $23,278 per violation per day, adjusted for inflation ^[9]. FCC enforcement tends to target carriers and large-scale operations, but small businesses are not exempt.

Willfulness is the multiplier to watch. If you knew the rules and called anyway, or if you continued calling after receiving cease-and-desist letters, courts routinely find willfulness and apply the $1,500 rate. Document your compliance program. Written policies, training records, and scrubbing logs are your evidence that violations were not willful if litigation comes.

What DNC and scrubbing requirements apply to predictive dialer campaigns?

The National Do Not Call Registry, administered by the FTC under the Telemarketing Sales Rule (16 C.F.R. Part 310) and incorporated into TCPA enforcement, prohibits telemarketing calls to registered numbers without an established business relationship or prior written consent ^[10]. Companies that make more than 1,250 telemarketing calls per year must register with the registry and scrub their lists.

Scrubbing frequency matters. The FTC's rule requires scrubbing against the registry no more than 31 days before a call. In practice, most compliance teams run a scrub before every new campaign and at least monthly for ongoing campaigns. The registry does not cover debt collection calls, which fall outside the TSR's telemarketing definition, but state DNC laws may cover them.

Beyond the federal registry, you need an internal DNC list. Any consumer who asks not to be called must be added to your company-specific DNC list within a reasonable time, and the TCPA regulations require honoring those requests for at least 5 years ^[5]. Your predictive dialer should pull from this internal list at launch time, more than at upload time, so a request that comes in during a campaign is honored in real time.

State DNC lists add another layer. Florida, Texas, Indiana, and several other states maintain their own lists separate from the federal registry. If you are running multi-state campaigns, your scrubbing process needs to hit state lists too. For a full look at how TCPA compliance and DNC rules interact at the state level, the variation is significant enough that a state-by-state check is worth doing before you launch.

One more thing people overlook: wireless numbers on the federal DNC registry. Wireless numbers can be registered, and the FTC scrub should catch them. But wireless numbers also have independent TCPA protections even if not on the registry, so scrubbing the DNC list does not substitute for consent verification on cell phones.

How do you build a compliant predictive dialer program from scratch?

Start with your list. Every number on it should have a documented consent chain: where the number came from, when consent was obtained, what disclosures were given, and which entity received consent. If you bought leads, get the consent documentation from the seller before you dial one number. Undocumented consent is no consent in litigation.

Scrub before every campaign. Run the list against the National DNC Registry (scrub no older than 31 days), your internal DNC list, applicable state DNC lists, the FCC Reassigned Numbers Database, and the TCPA Litigator List (a commercially maintained list of serial TCPA plaintiffs who actively seek to generate cases). The last one is not legally required but is practically smart.

Configure your dialer settings before launch:

• Set the abandon rate target at or below 1.5%
• Set calling hours to 8 a.m. to 9 p.m. local time for the called party (not your time zone)
• Load the required abandoned call message with your company name and callback number
• Enable real-time DNC flagging so agents can suppress numbers during the call

Train your agents on consent revocation. When a consumer says "stop calling me," that is a revocation. The agent must log it immediately, and the dialer must suppress that number from the next pull. A verbal request is legally sufficient; you cannot require a written request.

Audit quarterly. Pull a sample of 200 to 500 calls from the past 90 days and check whether every called cell phone had valid written consent documented at call time. If you find gaps, fix the process, retrain the team, and document the correction. That paper trail is what separates a manageable compliance issue from a willful violation if the FTC or a plaintiff attorney comes knocking.

LeadCompliant's compliance kit includes a predictive dialer scrubbing checklist and a consent documentation template if you want a starting framework rather than building one from scratch.

For teams that also send follow-up texts after dialer calls, the same consent standards apply to SMS. The rules for SMS opt-in are worth reviewing alongside your voice consent process, since a single form can capture both.

Are there any safe harbors or exceptions for predictive dialer calls?

A few narrow exceptions exist, and people frequently overclaim them.

The established business relationship (EBR) exception once provided broad cover. The FCC eliminated the EBR exception for wireless numbers in 2012 ^[5]. It no longer matters that someone bought from you before; if you are calling their cell phone with an autodialer, you need fresh written consent for telemarketing calls. The EBR still matters for the National DNC Registry (a purchase or inquiry within 18 months creates an EBR that lets you call a DNC-listed residential landline), but do not confuse that with cell phone consent.

The one-time confirmation message exception allows a single informational text to a number that a person provided, confirming that the person wants to receive further messages. This is a narrow pathway for SMS, not a general license for calling campaigns.

The emergency calls exception under 47 U.S.C. § 227(b)(1)(A) exempts calls "made for emergency purposes." Courts read this extremely narrowly. Your marketing call is not an emergency.

The manually dialed call exception is real and often misunderstood. If a human agent physically dials each number with no autodialer involved, the TCPA's ATDS provisions do not apply to that call. Some teams use this for high-value prospects, manually dialing a small list while using a predictive dialer for the broader campaign. Keep those two populations strictly separated in your records.

For collections specifically, the prior express consent that comes with account origination is the main exception, as discussed above. But that consent does not survive number reassignment, and the consent may be limited to the purpose originally communicated. If a consumer gave a cell phone number to apply for a credit card, that consent to contact about the account does not automatically become consent to contact about a different account or for cross-sell purposes.

How do state laws add requirements beyond the federal TCPA for predictive dialers?

The TCPA sets a floor. States can and do go higher.

Florida's Telephone Solicitation Act (FTSA), amended in 2021, added a private right of action for autodialer calls and texts made without prior express written consent, with $500 per call damages. Florida also banned calls made with an automated system that selects or dials numbers, which is broad enough to capture most predictive dialers regardless of number generation method ^[4].

California does not have a standalone predictive dialer statute, but the California Consumer Privacy Act (CCPA) affects how you handle the personal data driving your dialer campaigns. If a consumer opts out of the sale of their personal information, that affects whether a lead vendor can share their data with you for dialing purposes.

Washington state's automatic dialing and announcing device (ADAD) statute predates the TCPA and covers both commercial and non-commercial calls. Texas, Pennsylvania, and North Carolina all have state DNC lists and telemarketing registration requirements that interact with dialer campaigns.

Here is the practical rule. If you call into more than five states, you need a state-by-state review before launch. The variation is real enough that a campaign legal in one state can generate liability in another. This is not a scare tactic. It is just how the patchwork is built. The lead generation compliance news page tracks state legislative activity that affects dialer campaigns as new bills move.

What should you do if you receive a TCPA demand letter about predictive dialer calls?

Stop calling the number in question immediately. Add it to your internal DNC list. Do not destroy or alter any records related to the call.

Then gather the call record: the timestamp, the number dialed, the agent who handled or attempted the call, the consent documentation in your system at the time of the call, and the scrub logs showing the number was checked before the campaign launched. That package is the starting point for any legal defense.

Do not ignore the letter. TCPA demand letters are often the first step in a shakedown by serial litigants who identify themselves by filing cases or sending pre-suit demands. That does not mean the demand is invalid. Ignoring it tends to escalate to a lawsuit, where your legal costs start at $15,000 to $30,000 just to answer the complaint and file initial motions.

Engage a TCPA-experienced attorney before responding. A response that admits you used an autodialer or that hints you lacked consent can be used against you. An attorney can evaluate whether you have a viable ATDS defense under Facebook v. Duguid, whether the consent chain holds, or whether the plaintiff's own conduct (giving a false number, for example) provides a defense.

Small sums settle quickly. Many pre-suit demands for single-plaintiff claims resolve in the $1,000 to $5,000 range when you have defensible consent documentation and can show the violation was isolated. Class actions are a different category and require separate strategic analysis.

This article is legal information, not legal advice. For any specific demand or litigation, talk to a licensed attorney with TCPA experience.

How do predictive dialer compliance rules apply to B2B calling?

The TCPA explicitly exempts calls to business numbers from the do-not-call provisions that apply to residential lines ^[1]. Calls to a business's main line for a business purpose are generally outside the TCPA's DNC reach.

But the cell phone protection under the TCPA does not depend on whether the number belongs to a business or a consumer. If you are calling a number that is a cellular number, even if the person uses it for business, the ATDS and consent provisions still apply. This catches a lot of B2B teams off guard. A salesperson's cell phone is still a cell phone.

The practical rule for B2B predictive dialer campaigns: calling a company's landline main number or a direct-dial landline office number with a predictive dialer is generally lower TCPA risk. Calling a mobile number associated with a business contact still requires consent analysis or a reliable manual-dial process.

For teams running B2B campaigns that include lead gen and data platforms, the b2b lead generation platforms gdpr compliance page covers how European data obligations interact when your list includes EU-based contacts, which adds another compliance dimension beyond TCPA.

The FDCPA does not apply to B2B debt collection (it covers consumer debts), but commercial debt collectors using predictive dialers still face TCPA cell phone exposure if they are reaching mobile numbers.

How do you document consent for predictive dialer calls in a way that holds up in court?

Courts have been clear that the burden of proof for consent falls on the caller. "The party claiming prior express consent bears the burden of proving it," per the FCC's 2012 rules commentary, and case law consistently places that burden on the defendant in TCPA litigation ^[5].

What holds up:

A timestamped web form submission, with the IP address, the exact disclosure text shown at time of submission, and the phone number entered. The form should store a hash or screenshot of the page as it looked when the person submitted, because plaintiffs' attorneys will argue your current form is different from the one the consumer saw.

A recorded verbal consent, with the date, time, agent ID, and exact script read to the consumer. This is harder to fake and holds up well, but it requires a storage and retrieval system that links the recording to the specific phone number in your dialer.

A signed paper form, scanned and attached to the contact record. Rare in modern operations but solid evidence.

What does not hold up:

A general statement in your terms of service that the consumer "may be contacted by telephone." Courts have rejected this as insufficient for TCPA written consent because it does not identify the specific autodialer technology or specific seller.

A lead seller's representation that consent was obtained, with no underlying documentation. If you cannot produce the original record, you do not have consent.

A record that shows consent was obtained but not for the specific number you dialed. If the consumer consented using their home number and you called their cell, that is a new consent requirement.

Store consent records for at least 4 years. The TCPA's statute of limitations is 4 years under 28 U.S.C. § 1658, and some states have longer windows. Build your CRM to attach consent evidence to each contact record and export it in litigation-ready format. If you cannot pull a consent record for a specific number in under 10 minutes, your documentation system is not production-ready. LeadCompliant's TCPA compliance tools include a consent audit log template designed for exactly this use case.

Frequently asked questions

Does Facebook v. Duguid mean predictive dialers are no longer regulated under the TCPA?

No. Facebook v. Duguid (2021) narrowed the ATDS definition to systems that use a random or sequential number generator, but many predictive dialers still qualify if they generate numbers or randomize any part of the dial sequence. Beyond ATDS classification, the TCPA's prerecorded voice prohibition and abandoned call rules still apply. State laws like Florida's FTSA use broader definitions that capture list-based predictive dialers regardless of the Supreme Court ruling.

Can a predictive dialer call a cell phone without consent for non-telemarketing purposes?

For informational (non-telemarketing) calls, the TCPA requires only prior express consent, which can be oral or written. For telemarketing, you need prior express written consent. The distinction matters: a bank calling about a potential fraud alert needs prior express consent; the same bank calling to sell a new credit card product needs written consent. Documenting which type of call you are making is part of a defensible compliance program.

What is the maximum allowed abandoned call rate under FCC rules?

The FCC caps the abandoned call rate at 2% of all calls answered by a live person per campaign per 30-day period. When a call is abandoned, you must play a prerecorded identification message within 2 seconds of the consumer answering. Setting your dialer's pacing algorithm to target 1.5% gives you a half-percent buffer against the ceiling.

Do debt collectors need TCPA consent to use a predictive dialer on cell phones?

Yes. The FDCPA governs collector conduct, but the TCPA governs the technology. Calling a cell phone with a predictive dialer for debt collection still requires prior express consent under the TCPA. Consent is typically established when the consumer provides their cell number at account origination. That consent does not survive number reassignment to a new person, which is why scrubbing against the FCC Reassigned Numbers Database is important for collection operations.

How often do I need to scrub my list against the National DNC Registry?

The FTC's Telemarketing Sales Rule requires that a scrub occur no more than 31 days before the call. For active ongoing campaigns, running a fresh scrub monthly is the practical minimum. High-volume operations often scrub weekly. You also need to maintain and check your internal company-specific DNC list, which must be updated within a reasonable time of any opt-out request and honored for at least 5 years.

Can a consumer revoke consent to be called by a predictive dialer verbally?

Yes. The FCC has confirmed that consent can be revoked by any reasonable means at any time. A verbal request during a call is legally sufficient revocation. You cannot require a written revocation request. When a consumer says stop calling, the agent must log the request immediately, and your system must suppress that number from future dialing. Failure to honor verbal revocations is a common source of willful violation findings.

What is the TCPA statute of limitations for predictive dialer call claims?

The federal statute of limitations under 28 U.S.C. § 1658 is 4 years from the date of the violation. Some states have longer limitation periods for state law TCPA analog claims. This means you need to retain consent records, scrub logs, and call records for at least 4 years, and ideally longer if you operate in states with extended windows.

Does the TCPA apply to B2B predictive dialer campaigns?

The TCPA's do-not-call rules generally exempt business-to-business calls to business lines. But the ATDS prohibition on calling cellular numbers applies regardless of whether the number is used for business. If your B2B campaign dials mobile numbers, you still need consent analysis. Calling a company's landline main number is lower risk; calling a salesperson's personal cell phone for business purposes still triggers TCPA cell phone protections.

What does 'prior express written consent' actually need to include?

Under FCC rules, a prior express written consent agreement must: (1) be a written, signed agreement; (2) clearly authorize calls or texts using an ATDS or prerecorded voice; (3) identify the specific seller or company making the calls; (4) include the telephone number to be called; and (5) disclose clearly that the consumer is not required to agree as a condition of any purchase. Electronic signatures satisfy the writing requirement.

What is the FCC Reassigned Numbers Database and do I have to use it?

The FCC Reassigned Numbers Database (RND), operational since 2021, lets callers check whether a number has been reassigned to a new subscriber since consent was obtained. Using it is not legally mandatory, but it creates a safe harbor: if you check the database before calling and the number shows no reassignment, you have a defense against TCPA liability if the number was later reassigned. For debt collectors and any caller working with older lists, the RND scrub is worth the per-query cost.

How does Florida's FTSA affect predictive dialer campaigns differently from the federal TCPA?

Florida's Telephone Solicitation Act (FTSA), amended in 2021, bans automated calls and texts made without prior express written consent and creates a private right of action with $500 per-call damages. The FTSA's definition of automated system is broader than the TCPA's post-Facebook v. Duguid definition and can capture list-based predictive dialers. Florida also has its own state DNC list. Multi-state campaigns that include Florida numbers need separate FTSA analysis.

What records should I keep to defend a predictive dialer TCPA lawsuit?

Keep: the consent record for each cell phone number dialed (timestamped, with disclosure text), DNC scrub logs showing the number was checked before the campaign, the dialer configuration at the time of the call (abandon rate settings, calling hours), agent training records, and your internal DNC list with opt-out timestamps. Retain all of these for at least 4 years. If you cannot pull all of this for a single number within 10 minutes, your documentation system needs improvement.

Are there criminal penalties for TCPA predictive dialer violations?

The TCPA itself is a civil statute; it does not create criminal liability directly. However, large-scale violations involving fraud, wire fraud, or violations of FTC orders can trigger criminal exposure under other statutes. The FCC can issue civil forfeitures up to $23,278 per violation per day under 47 U.S.C. § 503(b). State attorneys general can also pursue injunctions and civil penalties under state telemarketing laws, some of which carry criminal misdemeanor provisions for willful violators.

Can I use a predictive dialer for political calls or surveys?

Political calls to cell phones using an ATDS still require prior express consent under the TCPA; the political exemption applies only to manually dialed calls. Survey calls fall in a gray area: purely non-commercial surveys may not be telemarketing, but courts have found liability when surveys include any promotional element. If your survey includes anything that could be read as marketing, treat it as telemarketing and get written consent before autodialing cell phones.

Sources

1. U.S. Code, 47 U.S.C. § 227, Telephone Consumer Protection Act: ATDS definition, $500/$1,500 per-violation damages, and core TCPA prohibitions
2. U.S. Supreme Court, Facebook, Inc. v. Duguid, 592 U.S. 395 (2021): ATDS must use random or sequential number generator; dialing from a stored list alone does not qualify
3. Florida Legislature, Florida Telephone Solicitation Act, Fla. Stat. § 501.059: Florida FTSA 2021 amendment, private right of action, $500 per-call damages, broader automated system definition
4. U.S. Code, 15 U.S.C. § 1692 et seq., Fair Debt Collection Practices Act: FDCPA calling hour restrictions (8am-9pm), cease-communication requirements, and workplace call prohibition
5. U.S. Code, 47 U.S.C. § 503(b), FCC forfeiture authority: FCC civil forfeiture authority up to $23,278 per violation per day (inflation-adjusted)
6. FTC, Telemarketing Sales Rule, 16 C.F.R. Part 310: National DNC Registry requirements, 31-day scrub window, registration threshold of 1,250 calls per year
7. FTC, National Do Not Call Registry, Information for Businesses: DNC Registry operation, registration requirements, and exemptions including established business relationship
8. U.S. Code, 28 U.S.C. § 1658, Federal statute of limitations: Four-year statute of limitations for federal civil claims including TCPA