Reg F for Collection Firms and Agencies: The 2026 Compliance Field Guide

First, who is the debt collector here?

The FDCPA defines debt collector in §1692a(6), with fact-specific branches and exclusions. Heintz v. Jenkins, 514 U.S. 291 (1995), confirms that attorneys are not categorically exempt merely because collection occurs through litigation. Agencies and firms should analyze their regular business, the owner of the debt, default timing, authority, communications, and jurisdiction with counsel rather than relying on a product label.

That framing matters because compliance risk in a collection practice does not distribute evenly. It concentrates in three places: contacting a consumer your file says is represented, missing the validation-notice clock, and continuing contact after a cease-communication request. Each is mechanical. Each is provable from your own records. And each is the kind of violation a consumer attorney can spot in a single document request.

The attorney-representation firewall: §1692c(a)(2)

Under §1692c(a)(2), a debt collector may not communicate with a consumer about a debt when the collector knows the consumer is represented by an attorney with respect to that debt and knows, or can readily ascertain, the attorney's name and address. The exceptions are narrow: the attorney fails to respond within a reasonable period, the attorney consents to direct contact, or the consumer initiates the communication.

On paper this is simple. In practice it fails at the seams between systems:

• The representation letter arrives in one channel and the outreach runs in another. A fax to the office, a letter to a P.O. box, a note taken on a call: if the flag does not reach the system that sends the next message, the next message goes out.
• Representation is per debt, not per person. A consumer can be represented on one account and not another. A person-level flag over-blocks; no flag under-blocks; the correct unit is the account.
• Staff turnover erases tribal knowledge. The negotiator who took the representation call knows; the colleague covering the desk next week does not.

The structural fix is a pre-send check: every outbound message is evaluated against the representation and cease-communication marks on the account at send time, before it leaves, in every channel. In the Debt Digest workspace that check is built into how outbound behaves: a send that hits a representation or cease mark is blocked, and the blocked attempt is logged with the reason, so your compliance lead can see what the firewall stopped and why. The evidence that your firm honors §1692c(a)(2) stops being a training assertion and becomes a queryable log.

The validation notice: §1692g timing and content

Section 1692g(a) requires that, within five days after the initial communication with a consumer, the collector send a written validation notice, unless the required information was contained in the initial communication or the consumer has paid the debt. The notice must state:

Reg F §1006.34 then specifies the validation information in operational detail: the itemization date, the itemization of the current amount of the debt (interest, fees, payments, and credits since the itemization date), and the consumer-response information. Model Form B-1 provides a safe harbor for content and format; deviating from it is permitted but shifts the burden of proving the notice was clear and conspicuous back onto you.

Two operational points that generate findings:

• The five-day clock runs from the initial communication, whatever the channel. A voicemail that qualifies as a communication starts it. If your intake process and your notice generation live in different systems, the clock can start before anyone is watching it.
• A timely written dispute freezes collection. Under §1692g(b), if the consumer disputes in writing within the 30-day window, collection must cease until verification is mailed. The dispute flag has to reach every channel that could otherwise send, immediately, not at the next batch sync.

Documenting cease-communication requests: §1692c(c)

Under §1692c(c), when a consumer notifies a collector in writing that they refuse to pay or want communication to stop, the collector must stop, with three narrow exceptions: to advise that collection efforts are being terminated, to notify the consumer that specified remedies may be invoked, or to notify the consumer that a specific remedy will be invoked.

The violation pattern is rarely a collector who ignores the letter. It is a cease flag that stops the dialer but not the email template, or a request logged in the notes field of a system that outbound never reads. Documentation practice that survives scrutiny looks like this:

• Record the request the day it arrives, with the date received, the channel it arrived on, and an image or content hash of the writing itself.
• Propagate the flag to every outbound channel at once. Calls, letters, email, portal messages: one mark, all channels, no per-channel toggles that can drift.
• Log every blocked attempt. A record showing your system refused sends after the request date is affirmative evidence, not just an absence of complaints.
• Keep the exception communications inside the same thread, so a termination notice or remedy notice is timestamped against the cease date it follows.

In the Debt Digest workspace, the cease mark and the representation mark ride the same pre-send firewall, and every negotiation round, notice record, and blocked send lands on one timestamped account timeline. One click prints the matter file: contact history, every negotiation round, and notice records with content hashes. The same artifact answers a creditor client, an examiner, or a court.

The call-frequency caps: Reg F §1006.14(b)

Reg F §1006.14(b) presumes a violation when a collector places more than 7 telephone calls to a consumer about a particular debt within a rolling 7-day window, or places any call within 7 days of having had a telephone conversation about that debt. The counting unit is the individual debt, not the consumer; voicemails count as calls; and the window rolls rather than resetting weekly. If your practice leans on phone-heavy workflows, your call-attempt counter has to be per debt and per rolling window, or you are estimating your own exposure.

One reason bilateral, portal-based negotiation keeps gaining ground in collection practices: a consumer who proposes and counters in writing, on their own schedule, is a file that resolves without pressing against the call caps at all.

Where role-aware workflow software fits

A software relationship does not transfer, shrink, or erase a participant’s legal duties. What it can change is the enforcement surface. Approved mechanical rules belong in software:

• The workspace behaves like the statute reads. Representation and cease marks gate outbound at send time. Below-floor settlement offers route to the creditor for review instead of slipping through. Every round of offer, counter, and accept is timestamped as it happens.
• The evidence assembles itself. The audit log is the timeline; the matter file is one click; notice records carry content hashes. Discovery, an examiner inquiry, and a creditor client report are the same export.
• Your book performance is visible in the same terms your creditor clients use at review time: resolution rate, liquidation by placement month, median days to resolve.

And because Debt Digest is infrastructure rather than a competing collector, the economics are flat: a per-seat monthly subscription, never a percentage of recovery, so the platform has no stake in how any individual account resolves.

What a demo engagement looks like

Firms and agencies evaluating the workspace usually want to see the compliance behavior with their own eyes before putting real placements on it. The standard sequence:

• A 30-minute walkthrough of the workspace against your current settlement workflow: intake to offer to counter to acceptance to the printed matter file.
• A sandbox demo with sample accounts, so your compliance lead can watch the pre-send firewall block a send on a represented account and inspect the log entry it leaves.
• A pilot at no platform fee, on a defined slice of your book, with the same audit trail from day one.
• A flat per-seat subscription after the pilot. Firms from $300 per seat per month; agencies from $200 per seat per month. The bill never keys to recovered dollars.
• Onboarding measured in weeks, not quarters. The onboarding path is designed to run from first call to first settled account in about two weeks.

Collection agencies: the same workspace, scoped to agency workflows, is covered on the agency overview.