Seven Calls in Seven Days: What Reg F Actually Says About Call Frequency

Reg F's 7-in-7 call frequency presumptions in the CFPB's own words: what counts as a call, per-debt counting, exclusions, and how NYC's 3-in-7 rule differs.

//

Compliance and Regulation

//

11 min read

Key takeaways

  • The CFPB's FAQs say "The Debt Collection Rule does not impose a specific 'limit' or 'cap' on the frequency of telephone calls."

  • Under 12 CFR 1006.14(b)(2), a debt collector is presumed to comply if it calls a particular person about a particular debt no more than seven times in seven consecutive days, and not within seven consecutive days after a telephone conversation about that debt.

  • Official comment 14(b)-1 says "placing a telephone call" "includes conveying a ringless voicemail" and "does not include sending an electronic message (e.g., a text message or an email)."

  • Section 1006.14(b)(4) defines "particular debt" as "each of a consumer's debts in collection," so the count runs per debt, not per person.

  • Per the NYC DCWP FAQ, the city's SHIELD Rule limits communications "across all media," excluding mailed letters, to three per distinct consumer account in a seven-day period, starting Jan 1, 2027.

Status as of Tuesday, Oct 27, 2026, CT: The text quoted below is the eCFR version of 12 CFR Part 1006 current as of Oct 23, 2026. NYC's SHIELD Rule amendments take effect Jan 1, 2027, per DCWP's FAQ dated Oct 22, 2026. We'll update this line if either changes.

The short version. Regulation F doesn't set a hard cap on collection calls. In the CFPB's words, "The Debt Collection Rule does not impose a specific 'limit' or 'cap' on the frequency of telephone calls." What it sets instead is a pair of presumptions in 12 CFR 1006.14(b)(2): a debt collector is presumed to comply if it calls a particular person about a particular debt no more than seven times in seven consecutive days, and not within seven consecutive days after a telephone conversation about that debt. Calls beyond either frequency are presumed to violate the rule. Both presumptions can be rebutted, ringless voicemails count as calls, texts and emails aren't counted as calls, and the counting runs per debt, not per person.

Who this is for

Written for owners, operators, and compliance leads at collection agencies, debt buyers, law firms that collect, and the lenders and vendors that work with them, plus anyone building or buying software that places collection calls.

On scope, the regulation speaks for itself. 12 CFR 1006.1(c)(1) says "this part applies to debt collectors, as defined in Sec. 1006.2(i), other than a person excluded from coverage by section 1029(a) of the Consumer Financial Protection Act of 2010." The definition of "debt" at 1006.2(h) covers obligations arising from transactions "primarily for personal, family, or household purposes." Our Debt Collector (FDCPA) entry quotes the full definition and its exclusions. Whether a particular team or portfolio falls inside those lines is the kind of question teams often review with their compliance team or counsel.

Somewhere in every collection shop there's a dashboard tile that says "Attempts: 7/7." It looks like a speed limit. The regulation it comes from reads more like a rebuttable presumption with a lot of footnotes, and the footnotes are where the counting gets interesting.

What the rule says, in its own words

The prohibition comes first. Section 1006.14(b)(1) says a debt collector "must not place telephone calls or engage any person in telephone conversation repeatedly or continuously with intent to annoy, abuse, or harass any person at the called number." That tracks the 1977 statute, 15 U.S.C. 1692d(5), which lists "Causing a telephone to ring or engaging any person in telephone conversation repeatedly or continuously with intent to annoy, abuse, or harass any person at the called number."

Then the presumptions. Under 1006.14(b)(2)(i), a debt collector is presumed to comply with (b)(1) "if the debt collector places a telephone call to a particular person in connection with the collection of a particular debt neither:

(A) More than seven times within seven consecutive days; nor

(B) Within a period of seven consecutive days after having had a telephone conversation with the person in connection with the collection of such debt. The date of the telephone conversation is the first day of the seven-consecutive-day period."

And the flip side, 1006.14(b)(2)(ii): a debt collector is presumed to violate (b)(1) if it places calls "in excess of either of the telephone call frequencies."

The CFPB's FAQs call these the "call frequency prong" and the "conversation frequency prong," and describe the window as "seven consecutive calendar days."

What counts as a call

This is where an attempt counter and the rule can drift apart.

  • Ringless voicemail counts. Official comment 14(b)-1: "'placing a telephone call' includes conveying a ringless voicemail but does not include sending an electronic message (e.g., a text message or an email) that may be received on a mobile telephone."
  • Unconnected calls are excluded. Section 1006.14(b)(3)(ii) excludes calls "Not connected to the dialed number." Comment 14(b)(3)(ii)-1 says a call connects if it's answered (even if it drops), if it rings unanswered, or if it reaches voicemail. A busy signal or a not-in-service message doesn't connect.
  • Wrong numbers drop out. Comment 14(b)(2)(i)-3 says that if a collector calls a number during a seven-day period and then learns the number isn't that person's, those calls "are not considered to have been telephone calls placed to that person during that seven-consecutive-day period." The CFPB's FAQs cover misdirected calls too.

