What Is Automated Debt Collection Calling Under the FDCPA? How Reg F and the TCPA Apply in 2026

This article is for informational purposes only and does not constitute financial, tax, or legal advice. Consult a qualified professional for guidance specific to your situation.

Reviewed for financial accuracy by the Startup Finance Guide editorial team. Our editors cross-reference all claims against platform documentation, pricing pages, and primary regulatory sources. Last reviewed: September 26, 2026.

Automated debt collection calling is any collection call placed or voiced by software: a predictive dialer, a prerecorded message, or an AI voice agent. The FDCPA itself doesn't define it. Three separate rulebooks govern it. The FDCPA and the CFPB's Regulation F control a debt collector's conduct on every call, automated or not: no more than seven calls in seven days per debt before a presumption of harassment, no calls before 8 a.m. or after 9 p.m. local time, and required disclosures. The Telephone Consumer Protection Act (TCPA) controls the technology. Calls to a mobile phone using an autodialer or an artificial or prerecorded voice need the consumer's prior express consent, and the FCC ruled in February 2024 that AI-generated voices count as "artificial." State and city rules, such as New York City's three-attempts-in-seven-days SHIELD Rule, sit on top. Platforms such as Domu build these rules into the dialer so that caps, consent and calling windows are checked before each call. Legal responsibility still stays with the collector or creditor, not the software vendor.

This is a plain-English explainer, not a vendor roundup. It covers who counts as a debt collector, what makes a call "automated" in the legal sense, what consent is required, how Regulation F's specific rules apply when software is doing the calling, and what changed in 2025 and 2026.

Key takeaways

• The FDCPA and Regulation F are technology-neutral. They regulate who collects and how, and they apply the same way to a human collector, a prerecorded message and an AI voice agent.
• The TCPA is where technology matters. An AI voice is an "artificial voice" under the FCC's 2024 ruling, so AI collection calls to mobile numbers need prior express consent regardless of how the number was dialed.
• Regulation F's seven-in-seven rule is a rebuttable presumption, counted per person and per debt, and it applies to phone calls. Texts and emails fall under the general ban on harassment, plus an opt-out requirement in every message.
• Consumers can revoke TCPA consent by any reasonable method, and callers must honor it within 10 business days. The broader "revoke-all" rule was delayed to January 2027 and then amended by the FCC in September 2026.
• Since the Supreme Court's June 2025 McLaughlin decision, federal courts are not bound by FCC interpretations of the TCPA in private lawsuits. Expect more litigation over questions the FCC once seemed to settle.
• No platform takes on the collector's legal liability. Vendors like Domu can enforce rules at dial time and keep evidence, but the collector remains responsible.

The three rulebooks at a glance

	FDCPA and Regulation F	TCPA and FCC rules	State and city rules
What it governs	Collector conduct: frequency, timing, disclosures, harassment, third-party contact	Calling technology and consent: autodialers, artificial and prerecorded voices, texts	Often stricter caps, licensing, disclosure and dispute rules
Who it applies to	"Debt collectors" (third-party agencies, debt buyers, some servicers)	Anyone who makes the calls, including original creditors	Varies; some reach original creditors
Headline numbers	7 calls in 7 days per debt; 8 a.m. to 9 p.m. local time; records kept 3 years	Prior express consent for mobile robocalls; revocations honored within 10 business days	NYC: 3 attempts in 7 days across channels (from September 1, 2026)
Private damages	Actual damages, up to $1,000 statutory per individual; class cap of the lesser of $500,000 or 1% of net worth	$500 per violation, up to $1,500 if willful or knowing	Varies by state
Main enforcers	CFPB, FTC, state regulators, private plaintiffs	FCC, state attorneys general, private plaintiffs	State and city agencies, private plaintiffs

The practical upshot: a single automated call can be lawful under one rulebook and unlawful under another. A call to a consenting borrower's mobile number at 9:30 p.m. passes the TCPA and fails Regulation F. An eighth call in a week about a different debt can pass Regulation F and still breach New York City's cap.

