FDCPA and Regulation F rules for AI collection calls: a call-by-call checklist
Short answer
An AI collection agent follows the same FDCPA and Regulation F (12 CFR part 1006) rules as a human collector. It must name the business, verify the right party before any account detail, give the debt collector disclosure, call 8 a.m. to 9 p.m. local time, stay within seven-in-seven and honor stop, dispute and attorney requests. A voicemail that mentions the debt needs the disclosure, so keep voicemails limited-content.
On this page
- Does Regulation F treat an AI agent differently from a human collector?
- When may the agent call, and how often?
- What must the agent confirm and say on a live call?
- What can an AI agent leave on voicemail?
- How should the agent handle stop, dispute and attorney requests?
- What rules apply when the agent takes a payment?
- What must the agent never say?
- Which rules can one transcript settle, and which need the dial log?
- Questions
- Sources
An AI collection agent repeats its mistakes on every call until someone notices. A prompt change that drops the disclosure drops it everywhere. An agent that recomputes a balance can quote one your system of record never held. One tuned to push past objections keeps talking after the consumer says it's a bad time. That's how a release that passes its tests can still break a rule.
Regulation F is the Consumer Financial Protection Bureau's rule, at 12 CFR part 1006, that implements the Fair Debt Collection Practices Act (FDCPA). It sets out how debt collectors may call and message consumers and what records they must keep. Neither law mentions AI. This checklist follows an AI collection call from dialer to hang-up, cites the section behind each item, and ends with which rules a transcript can actually prove.
Does Regulation F treat an AI agent differently from a human collector?
No. Reg F defines a communication as conveying information about a debt "through any medium" (12 CFR 1006.2(d)), so a synthetic voice on the collector's line is the collector talking. The eCFR shows no amendment to part 1006 since 2023.
$1,000
maximum statutory damages per individual FDCPA action, on top of actual damages and attorney's fees
$500,000
cap on statutory damages in a class action, or 1% of the collector's net worth if less
Regulators can add civil money penalties under the Consumer Financial Protection Act for each day a violation continues (12 U.S.C. 5565(c)). An AI flaw repeats on every call until its release is fixed.
Some provisions assume a person. The assumed-name allowance in 1006.18(f) covers a collector's employees. A location call under 1006.10 requires the caller to identify "himself or herself individually by name." An AI persona fits neither. Every call must meaningfully disclose the caller's identity (1006.14(g)), so the opening names the business, by a registered name that doesn't signal debt collection. And an agent that claims to be human when asked is hard to square with 1006.18(d)'s ban on false representations.
When may the agent call, and how often?
Between 8 a.m. and 9 p.m. in the consumer's local time, and never at a time the consumer has ruled out. To keep Reg F's presumption of compliance, make no more than seven calls in seven days to one person about one debt. After a conversation about the debt, make no calls about it for seven days, counting the day of the conversation as day one. Some states set tighter limits.
Convenient hours in the consumer's time zone
Absent knowledge to the contrary, calls before 8 a.m. or after 9 p.m. local time at the consumer's location are inconvenient (1006.6(b)(1)(i)). When your records disagree about where the consumer is, the official interpretations say to call only at times convenient in every location they point to. The CFPB's example is a cell number with an Eastern area code and a home address in the Pacific time zone. That leaves 11 a.m. to 9 p.m. Eastern.
Times and places the consumer names bind too. Told it's a bad time, the agent may ask when would be better. It may not ask the consumer to keep going: the commentary to 1006.6(b)(4)(i) forbids asking for consent to continue that inconvenient communication. An agent tuned to say "this will only take two minutes" breaks that every time.
What counts toward the seven-in-seven (7-in-7) presumption?
Reg F presumes a collector complies with the ban on calling repeatedly to annoy or harass if it meets two limits (1006.14(b)(2)). It calls a particular person about a particular debt no more than seven times within seven consecutive days. And it doesn't call at all within seven consecutive days after a telephone conversation about that debt, counting the day of the conversation as day one. Exceed either limit and the presumption flips to a presumed violation.
- Day 1
His cell rings unanswered: counts, 1 of 7
- Day 1
His landline reaches voicemail and no message is left: counts, 2 of 7, because both lines are one person
- Day 2
A busy signal, a not-in-service tone, a text and an email: none of them counts
- Day 3
A ringless voicemail: counts, 3 of 7
- Day 4
Daniel answers and discusses the debt: counts, 4 of 7, and day 4 is day one of a seven-day pause
- Days 5 to 10
No calls about this debt
- Day 11
Calls may resume, still no more than seven in any seven days
Illustrative. Counting rules from 12 CFR 1006.14(b) and its official commentary.
The commentary settles the rest. A call counts once it's placed and connects, including one answered and then dropped. Calls to the consumer's attorney don't count. Neither do calls placed with the person's prior consent, given directly to the collector, for up to seven days (1006.14(b)(3)). That consent ends sooner if it was for a shorter time, if it's revoked, or if a conversation about the debt takes place (comment 14(b)(3)(i)-2).
The count runs per debt, not per consumer. A medical debt and a card debt have two separate counts. A conversation about both counts toward both, and an unanswered call can go toward either. Student loans serviced under one account number are one debt (1006.14(b)(4)). A conversation the consumer starts also starts the seven-day clock.
It's a presumption, not an allowance: the commentary says two unanswered calls to one number within five minutes, or seven in one day, can rebut compliance inside the limits.
Where state law is stricter
Massachusetts allows a licensed debt collector two telephone or text communications it initiates per debt in each seven-day period to a consumer's home or cell phone (209 CMR 18.16(1)(d)). It holds creditors to two as well, recorded messages included (940 CMR 7.04(1)(f)). Set the dialer to the strictest rule for the consumer's state, using the account's address.
What must the agent confirm and say on a live call?
Four things, in order: the business and the recording, the right party, the disclosure, and on a first contact, the validation clock.
- The business named at the start, not only the AI persona Reg F 1006.14(g)
- The recording announced in the opening, on every call State law
- The right party confirmed by the identity tool, not a guess Reg F 1006.6(d)
- If someone else answers, nothing about why the agent is calling Reg F 1006.6(d)
- The disclosure: in full on the initial communication, "from a debt collector" on every later one FDCPA 1692e(11)
- The disclosure in the language of the call, or in both if the call switches Reg F 1006.18(e)(4)
Reg F doesn't require recording calls. It does require keeping each recording for three years after the call (1006.100(b)). Whether you may record is a question of federal and state law:
| Law | Who must consent to a recording |
|---|---|
| Federal, 18 U.S.C. 2511(2)(d) | One party to the call |
| California, Penal Code 632 | All parties to a confidential call |
| California, Penal Code 632.7 | All parties to any call involving a cell or cordless phone |
| Washington, RCW 9.73.030 | All parties, but a recorded announcement counts as consent (subsection (3)) |
The agent rarely knows where the consumer is standing, so it announces the recording on every call.
- Right party. A collector can't discuss the debt with third parties (1006.6(d)(1)). Reg F treats the consumer's spouse as the consumer here (1006.6(a)(1)), though your standard operating procedure (SOP) can be stricter.
- Disclosure. In the initial communication, the collector must say it is attempting to collect a debt and that any information obtained will be used for that purpose. In every later one, it must say the communication is from a debt collector (15 U.S.C. 1692e(11), 1006.18(e)). An inbound call returning a voicemail can itself be the initial communication. When the initial communication is a call, the full disclosure must be repeated in the initial written communication (1006.18(e)(1)), so the letter workflow has to know the call came first.
- Validation. Validation information, listed in 1006.34(c), is the debt's details and the consumer's rights, including how to dispute it. If this call is the initial communication, it must be given on the call or sent in a validation notice within five days (1006.34(a)(1)).
What can an AI agent leave on voicemail?
The safe message is a limited-content message: a voicemail for a consumer that contains four required items, may contain four optional ones, and contains nothing else (1006.2(j)). The required items are a business name that doesn't indicate debt collection, a request that the consumer reply, the name of one or more natural persons to contact, and a phone number. The optional ones are a salutation, the date and time of the message, suggested times to reply, and a statement that any of the company's representatives or associates can take the reply.
A limited-content message isn't a communication, so it needs no disclosure. It is an attempt to communicate, though, so the call counts toward seven-in-seven. Add anything that conveys information about the debt and the voicemail becomes a communication that needs the disclosure (comment 18(e)-1). It can also reveal the debt to whoever plays it.
| Breaks the limited-content message | Stays within it |
|---|---|
| A business name that signals debt collection | A business name that doesn't, such as "Quillfeather Services" |
| "This message is from a debt collector" | Nothing about what the business does |
| "I'm trying to reach Daniel Reyes" | "Please call me back" |
| "Call Maya back," when Maya is the AI persona | The name of a natural person to contact: a real employee, or their consistent assumed name |
| "It's about your Alder Card balance," or any other detail about the debt | Only the optional extras: a salutation, the date and time, and suggested times to reply |
| "Our credit card receivables group can help" | "Any of our representatives can help" |
Each row pairs something that breaks the message with what to say instead. The breaking side of rows two and three, taken together, is the CFPB's own failing example. Comment 2(j)-1 in the official interpretations rejects a voicemail with "a statement that the message is from a debt collector and a request to speak to a particular consumer." The last row comes from comment 2(j)(2)-1, which rules out naming a "credit card receivables group".
The TCPA pulls the other way. Every artificial or prerecorded voice message must open with the business's registered name (47 CFR 64.1200(b)(1)), and the FCC treats AI voices as artificial (FCC 24-17). If your registered name says "collections," the two rules collide on every AI voicemail, so settle it with counsel first. The consent side is in TCPA consent for AI voice calls after the FCC's 2024 ruling.
How should the agent handle stop, dispute and attorney requests?
Each differently: "stop calling" ends calls to that person, a lawyer moves contact to the lawyer, and a spoken dispute is recorded without halting collection.
| When the consumer | The agent | The rule |
|---|---|---|
| Asks not to be called, or rules out one number and keeps another | Acknowledges it, stops collection talk and writes it to whatever drives the dialer | After a request not to use a medium, the collector may not use it to reach that person, so "stop calling" ends calls (1006.14(h)) |
| Asks in writing that communication cease | Makes no further collection contact | Communication ends except to say collection is stopping or a specified remedy may be invoked (1006.6(c)) |
| Has a lawyer for this debt | Asks for the lawyer's name and contact details, then stops talking to the consumer about the debt | Once the collector knows of the lawyer and knows, or can readily find, the name and address, it contacts the lawyer instead (1006.6(b)(2)) |
| Disputes the debt on the call | Records the dispute and, if your SOP says so, explains how to dispute in writing, without saying anything that overshadows or contradicts that right (1006.38(b)) | Credit information can't be reported without saying the debt is disputed, written dispute or not (1006.18(c)(2)). Only a written dispute within the validation period halts collection of the disputed amount until verification is sent (1006.38(d)(2)) |
What rules apply when the agent takes a payment?
Three, one from Regulation E and two from Reg F. A fee for paying by phone has to trace to the agreement or the law, so the agent quotes only what the payment tool returns.
- No amount collected, including interest, a fee, a charge or an expense, unless the agreement creating the debt expressly authorizes it or the law permits it Reg F 1006.22(b)
- A check or other payment instrument postdated by more than five days accepted only with written notice to the consumer 3 to 10 business days before it's deposited Reg F 1006.22(c)(1)
- Recurring debits from the consumer's account only with an authorization in a writing signed or similarly authenticated by the consumer, and a copy to the consumer from whoever obtains it Reg E 1005.10(b)
What must the agent never say?
First, a balance it didn't read from the system of record on the call. Misstating the amount or legal status of a debt is a false representation (1006.18(b)(2)), and a model that recomputes a balance can misstate it.
- Quotes only the balance the system of record returned on this call Reg F 1006.18(b)(2)
- Threatens nothing it can't lawfully do or doesn't intend to do Reg F 1006.18(b)(3), (c)(1)
- Never implies a lawyer is involved when none is Reg F 1006.18(b)(1)(iii)
- Never threatens to sue on a time-barred debt Reg F 1006.26(b)
- Uses no abusive or profane language Reg F 1006.14(a), (d)
Which rules can one transcript settle, and which need the dial log?
One transcript, with the tool-call log, settles what the agent said and did on that call. That covers the right-party check (with the identity tool's result), the disclosure, a captured voicemail's content, the stop request itself, and quoted amounts and threats (with the balance tool's result). The rest needs outside records. The commentary to 1006.100 names telephone call logs as the records that evidence compliance with the repeated-calls rule.
| What one transcript can't show | The record that shows it |
|---|---|
| Whether the call fell inside 8 a.m. to 9 p.m. everywhere the consumer may be (1006.6(b)(1)) | Call time, the account's address and every number's area code |
| Whether seven-in-seven held (1006.14(b)(2)) | The dial log across all numbers, with outcomes and conversation dates |
| Whether any call followed a stop request (1006.14(h)) | The dial log after the request |
| Whether the full disclosure or the later one was owed (1006.18(e)) | Contact history |
| Whether a written cease or dispute arrived (1006.6(c), 1006.38) | Mail and email records, and validation dates |
| Whether a threat to sue concerned a time-barred debt (1006.26(b)) | Limitations data |
| Whose number heard the voicemail (1006.2(j)) | A record of whose number it is |
One call, graded against the example collections SOP (rev 7), the fictional one every guide on this blog uses:
Agent: Hi, this is Maya, an automated assistant calling for Quillfeather Services on a recorded line. Am I speaking with Daniel Reyes?
1.1 met Opening: business named and recording announced in the opening
Customer: Yes, that's me.
Agent: Thanks, Daniel. To protect your privacy, please confirm your date of birth.
Customer: March 4, 1986.
1.2 met Right party: verify_identity returned a match at 00:16, before any account detail
Agent: Thank you. Quillfeather Services is a debt collector. This is an attempt to collect a debt, and any information obtained will be used for that purpose.
2.3 met Disclosure: given before the debt was discussed
Customer: Look, I'm at work. I can't really talk right now.
Agent: I understand. This will only take two minutes. Your balance with Alder Card is $1,284.16.
5.3 missed Inconvenient time: consumer said "I can't really talk right now" and the agent kept going instead of offering another time
2.4 met Balance: $1,284.16 matches get_balance at 00:41
5.1 not checked Calling hours: needs the call time, the account's address and every number's area code
5.2 not checked Call frequency: needs the dial log for Daniel and this debt
Loops grades every collection call against rules like these. Each verdict quotes the line or tool call it relied on. Rules that need records Loops doesn't read, such as call frequency, can't be checked from the call, and a stretch the transcript can't settle goes to a person. The guide to auditing AI voice agent calls against your SOP covers turning an SOP into rules like these. This post is general information, not legal advice.
Next, sort every rule in your SOP into the two columns above. Grade the transcript rules on every call. Don't report a seven-in-seven or calling-hours figure until the dial log, address file and account notes are joined to the calls behind it. The free 30-day audit shows last month's calls graded that way.
Questions
Does an AI debt collection agent have to say it's an AI?
Neither the FDCPA nor Regulation F has an AI disclosure rule. But Reg F's assumed-name allowance in 1006.18(f) is written for a collector's employees, and 1006.18(d) bars false representations, so an agent that claims to be a person when asked is exposed. The FCC proposed AI-call disclosure rules in August 2024 (FCC 24-84), but as of September 23, 2026 none are in 47 CFR 64.1200. Check state law as well.
Do text messages or emails count toward Regulation F's seven-in-seven limit?
No. The official commentary to 12 CFR 1006.14(b) says placing a telephone call includes leaving a ringless voicemail but not sending a text or email, even one received on a mobile phone. They still count toward the general ban on harassment: the commentary's example of seven unanswered calls in a week plus repeated emails is likely a violation of 1006.14(a) (comment 14(a)-2). Texts and emails also need an opt-out notice in each message (1006.6(e)).
How long must a collector keep AI call recordings and dial logs?
Reg F doesn't require recording calls, but a collector that records must keep each recording for three years after the date of the call (12 CFR 1006.100(b)). Other records that evidence compliance, which the commentary says include telephone call logs, must be kept from the start of collection activity on a debt until three years after the last collection activity on it (1006.100(a)).
Does Regulation F apply when a lender's own AI agent calls its customers?
Usually not. Reg F's collector rules apply to debt collectors as defined in 12 CFR 1006.2(i), and a creditor collecting its own debts in its own name generally isn't one, unless it uses a name suggesting a third party is collecting. A lender is still bound by the Consumer Financial Protection Act's ban on unfair, deceptive or abusive acts or practices (12 U.S.C. 5536(a)(1)(B)). Some state laws cover creditors collecting their own debts, such as California's Rosenthal Act (Civil Code 1788.2(c)), and the TCPA applies either way.
Sources
- 12 CFR Part 1006, Debt Collection Practices (Regulation F), eCFR
- Supplement I to Part 1006, Official Interpretations, eCFR
- 12 CFR 1005.10, Preauthorized transfers (Regulation E), eCFR
- 15 U.S.C. 1692e, False or misleading representations, Legal Information Institute, Cornell Law School
- 15 U.S.C. 1692k, Civil liability, Legal Information Institute, Cornell Law School
- 12 U.S.C. 5536, Prohibited acts, Legal Information Institute, Cornell Law School
- 12 U.S.C. 5565, Relief available, Legal Information Institute, Cornell Law School
- 47 CFR 64.1200, Delivery restrictions, eCFR
- Declaratory Ruling, Implications of Artificial Intelligence Technologies on Protecting Consumers from Unwanted Robocalls and Robotexts (FCC 24-17), Federal Communications Commission
- 18 U.S.C. 2511, Interception and disclosure of wire, oral, or electronic communications prohibited, Legal Information Institute, Cornell Law School
- California Penal Code section 632, California Legislative Information
- California Penal Code section 632.7, California Legislative Information
- RCW 9.73.030, Intercepting, recording, or divulging private communication, Washington State Legislature
- 209 CMR 18.16, Communication in connection with debt collection (Massachusetts), Legal Information Institute, Cornell Law School
- 940 CMR 7.04, Contact with debtors (Massachusetts), Legal Information Institute, Cornell Law School
- California Civil Code section 1788.2 (Rosenthal Fair Debt Collection Practices Act), California Legislative Information