- Home
- Collections and loan servicing
Compliance audit for every AI collection call: FDCPA, Reg F and TCPA
Loops grades every call your AI agent makes, and your human collectors too, against your collections SOP and the FDCPA, Regulation F and TCPA rules your compliance lead approves. Every verdict quotes the line it relied on.
Live todayon every AI call at three US collection agencies
NDA and DPA before any access · Read-only key or webhook · Never writes to your agent · US data · SOC 2 Type II under NDA · Trust center
One call, graded rule by rule
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 · business named and recording announced in the opening
Customer: Yes, that's me.
Agent: Thanks. Please confirm your date of birth.
Customer: March 4, 1986.
1.2 met · verify_identity returned a match at 00:14
Agent: Your balance with Alder Card is $1,284.16, 94 days past due.
2.3 missed · no debt collector disclosure before the debt
Customer: I can do $107 on the 3rd.
Agent: You're set for $107 on October 3.
4.1 met · log_promise returned success at 00:39
5.2 not checked · call frequency needs your dial log
What the last release changed
The same rules, graded the same way, on live calls from the same weeks, release against release. Rule 2.3 regressed in v14, so Loops listed all 190 calls for remediation; the stop-calling change is too small to call yet.
| Rule | Read | v13 missed | v14 missed | Change | 95% interval |
|---|---|---|---|---|---|
| 1.2 Right party | Improved | 1.4% (163 of 11,640) | 0.8% (94 of 11,720) | −0.6 pts | −0.9 to −0.3 |
| 2.3 Disclosure | Regressed | 0.3% (30 of 10,040) | 1.9% (190 of 10,010) | +1.6 pts | +1.3 to +1.9 |
| 3.2 Payment plan | Improved | 9.8% (417 of 4,260) | 5.1% (221 of 4,330) | −4.7 pts | −5.8 to −3.6 |
| 4.1 Promise logged | Improved | 6.5% (84 of 1,290) | 3.2% (44 of 1,370) | −3.3 pts | −5.0 to −1.7 |
| 4.2 Stop calling | Too close to call | 2.9% (7 of 245) | 6.0% (14 of 232) | +3.2 pts | −0.6 to +7.3 |
Sample data. Intervals are Newcombe score intervals for the difference in miss rates.
What Loops checks on every collection call
You start from this library and your own SOP, and your compliance lead approves each rule beside the text it came from.
| Rule | What passes | Evidence |
|---|---|---|
| 1.1 Opening47 CFR 64.1200(b)(1); 12 CFR 1006.14(g) | The registered business name, one that doesn't signal debt collection, and the recording are announced in the opening | Quoted line |
| 1.2 Right party before any account detailFDCPA §805(b); 12 CFR 1006.6(d) | Identity confirmed, or the verification tool returned a match, before the balance is mentioned | Quoted line and tool-call record |
| 2.3 Debt collector disclosure (third-party collectors)FDCPA §807(11); 12 CFR 1006.18(e)(1), (2) | The full disclosure in the initial communication, and "from a debt collector" in every later one, before the debt is discussed | Quoted line |
| 2.4 Balance12 CFR 1006.18(b)(2)(i) | The stated balance matches what the balance lookup returned on the call | Quoted amount and tool-call record |
| 3.3 Payment authorization12 CFR 1005.10(b) for recurring debits; Nacha rules for phone-authorized ACH | Amount, date, account and how to revoke are read back and recorded before a payment is taken | Quoted line and tool-call record |
| 4.2 Stop calling12 CFR 1006.14(h) | The request is acknowledged, collection talk stops, and it is logged so no later call goes to that number | Quoted line, tool-call record, then your dial log |
| 4.3 Attorney representation12 CFR 1006.6(b)(2) | The agent asks for the lawyer's name and number and stops collecting | Quoted line and tool-call record |
| 4.4 Dispute12 CFR 1006.38 | The dispute is recorded and flagged, and nothing said overshadows the right to dispute | Quoted line and tool-call record |
| 5.1 Calling hours12 CFR 1006.6(b)(1)(i) | The call falls between 8 a.m. and 9 p.m. in every time zone the consumer may be in | Call time, the account's address and every number's area code |
| 5.2 Call frequency12 CFR 1006.14(b)(2) | Within Reg F's presumption: at most 7 calls in 7 days, and none in the 7 days after a conversation, per person and per debt | Your dial log |
| 5.4 State call capse.g. Massachusetts, 940 CMR 7.04(1)(f) and 209 CMR 18.16(1)(d) | Calls stay within the stricter limit of the consumer's state, such as two in seven days in Massachusetts | Your dial log and the account's address |
| 6.1 Voicemail12 CFR 1006.2(j) | Messages stay within the limited-content message unless no one else can hear them | Transcript of the message |
| 6.2 Consent for an AI-voice call47 U.S.C. §227(b); FCC 24-17 | Consent on file for calls to wireless numbers; residential calls within the exemption, with the opt-out | Your consent records |
Rules that span several calls, like call frequency and consent, need your dial log and consent records. Without them Loops grades what happens inside each call and marks those rules as not checked, never as passed.
Your first 30 days
- Day 0: connect. Sign the NDA and DPA, connect your platform with a read-only key or a webhook, and send your SOP. Add your dial log and consent records so frequency and consent get checked, and a daily payments file if you want dollars in the report.
- Days 1 to 2: approve the rules. Your compliance lead reviews each rule beside the SOP text it came from.
- Within 72 hours: the first audit. Last month's calls, graded rule by rule, with the evidence for every verdict.
- Day 30: your report. Yours to keep, including how often Loops agreed with your reviewers. Nothing renews on its own.
What your compliance lead gets
- Every verdict with the quoted line, the tool-call record, the rule version and who approved it, and the grader version.
- Calls a transcript can't settle, marked for review instead of guessed.
- Each rule's miss rate, this release against the last, on live calls, with the calls behind any change.
- Your human floor graded on the same rules, on the same screen.
- Exports as PDF or CSV for an examiner or a client auditor, and verdicts by API for your compliance log.
Guides for collections teams
Questions
Does Loops replace our compliance review?
No. Your compliance lead approves every rule before anything is graded, your reviewers can overturn any verdict, and the day-30 report measures how often Loops agreed with them on your own calls. Loops makes review cover every call instead of a sample; the judgment stays with your team.
Is sending our calls to Loops a third-party communication under the FDCPA?
The FDCPA bars discussing a debt with third parties (15 U.S.C. 1692c(b); 12 CFR 1006.6(d)). In 2021 an Eleventh Circuit panel held in Hunstein v. Preferred Collection that sending consumer data to a letter vendor could be one; in 2022 the full court dismissed the case for lack of standing without deciding that question. Loops receives your calls only as your service provider under a signed DPA, uses them only to grade them for you, never contacts a consumer, and deletes them on the schedule you set. Your counsel makes the call, and we will answer their questions in writing.
Can Loops check Reg F's call frequency limit?
Yes, when you send your dial log. Frequency depends on every attempt to reach the consumer about a debt, not just the calls your AI agent completed, so Loops needs the log to count them. Without it, the rule is marked not checked rather than passed.
Do our human collectors get graded too?
Yes. Send recordings from your human floor by upload or SFTP and they are graded against the same rules as your AI agent, on the same screen, so you can compare the two fairly.
What can we hand an examiner or a client auditor?
For any call, account or date range: each rule's verdict, the quoted line, the tool-call record, the rule version and who approved it, the grader version, and any reviewer override with who made it and when. It exports as PDF or CSV.
General information, not legal advice. Rule citations are to the FDCPA (15 U.S.C. §1692 and following), Regulation F (12 CFR part 1006), the TCPA and the state rules named. Sample calls and figures are illustrative.