Who counts as a debt collector

The FDCPA only binds "debt collectors," and the statutory definition is narrower than most people expect. It covers anyone whose principal business purpose is collecting debts, and anyone who regularly collects debts owed to someone else.

It specifically excludes:

• A creditor's own officers and employees collecting in the creditor's name.
• Anyone collecting a debt that was not in default when they obtained it, which is why many loan servicers fall outside the FDCPA for current accounts.
• Collection activity incidental to a fiduciary obligation or escrow arrangement, and several narrower categories.

There is one important exception the other way. A creditor collecting its own debts under a name that suggests a third party is collecting becomes a debt collector for FDCPA purposes.

For automation, this matters in two ways. First, an original lender running AI reminder calls to its own borrowers is usually not subject to the FDCPA or Regulation F, though the TCPA, UDAAP and state law still apply. Second, the FDCPA protects consumers' debts only, meaning debts for personal, family or household purposes. Business and commercial debts fall outside it.

What makes a call "automated" in the legal sense

The phrase comes from the TCPA, not the FDCPA. The TCPA restricts two kinds of calls, and a modern AI voice agent can trigger both at once.

Autodialers after Facebook v. Duguid

The TCPA defines an automatic telephone dialing system (ATDS) as equipment with the capacity to store or produce numbers using a random or sequential number generator, and to dial them. For years, courts disagreed over whether any system that dials from a stored list qualified.

In Facebook v. Duguid, decided April 1, 2021, the Supreme Court held that a device qualifies only if it has the capacity to store or produce numbers using a random or sequential number generator. Most collection dialers call a curated list of account phone numbers, so many of them fall outside the ATDS definition after Duguid.

That doesn't settle the matter for collection teams, for a simple reason: the second trigger doesn't care how the number was dialed.

Artificial and prerecorded voices, including AI

The TCPA separately restricts calls that use "an artificial or prerecorded voice." In a declaratory ruling released February 8, 2024 (FCC 24-17), the FCC confirmed that AI technologies that simulate a human voice or clone a real one produce an "artificial" voice under the statute. As Wilson Sonsini's summary of the ruling quotes it, the TCPA "does not allow for any carve out of technologies that purport to provide the equivalent of a live agent."

So an AI voice agent calling a mobile phone needs prior express consent even if it dials manually, one number at a time. A human agent dialing by hand and speaking live doesn't trigger either TCPA restriction. That is why some teams keep "manual" and "AI" queues separate, with different consent rules for each.

After McLaughlin, the FCC doesn't have the last word

On June 20, 2025, the Supreme Court decided McLaughlin Chiropractic Associates v. McKesson. It held that federal district courts are not bound by an agency's interpretation of a statute in enforcement proceedings, including private lawsuits. Courts must give the FCC's reading "appropriate respect" but decide for themselves what the TCPA means.

For automated collection calling, this cuts both ways. Defendants can now argue that an FCC interpretation is wrong without having challenged it first. Plaintiffs can do the same. The FCC's AI-voice ruling rests on the ordinary meaning of "artificial," so it seems likely to hold up. But older FCC positions on consent are now open to fresh argument in court.

When automated collection calls are allowed

Mobile phones: prior express consent

Under 47 CFR 64.1200(a)(1), calls to a mobile number using an autodialer or an artificial or prerecorded voice require the called party's prior express consent, unless an emergency or specific exemption applies.

For debt collection, the key FCC interpretation dates to 2008. The Commission said that giving a mobile number to a creditor, for example on a credit application, "reasonably evidences prior express consent" to be called at that number about the debt. That consent generally extends to a third-party collector acting for the creditor.

Two cautions. The consent covers the number the borrower provided, not a number a skip-tracing vendor found. And after McLaughlin, a court can reexamine how far that 2008 interpretation reaches.

If the call includes any advertising or telemarketing, such as pitching a new loan product during a collection call, the stricter standard of prior express written consent applies.

Residential landlines: three calls in 30 days

