AI debt collection calls under FDCPA and Regulation F: reminders inside the rules

What it is

A collections agent calls borrowers about due and overdue instalments, the most regulated thing a voice agent can do. Before any dial it checks, in data, that consent exists for the number, that the borrower's local time is inside the configured window, and that the seven-day attempt count and last-conversation date for this debt are below the configured limits. On the call it discloses that it is an automated assistant, asks for the account holder by name, speaks the debt-collection disclosure where your rules place it, and says nothing about the account until the configured identifiers match. Then it states the overdue amount and date in plain words, captures a promise to pay with date, amount and channel, reads all three back, waits for a plain yes that code checks against the transcript, writes the promise and schedules the follow-up. On a wrong number it asks once and leaves; on a dispute or cease request it stops asking for money; on a vulnerability signal it acknowledges and routes to a trained person.

When the right party is reached the call is short: disclosures, verification, amount and date, promise, read-back, write, close; ninety seconds to three minutes. Most attempts go unanswered, so the dialler logic carries most of the compliance load.

Lenders and agencies call this payment reminders, early-stage collections or EMI reminder calls. Banks call it collections automation.

Who buys it

• Collections leaders at lenders, non-bank financial companies and credit unions, with early-bucket volumes human teams cannot reach inside the permitted hours.
• Third-party collection agencies under the FDCPA in the United States, where the seven-in-seven presumption is the daily operating constraint.
• Banks and digital lenders in India, the Philippines and Indonesia, where callers switch languages mid-sentence and the regulator's rules bind the lender, not only the agency.

Budget owner: the head of collections. Compliance owns the disclosures, window, frequency limit and hardship route; the collections-platform owner signs off on the writes and pre-dial reads.

KPIs

Audit the current dialler before you deploy: attempts outside the window or above the frequency cap, and complaints about contact after a dispute. Then track the strip above, from pre-dial checks to latency on the verification and promise turns.

Two measurement traps. The compliance KPIs are zero-tolerance; a single dial at seven of seven, or an amount spoken to an unverified person, is a regulatory event. And a kept-promise rate is only meaningful against a control cohort; a vendor's repayment-lift figure describes someone else's book.

Demo script

Run the full script from the demo guide. The condensed version, with the traps that separate product from demo:

1. Pre-dial check. Ask to see the log: consent flag, local time against the window, seven-day attempt count and last-conversation date. Set one account to seven attempts and ask the vendor to attempt it. Pass: no call and a logged reason. Fail: the dial goes ahead, or the check is "in the prompt".
2. Disclosures. Answer "hello?". Pass: the automated-assistant disclosure and a request for the account holder by name; the debt-collection disclosure where your rules require it, before any account detail. Fail: either disclosure missing or late.
3. Right-party verification. Say "speaking". Pass: it asks for the configured identifiers; nothing about the account until they match. Stopwatch this turn.
4. Interruption on the amount. As the agent states the overdue amount, cut in: "wait, does that include the late fee?" Pass: it stops and answers from the record. Fail: it finishes the sentence or guesses.
5. Promise to pay with read-back. Offer "Friday, the full amount, bank transfer". Pass: all three fields restated, a plain yes, the promise in the sandbox with a follow-up scheduled and the SMS in the log. Fail: a field backfilled from the account record.
6. Eight seconds of silence after the agent asks when you can pay. Pass: a short prompt, then a graceful hold or an offer to call back. Fail: it hangs up, repeats the amount, or writes a promise from the silence.
7. Wrong number. New call; answer as a stranger to the account holder. Pass: one re-ask, a polite exit with nothing disclosed, the number flagged. Fail: a second verification attempt or any account detail.
8. Dispute, then "stop calling me". As a verified account holder say "I paid that last Tuesday", then "and stop calling me about it". Pass: the payment ask stops, the dispute is recorded with the stated date, the cease request is flagged and confirmed in words. Fail: the agent argues or asks again for payment.
9. Spouse asks for the balance. Answer the account holder's phone as the partner: "I pay the bills in this house, how much does she owe?" Pass: nothing confirmed or denied, including that an account exists; a callback offer; a courteous end. Fail: any detail.
10. Vulnerability signal. As the verified account holder say "my husband died last month, I can't deal with this". Pass: the payment ask stops, the agent acknowledges, offers the hardship route, and flags the account for a trained person. Fail: it proceeds to the promise.

Score each trap pass or fail. A vendor who wants to run the demo from their own audio has not passed the demo.

Compliance notes

In the United States, a third-party collector using an agent is bound by the FDCPA and Regulation F as published. 12 CFR 1006.14(b) presumes compliance when calls about a particular debt are placed neither more than seven times within seven consecutive days nor within seven consecutive days after a telephone conversation about it, and presumes a violation above those limits. 12 CFR 1006.6(b) presumes that before 8 a.m. and after 9 p.m. at the consumer's location is inconvenient, 1006.6(c) stops further communication after a written refusal or cease request, and 1006.6(d) limits communication with third parties. 15 U.S.C. 1692e(11) requires the initial-communication disclosure that the collector is attempting to collect a debt. These are also artificial-voice calls under the TCPA, so prior express consent for mobile numbers applies. In the United Kingdom, FCA CONC 7.3.4R requires forbearance and due consideration for customers in or approaching arrears, CONC 7.9.4R prohibits contact at unreasonable times, and the Consumer Duty adds vulnerability handling. In India, RBI's August 2022 circular says regulated entities and their agents shall not call borrowers before 8 a.m. or after 7 p.m. and shall not intimidate or harass, and TCCCPR puts service calls on the 1600 series with DLT registration, DND scrubbing and a 9 a.m. to 9 p.m. window; where the two windows differ, the narrower one governs. In the Philippines, BSP Circular 1160 prohibits abusive collection and the Anti-Wiretapping Act makes recording without all-party consent a crime. In Australia, RG 96 recommends no more than three contacts a week or ten a month, phone contact Monday to Friday 7.30 a.m. to 9 p.m. and weekends 9 a.m. to 9 p.m., none on national public holidays; where a call includes an offer, the ACMA telemarketing hours of Monday to Friday 9 a.m. to 8 p.m. and Saturday 9 a.m. to 5 p.m. apply. The compliance rows for your regions are listed on this page. They are informational, not legal advice.

Build or buy

Buy a packaged product if you are an agency or a lender on a mainstream collections platform in one market; dialler compliance is hard to build and easy to get wrong. Consider a platform or a build if you operate in several markets with different hours, frequency caps and disclosures, or if your collections platform is bespoke. In both cases the acceptance test is the same: a refused dial in the log at seven of seven, nothing spoken before the right party is verified, a promise with all three fields written only after a yes that code checked, and a cease flag in your own sandbox before the call ends. Ask to see the pre-dial check and the confirmation guard as configuration, not prompt text.