Telephone-frequency compliance cannot be managed reliably with a daily dial count. Regulation F evaluates calls to a particular person about a particular debt across rolling seven-day windows and also addresses calls after a telephone conversation. A collection platform therefore needs account-level history, clear exclusions, and a decision recorded before every dial.

This educational guide explains how recovery teams can turn the federal rule into an auditable workflow. It is not legal advice, and state law, consent, account type, and the facts of a communication may create additional requirements. Kaizen's Recovery Suite centralizes account activity and communication workflows so teams can apply their approved policies consistently.

Understand the two federal frequency presumptions

Under 12 CFR 1006.14, subject to specified exclusions, a debt collector is presumed to violate the repeated-call prohibition if it places more than seven calls within seven consecutive days to a particular person about a particular debt, or places a call within seven consecutive days after a telephone conversation with that person about that debt. The date of the conversation is the first day of the second period.

Staying below those frequencies creates only a presumption concerning frequency. It does not make the content, time, place, cumulative conduct, or other circumstances automatically compliant.

Choose the correct counting key

The control should associate every attempt with the person, debt, number dialed, time, channel, campaign, and outcome. Counting only at the phone-number level can miss attempts to the same person across numbers. Counting only at the consumer level can combine separate debts incorrectly. Preserve both the operational identity and the rule-specific debt relationship.

Use a rolling window, not a calendar week

A Monday-to-Sunday report is insufficient because any call may create a new seven-consecutive-day window. Before a dial, calculate qualifying calls in the relevant lookback period and check whether a conversation has opened a post-conversation period. Perform the decision at execution time, not only when a campaign list is built.

Classify every outcome consistently

• unanswered call;
• busy, failed, or disconnected attempt;
• limited-content message;
• other voicemail;
• conversation with the consumer;
• conversation with another person;
• wrong number confirmed;
• consumer-initiated callback;
• call placed with qualifying direct prior consent;
• call required by or responding to a specific consumer request.

Outcome labels must have written definitions, representative training, and quality review. A generic “contact” code is too ambiguous to drive the next-call decision.

Model exclusions as evidence-backed events

Section 1006.14 describes calls excluded from the frequency calculations, including certain calls placed with prior consent given directly to the collector for a limited period. Do not represent an exclusion as a permanent account flag. Store who gave consent, to whom, for which debt, the scope, the time received, the permitted period, any revocation, and the call that used it.

Coordinate every dialer and manual call

The count must include qualifying calls from predictive dialers, preview campaigns, representatives, supervisors, vendors, and other integrated systems. Reserve the right to dial centrally or update the account timeline immediately. Two systems reading yesterday's count can each approve a call that the combined history should block.

Handle multi-debt and multi-party accounts deliberately

Define how the policy treats a single conversation covering multiple debts, joint consumers, authorized representatives, and numbers shared with third parties. These scenarios require a documented interpretation and sometimes human review. Do not let campaign configuration make the legal determination silently.

Build preventive and detective controls

• pre-dial eligibility check with a recorded reason;
• automatic suppression when a threshold or conversation window applies;
• supervisor workflow for ambiguous identity or consent;
• daily exception report for late-arriving calls;
• reconciliation across dialer and account histories;
• alerts for repeated overrides or missing outcomes;
• sample review of excluded calls and conversation coding.

Pair these controls with the broader omnichannel workflow so a blocked call does not trigger an inappropriate message on another channel.

Conclusion

A defensible call-frequency control is a real-time decision system built on accurate identities, rolling windows, conversation outcomes, and evidence for every exclusion. Centralize the history, stop conflicting dialers, and review exceptions before they become patterns. Explore Kaizen Recovery Suite or contact Kaizen to discuss communication controls.

Frequently asked questions

Does seven calls mean seven calls per week?

No. The federal presumption uses seven consecutive days and applies in relation to a particular person and particular debt, subject to exclusions.

Does a limited-content voicemail count as a call?

The act of placing the telephone call generally matters for frequency; teams should review the rule and its exclusions with qualified counsel.