Calls to residential landlines using an artificial or prerecorded voice are treated differently. A commercial call that doesn't include advertising or telemarketing, which covers most collection calls, can be made without consent, but only up to three calls within any 30-day period to that line. The caller must also honor opt-out requests and provide an automated opt-out mechanism in the message (64.1200(a)(3)(iii) and (b)).

Revoking consent

Consumers can revoke consent by any reasonable method. Replying "stop," "quit," "end," "revoke," "opt out," "cancel" or "unsubscribe" to a text counts automatically, as does using an automated opt-out on a call. Under 64.1200(a)(10), callers must honor a revocation within a reasonable time, not to exceed 10 business days, and may not require one exclusive way of revoking.

A separate "revoke-all" provision would have made a revocation on one topic apply to all of a caller's robocalls and robotexts. The FCC delayed it to April 11, 2026 and then to January 31, 2027, as the Consumer Financial Services Law Monitor reported. On September 9, 2026, the FCC issued amendments narrowing that rule, including letting callers designate an FCC-approved opt-out method as their exclusive method, according to Hunton's summary. The amendments take effect 30 days after Federal Register publication. Check the current text before you rely on either version.

What the Do Not Call Registry does and doesn't cover

The national Do Not Call rules in 64.1200(c) apply to "telephone solicitations," defined as calls encouraging the purchase, rental or investment in property, goods or services. A pure collection call isn't a telephone solicitation, so the national registry doesn't bar it. A call that mixes collection with a sales pitch can be. Many collectors still scrub against internal do-not-call lists, because an internal list is where "don't call me again" requests end up.

How Regulation F applies when software does the calling

Regulation F took effect November 30, 2021. None of its rules mention AI, and none need to. They apply to every call a debt collector places, and an automated system has to enforce them on every attempt.

Call frequency

Under 1006.14(b), a debt collector is presumed to comply with the ban on repeated or continuous calls if it calls a particular person about a particular debt:

• no more than seven times within seven consecutive days, and
• not at all within seven consecutive days after having a telephone conversation with that person about the debt (the conversation day counts as day one).

Exceeding either threshold creates a presumption of a violation. Both presumptions can be rebutted with evidence about the circumstances.

The details matter for software:

• It is per debt. A consumer with three accounts in collection can, in principle, receive seven calls per account. Regulation F treats student loans serviced under one account number as a single debt. Stacking calls this way is legal under the presumption but still carries harassment risk.
• It counts calls placed, not calls answered. A call that goes to voicemail counts. A call that is "not connected to the dialed number," such as one that hits a network error, does not.
• Some calls are excluded. Calls made within seven days after the consumer gives prior consent directly to the collector don't count, and neither do calls to the consumer's attorney or the creditor.
• It applies to phone calls only. Texts and emails fall under the general harassment ban in 1006.14(a) rather than a numeric presumption.

Time and place

Calls before 8 a.m. or after 9 p.m. at the consumer's location are presumed inconvenient (1006.6(b)(1)). An automated system needs a reliable local time for each consumer. Area codes are a weak proxy for mobile numbers, because people keep their numbers when they move. If a consumer says a time is inconvenient, the collector can't keep calling then. The CFPB has cited collectors whose agents kept talking after consumers said they were driving or at work.

Disclosures

Under 1006.18(e), the first communication with a consumer must disclose that the collector is attempting to collect a debt and that any information obtained will be used for that purpose. Each later communication must disclose that it is from a debt collector. An AI agent has to deliver these reliably, in the same language as the rest of the call.

Before any of that, the collector has to reach the right person. Discussing a debt with anyone other than the consumer, their attorney or a few other permitted parties is generally prohibited (1006.6(d)). This is why identity verification before disclosing anything about the debt is standard in collection scripts, human or AI.

Limited-content messages

A voicemail can avoid being a "communication," and so avoid the disclosure requirements and third-party disclosure risk, if it qualifies as a limited-content message under 1006.2(j). It must include a business name that doesn't indicate debt collection, a request to reply, "the name or names of one or more natural persons" the consumer can contact, and a phone number. It can include only a few optional items, such as a salutation and suggested times to call back.

