Reg F’s 7-in-7 rule and AI dialers, explained

The 7-in-7 call presumption sounds simple until an AI dialer scales your volume. Here’s what the rule actually says, where it bites, and why cross-channel counting is the part most systems miss.

Regulation F’s call-frequency limit is one of the most misread rules in collections. People remember “seven calls” and stop there. When you put an AI dialer behind it — a system that can attempt far more calls than a human floor ever could — the details of what counts, per what, and over what window become the difference between a clean program and a presumed violation.

What the rule actually presumes

Reg F establishes a rebuttable presumption that you have violated the law if you place more than seven calls to a person in connection with a particular debt within a seven-day period. Two words carry the weight: rebuttable, meaning you can argue the facts, and per debt, meaning the count is tied to the specific debt, not just the phone number or the person in general.

Because it is a presumption, exceeding the threshold does not automatically end the analysis — but you do not want to run a program that lives on the wrong side of it and hope to rebut. The practical target is to stay under the line by design and keep the records that prove you did.

Why AI dialers change the risk profile

An AI voice agent can place, retry, and reschedule calls at a pace that makes frequency mistakes easy to commit and hard to notice. Speed is only an asset if the system counts against the limit before it dials, not after. The moment the dialer treats the cap as a report you read later rather than a gate it enforces up front, volume becomes liability.

• The count must be keyed to the debt, not merely the number or the account holder.
• The seven-day window has to roll continuously, not reset on a fixed calendar.
• Attempts, connects, and reschedules all need consistent, defensible treatment.
• The gate should stop the eighth attempt, not simply log that it happened.

The part most systems miss: other channels

Reg F’s call presumption is only one clock. NYC’s rule, effective January 2027, caps three communications per account per seven days across all channels combined — calls, texts, and more counted together. A dialer that tracks calls in isolation can be perfectly compliant on 7-in-7 and still blow past a cross-channel cap because nothing was keeping a unified ledger.

That is why frequency has to be a shared, account-level ledger rather than a per-channel counter. Teltura keeps exactly that: a compliance ledger tracking consent, disclosure, recording, and cross-channel contact frequency, so the count that governs the next call already includes every channel that reached the consumer.

Treat 7-in-7 as a gate your dialer enforces before it calls, keyed to the debt and counted across every channel — not a number you reconcile after the fact. The unified frequency ledger is what lets AI volume stay compliant.