So a call that rings eight times and nobody picks up is a call. A call that hits a fast busy isn't. A dialer that logs both as "attempts" and a rule that counts only one of them will produce two different numbers.

The exclusions

Section 1006.14(b)(3) lists three kinds of calls excluded from the frequencies:

  1. Calls "Placed with such person's prior consent given directly to the debt collector and within a period no longer than seven consecutive days after receiving the prior consent." Comment 14(b)(3)(i)-2 says consent expires when a shorter period the person gave has ended, when the person revokes it, or when the collector "has a telephone conversation with the person regarding the particular debt."
  2. Calls "Not connected to the dialed number."
  3. Calls "Placed to the persons described in Sec. 1006.6(d)(1)(ii) through (vi)," which is the consumer's attorney, a consumer reporting agency, the creditor, the creditor's attorney, and the debt collector's attorney.

Per debt, not per person

Section 1006.14(b)(4) says "particular debt means each of a consumer's debts in collection," with a separate provision for student loans serviced under a single account number. The official interpretation's example is blunt about what that means: comment 14(b)(4)-2.i describes a collector placing 21 unanswered calls to one consumer across three debts, seven per debt, within seven days, and says that pattern is presumed to comply. The next example, comment 14(b)(4)-2.ii, says a limited-content message left on a call meant to discuss two debts may be counted "as one telephone call placed toward either of the particular debts."

The CFPB's Ask CFPB page puts the student loan wrinkle this way: "in the case of student loan debt, depending on the facts, multiple debts could be counted together as one 'particular debt,' so the limits would apply to those debts as a group."

A presumption, not a ceiling

Both presumptions can be rebutted. Comment 14(b)(2)(i)-2 lists facts that could rebut the presumption of compliance, including "two unanswered telephone calls to the same telephone number within five minutes" and "seven telephone calls to the same telephone number within one day." Other listed factors include the pattern of voicemails, the content of the person's prior communications, and the collector's prior conduct. The comment also says that "it is assumed that debt collectors intend the natural consequence of their actions."

The Ask CFPB page gives the consumer-facing version: "if the debt collector placed seven calls to you about a debt within a seven-day period, but all seven calls were made on the same day, they could be violating the law."

Going the other way, comment 14(b)(2)(ii)-2 lists facts that could rebut the presumption of a violation, among them calls required by other law (the comment's example is a mortgage servicer's early intervention calls under Regulation X, 12 CFR 1024.39(a)), calls during active litigation, a consumer's request for information, and time-sensitive situations such as a dropped call during settlement talks.

Texts, emails, and the cumulative picture

The 7-in-7 counts are about telephone calls. Comment 14(b)(1)-1 says a collector that complies with 1006.14(b)(1) complies with the broader harassment prohibition "solely with respect to the frequency of its telephone calls." The Ask CFPB page says the presumptions "only apply to telephone calls placed by the debt collector to you and don't apply to other forms of communication, including text messages, emails, in-person interactions, or social media messages, which have other protections."

That isn't the end of the channel question, though. Comment 14(a)-2 says whether conduct is harassing "may depend on the cumulative effect of the debt collector's conduct through any communication medium." Its example is a collector that places seven unanswered calls in seven days, within the presumption, and also sends "multiple additional unsolicited emails." The comment's conclusion: "It nevertheless is likely that the cumulative effect of the debt collector's telephone calls and emails is harassment."

Other parts of Reg F speak to other channels. Section 1006.6(e) requires electronic communications to include "a clear and conspicuous statement describing a reasonable and simple method by which the consumer can opt out of further electronic communications." Section 1006.14(h) covers consumer requests about which media to use. The TCPA's separate opt-out rules sit on top of all this; our FCC 26-67 post quotes the newest ones.

Reg F's 7-in-7 next to NYC's 3-in-7

New York City's amended SHIELD Rule adds a different count. DCWP's FAQ (dated Oct 22, 2026) says the amendments "will take effect on January 1, 2027," and that Section 5-77(b)(1)(iii) "explicitly limits communications with NYC consumers to three communications per distinct consumer account within a seven-day period across all media, excluding mailed letters, with some exceptions." DCWP calls it the "3 x 7 Frequency Limit" and adds: "This limit is per-account, not per-consumer."