That natural-person requirement raises a question for AI personas. A message that gives only an AI persona's name as the contact may not meet the definition. Regulation F doesn't address this directly. The cautious approach is to name a real employee or team the consumer can reach, and to have counsel review persona voicemail scripts.

Separately, the TCPA requires every artificial or prerecorded voice message to state, at the start, the name of the business responsible for the call and, during or after the message, a callback number (64.1200(b)). A limited-content message's business name has to satisfy both rules at once.

Identity and assumed names

A collector can't place calls without meaningfully disclosing the caller's identity (1006.14(g)). Regulation F lets individual employees use an assumed name if they use it consistently and the collector can identify who used it (1006.18(f)). It says nothing about AI personas. Some states now address AI directly. Utah, for example, requires businesses to disclose generative AI when a consumer clearly asks and, under its 2025 amendments, to disclose proactively in certain "high-risk" interactions involving sensitive data such as financial information.

Electronic follow-ups and opt-outs

Most automated campaigns mix calls with texts and email. Every email or text from a debt collector must include a clear, simple way to opt out of further electronic messages to that address or number (1006.6(e)). Once a consumer asks the collector to stop using a medium, the collector must stop using it (1006.14(h)). Regulation F doesn't require a collector to offer the same options on every channel. But a digital validation notice has to be delivered in line with the E-SIGN Act's consumer consent requirements (1006.42(b)).

Records

Under 1006.100, a debt collector must keep records that show compliance or noncompliance from the start of collection activity until three years after its last collection activity on the debt. If it records calls, it must keep each recording for three years after the date of the call. For AI calls, that should mean keeping the audio, the transcript and the rules the system applied at the moment of dialing.

Walking through one automated call

Here is how the rules stack up on a single AI voice call from a third-party collector to a borrower's mobile phone.

Moment	Rule that applies	What the system has to check or do
Before dialing	TCPA 64.1200(a)(1); FCC 24-17	Prior express consent exists for this number and hasn't been revoked
Before dialing	Reg F 1006.14(b)	Fewer than 7 calls to this person about this debt in 7 days; no conversation in the last 7 days
Before dialing	Reg F 1006.6(b)(1)	Local time at the consumer's location is between 8 a.m. and 9 p.m.
Before dialing	State or city law (e.g., NYC SHIELD)	Stricter caps across all channels, if the consumer is covered
Call connects	Reg F 1006.14(g); TCPA 64.1200(b)	Meaningful identification of the caller; business name stated at the start of an artificial voice message
Before discussing the debt	Reg F 1006.6(d)	Confirm the right party is on the line
During the call	Reg F 1006.18(e)	Initial or subsequent debt collector disclosure
During the call	Reg F 1006.14 and 1006.18	No threats, false statements or wrong amounts; route disputes, attorney representation and bankruptcy mentions to a human
If the consumer says stop	TCPA 64.1200(a)(10); Reg F 1006.14(h)	Record the revocation; stop within 10 business days at most; stop using that medium
Voicemail	Reg F 1006.2(j)	Limited-content message only, or a full communication with disclosures and third-party risk
After the call	Reg F 1006.100	Retain the recording three years from the call date and other records three years after last activity

What doesn't apply the way people think

A few rules get attached to debt collection calling that don't legally belong there.

• The 3% abandonment cap. The FCC's rule in 64.1200(a)(7) limits abandoned calls to 3% of answered calls per campaign over 30 days, but it applies to telemarketing calls. A pure collection campaign isn't telemarketing. Keeping abandonment low is still good practice, because dropped calls annoy people and silent calls can look like harassment.
• The national Do Not Call Registry. It governs telephone solicitations, as covered above, not collection calls.
• "Instant" opt-out as a legal standard. The TCPA deadline is 10 business days. Honoring stops in minutes is a strong operational goal, not the legal floor.
• Mini-Miranda on every call. Only the first communication needs the full "attempt to collect a debt" statement. Later ones need to say they are from a debt collector.

