--- title: "FDCPA & CFPB Regulation F for AI Debt-Collection Voice in 2026" description: "Regulation F mini-Miranda, time-place restrictions, and 7-in-7 call caps apply to AI dialers exactly as to humans. Here is the wording, the call-window math, and the audit trail every voice bot needs in 2026." canonical: https://callsphere.ai/blog/vw8f-fdcpa-cfpb-ai-debt-collection-voice-2026 category: "AI Strategy" tags: ["FDCPA", "CFPB", "Regulation F", "Debt Collection", "Voice AI", "Compliance"] author: "CallSphere Team" published: 2026-03-15T00:00:00.000Z updated: 2026-05-08T17:24:47.438Z --- # FDCPA & CFPB Regulation F for AI Debt-Collection Voice in 2026 > Regulation F mini-Miranda, time-place restrictions, and 7-in-7 call caps apply to AI dialers exactly as to humans. Here is the wording, the call-window math, and the audit trail every voice bot needs in 2026. > Regulation F mini-Miranda, time-place restrictions, and 7-in-7 call caps apply to AI dialers exactly as to humans. Here is the wording, the call-window math, and the audit trail every voice bot needs in 2026. ## What the rule says 12 CFR Part 1006 (Regulation F, the CFPB's implementation of the FDCPA) governs every consumer-debt collector — including AI voice agents. Three pillars: (1) the **mini-Miranda** disclosure on every call ("This is an attempt to collect a debt..."), (2) the **7-in-7 call cap** (no more than 7 calls in 7 days, no further call within 7 days of a phone conversation), and (3) **time-place limits** (no calls before 8 a.m. or after 9 p.m. local time, no calls to known-inconvenient places). New York City's SHIELD rule, effective April 2026, layers stricter language-access and identity-verification disclosures on top. ## What AI voice/chat must do The AI must (a) play the mini-Miranda before any debt content, (b) verify right-party contact before disclosing balance, (c) honor "stop calling" and cease-comm requests in real time, (d) tag every dial against a per-consumer 7-in-7 counter, and (e) log timestamp, disclosure text, and consumer response for the 3-year record retention rule. Best practice in 2026: when asked, the AI must self-disclose as automated and offer a human transfer. ```mermaid flowchart TD A[Inbound or outbound dial] --> B{Within 8a-9p local?} B -- No --> Z[Block · log reason] B -- Yes --> C{7-in-7 cap hit?} C -- Yes --> Z C -- No --> D[Right-party verify] D --> E[Mini-Miranda played] E --> F{Asked 'are you AI?'} F -- Yes --> G[Disclose AI · offer human] F -- No --> H[Continue script] H --> I[Log transcript · disclosure proof] ``` ## CallSphere posture CallSphere runs **37 production agents · 90+ tools · 115+ Postgres tables · 6 verticals · HIPAA + SOC 2 aligned**. The Collections agent ships with a Regulation F template: mini-Miranda is pinned as a non-removable system message, the call-cap counter is a Postgres trigger on `collection_calls`, and every transcript is encrypted at rest with a 7-year retention default. **Pricing: $149 Starter / $499 Pro / $1,499 Scale**, **14-day no-card trial**, **22% recurring affiliate Year 1**. ## Compliance checklist 1. Mini-Miranda recorded as audio asset, not LLM-generated, to guarantee identical wording 2. Per-consumer 7-in-7 counter with timezone-aware reset 3. Cease-comm hotword detector (stop, do not call, attorney) with auto-suppression list write 4. AI self-disclosure path on prompt 5. Transcript + timestamp retained 3 years minimum 6. Quarterly fair-debt audit of 1% sample ## FAQ **Does the 7-in-7 cap reset per phone number or per debt?** Per debt account per consumer, regardless of channel. **Can the AI leave a voicemail?** Yes — Reg F's "limited-content message" carve-out applies, but the message must omit the mini-Miranda and any debt detail. **What about texts?** SMS counts toward the 7-in-7 only if the consumer has consented to text; otherwise it can be a violation. **Does NYC SHIELD apply nationwide?** No — only to consumers physically in NYC, but most collectors apply it to all NY consumers as a safe harbor. **Penalty per violation?** Up to $1,000 statutory + actual damages + attorney fees per consumer; class actions can scale into the millions. ## Sources - CFPB Regulation F (12 CFR Part 1006) - [https://www.consumerfinance.gov/rules-policy/regulations/1006/](https://www.consumerfinance.gov/rules-policy/regulations/1006/) - CFPB Debt Collection Rule FAQs - [https://www.consumerfinance.gov/compliance/compliance-resources/other-applicable-requirements/debt-collection/debt-collection-rule-faqs/](https://www.consumerfinance.gov/compliance/compliance-resources/other-applicable-requirements/debt-collection/debt-collection-rule-faqs/) - eCFR - 12 CFR Part 1006 Regulation F - [https://www.ecfr.gov/current/title-12/chapter-X/part-1006](https://www.ecfr.gov/current/title-12/chapter-X/part-1006) - NYC SHIELD Debt Collection Rule 2026 - [https://www.consumerfinancemonitor.com/2026/03/05/new-york-city-adopts-sweeping-shield-debt-collection-rule-how-it-differs-from-prior-dcwp-rules-and-cfpb-regulation-f/](https://www.consumerfinancemonitor.com/2026/03/05/new-york-city-adopts-sweeping-shield-debt-collection-rule-how-it-differs-from-prior-dcwp-rules-and-cfpb-regulation-f/) - FDIC Fair Debt Collection Practices Act Manual - [https://www.fdic.gov/consumer-compliance-examination-manual/vii-3-fair-debt-collection-practices-act](https://www.fdic.gov/consumer-compliance-examination-manual/vii-3-fair-debt-collection-practices-act) ## Reading "FDCPA & CFPB Regulation F for AI Debt-Collection Voice in 2026" Through a CFO Lens If you handed "FDCPA & CFPB Regulation F for AI Debt-Collection Voice in 2026" to a CFO, the first question wouldn't be "is the model good" — it would be "what does the cost curve look like at 10x volume, and what's the off-ramp if a competitor underprices us in 18 months." That's the actual AI strategy lens, and the deep-dive below is written for that audience rather than for the "AI is the future" pitch deck. ## AI Strategy Deep-Dive: When AI Buys Advantage vs. When It's Just Expense AI buys real advantage in three places: workflows where speed-to-response is the moat (inbound voice, callback windows, after-hours coverage), workflows where 24/7 staffing is structurally unaffordable, and workflows where vertical depth — knowing the language, regulations, and edge cases of one industry — makes a generalist tool useless. Outside those three, AI is mostly expense dressed up as innovation. The cost of waiting is the metric most strategy decks miss. Every quarter without AI in a high-volume customer-contact workflow is a quarter of measurable lost revenue: missed calls, slow callbacks, after-hours leads going to a competitor that picks up. We've seen single-location healthcare and home-services operators recover 15–25% of "lost" inbound volume in the first 60 days simply by eliminating the after-hours and overflow gap. That recovery is the floor of the ROI case, not the ceiling. Vertical AI beats horizontal AI in regulated, language-dense, or workflow-specific environments. A horizontal voice agent that can "do anything" usually does nothing well in healthcare intake or real-estate showing scheduling. A vertical agent that already knows insurance verification, HIPAA-aligned messaging, or MLS workflows ships in days, not quarters. What to measure: containment rate, escalation accuracy, after-hours capture, average handle time, and cost per resolved interaction — not raw call volume or "AI conversations." ## FAQs **What's the smallest pilot that proves fdcpa & cfpb regulation f for ai debt-collection voice in 2026?** In production, the answer is less about the model and more about the workflow wrapping it: the function tools, the escalation rules, and the integration handshakes with CRM and calendar. Pricing is transparent: Starter $149/mo, Growth $499/mo, Scale $1,499/mo, with a 14-day trial that requires no card. The pricing table is the contract — no per-seat seats, no surprise per-minute overage on standard plans. **Who owns fdcpa & cfpb regulation f for ai debt-collection voice in 2026 once it's live?** Total cost of ownership is the line item that surprises buyers six months in — not licensing, but operating overhead. Channels run on one platform: voice, chat, SMS, and WhatsApp. That avoids the typical mistake of buying voice from one vendor, chat from another, and SMS from a third — then paying systems-integration cost to stitch the conversation history together. Compared with a hire (or a 24/7 BPO contract), the math usually clears inside one quarter on contained workflows. **What are the failure modes of fdcpa & cfpb regulation f for ai debt-collection voice in 2026?** The honest failure modes are integration drift (a CRM field changes and the agent silently misroutes), undefined escalation rules (the agent solves 80% but the 20% has no human owner), and prompt rot (the agent works on launch day, drifts in week eight). All three are operational, not model problems, and all three are fixable with the right ownership model. ## Talk to a Human (or Hear the Agent First) Book a 20-minute working session with the CallSphere team — we'll map the workflow, scope a pilot, and quote it on the call: https://calendly.com/sagar-callsphere/new-meeting. Or hear a live agent on the matching vertical first at https://sales.callsphere.tech. --- Source: https://callsphere.ai/blog/vw8f-fdcpa-cfpb-ai-debt-collection-voice-2026