For collections operators running outbound floors: what the CFPB rule actually presumes, which attempts count against the caps, and how to make the dialer enforce it.
How many times can a debt collector call under Regulation F?
Regulation F presumes a violation when a debt collector places more than seven calls within seven consecutive days to a person about a particular debt, or calls within seven days after a telephone conversation about that debt. Seven or fewer creates a presumption of compliance. Both presumptions are rebuttable, and the caps apply per debt, not per consumer.
Two prongs, two presumptions, and a window that rolls.
Regulation F is the CFPB's implementing regulation for the Fair Debt Collection Practices Act, in force since November 30, 2021. The call frequency provision sits at 12 CFR 1006.14(b), and it is built on presumptions rather than hard caps, which matters more than most compliance decks admit.
A debt collector is presumed to violate the prohibition on repeated or continuous calls if it places a telephone call to a particular person, in connection with the collection of a particular debt, either more than seven times within seven consecutive days, or within a period of seven consecutive days after having had a telephone conversation with that person about the debt. The rule treats the day of the conversation as day one of that cooldown. Stay at seven or fewer, and outside the post-conversation window, and the rule presumes compliance instead.
Three details get missed in practice. The window is seven consecutive days, rolling, not a calendar week that resets on a Monday. The count runs per person and per debt, so one consumer with several accounts on the floor means several counters, which we come back to below. And both presumptions are rebuttable, so seven is not a license to dial.
One honest caveat before the detail: this is a summary of what the rule and the CFPB's official interpretations say, not legal advice, and both enforcement posture and state overlays keep moving. Check the current text and involve qualified counsel before hard-coding anything that matters.
The counting unit is the particular debt, and multi-debt files multiply counters, not permission.
The counting unit in 1006.14(b) is the particular debt, defined in the rule as each of a consumer's debts in collection. A consumer with three accounts on your floor carries three separate counters. Read literally, that permits up to 21 presumptively compliant attempts to one person in a week.
Nobody should build to that number. The presumption of compliance only covers harassment claims based solely on call frequency, and the CFPB's FAQs are explicit that it can be rebutted with evidence of intent to annoy, abuse, or harass: calls in rapid succession, the content of earlier conversations, prior conduct toward that consumer. Hammering one household 21 times in a week across three debts is close to a textbook fact pattern for defeating your own presumption. The setups we audit that handle this well cap at debt level for the rule and monitor at person level for the risk.
Two more scope points come straight from the official interpretations and FAQs:
Student loans get their own definition. For student loan debts, a particular debt means all the loans that were serviced under a single account number at the time the collector obtained them. Five loans under one servicing account number is one debt and one counter, not five. Loans acquired under separate servicing accounts keep separate counters, which is why the intake data mapping on student portfolios deserves more attention than it usually gets.
The free Five9 Health Check is 17 questions and takes a few minutes. It covers attempt counting, suppression, disposition mapping, and the other places frequency compliance quietly breaks.
Connected is broader than answered, and narrower than dialed.
The frequency caps track telephone calls placed, and the official interpretations define placed more broadly than most dialer default reports do. A call counts when it connects to the dialed number: answered by a person, answered by voicemail, or simply ringing with no answer. Ringless voicemail drops count too, since the commentary says placing a telephone call includes conveying a ringless voicemail.
| Attempt outcome | Counts toward 7-in-7 |
|---|---|
| Answered by the person | Yes, and a genuine conversation also starts the seven-day cooldown |
| Rings, no answer | Yes |
| Voicemail reached, message left or not | Yes |
| Ringless voicemail drop | Yes |
| Busy signal, or number not in service | No, the call never connected |
| Text message or email | No, the frequency caps cover telephone calls only |
| Inbound call from the consumer | No |
Three exclusions in 1006.14(b)(3) take calls out of the count entirely: calls placed with the person's prior consent given directly to the debt collector (that consent is only good for a maximum of seven days, however long the consumer offered), calls that never connect to the dialed number, and calls to the consumer's attorney and the other professionals listed in 1006.6(d)(1)(ii) through (vi).
The cooldown prong is worded around having had a telephone conversation with the person. A message left in voicemail is a call placed, but operators typically treat only genuine two-way, right-party contact as triggering the seven-day suppression, and build the disposition set so agents can record that distinction cleanly. Texts and emails sit outside the call caps, though they remain covered by the general harassment prohibition in 1006.14(a), and some state rules do count them. Massachusetts does, as covered further down.
Both presumptions can be argued away, in either direction.
Both presumptions can be overturned, and the CFPB's FAQs set out the sort of evidence that does it. A collector inside the caps can still be found in violation where the pattern shows intent to harass: back-to-back calls minutes apart, concentrated bursts, or a history of abusive conduct with that consumer. A collector over the caps can defend the excess in limited circumstances, for example where a call was required by law, returned a consumer's own request, or conveyed urgent information that prevented demonstrable harm.
The practical reading for a dialing operation is that the caps are the floor of the control framework, not the whole of it. Pace, spread, and prior contact history all belong in the QA view alongside the raw count. We treat any file that hits its cap on consecutive rolling windows as a review trigger, because that cadence is legal on paper and hard to defend as anything other than pressure.
Five load-bearing pieces of configuration, and the one failure mode that causes most breaches.
Policy documents do not stop a dialer. Configuration does, and the configuration has five load-bearing parts.
The failure mode that pays our invoices is the list reload. Attempt counters held at campaign or list level quietly reset to zero when the overnight file replaces yesterday's, and the platform will then happily dial a capped account at 8am with a clear conscience. Counts belong in the system of record, keyed to the debt, and either synced back into the dialer's contact history or enforced by dial-time rules that read cumulative attempts. After any migration or list rebuild, the first thing worth checking is whether Monday's attempts still exist on Tuesday. Our note on outbound list strategy covers the wider hygiene, and the collections-specific build is in Five9 for collections.
Regulation F limits how often. The TCPA limits how.
Regulation F governs how often a collector may call. The Telephone Consumer Protection Act governs how the call may be placed. Under 47 U.S.C. 227(b)(1)(A)(iii), calls to a cell phone using an automatic telephone dialing system or an artificial or prerecorded voice require the called party's prior express consent. Collections calls are informational rather than telemarketing, so the working consent standard is prior express consent rather than the written form telemarketers need, and in practice it usually traces back to the consumer having provided the number in connection with the debt.
The Supreme Court narrowed the autodialer definition in Facebook v. Duguid (April 2021): equipment must store or produce numbers using a random or sequential number generator to qualify. That helped, but it did not end litigation over which dialer configurations fall inside the definition, and it did nothing for prerecorded or artificial voice, which stays restricted however the call was launched. This is why collections floors keep non-consented cell numbers off predictive campaigns entirely and run them through human-initiated clicker modes. Five9's TCPA Manual Touch Mode is the platform's version: the relevant lists sit on a separate system with no autodial capacity, and an agent initiates every call. We run floors in both modes daily, and blending them (predictive for consented numbers, manual touch for the rest) is a solved problem when the consent flags in the CRM are trustworthy, and a mess when they are not.
Consent is also now easier to lose. FCC rules effective April 11, 2025 let consumers revoke consent by any reasonable means, including standard words like stop or cancel in reply to a text, and require revocation to be honored within a reasonable time not exceeding ten business days. The further requirement to treat a revocation of one message type as covering all robocalls and robotexts from that caller has been delayed twice, first by a waiver order and then by an extension, and currently sits at January 31, 2027. Worth keeping separate as well: the seven-day call frequency consent in 1006.14(b)(3) is a different animal from TCPA prior express consent, and merging them into one CRM field creates errors in both directions. The interaction with abandonment rules on predictive campaigns is its own topic, covered in our piece on TCPA abandonment rules.
Massachusetts allows two calls in seven days, per debt, and counts texts.
Federal presumptions are the ceiling of leniency, not the national standard. Massachusetts is the sharpest example: under the Attorney General's debt collection regulation, 940 CMR 7.04(1)(f), a creditor may initiate no more than two communications by telephone in each seven-day period to a debtor's residence, cell, or other personal number, and no more than two in each 30-day period at other numbers, for each debt. The Division of Banks imposes the same two-in-seven standard on licensed third-party collectors in its own regulation, 209 CMR 18.16(1)(d), so the limit reaches both first-party and agency floors. The Massachusetts text also counts text messaging and recorded audio messages as initiated telephone communications, which the federal caps do not.
Two in seven versus seven in seven is not a tuning difference, it is a different campaign design. Other states and cities have their own variants at points between the two. The workable pattern is per-state suppression profiles in the dialer: the consumer's state drives which cap applies, and the strictest applicable rule wins where several could. A single national profile set to the federal presumption is an audit finding waiting to be written. State legislatures amend these rules regularly, so the profile table needs a named owner and a review cadence, and questions about what a specific state currently requires belong with counsel rather than a configuration guide.
Presumptions are argued with records, so keep records worth arguing with.
Presumptions are argued with records. If a claim lands, the questions are concrete: how many connected attempts hit this debt in the trailing week, which disposition triggered which cooldown, and what rule permitted each dial. An operation that can answer from logs is in a very different position from one reconstructing events out of agent memory and a CSV export.
The build that stands up is unglamorous. Every attempt stamped with time, number dialed, debt id, disposition, and the rule that allowed it, retained in line with the record retention policy and reconciled monthly against the system of record. In the audits we run, the gap is rarely the policy and usually the plumbing: a counter that did not survive a reload, a disposition added in March that nobody mapped, a state profile still reflecting last year's text. The floors that stay clean treat the frequency engine as production infrastructure with an owner, monitoring, and change control, the same as the telephony itself. If that engine is currently a spreadsheet and good intentions, our managed services team spends a fair amount of its week fixing exactly that.
It is shorthand for the call frequency presumptions in Regulation F, at 12 CFR 1006.14(b). A debt collector is presumed to violate the prohibition on repeated or continuous calls if it places more than seven calls within seven consecutive days to a person about a particular debt, or calls within seven days after a telephone conversation about that debt. Seven or fewer, outside the cooldown, is presumed compliant. Both presumptions can be rebutted with evidence.
Under federal Regulation F, a collector is presumed compliant at up to seven call attempts in any seven consecutive days per debt, and presumed in violation above that or when calling within seven days of a telephone conversation about the debt. The caps apply per debt, so a consumer with multiple debts can lawfully receive more calls in total. Several states are stricter; Massachusetts, for example, limits collectors to two initiated calls per seven-day period per debt.
Yes. The CFPB's official interpretations treat a call as connected, and therefore countable, when it is answered, reaches voicemail, or simply rings without being answered. Ringless voicemail drops also count as calls placed. Attempts that never connect, such as a busy signal or a number not in service, do not count, and neither do inbound calls the consumer makes to the collector.
No. The Regulation F frequency caps apply to telephone calls only, so texts, emails, and social media contacts do not increment the 7-in-7 count. They remain subject to the general prohibition on harassing, oppressive, or abusive conduct, and some state rules do count them: the Massachusetts debt collection regulation treats text messages and recorded audio messages as initiated telephone communications within its two-per-seven-day limit.
Per debt. Regulation F defines a particular debt as each of a consumer's debts in collection, so a consumer with three accounts carries three separate counters. The limit does apply per person across all phone numbers, so calling eight different numbers about one debt still breaches the presumption. A single conversation covering several debts starts the seven-day cooldown for every debt discussed, and heavy calling spread across many debts can rebut the compliance presumption.
Student loans get a special definition. For frequency purposes, a particular debt means all the student loan debts that were serviced under a single account number at the time the debt collector obtained them. A borrower with five loans under one servicing account number is one debt and one counter, not five. Loans acquired under separate servicing account numbers keep separate counters, which makes accurate intake mapping on student portfolios genuinely important.
Often yes, but the TCPA constrains how. Calls to cell phones using an automatic telephone dialing system or a prerecorded or artificial voice require the called party's prior express consent, which for collections usually traces back to the consumer providing the number in connection with the debt. After Facebook v. Duguid narrowed the autodialer definition in 2021, litigation over dialer configurations continues, so collections operations typically dial non-consented cell numbers through human-initiated manual modes rather than predictive campaigns.
No, it is a rebuttable presumption. Seven or fewer calls per debt per week creates a presumption of compliance with the frequency-based harassment prohibition only, and the CFPB's FAQs confirm it can be overcome with evidence of intent to annoy, abuse, or harass, such as calls placed in rapid succession or a pattern of abusive conduct. Equally, a collector who exceeds the caps can rebut the violation presumption in limited circumstances, for example calls required by law.
Yes. A call that reaches voicemail is a connected call and counts toward the frequency caps whether or not a message is left, and the official interpretations say placing a call includes delivering a ringless voicemail. The seven-day cooldown prong is different: it is triggered by having had a telephone conversation with the person, so operators typically configure only genuine two-way contact dispositions to start the cooldown, while every connected attempt increments the counter.
We build and run Five9 collections floors: frequency engines, consent segmentation, manual touch blending, and the audit trail behind them. A dedicated pod, not a ticket queue. Tell us what your floor looks like and we will tell you honestly what needs work.
Talk to us