Debt CollectionNov 18, 20266 min read

Reg F Call Limits Explained: The 7-in-7 Rule and How AI Agents Respect It

Under Regulation F, a collector is presumed to be harassing a consumer if it calls about a debt more than seven times in seven consecutive days, or calls…

Last updated: November 2026

Direct answer: Under Regulation F, a collector is presumed to be harassing a consumer if it calls about a debt more than seven times in seven consecutive days, or calls within seven days after a phone conversation about that debt. Calls are also barred before 8 a.m. and after 9 p.m. in the consumer's time. This is general information, not legal advice. Confirm your policy with counsel.

Why this rule exists

Before 2021, debt collectors worked under the Fair Debt Collection Practices Act with only a vague ban on calling "repeatedly or continuously." Everyone argued about what that meant. Lawsuits followed.

Regulation F, issued by the Consumer Financial Protection Bureau, replaced the guesswork with numbers. It took effect in November 2021. The numbers are not a guarantee of safety. They are a line that, once crossed, shifts the burden onto the collector to show the calls were not harassing.

If you run collections, those numbers belong on the wall.

At a glance

RuleWhat it saysPractical meaning
Seven calls in seven daysMore than seven attempts on one debt in seven consecutive days raises a presumption of harassmentCount every attempt, including unanswered ones
Seven days after a conversationA call within seven days after a phone conversation about that debt raises the same presumptionAfter you talk, wait
Calling hoursNo calls before 8 a.m. or after 9 p.m. in the consumer's local timeKnow the time zone of each consumer
Per debt, not per consumerLimits apply to each debtA consumer with two debts may have two counts
VoicemailLimited-content messages follow specific content rulesKeep messages short and compliant

What counts as a call

The limit applies to call attempts, not only to conversations. A call that rings out counts. A call that goes to voicemail counts. A call that reaches the wrong number is complicated, and the safest policy is to flag and stop.

This catches teams by surprise. A dialer that fires at an account three times a day, with no one picking up, burns the entire weekly allowance by Tuesday. The consumer never heard from you, and you have no calls left for the days when they might answer.

So the question for every operation is not "how many calls can we make?" It is "how do we make the best use of the calls we are allowed?"

The conversation reset

The second half of the rule gets less attention. After you have a telephone conversation with the consumer about the debt, a call within the next seven days raises the presumption.

That has a design consequence. If you spoke on Monday and the consumer promised to pay on Thursday, your follow-up call on Thursday needs careful handling. Many teams use text or email for that reminder, or rely on a consumer-requested time. The point is that your systems need to know a conversation happened, not just that a call was placed.

Consumer preferences change the picture

Reg F also lets consumers tell you how they would like to be contacted, including limits on time and place. A consumer who says "only call me after six" has moved the line. Your system must honor it and record it. A consumer who asks you to stop calling, or to communicate only by another channel, creates obligations that your platform must handle immediately.

The practical lesson: contact preferences are data, and every system that touches the consumer needs the same data.

How a well-built voice agent respects the limits

Compliance by memo does not work at scale. Compliance by system does.

It checks before it dials. The agent's rules engine confirms the time window, the call count and any stop or dispute flags before a call goes out. A call that breaks a rule does not happen.

It counts every attempt. Unanswered calls and voicemails register against the limit. The count lives in one place, not in each collector's head.

It knows when you last spoke. A completed conversation sets a clock. The agent reads that clock before the next attempt.

It makes each attempt count. Because the agent holds the whole conversation, verifies identity and captures a promise, a connected call tends to do more work than a ring and a hangup.

It records everything. Every utterance is logged, giving you evidence of what was said and when.

Vodex builds its collections agents around FDCPA, Reg F and TCPA requirements, and holds SOC 2 Type II, ISO 27001 and HIPAA credentials. Its agents work inside configured calling windows and limits and log each call for audit. Rules differ by portfolio and by state, so your compliance team should review the configuration before launch.

A worked example

Take one debt on one account. On Monday, your system tries twice, once in the morning and once at lunch. Both ring out. On Tuesday it tries once and reaches voicemail. On Wednesday it tries twice more. That is five attempts in three days.

You have two attempts left before Sunday, and you do not yet know whether the consumer is reachable. If the next attempt connects and a conversation happens on Thursday, the seven-day clock after that conversation starts, and the next call should wait.

Now see why spacing matters. The same five attempts, spread across a week and timed for the hours the consumer tends to answer, would have left room to adjust. Planning beats volume. A system that plans attempts, rather than firing them, is the only kind that stays inside the line without constant manual checking.

Common mistakes

Counting by consumer, not by debt. The limit attaches to each debt. Your count should too.

Ignoring voicemail attempts. A voicemail is still an attempt.

Forgetting the time zone. A consumer's area code is not a reliable guide to where they are today. Use the best location data you have.

Letting two systems dial the same account. If a dialer, a text platform and an agent all act independently, you can break the limit without knowing it. Centralize the count.

Treating the rule as a target. Seven in seven is a presumption line, not a goal. Many teams choose a lower internal ceiling.

A policy worth writing down

Whatever platform you use, put these decisions on paper:

  1. Your maximum attempts per debt per week.
  2. Your internal calling hours, which may be narrower than the legal ones.
  3. How you record and honor contact preferences.
  4. How a conversation resets your cadence.
  5. Who reviews exceptions.

Then test the system against the paper. Ask the vendor to show you a day when the limit blocked a call. A platform that has never blocked a call is a platform you should question.

Frequently asked questions

It presumes harassment if a collector calls about a debt more than seven times in seven consecutive days, or calls within seven days after a phone conversation about that debt.

Call attempts count, including those that go to voicemail. Confirm the details of limited-content messages with counsel.

Not before 8 a.m. or after 9 p.m. in the consumer's local time.

Yes, when it is configured to check hours, counts and flags before every call. Vodex builds its agents for Reg F, FDCPA and TCPA, and your counsel should review the setup.

No. It is general information. Consult a qualified attorney for your situation.

SOC 2 Type II · ISO 27001 · 24/7 support

Ready to supercharge
your engagement?

Join the enterprises already using Vodex to turn reminders, collections and follow-ups into recovered revenue.