Governed AI for Debt Collection

By Jeffery Hartman — entrepreneur, builder, and deal maker in receivables (known as “The Don of Debt”) | Category: AI & Fintech Automation | Published: 2025-11-12 01:39:25

Let’s be direct. In debt collection, an AI proposal that cannot be documented, tested, and reviewed creates an operational-risk question—not a promise of compliance or recovery results.

My approach is evidence first: define the intended use, establish controls, and validate any pilot before I describe a result. This article does not make a product-performance, legal-compliance, or ROI guarantee.

The Core Principle: Compliance-First AI

For any prospective deployment, I would start with a written governance plan identifying the intended use, data inputs, decision boundaries, human-review points, test records, incident escalation, and change control. The NIST Artificial Intelligence Risk Management Framework (AI RMF 1.0) (reviewed October 8, 2026) is a voluntary, non-sector-specific risk-management resource; it is not a legal safe harbor, a certification, or validation of a particular system.

For debt collectors as defined in the FDCPA, CFPB Regulation F (reviewed October 8, 2026) establishes federal rules for collection activities. Its electronic-communication rule requires a clear and conspicuous statement of a reasonable and simple opt-out method for the address or number used. CFPB § 1006.6 (reviewed October 8, 2026) Separate FCC delivery restrictions can apply to particular calls or texts. 47 CFR § 64.1200, Delivery restrictions (reviewed October 8, 2026) Applicability depends on the entity, communication, technology, consumer facts, jurisdiction, and applicable state law; qualified counsel should review the design before deployment.

How I Would Measure a Pilot

I would not promise an RPC increase, liquidation lift, complaint-rate reduction, QA-error reduction, or other KPI result in advance. Any comparison needs a written, dated protocol that states the eligible population, baseline, numerator, denominator, geography, reporting period, data source, exclusions, attribution method, and validation limits. Those details are not supplied in this article.

Any commercial commitment must be stated in a signed agreement after the parties agree on the protocol, remedies, and exclusions; performance, compliance, and collection outcomes remain fact-dependent.

The Bottom Line

I do not treat an AI tool as a substitute for documented controls, testing, legal review, or accountability. The appropriate approach depends on the collector, portfolio, communication channel, technology, jurisdiction, and facts at hand.

Schedule an AI-in-Collections Strategy Session

Schedule an AI-in-Collections Strategy Session

Related Strategic Briefings

Discuss Portfolio Valuation & Liquidity

Looking to structure a portfolio sale or optimize recovery yield? Schedule a strategic call with Jeffery Hartman or test our Portfolio Recovery Valuation Tool.