Voicemail, Text and Email Under Regulation F: What a Message May Actually Say

TL;DR

• Regulation F defines a limited-content message at 12 CFR §1006.2(j) as a voicemail for a consumer containing all of a short required list, optionally a second short list, and no other content. Adding one helpful sentence takes the message outside the definition.
• A limited-content message is not a "communication" under §1006.2(d), which is why it exists. But it is still a telephone call placed, so it counts toward the seven-calls-in-seven-days presumption at §1006.14(b)(2).
• Every email and text carries an opt-out. Under §1006.6(e) an electronic communication must include "a clear and conspicuous statement describing a reasonable and simple method" to opt out, and the method cannot demand a fee or information the collector does not need.
• §1006.14(h) prohibits communicating through a medium after the person has asked that the medium not be used — a channel-level preference that sits beside, not inside, the general cease rule.
• The CFPB received approximately 387,400 debt collection complaints in 2025, and communications conduct is a recurring theme in them. Messaging rules are cheap to enforce in a dialer and a template; they are expensive to enforce in agent memory.

Why this matters

As of September 2026.

This is for the operations and compliance people who own what a servicing team leaves on a voicemail, puts in a text and sends in an email: collections managers at automotive finance companies, dealer principals running their own portfolios, and the person who signs off on message templates.

Most Regulation F coverage focuses on call frequency and the 8 a.m. to 9 p.m. window. Those matter, and our Regulation F guide for creditors walks the rule section by section. This post covers the narrower question that generates more day-to-day operating decisions: given that you are allowed to reach out, what may the message itself contain? Everything below is orientation on what the rule text says, not legal advice, and whether a particular engagement falls inside the rule's definition of a debt collector is determined with your counsel.

The limited-content message: a very short list, and nothing else

The concept is unusual enough to be worth stating plainly. Regulation F creates a category of voicemail that is deliberately not a "communication." Section 1006.2(d) defines a communication as "the conveying of information regarding a debt directly or indirectly to any person through any medium." A message that conveys no information regarding a debt is therefore not a communication, and the third-party disclosure problem — a spouse, a roommate or a colleague hearing the message — largely falls away.

Section 1006.2(j) sets out what such a message may contain. The required content is a business name that does not indicate the caller is in the debt collection business, a request that the consumer reply to the message, the name or names of one or more natural persons the consumer can contact, and a telephone number the consumer can use to reply. The optional content is short: a salutation, the date and time of the message, suggested dates and times the consumer may reply, and a statement that if the consumer replies they may speak to any of the company's representatives.

And then the sentence that does the work: the message must include the required content, may include the optional content, and no other content. Not the account number. Not the balance. Not "regarding your vehicle." Not a helpful "we may be able to work something out." Any of those puts the message outside §1006.2(j), and once it is outside, it is an ordinary communication with all the ordinary consequences.

This is a template problem, not a training problem. A floor that leaves limited-content messages should have exactly one approved script, locked, with the agent's own first name as the contact person, and a supervisor who checks recordings against it.

The trap: a limited-content message still counts as a call

The most common misreading is that because a limited-content message is not a communication, it does not count toward the call-frequency presumption. It does.

Section 1006.14(b)(2)(i) is written in terms of placing a telephone call, not in terms of communicating: a debt collector is presumed to comply if it "places a telephone call to a particular person in connection with the collection of 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." Section 1006.14(b)(3) lists the calls that do not count — calls placed with the person's prior consent given directly to the debt collector and within at most seven consecutive days after the collector receives that consent, calls "not connected to the dialed number," and calls to the parties listed in §1006.6(d)(1)(ii) through (vi). Voicemail is not on that list, and the Bureau's official interpretation treats a call that reaches voicemail as connected.

So the practical rule for a servicing floor is: a limited-content message reduces disclosure risk, and still counts as one of the seven calls the presumption measures. Teams that treat voicemails as free attempts run out of frequency budget by Wednesday and then have nothing left for the days the borrower is most likely to answer.

Email and text: the procedures and the opt-out

Electronic channels get their own treatment because the disclosure risk is different — a work email address or a reassigned mobile number can put debt information in front of the wrong person.

Section 1006.6(d) sets out procedures a collector can follow to manage that risk, built around which email address or telephone number is being used and how it was obtained: an address or number the consumer has used to communicate about the debt, one provided with consent, or one obtained through a prescribed process involving the creditor. The mechanism is procedural — the rule describes reasonable procedures rather than a single permitted address — and it pairs with the requirement not to use an address or number the collector knows has led to a prohibited third-party disclosure.

Then the part every template carries under Regulation F's standard. Under §1006.6(e), a collector communicating electronically must include "a clear and conspicuous statement describing a reasonable and simple method by which the consumer can opt out" of further electronic communications to that address or number. The method cannot require the consumer to pay a fee or to provide information the collector does not need. In practice that means a visible opt-out line in every email footer and every text, an opt-out that is honored by the system rather than by a person, and a log entry when it is exercised.

Finally, §1006.14(h) prohibits communicating or attempting to communicate with a person through a medium of communication if that person has requested the collector not use that medium. This is a channel-level preference, and it is separate from a general cease request under §1006.6(c). A borrower who says "stop texting me, call me instead" has made a §1006.14(h) request, not a cease request, and a system that collapses the two either over-suppresses a cooperative borrower or under-suppresses one who asked for quiet.

Mapping the rules to operating controls

