Quick answer: Yes, if it follows a human collector’s rules plus the TCPA’s artificial-voice rules. Regulation F bars AI debt collection calls before 8 a.m. or after 9 p.m. local time and presumes compliance at up to seven calls per debt in seven days, none for seven days from a conversation. Australia’s RG 96 recommends at most three contacts a week. Landlines and some states are stricter.
Sources, read 8 October 2026: Regulation F (12 CFR Part 1006) with its official interpretations, 47 CFR § 64.1200, FCC 24-17 and FCC 07-232, and ACCC/ASIC RG 96. Not legal advice.
Can an AI voice agent make debt collection calls?
Yes. Nothing in Regulation F, the FCC’s TCPA rule at 47 CFR 64.1200 or the Australian guideline bans it. An AI debt collection call is a call placed by software speaking in a generated voice to collect a consumer debt. The rules regulate the collector and the call, not the technology: Regulation F’s text, including its official interpretations, never mentions artificial intelligence (we searched all of Part 1006 on 8 October 2026).
What the AI changes is the federal telephone layer. FCC Declaratory Ruling 24-17 (adopted 2 February 2024, released 8 February 2024) says: “we confirm that the TCPA’s restrictions on the use of ‘artificial or prerecorded voice’ encompass current AI technologies that generate human voices.” Those calls “require the prior express consent of the called party to initiate such calls absent an emergency purpose or exemption.”
The one-line answer: an AI voice agent can collect a debt by phone if the collector holds the consent the TCPA requires for an artificial voice and the dialler enforces Regulation F’s clocks, hours and disclosures in code, not in a prompt.
Who this applies to, and what it does not cover
- Third-party debt collectors. Regulation F applies to a “debt collector” as defined in 12 CFR 1006.2(i): a business whose principal purpose is collecting debts, or anyone who regularly collects debts “owed or due, or asserted to be owed or due, to another.”
- Creditors collecting their own debts in their own name. Excluded: 1006.2(i)(2)(i) carves out “any officer or employee of a creditor while the officer or employee is collecting debts for the creditor in the creditor’s name.” A creditor using a name that implies a third party is pulled back in. A subscription business recovering its own failed card payments sits here, a workflow covered in failed-payment recovery with voice and SMS agents. The TCPA still applies to its AI voice, and some states regulate creditors directly (Massachusetts, below).
- Business debts. A “debt” under 1006.2(h) arises from a transaction “primarily for personal, family, or household purposes”, and a consumer is a natural person. A company’s unpaid invoice is outside Regulation F.
Sales calls are a different regime. The FCC’s 2008 ACA International ruling (FCC 07-232) states that “calls solely for the purpose of debt collection are not telephone solicitations and do not constitute telemarketing.” That cuts in the collector’s favour: the written-consent rule in our breakdown of the TCPA rules for AI cold calling does not apply to a pure collection call, nor does the Do Not Call solicitation regime. Add a pitch and the call is no longer “solely” collection.
The two-clock rule: how often an AI dialler may call about one debt
We call it the two-clock rule: each person-and-debt pair has two clocks, and the dialler may call only when both read green. Both come from 12 CFR 1006.14(b)(2)(i), which presumes compliance with the FDCPA’s ban on repeated calls if a collector places a call to a particular person about a particular debt neither:
- “(A) More than seven times within seven consecutive days; nor
- (B) Within a period of seven consecutive days after having had a telephone conversation with the person in connection with the collection of such debt. The date of the telephone conversation is the first day of the seven-consecutive-day period.”
Clock A is a rolling seven-day counter, not a calendar week: any seven consecutive days may hold at most seven counted calls. Clock B is a lock: after a conversation on day 1, the next call is day 8. Exceed either and 1006.14(b)(2)(ii) flips the presumption to a violation.
Three details change what an AI dialler must count, all from the CFPB’s official interpretations in Supplement I:
- What counts as a call. A call that rings unanswered counts. A call that reaches voicemail counts “even if the debt collector is unable to leave a voicemail.” A ringless voicemail counts. A busy signal or a not-in-service tone does not, because 1006.14(b)(3)(ii) excludes calls “not connected to the dialed number.” Texts and emails are not calls for this rule.
- Per debt, not per consumer. 1006.14(b)(4) defines “particular debt” as each of a consumer’s debts in collection, with one exception: student loans serviced under a single account number count as one debt. The commentary’s worked example allows 21 unanswered calls in seven days to one consumer with three debts, seven per debt.
- Consent pauses the counter, briefly. Under 1006.14(b)(3)(i), calls placed with the person’s prior consent, given directly to the collector, do not count for up to seven consecutive days. It ends early on a shorter stated period, revocation, or a conversation about the debt. “Call me back on Monday” is consent; a creditor’s file note is not.
These are presumptions, not a cap. The commentary lists factors that can rebut a presumed violation, such as redialling a dropped settlement call or warning of a creditor’s late fee before a grace period ends. It works the other way too: seven calls to the same number in one day, or two within five minutes, can rebut the presumption of compliance. And staying inside the clocks protects you “solely with respect to the frequency” of calls: a cumulative wave of calls, emails and texts can still be harassment under 1006.14(a).
US and Australian cadence rules side by side
| Rule | US: Regulation F (third-party collectors) | US: TCPA for an AI voice | Massachusetts: 940 CMR 7.04 (creditors) | Australia: ACCC/ASIC RG 96 |
|---|---|---|---|---|
| What is counted | Calls placed that connect: answered, ringing, voicemail, ringless voicemail. Not busy or not-in-service. | Calls initiated with an artificial voice | Communications initiated via telephone: a live call, a text message or a recorded audio message | Contacts actually made: a conversation, a voicemail left, an email, an SMS. An unanswered call with no message is an “attempted contact”. |
| Frequency limit | Presumed compliant at no more than 7 calls in 7 consecutive days, per person, per debt | Residential landline without consent: no more than 3 calls in any consecutive 30 days, with opt-outs honoured (64.1200(a)(3)(iii)) | No more than 2 per 7-day period to residence, mobile or personal number; 2 per 30 days to other numbers; per debt | Recommended no more than 3 contacts a week, or 10 a month at most, per account |
| After a conversation | No call for 7 consecutive days, the conversation day being day 1 | No separate rule | No separate rule | Leave a reasonable interval; no number given |
| Calling hours | Not before 8:00 a.m. or after 9:00 p.m. at the consumer’s location, absent knowledge to the contrary | The 8 a.m. to 9 p.m. rule in 64.1200(c)(1) covers telephone solicitations, which collection calls are not | Normal waking hours; if unknown, 8:00 A.M. to 9:00 P.M. eastern time | Phone: weekdays 7:30 am to 9 pm, weekends 9 am to 9 pm, debtor’s local time; no contact recommended on national public holidays |
| Consent | Prior consent given directly to the collector lifts the counter for up to 7 days | Mobile: prior express consent, e.g. the number given to the creditor in the transaction that created the debt (FCC 07-232) | A call responding to the debtor’s request is not “initiated” | Stop at the limits unless the debtor invites contact or another legitimate reason applies |
| Legal status | Regulation; presumptions rebuttable | Regulation and statute | State regulation (unfair or deceptive act) | Guidance that “does not have legal force”; the law underneath is ACL s 50 and ASIC Act s 12DJ |
Read across the frequency row and Regulation F is not the strictest limit: a residential landline without consent allows three artificial-voice calls in thirty days, a Massachusetts creditor two communications a week, and RG 96 counts an AI agent’s voicemails, emails and texts, not just its calls.
A worked schedule: one AI dialler, one debt, sixteen days
The dialler calls at 10:00 and 16:00 daily until it reaches the consumer, on a mobile number given to the original creditor on the credit application (prior express consent under FCC 07-232). One debt, no consent given to the collector directly, no inconvenient times on file. The counts are the output of the gate function in the next section; the last column applies RG 96’s definition of contact to the same calls.
| Day | 10:00 | 16:00 | Clock A: counted calls in the 7 days ending that day | Clock B | RG 96 contact? |
|---|---|---|---|---|---|
| 1 (Mon) | Voicemail, limited-content message | Rang, no answer | 2 | Open | 1 contact (the voicemail), 1 attempt |
| 2 (Tue) | Busy signal (not counted) | Rang, no answer | 3 | Open | 2 attempts |
| 3 (Wed) | Rang, no answer | Rang, no answer | 5 | Open | 2 attempts |
| 4 (Thu) | Rang, no answer | Voicemail, limited-content message | 7 | Open | 1 contact, 1 attempt |
| 5 to 7 (Fri to Sun) | Blocked | Blocked | 7: the window is full | Open | None |
| 8 (Mon) | Rang, no answer | Rang, no answer | Day 1’s two calls drop out, so 5 before calling, 7 after | Open | 2 attempts |
| 9 (Tue) | Conversation about the debt | Blocked | 7 | Locked, days 9 to 15 | 1 contact |
| 10 to 15 | Blocked | Blocked | Falling | Locked | None |
| 16 (Tue) | Call allowed | Call allowed | 0 before calling | Open | Depends on outcome |
Three things fall out. First, a twice-daily cadence fills Clock A in four days and the dialler sits idle for three: the constraint on an AI collector is not how fast it can dial but how few connected calls it may place. Second, one conversation costs a week of silence unless the consumer consents to a follow-up, so the agent should ask when to call back. Third, the first nine days produce only three RG 96 contacts (two voicemails and one conversation) but eight unanswered attempts, and RG 96 says plainly that an automated dialler returning a number to the queue “within a short space of time after each attempted contact” may be undue harassment. The cadence that passes Regulation F’s clock is not automatically one an Australian collector should run.
Had the number been a residential landline with no consent, the schedule would have spent its whole TCPA allowance of three artificial-voice calls in thirty days by day 2’s afternoon call. We found nothing in 64.1200 on whether a busy signal counts toward the three, so assume it does.
The dial gate in code, tested against the CFPB’s own examples
The two clocks belong in the dialler, not in the agent’s prompt: a language model asked “may I call again?” will sometimes say yes, and a function cannot be talked into it. This is the gate that produced the table above:
from datetime import timedelta
CONNECTED = {"conversation", "voicemail", "rang_no_answer", "ringless_voicemail"}
def may_call(history, day, consent_day=None):
"""history: list of (date, outcome) for ONE person and ONE debt."""
def excluded(d): # 1006.14(b)(3)(i): calls after consent, within 7 days, until a conversation
if consent_day is None or not (consent_day < d <= consent_day + timedelta(days=6)):
return False
return not any(o == "conversation" and consent_day < c < d for c, o in history)
if excluded(day):
return True
counted = [(d, o) for d, o in history if o in CONNECTED and not excluded(d)]
in_window = sum(1 for d, _ in counted if day - timedelta(days=6) <= d <= day)
last_talk = max((d for d, o in history if o == "conversation"), default=None)
clock_a = in_window <= 6 # (A) not more than 7 in 7 days
clock_b = last_talk is None or day >= last_talk + timedelta(days=7) # (B)
return clock_a and clock_bWe tested it against nine worked examples in Regulation F’s official interpretations (comments 14(b)(2)(i)-1.i, 14(b)(2)(ii)-1.i and 1.ii, 14(b)(3)-3.i to 3.iii, 14(b)(3)(ii)-1, and, with a companion calling-hours function, both examples in 6(b)(1)(i)-2). All passed on 8 October 2026. It is deliberately conservative (a call counts before anyone knows if it will connect) and knows nothing about content, cease requests or the cumulative effect of texts and emails; those need their own gates.
What time can an AI debt collection call be made?
Under 12 CFR 1006.6(b)(1)(i), “a time before 8:00 a.m. and after 9:00 p.m. local time at the consumer’s location is inconvenient” absent knowledge to the contrary.
“Local time at the consumer’s location” is not the area code. If the collector’s records conflict, comment 6(b)(1)(i)-2 says the collector complies by calling at a time that is convenient in every location the records suggest. The CFPB’s own example: a mobile with an Eastern area code and a home address in the Pacific zone gives a window of 11:00 a.m. to 9:00 p.m. Eastern. Time-zone mistakes are the subject of our piece on an AI agent that called someone at 9pm in Perth.
“Knows or should know” means what the consumer says, and what the file says, sets the rules. In the commentary’s example the consumer says “I cannot talk now”, the collector asks when would suit, and the times named as bad become prohibited until the consumer says otherwise. The agent must write that into a record the dialler reads, and the dialler must also read the creditor’s notes: in the commentary’s other example, a file note that the consumer cannot be disturbed on Tuesdays and Thursdays makes those days off limits. The same section bars calls at an inconvenient place, to a consumer known to have an attorney for the debt whose name and address the collector knows or can readily ascertain (unless the attorney fails to respond within a reasonable time or consents), and to a workplace whose employer prohibits them. Prior consent given directly to the collector during a compliant communication, or a court’s permission, lifts these limits.
For Australia, RG 96’s reasonable contact times are 7:30 am to 9 pm on weekdays and 9 am to 9 pm on weekends, in the debtor’s state or territory, with no contact recommended on national public holidays. A debtor’s reasonable wishes, such as a shift worker’s, override the table; conversely, a collector may alter the time after reasonable efforts over a reasonable period have failed. Footnote 11 notes that South Australia’s Fair Trading Act prohibits telephone calls to demand payment on any public holiday.
What the AI has to say: mini-Miranda, voicemail and identity
The mini-Miranda. 12 CFR 1006.18(e)(1) requires a collector to “disclose in its initial communication with a consumer that the debt collector is attempting to collect a debt and that any information obtained will be used for that purpose,” and to repeat it in the first written communication if the first one was oral. Every later communication must say it is from a debt collector (1006.18(e)(2)). Formal legal pleadings are exempt. Under 1006.18(e)(4) the disclosure must be in the language of the communication, completely and accurately translated; the commentary requires both languages for a communication held partly in English and partly in Spanish. A multilingual AI agent needs that as a test case.
Right party first. 1006.6(d)(1) bars communicating about the debt with anyone other than the consumer, the consumer’s attorney, a consumer reporting agency where permitted, the creditor, the creditor’s attorney, or the collector’s attorney, subject to exceptions such as acquiring location information under 1006.10. For this section “consumer” also covers the consumer’s spouse, a minor consumer’s parent, a legal guardian, an executor or administrator, and a confirmed successor in interest (1006.6(a)). An AI agent must confirm it is speaking to one of them before it says anything about a debt. A location call to a third party must not say the consumer owes a debt, and the caller must “identify himself or herself individually by name”: a question for counsel when the caller is software.
The voicemail. A limited-content message under 1006.2(j) is not a “communication” (official interpretation 18(e)-1), so it needs no mini-Miranda and discloses nothing to whoever plays the tape. Required: a business name for the collector that does not indicate it is in the debt collection business; a request to reply; “the name or names of one or more natural persons whom the consumer can contact to reply”; and a phone number. Permitted extras: a salutation, the date and time, suggested reply times, and a statement that any representative can help. Nothing else. An AI persona’s name is not obviously a natural person’s, so the safe build names a human team member as the reply contact.
Identity and opt-outs. 1006.14(g) bars calls that do not meaningfully disclose the caller’s identity; 64.1200(b) requires every artificial-voice message to open with the responsible business’s registered name, give a callback number and, for calls under the three-in-thirty residential exemption, an automated opt-out. “Stop calling” is a request under 1006.14(h) not to use telephone calls at all, and 64.1200(a)(10) lets consent be revoked “by using any reasonable method”. Recorded calls must be kept for three years after the date of the call (1006.100(b)); other records evidencing compliance, such as the dialler’s log of why each call was allowed, for three years after the last collection activity on the debt (1006.100(a)).
“Am I talking to a robot?” Regulation F does not require an AI disclosure. 1006.18(f) lets an employee use a consistent assumed name and 1006.18(d) bars deceptive means; the text does not say how either applies to an AI persona. State law may require disclosure outright: see the US state AI call-disclosure patchwork.
When an AI collector should stop and hand over to a human
The handoff logic we would build, with the rule behind each row:
| Signal on the call or in the file | What the dialler must do | Rule behind it |
|---|---|---|
| Clock A shows 7 counted calls in the last 7 days for this debt | No call until the window drops to 6 | 12 CFR 1006.14(b)(2)(i)(A) |
| A conversation about the debt happened today or in the previous 6 days | No call until day 8, unless the consumer gave consent directly | 1006.14(b)(2)(i)(B), (b)(3)(i) |
| Consumer says “stop calling” | Remove the phone medium for this person | 1006.14(h); 47 CFR 64.1200(a)(10) |
| Written refusal to pay or cease-communication notice | Stop; human sends any of the three permitted notices | 1006.6(c) |
| Consumer names an attorney for this debt | Once the attorney’s name and address are known or readily ascertainable, stop calling the consumer unless the attorney consents or fails to respond in a reasonable time | 1006.6(b)(2) |
| Consumer disputes the debt or says it is not theirs | Human review; disputes have their own rules in 1006.38 | 1006.38; commentary 14(b)(2)(i)-2.iii |
| Someone other than the consumer, or a person 1006.6(a) treats as the consumer, answers | Say nothing about a debt; location script only | 1006.6(a), (d)(1); 1006.10(b) |
| Hardship, mental health or family violence cues (Australia) | Human handoff under the vulnerable-debtor policy | RG 96 section 23, Compliance programs: policies “for identifying and dealing with vulnerable debtors” |
| 3 contacts this week or 10 this month on this account (Australia) | Stop unless the debtor invites contact or another legitimate reason applies | RG 96 part 2, section 5 |
Every row is a deterministic check, not a judgement left to the model.
Building outbound voice agents that need gates like these? Apply For Partnership
Is AI debt collection legal in Australia?
Yes, on the same terms as human collection. RG 96, the ACCC and ASIC’s Debt collection guideline, is the edition ASIC lists as issued 13 April 2021 (read 8 October 2026; the ACCC’s copy would not load from our server). It has no AI-specific section, but it addresses two things an AI collector does: automated dialling and new contact channels. On diallers: unreasonably frequent attempted contact “may occur, for example, where an automated dialler is used to make calls and a debtor’s number is returned to the queue within a short space of time after each attempted contact.” On new channels: “emerging technologies (such as voice messaging, or other online systems)” may be acceptable where the collector reasonably believes contact will be with the debtor only and the channel is not shared.
RG 96 itself says: “This guideline does not have legal force.” But the law underneath it, section 50 of the Australian Consumer Law and section 12DJ of the ASIC Act on undue harassment and coercion, is enforceable; a creditor can bind itself to the guideline by contract; and external dispute resolution schemes may consider it. And it counts differently from Regulation F: a voicemail, an email and a text are three separate contacts, so cross-channel follow-up uses the weekly allowance fast.
Where this fits with Zian AI
Zian AI builds autonomous sales and support agents for phone, SMS, email and WhatsApp in 30+ languages, with HubSpot, Salesforce, HighLevel and Zapier integrations. Collections is not one of our listed niche agents, and nothing here claims a Zian agent is configured for Regulation F or RG 96. The overlap is pacing: SmartReach AI™ orchestrates message, channel and timing with follow-up pacing, and the two clocks, the time window and the handoff table are pacing rules with legal consequences. The wider rule set for AI outreach, across the Spam Act, the TCPA and the GDPR, is in our AI outreach compliance overview. Zian is in partnership-application beta.
Frequently asked questions
Can AI make debt collection calls?
Yes. Nothing in Regulation F, the FCC’s TCPA rule at 47 CFR 64.1200 or the ACCC/ASIC guideline bans it, and the rules that bind a human collector bind the AI too. In the US the AI voice also counts as an “artificial” voice under the TCPA after FCC 24-17, so a call to a mobile needs prior express consent, such as a number the consumer gave the creditor in the transaction that created the debt.
How many times can a debt collector call in a week?
Under Regulation F a collector is presumed compliant at no more than seven calls in seven consecutive days to a person about a particular debt, and no call in the seven days after a conversation about it, the conversation day being day one. That is the text of 12 CFR 1006.14(b)(2).
What are the FDCPA collection call time rules?
Regulation F treats a call before 8:00 a.m. or after 9:00 p.m. at the consumer’s location as inconvenient unless the collector knows otherwise. If the records point to two time zones, the call must be convenient in both. A time the consumer has said is inconvenient is off limits until they say it is not.
Does an AI debt collection voicemail need the mini-Miranda?
Not if it is a limited-content message: a business name that does not reveal debt collection, a request to reply, the name of one or more natural persons to contact, and a phone number, plus a few permitted extras. A voicemail that conveys information about a debt needs the disclosure.
Does an AI debt collector have to say it is an AI?
Regulation F does not require it, but it bars false representations and requires the caller’s identity to be meaningfully disclosed, and state law may add an AI disclosure duty. The low-risk build answers “am I talking to a robot?” truthfully every time.
How many times can a debt collector contact me in Australia?
The ACCC and ASIC guideline recommends no more than three contacts a week, or ten a month at most, per account, counting contacts actually made, including voicemails, emails and texts. It treats phone contact between 7:30 am and 9 pm on weekdays and 9 am and 9 pm on weekends as appropriate. The guideline has no legal force, but harassment law does.
Building an outbound voice agent for a regulated workflow? Apply For Partnership
Where every figure on this page comes from
| Figure | Who published it | Link | Date read |
|---|---|---|---|
| No more than 7 calls in 7 consecutive days; no call within 7 days after a conversation, conversation day is day 1 | CFPB, 12 CFR 1006.14(b)(2) (eCFR) | ecfr.gov § 1006.14 | 8 October 2026 |
| Prior-consent exclusion for up to 7 consecutive days | CFPB, 12 CFR 1006.14(b)(3)(i) | ecfr.gov § 1006.14 | 8 October 2026 |
| 21 unanswered calls in 7 days across 3 debts presumed compliant; 2 calls within 5 minutes or 7 in one day as rebuttal factors | CFPB, Regulation F Supplement I, comments 14(b)(4)-2.i and 14(b)(2)(i)-2.i | ecfr.gov Part 1006 | 8 October 2026 |
| Inconvenient before 8:00 a.m. and after 9:00 p.m. local time; 11:00 a.m. to 9:00 p.m. Eastern example | CFPB, 12 CFR 1006.6(b)(1)(i) and comment 6(b)(1)(i)-2.i | ecfr.gov § 1006.6 | 8 October 2026 |
| Limited-content message: 4 required items, 4 optional items | CFPB, 12 CFR 1006.2(j) | ecfr.gov § 1006.2 | 8 October 2026 |
| 3 artificial-voice calls in any consecutive 30 days to a residential line without consent (commercial, not telemarketing) | FCC, 47 CFR 64.1200(a)(3)(iii) (eCFR) | ecfr.gov § 64.1200 | 8 October 2026 |
| AI-generated voices are “artificial” under the TCPA; adopted 2 February 2024, released 8 February 2024 | FCC, Declaratory Ruling FCC 24-17 | docs.fcc.gov FCC-24-17A1 | 8 October 2026 |
| Number given to the creditor in the transaction = prior express consent for debt calls; collection calls are not telemarketing; released 4 January 2008 | FCC, Declaratory Ruling FCC 07-232 | docs.fcc.gov FCC-07-232A1 | 8 October 2026 |
| 2 communications per 7 days to a personal number, 2 per 30 days to other numbers; 8:00 A.M. to 9:00 P.M. eastern time | Massachusetts Attorney General, 940 CMR 7.04(1)(f) and (g) (reproduced by Cornell LII; mass.gov blocked our server) | law.cornell.edu 940 CMR 7.04 | 8 October 2026 |
| No more than 3 contacts a week or 10 a month; phone 7:30 am to 9 pm weekdays, 9 am to 9 pm weekends; issued 13 April 2021 | ACCC and ASIC, RG 96 Debt collection guideline | asic.gov.au RG 96 PDF | 8 October 2026 |
| Call recordings kept 3 years after the call; other compliance records 3 years after the last collection activity | CFPB, 12 CFR 1006.100(a) and (b) | ecfr.gov § 1006.100 | 8 October 2026 |