Debt collection calling playbook for compliant call blocks

What this playbook covers, and what it refuses to do

This playbook organizes collection calling around one premise: the agency’s compliance controls exist first, and the dialer’s job is to execute them without improvisation. It covers the released-account pipeline, block structure, same-day routing, third-party and voicemail discipline, dispositions, and KPI ranges. It refuses to pretend the tool computes frequency rules or validates debts; those are the agency’s duties under 12 CFR 1006 and 15 U.S.C. 1692.

The released-account pipeline

Nothing dials without a release. The compliance team screens each portfolio against current contact counts, cease and dispute flags, deceased and representation statuses, and state licensing, then releases a queue with those facts attached. Hygiene rules the block inherits:

• The dialer’s list mirrors the release exactly; rows removed by compliance disappear the same hour.
• Internal do-not-call suppression runs before every block, and consumer-stated contact constraints override defaults.
• The contact ledger computes the 7-in-7 frequency presumption of 12 CFR 1006.14(b)(2)(i) per consumer per debt, with the exclusions of 1006.14(b)(3), and the block only dials rows the ledger cleared.
• TCPA wireless restrictions at 47 CFR 64.1200(a)(1) apply on top; the release process flags wireless numbers for the treatment the agency’s policy and counsel require.

Call block structure

Morning block, 9:00 to 11:00 consumer-local. Released accounts, fresh attempts inside the assumed convenient window of 8 a.m. to 9 p.m. per 12 CFR 1006.6(b) and 15 U.S.C. 1692c(a).

Afternoon block, 1:00 to 3:00. Callbacks the consumer requested, worked inside their stated windows with the prior note on screen.

Late block, 5:00 to 7:00. Working consumers unreachable during the day; still inside the window, still inside the ledger.

One connect at a time. A second line lighting mid-call is parked with the callback promise and dialed from the queue; a collection call is never rushed toward the next ring.

Same-day routing

Three items move to servicing the same day, every time, with the recording as evidence:

• Cease requests under 15 U.S.C. 1692c(c): suppress in the dialer immediately, record the wording, confirm in writing where the agency’s process requires.
• Disputes under 12 CFR 1006.38: log the disputed amount and the consumer’s words, stop arguing on the phone, let the written process run.
• Validation requests under 15 U.S.C. 1692g and 12 CFR 1006.34: route to the notice process, and note that the request was made so the timeline is provable.

The day a routing slips is the day the recording stops being protection. Same-day completion is reviewed as a KPI, not a hope.

Third-party and voicemail discipline

Third-party calls are one sentence deep: identity, from-a-debt-collector disclosure, and a request to reach the consumer or leave a callback, per 12 CFR 1006.6(d), 15 U.S.C. 1692c(b) and the location limits of 1692b. The moment identity is in doubt, the call ends. Voicemails read the approved limited-content script only: collector identified, callback requested, no account details, because a voicemail can be heard by anyone.

Dispositions and what they mean

• Promise to pay / Payment plan: dated, specific, inside the approved options, confirmed in writing where the agency’s process requires.
• Paid: verified through the agency’s system, never assumed from a verbal claim alone.
• Validation requested / Disputed: routed same day; the account’s treatment now runs on the written process.
• Cease request / Do not call: suppressed immediately, routed, recorded.
• Wrong party: logged and routed the same hour; pressing a wrong consumer is the category’s most expensive mistake.
• Unable to reach: attempt counts logged so the ledger stays honest.

The three-line workflow and AI summaries

Three lines fit collection work only when connects get full presence. The AI summary carries the identity confirmation, the convenience check, the disclosure given, the consumer’s statements in their words, the routing completed and the next step. It exports to the contact ledger the same day; the ledger is the compliance system of record, and the summary is its freshest input. Recording disclosure runs wherever all-party consent applies.

KPI targets

Ranges against production reference points. In production use across 3-line sessions over 90 days, the median operator ran about 85 dials per active hour and roughly 600 dials per operator day, with person connects around 17.8 percent. Planning ranges for collection blocks:

• Dials per active hour: 60 to 90; released queues with live numbers run at the top.
• Right-party contacts: 8 to 18 percent of dials on aged portfolios; judge blocks on this, not raw dials.
• Resolution rate on right-party contacts: 15 to 30 percent producing a promise, plan or payment.
• Same-day routing completion: 100 percent, no exceptions, no average.
• Frequency exceptions: zero, computed by the ledger, verified weekly.

These figures are measured in production use, 3-line sessions, 90 days; they are reference points, not a promise of results.

Counsel review notice

Collection is a counsel-review-first category: the agency’s compliance program owns the contact ledger, frequency tracking, validation and dispute processes, state licensing and script approval, and counsel reviews all of it. This guide describes rules, not compliance advice, and no block runs on a list the compliance team has not released.

Compliance in one paragraph

Regulation F presumes compliance with the harassment prohibition under the 7-in-7 rule of 12 CFR 1006.14(b)(2)(i) with exclusions in (b)(3); times and places are limited by 12 CFR 1006.6 and 15 U.S.C. 1692c(a); third-party contacts by 1006.6(d) and 1692c(b), with location information under 1692b. Validation runs under 1692g and 1006.34; disputes under 1006.38; harassment and false representations prohibitions under 1692d and 1692e; cease requests under 1692c(c). TCPA wireless restrictions at 47 CFR 64.1200(a)(1) apply on top, and state collection, licensing and all-party recording rules vary. A dialing tool does not maintain the compliant contact ledger, apply the frequency rules, generate validation notices or decide who may be contacted.