The reason to read the rule closely is that almost every requirement maps to something you configure once rather than something an agent remembers.

What the rule governs	Section	The control that enforces it
What a voicemail may contain	§1006.2(j)	One locked script; no free-text voicemail field; recording review against the script
Whether a voicemail spends an attempt	§1006.14(b)(2), (b)(3)	Dialer counts voicemails as attempts per person per debt
Time of day	§1006.6(b)(1)(i)	Contact window evaluated in the consumer's time zone, not the floor's
Opt-out on electronic messages	§1006.6(e)	Opt-out language in the template, not the agent's discretion; system-side suppression
Channel preference	§1006.14(h)	A per-channel suppression flag distinct from the cease flag
Cease requests	§1006.6(c)	Logged in the client's system of record on receipt

A first-party program run under a creditor's name gets the same treatment at TEKS regardless of classification, because the cost of configuring these controls is close to zero and the cost of relying on memory is not. The collections and accounts receivable support page describes how the controls are set up inside a client's own platform, and the BHPH insurance verification program page shows the same discipline applied to a non-collections workflow.

An illustrative operating example

The example is illustrative and composed to show the interaction between two rules. It is not a client result.

A servicing floor decides to lead with voicemail because "voicemails are not communications." Over four days it places six calls on an account, leaving a compliant limited-content message each time. On day five the borrower's own callback comes in and the agent has a conversation and takes a promise to pay.

Two constraints have now bound at once. The six voicemails counted as six of the seven calls in seven consecutive days that fit within §1006.14(b)(2)(i)(A), the first of the two conditions for the presumption of compliance. And the conversation on day five starts a fresh seven-day period under §1006.14(b)(2)(i)(B), during which calls about that debt fall outside the presumption of compliance. The floor's plan to "follow up hard on day six" was never available, and nobody would have noticed until an audit, because each individual message was perfectly drafted.

The fix is not a memo. It is a dialer that counts voicemail attempts, applies the conversation reset automatically, and shows the agent the remaining budget on the account screen.

What operators say

The best available account of how collection operations describe their own messaging conduct comes from the CFPB's record of company responses to complaints.

In its 2025 Consumer Response Annual Report, published March 2026, the Bureau reports that consumers "complained about collection tactics, including calls that they claimed were made too often or outside permitted hours" and that "companies maintained that their calling practices conformed with applicable requirements and they frequently reported adding the consumers' phone numbers to their Do Not Call lists."

That exchange is the whole argument for configuring rather than instructing. Both sides can be describing the same account honestly — the consumer counting attempts as experienced, the company counting attempts as logged — and the only thing that settles it is a system record showing the attempt count, the channel, the local time and the suppression state at the moment of each attempt.

Frequently asked questions

What is a limited-content message under Regulation F?

It is a voicemail defined at 12 CFR §1006.2(j) that contains only a business name not indicating debt collection, a request that the consumer reply, the name of one or more natural persons to contact, and a reply telephone number, plus an optional salutation, the date and time, suggested reply times, and a statement that the consumer may speak to any representative. It may contain no other content.

Does a limited-content message count toward the seven-calls-in-seven-days presumption?

Yes. Section 1006.14(b)(2) is framed around placing a telephone call, not around communicating, and the exclusions in §1006.14(b)(3) cover calls placed with the called person's prior consent given directly to the debt collector and within at most seven consecutive days after the collector receives that consent, calls not connected to the dialed number, and calls to certain listed parties. A voicemail reaching the consumer's mailbox is a connected call and spends an attempt.

What has to appear in a collection email or text message?

Under §1006.6(e), an electronic communication has to include a clear and conspicuous statement describing a reasonable and simple method for the consumer to opt out of further electronic communications to that address or number, and the method cannot require paying a fee or supplying information the collector does not need.

Is asking to stop being texted the same as a cease request?

No. A request not to use a particular medium is addressed by §1006.14(h), which prohibits communicating through a medium the person has asked the collector not to use. A written cease request under §1006.6(c) stops communication generally, with limited exceptions. Systems that use one flag for both either silence a borrower who only wanted a different channel or keep contacting one who asked for quiet.

Does Regulation F apply to a creditor servicing its own accounts?

By its terms, Regulation F governs debt collectors as the FDCPA defines them, and that definition excludes a creditor's own officers and employees collecting in the creditor's name. Whether an outsourced team working under a creditor's name falls inside the definition depends on how the engagement is structured and is determined with the creditor's counsel; state law may apply separately. TEKS runs every program to Regulation F's operating standards regardless of classification.

How many debt collection complaints did the CFPB receive in 2025?

Approximately 387,400, according to the CFPB's 2025 Consumer Response Annual Report published in March 2026. The Bureau sent about 304,700 of them — 79 percent — to companies for review and response, and companies responded to 97 percent of those.

The bottom line

Regulation F's messaging provisions are unusually mechanical, which is good news: almost nothing in them depends on judgment in the moment. A voicemail either contains only the §1006.2(j) content or it does not. An attempt either counted or it did not. An email either carried the §1006.6(e) opt-out or it did not. A channel preference was either honored by the system or left to an agent.

Operations that put those decisions into templates, dialer configuration and suppression flags get two things at once: fewer conduct complaints, and a record that can answer one. Operations that put them into training get neither, and find out during an examination or a dispute. If you want a team that works your accounts inside your systems with these controls configured from day one, tell us about your portfolio.