Reg F, 12 CFR 1006.14(b)(2)NYC SHIELD Rule, 6 RCNY 5-77(b)(1)(iii), per DCWP FAQ
EffectiveNov 30, 2021Jan 1, 2027
How the text frames itPresumptions of compliance and of violationDCWP: "explicitly limits"
Number in seven daysMore than seven calls, or any call within seven days after a conversationThree communications
UnitA particular person, a particular debtPer distinct consumer account
Channels countedTelephone calls, including ringless voicemail"all media," excluding mailed letters
Exclusions listedPrior consent, unconnected calls, certain personsDCWP's FAQ lists exclusions, including letters sent by mail, an initial communication solely to obtain consent for electronic communication, responses to consumer inquiries, "bounced email messages and calls to disconnected numbers," and communications about litigation or ordered by a court

Reg F has its own view on how it sits next to state and local rules. Section 1006.104 says a state law isn't inconsistent with the regulation "if the protection such law affords any consumer is greater." How any of that applies to a given NYC account is a question teams often take to their own compliance team or counsel. Our NYC chatbot rule post covers the city's other pending proposal.

What others have said

At AccountsRecovery.net's "Reg F at Five" webinar on Oct 20, 2026, John McNamara, chief growth officer at Avail, who said he "worked with economists at the CFPB," put it this way, per the published transcript: "the seven by seven for a lot of folks wasn't really the doom and gloom, the end of industry that people thought it was going to be." On counting, he said: "You've gotta count your attempts, right? You've gotta count your seven by seven."

Asked by host Mike Gibb whether Reg F is now just the floor given rules like New York City's, McNamara answered: "I think it's the floor." Rick Perr, a partner at Kaufman Dolowich, on the same panel: "the call rules in Massachusetts or the contact rules are different than the contact rules in New York, which is different than the seven and seven rule."

Questions for your team

  • When the dashboard says "7/7," which calls is it counting: dials, connected calls as the rule defines them, or something in between?
  • Where does a ringless voicemail land in the count today?
  • How does the count reset after a conversation, and what marks day one?
  • When a consumer gives consent to more calls, where is that recorded, and what closes the window?
  • For a consumer with three accounts in collection, is the count per account, per consumer, or both?
  • How do texts and emails show up next to the call count when someone looks at the cumulative picture?
  • For NYC accounts, which count is the system keeping after Jan 1, 2027?

Questions for AI agents and automation

A few questions come up when software places or schedules the calls:

  • Does the agent read the same counter the human team reads, or keep its own? If a person and an agent both call the same debt on the same day, which system has both calls?
  • How does the agent's call log classify outcomes like "rang, no answer," "voicemail," "busy," and "not in service," given that comment 14(b)(3)(ii)-1 treats them differently?
  • When an agent has a telephone conversation about the debt, how does that conversation date reach every other system that might call next?
  • If an agent hears consent to call again tomorrow, what record exists of who gave it, when, and for how long?
  • When the agent spaces its calls, what does the pattern look like next to the rebuttal examples in comment 14(b)(2)(i)-2?
  • Section 1006.100 requires records to be kept for three years, and the official commentary notes that "Nothing in Sec. 1006.100 requires a debt collector to record telephone calls." What does an agent's call record contain, and where does it live?

Questions, answered

Does Reg F cap collection calls at seven a week?

The CFPB says no: "The Debt Collection Rule does not impose a specific 'limit' or 'cap' on the frequency of telephone calls that a debt collector may place." It sets presumptions of compliance and of violation in 12 CFR 1006.14(b)(2).

What are the two parts of the 7-in-7 presumption?

Under 1006.14(b)(2)(i), calls to a particular person about a particular debt neither "More than seven times within seven consecutive days" nor "Within a period of seven consecutive days after having had a telephone conversation with the person in connection with the collection of such debt."

Does a ringless voicemail count as a call?

Yes, per official comment 14(b)-1, which says "placing a telephone call" "includes conveying a ringless voicemail."

Do texts and emails count toward the seven?

No. The same comment says placing a call "does not include sending an electronic message (e.g., a text message or an email)." Comment 14(a)-2 says the "cumulative effect" of conduct through any medium can still matter.

Is the count per consumer or per debt?

Per debt. Section 1006.14(b)(4) defines "particular debt" as "each of a consumer's debts in collection," with a student loan exception.

When did Reg F take effect?

Nov 30, 2021. The Federal Register notices for both final rules (85 FR 76734 and 86 FR 5766) give that date.

How is NYC's 3-in-7 limit different?

Per DCWP, it limits communications "across all media," excluding mailed letters, to three per distinct consumer account in a seven-day period, starting Jan 1, 2027.

From insight to action.

Explore how Paypath puts AI to work across the credit lifecycle.

Book a demo

Book a demo