Back to Insights
    Debt Collection

    The Velocity Violation: Litigating Regulation F's '7-in-7' Call Restriction

    By Rene McNulty, Esq. May 11, 2026 6 Min Read

    If a debt collector has been calling you multiple times a day, or has continued calling within days of a conversation in which you spoke with them about the debt, federal regulation may have been violated. Regulation F, the Consumer Financial Protection Bureau's rule implementing the Fair Debt Collection Practices Act, sets a specific numeric threshold for collection calls — and exceeding that threshold creates a presumption of harassment under federal law. The analysis below explains how the 7-in-7 rule works, why collection agencies systematically breach it, and what evidence proves a violation. For a broader overview of your FDCPA rights and a tool to track collector communications against federal limits, see our Know Your Rights: Debt Collection Harassment page.

    Telephone harassment under the FDCPA has historically been litigated against a "harassing, oppressive, or abusive" standard under 15 U.S.C. § 1692d — a behavioral test that often turned on subjective characterizations of collector conduct. The CFPB's Regulation F, codified at 12 C.F.R. § 1006.14, added a concrete numeric framework on top of that standard. The rule does not replace the § 1692d behavioral test; it supplements it with a quantitative trigger that shifts the analytical burden.

    What Does the 7-in-7 Rule Actually Prohibit?

    Under 12 C.F.R. § 1006.14(b)(2), a debt collector is presumed to have violated the FDCPA's harassment prohibition if, with respect to a particular debt, the collector places a telephone call to the consumer:

    • More than seven times within seven consecutive days; or
    • Within seven consecutive days after having had a telephone conversation with the consumer about that debt.

    The structure is a rebuttable presumption — calls that exceed the threshold are presumed to violate § 1692d, though the collector may attempt to rebut the presumption with evidence of the circumstances. Calls that fall below the threshold are not automatically lawful; they may still violate the broader § 1692d harassment standard if the surrounding circumstances make them harassing. The rule clarifies and quantifies one path to liability; it does not exhaust the FDCPA's harassment framework.

    Why Do Collection Agencies Routinely Cross the Threshold?

    Third-party debt collection is a volume-driven industry that relies on predictive dialing algorithms and omnichannel Customer Relationship Management (CRM) software. These systems are designed to maximize connection rates, and the engineering tradeoffs that maximize connections often produce regulatory breaches. Three common operational failure modes account for most violations:

    • Multi-number saturation. The dialer algorithm simultaneously contacts a consumer's mobile, home, and work numbers, rapidly exhausting the seven-call limit within days even though the calls to any single number remain modest.
    • Account cross-contamination. When a consumer has multiple accounts placed with the same agency (for example, three separate medical bills), the CRM may fail to suppress the dialer at the consumer level, producing dozens of calls per week across what appear to the consumer as a single contact relationship.
    • Disposition lag. A human agent completes a telephone conversation with the consumer but fails to properly code the call disposition in the CRM. The software does not register that the conversation occurred, and the dialer continues to contact the consumer in violation of the seven-days-after-conversation prong.

    None of these are deliberate decisions to violate the rule. They are operational features of automated collection infrastructure. The FDCPA, as enforced in the Eighth Circuit, treats violations as strict in the sense that intent is not an element — and the § 1692k(c) bona fide error defense available to collectors requires proof that the violation resulted from an isolated clerical mistake despite procedures reasonably adapted to avoid the specific error. A systemic failure to program an automated dialer for § 1006.14(b)(2) compliance is a procedural defect, not a bona fide error.

    What Evidence Establishes a 7-in-7 Violation?

    Effective claims under § 1006.14(b)(2) rest on a clean evidentiary record. The strongest cases combine two parallel data streams:

    • The consumer's records — phone records from the consumer's carrier (cell phone bills, screenshots of recent call logs, voicemail records), supplemented by personal notes of the date and substance of any telephone conversation with the collector.
    • The collector's records — dialer logs, telephony metadata, CRM call disposition records, and account-level contact histories obtained through litigation discovery.

    Cross-referencing the two data streams typically resolves any factual dispute about whether a call occurred, when it occurred, and whether the call was preceded by a qualifying telephone conversation. Where the consumer's carrier records and the collector's own dialer records both show a threshold breach, the rebuttable presumption is difficult for the collector to overcome.

    The FDCPA provides for actual damages, statutory damages, and fee-shifting under 15 U.S.C. § 1692k where a violation is established.

    Midwest Consumer Law PLLC handles FDCPA harassment matters in federal court.


    Legal Disclaimer: The insights and analysis provided in this publication are intended for educational and informational purposes only and do not constitute legal advice. Reading this article, or submitting information through this website, does not create an attorney-client relationship with Midwest Consumer Law PLLC. Every legal matter is unique, and prior results do not guarantee a similar outcome. If you believe your rights under the Fair Debt Collection Practices Act or other consumer protection statutes have been violated, you should seek the counsel of a qualified attorney to discuss the specific facts of your case.

    Free Case Review