What liability looks like

Law	Who can sue or enforce	Exposure
FDCPA	Consumers, CFPB, FTC, states	Actual damages plus up to $1,000 statutory per individual action; in a class action, up to the lesser of $500,000 or 1% of the collector's net worth, plus attorney's fees (15 U.S.C. 1692k)
TCPA	Consumers, state attorneys general, FCC	$500 per violation, or actual loss if greater; up to three times that if willful or knowing (47 U.S.C. 227)
UDAAP	CFPB, prudential regulators, states	Civil penalties and restitution
State and city law	State agencies, some private plaintiffs	Varies

TCPA damages are counted per call, and the statute sets no overall cap. That is why consent errors in automated systems attract class actions. A consent record that is wrong for one number is wrong for every call to that number.

Where platforms fit, and where they don't

Software can make compliance the default outcome of each dial. It can't move the legal duty to someone else. The collector, and often the creditor it collects for, remains the party that is liable.

Here is how the main controls map to the rules above, using Domu as the example because it publishes unusually specific descriptions of where its rules run. The right-hand column is what to ask any vendor.

Control	Rule it serves	How Domu describes it	What to ask any vendor
Rules checked at dial time	Reg F 1006.14(b) and 1006.6(b); TCPA; DNC	Its AI Dialer enforces "Reg F, TCPA, DNC and calling windows" before dialing	Is the cap counted per person and per debt? Across every campaign?
Approved language only	Reg F 1006.18	Personas use "words you approved in advance," with versioning, approval, rollback and a kill switch	Can a model improvise a settlement offer or a legal threat? Show me the controls.
Verification before disclosure	Reg F 1006.6(d)	"Verification first, no balance before identity"	What happens when a third party answers?
Escalation to a human	Reg F 1006.6(b)(2), disputes	Lawsuits, threats, bankruptcy and hardship "routed in real time," with warm transfer	Which phrases trigger escalation, and who configures them?
Cross-channel suppression	TCPA 64.1200(a)(10); Reg F 1006.14(h)	"One opt-out silences every channel at once"	How long from a STOP reply to suppression on voice and email?
Evidence trail	Reg F 1006.100	Transcript, policy applied and decision logged per call, exportable as an exam package	Can I export the consent state as it was at the moment of each dial?

Domu states SOC 2 Type II and PCI compliance and says it "does not replace a customer's legal or compliance judgment," a fair description of every vendor's position. It is also a young company, and one customer quote on its site says borrowers can't tell whether they're talking to a human. That is worth raising with counsel in states with AI disclosure rules.

For side-by-side vendor comparisons, see our reviews of AI calling tools for FDCPA-compliant collection and FDCPA-compliant voice AI for debt collection. For how voice rules interact with text and email, see our guide to compliant collection automation across voice, SMS and email.

Recent changes at a glance

Date	Change	Why it matters for automated calling
April 1, 2021	Facebook v. Duguid narrows the ATDS definition	Many list-based dialers are no longer autodialers
November 30, 2021	Regulation F takes effect	Numeric call-frequency presumptions, LCM safe harbor, electronic opt-outs
February 8, 2024	FCC 24-17: AI voices are "artificial"	AI voice calls to mobiles need prior express consent
2024 to 2025	FCC revocation rules	Any reasonable method; 10 business days to honor
June 20, 2025	McLaughlin v. McKesson	Courts interpret the TCPA for themselves
September 1, 2026	NYC SHIELD Rule takes effect	3 attempts in 7 days across channels; reaches some original creditors
September 9, 2026	FCC amends the delayed revoke-all rule	Effective 30 days after publication; supersedes the January 2027 date

Limitations

