Last updated 2026-07-10
TL;DR
You can legally run a predictive dialer, but only with prior express written consent from every cell number you dial, DNC scrubbing every 31 days, and proof your system either falls outside the TCPA autodialer definition or is covered by consent. Miss any step and each call costs $500 to $1,500 in statutory damages.
What is a predictive dialer and why does the TCPA care?
A predictive dialer is software that calls many numbers at once and uses an algorithm to predict when an agent will be free, then connects the next answered call to that agent. When a call lands and no agent is available, the system hangs up, delays, or plays a recorded message. That last part, the recorded message or the silent dead-air pause, is what draws federal attention.
The Telephone Consumer Protection Act of 1991, codified at 47 U.S.C. § 227, restricts any call made with an automatic telephone dialing system (ATDS) or a prerecorded voice to cell phones without prior express consent [1]. The statute defines an ATDS as equipment that has the capacity "to store or produce telephone numbers to be called, using a random or sequential number generator" and to dial those numbers [1]. That reads narrow. Thirty years of litigation and FCC rulemaking have pulled it in both directions.
Predictive dialers sit in a gray zone. A pure predictive dialer works from a defined list, not a random or sequential generator, so some courts have found it falls outside the ATDS definition. Others have not. And if your dialer plays any prerecorded or artificial-voice message, the prerecorded-voice prong of 47 U.S.C. § 227(b)(1)(A) applies no matter how the dialer picks numbers [1]. For that whole category of calls, the ATDS debate stops mattering.
What did the Supreme Court say about ATDS and predictive dialers?
In Facebook, Inc. v. Duguid (2021), the Supreme Court ended a circuit split and read the ATDS definition narrowly [2]. The Court held that a device must use a random or sequential number generator to store or produce numbers before it counts as an ATDS. A system that only dials from a stored list of specific, pre-set numbers is not an ATDS under that reading.
That was real good news for predictive dialer users. Most commercial predictive dialers pull from a CRM list of specific contacts, not a random or sequential generator. Under Duguid, those systems are not ATDSs. Three caveats matter, though.
First, the ruling touches the ATDS prong only. If your dialer plays a recorded message when an agent is not available, the prerecorded-voice prong still covers you, and Duguid does nothing there [1]. Second, state mini-TCPA laws in Florida, Oklahoma, Washington, and other states sometimes use broader autodialer definitions that Duguid does not preempt [3]. Third, if your vendor's system stores numbers and adds any randomization step to how it sequences them, the dialer could still qualify as an ATDS in some courts. Read your vendor contract. Ask the vendor directly, in writing.
What consent do you actually need to legally call cell phones with a predictive dialer?
This is where most small outbound teams get it wrong. The consent tier depends on the type of call.
For telemarketing or advertising calls to cell phones, 47 U.S.C. § 227(b) requires prior express written consent [1]. The FCC's 2012 TCPA rules define written consent as a signed agreement (an electronic signature counts) that clearly authorizes a specific seller to deliver autodialed or prerecorded calls, and that discloses the person is not required to consent as a condition of buying anything [4]. A checked opt-in box on a web form qualifies if the disclosure language is clear and the form logs a timestamp and IP address.
For non-commercial informational calls to cell phones, prior express consent (not necessarily written) may be enough. But almost no outbound sales or marketing call is purely informational, so treat written consent as your default.
Landlines get different treatment. The prerecorded-voice restriction applies to residential landlines for telemarketing [1], while ATDS calling to landlines is less restricted. Here is the practical rule for outbound sales teams: assume every number is a cell phone unless you hold carrier-grade line-type data proving otherwise. Misclassifying a cell as a landline and calling it without consent is a $500 to $1,500 per-call mistake.
Consent has to be specific to your company. A 2023 FCC declaratory ruling held that consent obtained through a comparison-shopping website that then sold leads to many marketers does not count as valid one-to-one consent for each of those marketers [5]. The Eleventh Circuit vacated and remanded that ruling in January 2025 on administrative-procedure grounds [5], but the FCC is expected to re-propose it. Teams relying on shared-consent lead sources should start rebuilding their consent records now.
What are the National DNC Registry rules for predictive dialer calls?
The National Do Not Call Registry is separate from the ATDS consent question, and you comply with both. Any telemarketer calling residential numbers must scrub against the Registry at least every 31 days [6]. The FTC enforces this under the Telemarketing Sales Rule; the FCC enforces a parallel version under the TCPA. Calling a number on the DNC list can cost up to $51,744 per violation under current FTC penalty levels [6].
For predictive dialer work specifically, scrub your call list against the Registry before every campaign upload, not once at the start of the month. If a prospect calls and asks to go on your internal DNC list, you have 30 days to honor that request and must keep the record at least 5 years [6].
See TCPA guidelines: what every outbound team must know in 2025 for a full breakdown of scrub timing and internal DNC maintenance.
B2B calls to business numbers that are not residential lines get more DNC flexibility, but the lines blur when you call a cell phone a business owner also uses personally. The TCPA b2b exemption for AI calls: what businesses actually get article covers that case.
What does a TCPA violation with a predictive dialer actually cost?
The statute sets damages at $500 per negligent violation and $1,500 per willful or knowing violation [1]. No per-day cap. Every single call counts on its own. A campaign that sends 50,000 calls to cell numbers without valid consent is $25 million to $75 million in exposure before attorney fees, and these cases draw plaintiff's attorneys because they are class-action friendly.
Real settlements show the range. UnitedHealthcare paid $2.5 million over alleged TCPA violations tied to automated calls [see unitedhealthcare-to-pay-2-5m-for-alleged-tcpa-violations]. Truist Bank settled a TCPA class action as well [see truist-bank-tcpa-class-action-settlement]. These are big companies with legal departments, and they still paid to settle. Small teams have fewer resources to fight, and per-call exposure can top their entire annual revenue.
Willfulness matters. A lot. If your team got a cease-and-desist letter, had a prior settlement, or has internal emails showing someone knew a list lacked valid consent, courts and plaintiffs push for the $1,500 treble amount. Document your compliance reviews in writing. That paper trail is your best defense.
How do you set up a predictive dialer operation that passes a TCPA audit?
There is no magic certification. A defensible operation has these pieces in place before the first call goes out.
Consent collection and storage. Every cell number in your dialer needs a timestamped, stored record of prior express written consent that names your company. Your web forms or third-party lead vendors must capture the date and time of consent, the URL or source of the form, the disclosure language shown to the user, and the specific company name authorized to call. Keep these records at least 4 to 5 years, because the TCPA statute of limitations is 4 years under 28 U.S.C. § 1658 [12].
DNC scrubbing on a 31-day cycle. Subscribe to the National DNC Registry through the FTC's Telemarketing Sales Rule process, export your list, scrub before every upload, and log the scrub date [6].
Line-type validation. Run every number through a carrier-grade lookup to split cell phones from landlines before dialing. This also flags reassigned numbers, which is the next step.
Reassigned number scrubbing. The FCC launched a Reassigned Numbers Database in 2021 [7]. If someone consented and then gave up their number, the new subscriber never agreed to anything. Calling that new subscriber is a violation. Query the database before each campaign.
Abandoned call rate. The FCC caps predictive dialer abandoned call rates at 3% of answered calls per campaign [4]. When a call is abandoned (connected with no agent available), the dialer must play an automated message with the company name and a callback number within 2 seconds of the person's greeting, and must not call that number again within 24 hours.
Agent-to-line ratio. There is no statutory maximum, but the 3% abandoned-call rule forces a practical ceiling. Most compliant operations run no more than 2.5 to 3 lines per agent.
LeadCompliant's free TCPA compliance kit has a pre-campaign checklist covering every step above, and you can use it without touching a paid feature.
See TCPA 2025: what changed, what it costs, and how to stay compliant for recent rule updates to layer on top of this framework.
Does the existing business relationship exemption let you skip consent for predictive dialer calls?
This is a common misconception, and it costs companies real money. There is an established business relationship (EBR) exemption. It is narrower than most sales managers assume.
For DNC Registry purposes, the EBR lets you call someone who bought from you in the past 18 months, or inquired in the past 3 months, even if they sit on the DNC list [6]. It does not override the TCPA consent requirement for autodialed or prerecorded calls to cell phones. These are two separate rule systems.
So an existing customer on the DNC list who bought from you last year: yes, you can call their landline about related products under the EBR. Call their cell phone with an autodialer or prerecorded message without their prior express written consent? Still a TCPA violation, EBR or not.
Read TCPA existing business relationship: what actually protects you for the full breakdown with case citations.
Are there predictive dialer compliance rules specific to state laws?
Yes, and they run stricter than the federal floor. The TCPA is a floor, not a ceiling. States can pile on restrictions, and several have.
Florida's Mini-TCPA (Florida Statute § 501.059, amended in 2021) covers calls made using an automated system for the selection or dialing of telephone numbers, a broader definition than the post-Duguid federal ATDS standard [3]. Florida does not require a random or sequential number generator. If your predictive dialer automates the selection of numbers, Florida regulates it. Florida also bans automated calls to any Florida number without prior express written consent, with a private right of action at $500 per call.
Oklahoma, Washington, and Maryland have their own expanded autodialer rules. If any of your outbound calls touch those states, your program needs a state-law overlay.
For the current state-law picture, TCPA news and Telemarketing rules news: what changed and what's coming in 2025-2026 both track legislative changes.
The safest operational posture: treat every call as if your strictest-state law applies to all of them. You lose a little coverage. You cut a lot of legal exposure.
What happens when someone revokes consent and you keep calling them?
Revocation must be honored promptly. The FCC's 2024 consent revocation order, effective January 27, 2025, requires callers to honor revocation requests within 10 business days [8]. A consumer can revoke through any reasonable means, including orally on a call, by text reply, or by email. You cannot contractually limit revocation to a single method.
For predictive dialer teams, this means your agents need a clear in-call opt-out capture process. When someone says stop calling me, that has to trigger an immediate suppression workflow that adds the number to your internal DNC list before the next dialing session. If your dialer pulls refreshed lists from your CRM overnight, CRM suppression must finish before that upload runs.
Calling someone who has revoked consent is almost always treated as a willful violation, which drops you into $1,500-per-call territory. See how to stop robocalls for how consumers document and report these calls, which feeds straight into TCPA litigation.
What should you ask a predictive dialer vendor before you sign?
Your vendor contract can shift some liability. Not all of it. Here are the questions that actually matter.
Does your system qualify as an ATDS under post-Duguid standards, and do you have a legal opinion on file? A reputable vendor can answer this.
Does the system integrate with the FCC Reassigned Numbers Database, and how often does it query? If not natively, what API do you expose for our own scrubbing?
What is the maximum abandoned call rate the system can enforce, and can we set a campaign-level cap at 3%? The FCC requires it, and you want it enforced in software, more than in a policy document.
Does the platform log consent records at the number level, or do we bring our own consent database? If we bring our own, how does the system link each dialed number to its consent record?
What indemnification do you offer if the system misdials or skips a suppression list? Most SaaS vendors disclaim all liability and hand the calling list back to you as your problem. Read the liability section of any vendor MSA closely.
If you are comparing vendors and want a structured checklist to hand them, LeadCompliant's compliance kit has a vendor vetting worksheet.
How does the 3% abandoned call rule work in practice?
The FCC's 2003 TCPA rulemaking (FCC 03-153) set the abandoned call rule: no more than 3% of calls answered by a live person may be abandoned during a single calling campaign, measured over any 30-day period [4]. An abandoned call is one where the system connects to a live human but no agent is available within 2 seconds.
Most predictive dialer software lets you set a target abandon rate in the settings. Set it at 2.5% to give yourself headroom. If volume spikes or agent attendance drops mid-session, the abandon rate climbs fast. The system should throttle dialing automatically when it nears the cap.
When a call is abandoned, the FCC requires the dialer to play a recorded message that includes the seller's name and phone number and states the call was for telemarketing. The company also cannot call that number again within 24 hours using an autodial system.
| Abandoned call requirement | Spec |
|---|---|
| Maximum abandoned rate | 3% of answered calls per campaign per 30 days |
| Time to connect agent | Within 2 seconds of person's greeting |
| Required message if abandoned | Company name, callback number, telemarketing disclosure |
| Cooldown after abandonment | No autodialed call to that number for 24 hours |
| Allowed calling hours | Between 8 a.m. and 9 p.m. caller's local time |
What compliance records should you keep, and for how long?
Documentation is your entire defense. When a plaintiff files a TCPA suit, the first thing their lawyer requests is your consent records for the numbers in the complaint. If you cannot produce them, you lose the motion and likely settle.
Keep these records at minimum.
Consent records: the signed or electronically submitted consent form with timestamp, IP address, source URL, and the disclosure text shown. Retain 5 years from the consent date, or 4 years past the last call, whichever is longer. The 4-year TCPA statute of limitations under 28 U.S.C. § 1658 is your floor [12].
DNC scrub logs: a record of every scrub run, which list version was used, and the date. Retain 5 years [6].
Internal DNC list: every opt-out request with date received and date suppressed. Retain 5 years.
Campaign-level abandoned call rate reports: monthly summaries showing your rate stayed under 3%. Retain 2 to 3 years.
Reassigned Numbers Database query logs: date and result for each number queried. Retain for the length of any active consent relationship plus 4 years.
If your dialer vendor stores these for you, get it in writing that they preserve them at least 5 years and that you own the data and can export it. Vendor shutdowns happen, and they take your records with them if the contract stays silent.
Frequently asked questions
Is a predictive dialer the same as a robocaller under the TCPA?
Not automatically. A predictive dialer that connects a live agent is not a robocaller in the common sense. But if your predictive dialer plays a prerecorded message when no agent is available, that call is subject to the TCPA's prerecorded-voice restrictions for cell phones, whether or not the dialing system qualifies as an ATDS. The prerecorded-voice prong is independent of the ATDS definition.
Does the Facebook v. Duguid ruling mean predictive dialers are now TCPA-free?
No. Duguid narrowed the ATDS definition to systems using a random or sequential number generator, which helps many list-based predictive dialers dodge the ATDS prong. But the prerecorded-voice restriction still applies on its own, state mini-TCPA laws often use broader definitions, and the 3% abandoned call rule and DNC requirements still apply. Duguid removed one risk, not all of them.
Can I call cell phones with a predictive dialer if I have a business relationship with the customer?
An existing business relationship gives you limited DNC Registry protection, not TCPA consent protection for autodialed or prerecorded calls to cell phones. You still need prior express written consent for each cell number you dial with an autodialer or prerecorded voice, regardless of the business relationship. Many companies confuse the EBR exemption with consent and land in litigation over it.
What is the statute of limitations for a TCPA lawsuit over predictive dialer calls?
Four years, under 28 U.S.C. § 1658, the general federal catch-all limitations period. Courts have consistently applied it to TCPA claims. Some state mini-TCPA laws set their own periods, shorter or longer. A call you made three and a half years ago can still generate a valid claim today, which is why long-term record retention matters.
Do I need consent to call landlines with a predictive dialer?
For telemarketing calls with a prerecorded voice to residential landlines, yes, prior express written consent is required under the FCC's 2012 rules. For live-agent calls to residential landlines, DNC Registry compliance is the main obligation, not prior express consent for the autodialed call itself. Business landlines have more flexibility. When in doubt, treat any number you cannot confirm as residential as requiring consent.
How often do I have to scrub my dialer list against the National DNC Registry?
At least every 31 days. The FTC's Telemarketing Sales Rule requires your calling list to be scrubbed against the most current version of the Registry no more than 31 days before any call. In practice, scrub on every upload. Lists go stale fast, and a number that was clean three weeks ago may have registered since.
What happens if my predictive dialer calls a reassigned number whose previous owner gave consent?
You are liable for the call to the new subscriber, who never consented. The FCC's Reassigned Numbers Database exists for this problem. Courts have generally held that consent belongs to the person, not the number. The FCC provides a safe harbor if you query the database before calling and it showed no reassignment, but that safe harbor is limited. Query before every campaign, more than once.
Can I use a predictive dialer for debt collection calls under the TCPA?
Debt collection calls to cell phones with an autodialer or prerecorded voice still require prior express consent under the TCPA. A 2015 TCPA amendment temporarily created an exception for calls collecting debts owed to or guaranteed by the federal government, but the Supreme Court struck that down in Barr v. American Association of Political Consultants (2020). Debt collectors follow TCPA consent rules like any other caller.
What disclosure do I have to play if my predictive dialer abandons a call?
The FCC requires a recorded message stating the company's name, its telephone number (not a 900 number or toll charge), and that the call was made for telemarketing. That message must play within 2 seconds of the person's greeting. You also cannot call that number again with an autodialer within 24 hours of an abandoned call.
Do text messages sent from a predictive dialer platform face the same TCPA rules?
Yes. The FCC treats text messages as calls under the TCPA, so texting cell phones from an automated system requires prior express written consent for marketing messages, just like voice calls. The 3% abandoned call rule does not apply to texts, but consent, DNC scrubbing, and opt-out honoring all do. See the text message marketing guide for SMS-specific rules.
What is the safe call window for predictive dialer outbound calls?
The TCPA and FCC rules limit calls to 8 a.m. through 9 p.m. in the called party's local time zone, not yours. If you call from New York and your prospect is in Los Angeles, 7:30 a.m. New York time is 4:30 a.m. in Los Angeles, which is a violation. Your dialer should enforce time-zone limits at the number level using area code or carrier data.
Can a TCPA lawsuit from predictive dialer calls become a class action?
Yes, and this is the main financial threat. TCPA claims are among the most class-action-friendly in federal law because the statutory damage is the same for every class member and the violations often look identical across thousands of calls. Settlements in large predictive dialer cases run into tens of millions of dollars. Companies like Credit One and Truist have faced exactly this kind of class exposure.
What does the FCC's 2024 consent revocation rule change for predictive dialer teams?
The FCC's 2024 order, effective January 27, 2025, requires callers to honor consent revocations within 10 business days through any reasonable means the consumer chooses. You cannot contractually restrict revocation to a single method like an email form. For dialer teams, agent scripts must capture verbal opt-outs in real time, and suppression must run before the next campaign upload.
Is there a way to use a predictive dialer for cold outreach without getting prior consent first?
For cell phones, no, not legally for marketing calls. If your dialer qualifies as an ATDS or uses prerecorded messages, every cold call to a cell number without consent is a TCPA violation. The one realistic exception is calls to business landlines in a true B2B context, and even there DNC rules apply. For cold outreach to cells, collect consent first through inbound opt-in campaigns or third-party leads with verified, one-to-one consent.
Sources
- U.S. Code, 47 U.S.C. § 227, Telephone Consumer Protection Act: TCPA statutory text defining ATDS, $500/$1,500 per-violation damages, and restrictions on autodialed and prerecorded calls to cell phones
- U.S. Supreme Court, Facebook Inc. v. Duguid, 592 U.S. 395 (2021): Supreme Court held an ATDS must use a random or sequential number generator to store or produce numbers; list-based dialers may not qualify
- Florida Legislature, Florida Statute § 501.059: Florida Mini-TCPA uses broader definition of automated system for selection or dialing of numbers, not requiring random or sequential number generator
- FTC, Telemarketing Sales Rule, 16 CFR Part 310: National DNC Registry scrub required every 31 days; EBR exemption periods (18 months/3 months); internal DNC retention 5 years; penalty up to $51,744 per violation
- FCC, Reassigned Numbers Database: FCC launched Reassigned Numbers Database in 2021 to allow callers to verify whether a number has been reassigned since consent was given
- U.S. Supreme Court, Barr v. American Association of Political Consultants, 591 U.S. 610 (2020): Supreme Court struck down the government-debt exception to TCPA autodialer restrictions in 2020, restoring full TCPA obligations for debt collection calls
- FTC, National Do Not Call Registry: FTC National Do Not Call Registry data and enforcement context for DNC scale
- U.S. Code, 28 U.S.C. § 1658, Statute of Limitations: Four-year general federal statute of limitations applied by courts to TCPA claims