• This is not legal advice. Whether a rule applies depends on your role (creditor, servicer, agency, debt buyer), the account's status, the consumer's state and the exact technology you use.
• Some questions are unsettled. Regulation F doesn't address AI personas, including whether a persona's name can serve as the natural person in a limited-content message. After McLaughlin, courts may revisit FCC interpretations that collectors have relied on for years.
• The rules are moving. The FCC's September 2026 revoke-all amendments were not yet in the eCFR text we reviewed on September 26, 2026. State AI disclosure laws are changing quickly.
• FCC primary documents were summarized through secondary sources. The FCC's website was unreachable when this article was prepared, so the AI voice ruling is described from a law firm summary that quotes it. The regulatory text we cite comes from the eCFR.
• Vendor descriptions are the vendor's own. We reviewed Domu's public product pages but didn't test the platform.

Conclusion

"Automated debt collection calling" isn't a single legal category. It sits at the overlap of three sets of rules. The FDCPA and Regulation F decide how often, when and how a debt collector may contact someone, and they don't care whether a person or a program places the call. The TCPA decides when software may place or voice the call at all, and since February 2024 an AI voice is plainly inside its reach. State and city rules, like New York City's SHIELD Rule, can be stricter than both.

For teams running automation, the practical rule is to enforce the strictest applicable limit before every dial, keep a consent record you can reproduce later, and send anything unusual to a human. Platforms like Domu can make that the default. The legal responsibility stays with you.

Frequently asked questions

Does the FDCPA prohibit robocalls or AI voice agents?

No. The FDCPA and Regulation F don't ban any calling technology. They regulate conduct, so an AI agent must follow the same frequency limits, calling hours, disclosure rules and harassment bans as a human collector. Restrictions on the technology itself come from the TCPA, which requires prior express consent for autodialed or artificial-voice calls to mobile phones.

Is an AI voice an "artificial voice" under the TCPA?

Yes, according to the FCC's February 2024 declaratory ruling (FCC 24-17), which covers voices generated or cloned by AI. After the Supreme Court's 2025 McLaughlin decision, courts aren't strictly bound by the FCC's reading, but the ruling rests on the plain meaning of "artificial," and collectors should treat AI voice calls as artificial-voice calls.

What is the 7-in-7 rule in Regulation F?

It is a presumption, not an absolute cap. A debt collector is presumed to comply with the ban on harassing calls if it calls a particular person about a particular debt no more than seven times in seven consecutive days, and not within seven days after a phone conversation about that debt. Going over either threshold creates a presumption of a violation, which the collector can try to rebut.

Do voicemails count toward the Regulation F call limit?

Yes. The presumption counts telephone calls placed, whether or not the call is answered, so a call that ends in a voicemail counts. Calls that never connect to the dialed number, such as those that fail because of a network problem, don't count.

Does the mini-Miranda warning have to be given on every automated call?

Not in full. The first communication must say the collector is attempting to collect a debt and that information obtained will be used for that purpose. Every later communication must say it is from a debt collector. A voicemail that qualifies as a limited-content message is not a communication, so it carries neither disclosure.

How quickly must a collector stop calling after a consumer revokes consent?

Under the FCC's TCPA rules, within a reasonable time not to exceed 10 business days. The consumer can revoke by any reasonable method, and texting words such as "stop" or "unsubscribe" counts automatically. Under Regulation F, a collector must also stop using any medium the consumer asks it not to use.

Are debt collection calls covered by the Do Not Call Registry?

Generally no. The national Do Not Call rules apply to telephone solicitations, meaning calls that encourage a purchase, rental or investment. A call that only collects a debt isn't a solicitation. A call that adds a sales offer can be.

Who is liable if an AI calling platform breaks the rules?

The collector that makes the calls, and often the creditor it collects for. Software vendors are generally not treated as the debt collector or as the party that makes the call, though that can depend on how involved the vendor is in each call. Contracts can shift costs between the parties, but not statutory liability to consumers.

---

This article reflects publicly available information as of September 2026 and does not endorse any specific platform. TCPA consent and revocation rules were amended by the FCC in September 2026 and courts may now interpret the TCPA independently of the FCC, so verify current requirements before relying on any summary here. Consult a licensed professional for guidance specific to your business.