Regulation F for Creditors and First-Party Programs: What Applies, What Does Not, and Why Programs Adopt the Standards Anyway

Regulation F is written for debt collectors. Most of the people who ask about it are not sure whether that phrase describes them: a buy-here-pay-here dealer working its own portfolio, an auto finance company servicing accounts it originated, or a lender that has handed early-stage contact to an outsourced team working in its name. This guide is for that reader. It explains what the rule is, who it covers by its own terms, what each operating standard says, and why programs that may sit outside the definition run to the standards anyway.

It is orientation, not legal advice. Where the rule text matters it is quoted and linked to the Consumer Financial Protection Bureau's own copy and to the Electronic Code of Federal Regulations. The legal classification of any particular program is a question of fact and is determined with the creditor's counsel; nothing here changes that.

What Regulation F is

Regulation F is the Bureau's rule implementing the Fair Debt Collection Practices Act (FDCPA), codified at 12 CFR Part 1006. The CFPB's final-rule page describes the 2020 rule as one that revises Regulation F “to prescribe Federal rules governing the activities of debt collectors, as that term is defined in the FDCPA.” The rule was published in the Federal Register on November 30, 2020 (85 FR 76734) and took effect November 30, 2021.

The text sits in the Electronic Code of Federal Regulations at 12 CFR Part 1006, under the title Debt Collection Practices (Regulation F). Section 1006.1(b) states the purpose: to carry out the purposes of the FDCPA, “which include eliminating abusive debt collection practices by debt collectors, ensuring that debt collectors who refrain from using abusive debt collection practices are not competitively disadvantaged, and promoting consistent State action to protect consumers against debt collection abuses.” Section 1006.1(c) sets the coverage: “this part applies to debt collectors, as defined in § 1006.2(i).”

Two features of the rule matter to a creditor reading it. First, it is a rule about conduct: how often to call, when, through which media, what to say and what to send. Second, every obligation in it is addressed to “a debt collector.” Whether that phrase reaches a given program is the threshold question, and the rule answers it by definition rather than by industry.

Who the rule covers, and where a creditor stands

The definition is in §1006.2(i): a debt collector is “any person who uses any instrumentality of interstate commerce or mail in any business the principal purpose of which is the collection of debts, or who regularly collects or attempts to collect, directly or indirectly, debts owed or due, or asserted to be owed or due, to another.” The words that carry the weight are “to another.” A creditor collecting a debt owed to itself is, on the face of the definition, collecting its own debt.

The definition then lists exclusions, and the first is the creditor's own staff. Under §1006.2(i)(2)(i) the term excludes an officer or employee of a creditor collecting debts for that creditor in the creditor's name. The statute the rule implements, 15 U.S.C. § 1692a(6), has the same structure: exclusion (A) covers “any officer or employee of a creditor while, in the name of the creditor, collecting debts for such creditor,” and exclusion (F) covers a person collecting a debt “which was originated by such person” or “which was not in default at the time it was obtained by such person.” Section 1692a(4) defines a creditor as “any person who offers or extends credit creating a debt or to whom a debt is owed,” excluding one who takes an assignment of a defaulted debt solely to facilitate collection for another.

One provision runs the other way, and it is the sentence a first-party program should read twice. Both the statute and the rule provide that the term includes any creditor that, in the process of collecting its own debts, uses any name other than its own that would indicate that a third person is collecting or attempting to collect such debts. A creditor that puts a different name on the letterhead, or lets a vendor answer under a name that is not the creditor's, has entered the definition by its own choice.

Where does that leave an outsourced team? Exclusion (A) is written for officers and employees of the creditor. A vendor's agents working under the creditor's name are not the creditor's employees, and the rule does not say that using the creditor's name alone takes a vendor outside the definition. Whether a given engagement is first-party servicing or third-party collection under the FDCPA depends on its facts: when the accounts are handed over (pre-default servicing or default-stage collection), whose name the consumer hears, whose systems hold the record, and who directs the work. That classification is made by the creditor with its counsel before the program starts. TEKS runs every collections support program to the standards below whatever that classification turns out to be.

The operating standards, section by section

Whatever the classification question yields, the substance of the rule is a set of operating standards, each short enough to configure. The sections below are the ones a phone-and-text program touches every day, quoted from the CFPB's eRegulations copy of the rule.

• Call frequency, §1006.14(b). A collector must not place calls “repeatedly or continuously with intent to annoy, abuse, or harass any person at the called number.” The rule then supplies a presumption: a collector is presumed to comply if it calls 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.” The day of the conversation is day one of that period, and exceeding either frequency creates a presumption of violation under §1006.14(b)(2)(ii). Section 1006.14(h)(1) adds that a collector must not use a medium of communication the person has asked it not to use.
• Inconvenient times and places, §1006.6(b)(1). No communication “at any unusual time, or at a time that the debt collector knows or should know is inconvenient to the consumer.” Absent knowledge to the contrary, “a time before 8:00 a.m. and after 9:00 p.m. local time at the consumer's location is inconvenient.” The consumer's location governs, not the caller's. The same paragraph covers unusual or inconvenient places; §1006.6(b)(3) bars contact at the workplace when the collector knows or has reason to know the employer prohibits it; and §1006.6(b)(2) bars direct contact with a consumer the collector knows is represented by an attorney, with limited exceptions.
• Cease requests and electronic opt-out, §1006.6(c) and (e). If a consumer notifies the collector in writing that the consumer refuses to pay or wants communication to stop, the collector “must not communicate or attempt to communicate further with the consumer with respect to such debt,” subject to the exceptions in paragraph (c)(2). A collector that communicates electronically “must include in such communication or attempt to communicate a clear and conspicuous statement describing a reasonable and simple method by which the consumer can opt out of further electronic communications or attempts to communicate by the debt collector to that address or telephone number.”
• Communication media, §1006.22. The section bars unfair or unconscionable means generally and, in paragraph (f), three specific media: communicating with a consumer about a debt by postcard; communicating through a social media platform where the message is viewable by the general public or the person's contacts; and sending email to an address the collector knows the employer provided, outside narrow exceptions.
• Validation information, §1006.34. A collector must provide validation information in its initial communication or within five days of it. The rule specifies an itemization date (one of five reference dates for the amount of the debt), a validation period ending 30 days after the consumer receives or is assumed to receive the information, and four categories of content: the debt collector communication disclosure, information about the debt, information about consumer protections, and consumer-response information.
• Sending required disclosures, §1006.42. Disclosures sent in writing or electronically must go out “in a manner that is reasonably expected to provide actual notice, and in a form that the consumer may keep and access later.” Electronic delivery of the validation notice must follow section 101(c) of the E-SIGN Act.
• False, deceptive or misleading representations, §1006.18. A collector must not use “any false, deceptive, or misleading representation or means in connection with the collection of any debt.” Paragraph (e) supplies the disclosures often called the mini-Miranda: in the initial communication, that the debt collector is attempting to collect a debt and that any information obtained will be used for that purpose; in each later communication, that the communication is from a debt collector.

Mapping each standard to an operating control

A standard is only as real as the control that implements it. The table pairs each section with the control a program actually runs. The pattern is consistent: the rule states an outcome, and the control is a configuration, a data field or a script line that produces it without depending on any one agent's memory. The seven-attempt presumption in §1006.14(b)(2), for example, is a counter and a hold timer, nothing more. Read alongside the BHPH collections cadence, the table is the compliance half of a first-party playbook.

Why first-party programs adopt the standards anyway

The first reason is that Regulation F is not the only law in the room. The Consumer Financial Protection Act gives the Bureau authority over unfair, deceptive or abusive acts or practices by any “covered person or service provider,” a category defined by the product offered rather than by the debt-collector definition. 12 U.S.C. § 5531(a) authorizes the Bureau to act to prevent a covered person or service provider “from committing or engaging in an unfair, deceptive, or abusive act or practice under Federal law in connection with any transaction with a consumer for a consumer financial product or service,” and 12 U.S.C. § 5536(a)(1)(B) makes it unlawful for a covered person or service provider “to engage in any unfair, deceptive, or abusive act or practice.” Section 5531(c)(1) describes an unfair act as one that causes or is likely to cause substantial injury to consumers which is not reasonably avoidable and is not outweighed by countervailing benefits. Whether a given creditor is a covered person is, again, a question for counsel; the point for an operator is that the UDAAP standard reaches conduct directly and does not wait for the debt-collector definition. Repeated calls, late-night calls, contact after a request to stop and misstated balances are the conduct Regulation F describes, and they are also the conduct a UDAAP analysis examines.

The second reason is state law, which often draws the line somewhere other than where the FDCPA draws it. Texas is the clearest example for a Dallas–Fort Worth lender. Texas Finance Code Chapter 392 defines “debt collector” as “a person who directly or indirectly engages in debt collection,” and “debt collection” as “an action, conduct, or practice in collecting, or in soliciting for collection, consumer debts that are due or alleged to be due a creditor” (§392.001(5)–(6)). Nothing in that definition limits it to debts owed to another. The chapter uses a separate, narrower term, “third-party debt collector,” defined by reference to 15 U.S.C. § 1692a(6), for the duties it reserves to outside collectors: the $10,000 surety bond in §392.101 and the initial and subsequent-communication disclosures in §392.304(a)(5). The prohibitions on harassment in §392.302, including “causing a telephone to ring repeatedly or continuously, or making repeated or continuous telephone calls, with the intent to harass a person at the called number,” and on threats, unfair means and misleading representations in §§392.301, 392.303 and 392.304, are addressed to a “debt collector” in the chapter's broad sense. A violation is actionable under §392.403 and is a deceptive trade practice under §392.404.

Other states draw the line differently. Illinois exempts from its Collection Agency Act “motor vehicle retail sellers collecting motor vehicle retail installment contracts originated by the motor vehicle retail seller” and “any person under contract with a creditor to notify the creditor's debtors of a debt using only the creditor's name” (205 ILCS 740/2.03(11) and (16)). A program with accounts in more than one state either keeps a state table or runs to one standard across the portfolio, and the Regulation F operating standards are the natural choice for that single standard because they are already specified to the level of a dialer setting. The coverage pages record, state by state, whether the collection statute reaches original creditors.

The third reason is the complaint record. The CFPB's FDCPA Annual Report 2025 reports approximately 207,800 debt collection complaints received in 2024, seven percent of all complaints the Bureau received that year. Among complaints about communication tactics, 51 percent concerned frequent or repeated calls and 34 percent concerned continued contact attempts despite a request to stop. Those two categories are what §1006.14 and §1006.6(c) address. A creditor that runs to those standards is running to the two most common communication complaints a consumer files, whichever statute the complaint is eventually reviewed under.

The fourth reason is the portfolio. The customer of a first-party program is still the creditor's customer; the next vehicle, the referral and the willingness to answer the phone all depend on how the collection conversation felt. The Federal Reserve Bank of New York's Q2 2026 Household Debt and Credit report put the annualized flow of auto loan balances into serious delinquency at 3.00 percent, against 2.93 percent a year earlier, so more accounts are reaching the stage where contact decides whether they cure. A program built on a seven-attempt cadence, a fixed calling window and a clean opt-out is also a program that keeps customers, which is why buy-here-pay-here dealers and auto finance companies that never expect to be classified as debt collectors run to it anyway.

What Regulation F does not settle for a first-party program

Running to the standards answers the conduct question. It leaves several others open, and a program that treats Regulation F as the whole map will miss them. The table lists the ones that come up in nearly every scoping conversation, with the place each answer actually lives. The definition in §1006.2(i) is the reason the first row exists: the rule defines a debt collector, but it does not classify anyone.

Building a first-party program to the standard

The standards become a program through configuration, documentation and supervision. The checklist below is what TEKS asks a client to have in place, or to build with us, before the first outbound attempt. It assumes the classification conversation with counsel has happened; several items change depending on its answer. The calling window in §1006.6(b)(1)(i) is the item most often configured wrong, because it is set to the office's clock instead of the consumer's.

• A per-debt attempt counter in the dialer that counts every number on the account and applies the seven-day hold after a connected conversation. A lower internal cap is a business choice the counter can hold.
• A consumer time-zone field on every account, populated from the address on file and corrected whenever a consumer says where they are. The 8:00 a.m. to 9:00 p.m. window runs on that field, not on the floor's clock.
• Cease, attorney-representation, workplace and requested-media flags with a source note, applied across every channel on the day they arrive.
• Opt-out language in every text and email template, automated STOP handling, and a record of which channel each consumer opted out of.
• Scripts in English and Spanish with fixed disclosure and identification lines, an authority matrix for promises and arrangements, and a rule that balances and fees are read from the system of record, never estimated.
• A note standard: right party or not, channel, time, what was discussed, any arrangement, next follow-up date and owner, entered in the creditor's system rather than a spreadsheet beside it.
• Call monitoring and a weekly review of attempt counts, window exceptions, opt-outs and disputes, with every exception traced to an account and an agent.
• Written decisions from counsel on validation information, state notices, autodialer consent and the classification itself, kept with the program documentation.

How TEKS runs first-party collections support

TEKS provides first-party collections support: agents dedicated to one client, working inside the client's own servicing system or DMS, under the client's name, on the client's scripts. The floor is in Guadalupe, in the Monterrey metropolitan area of Nuevo León, on a schedule aligned to U.S. Central business hours, with a U.S. office in Arlington, Texas. Every program is run to the Regulation F operating standards in the first table: the attempt counter, the consumer-local calling window from §1006.6(b), cease and opt-out handling, media restrictions and fixed disclosure language, whether or not counsel concludes the program is a debt collector under the FDCPA.

TEKS does not hold itself out as a collection agency, does not buy debt and does not collect in its own name. It does not publish a rate card; pricing follows the solution design. The collections support page lists the standards, why TEKS explains the dedicated-agent model, and a discovery call is where the scope, the portfolio and the classification conversation start. Two things a client will not find here are a performance target and a promise: attempt counts and windows are controls, and cure rates depend on the portfolio. The reason to write the controls down is that they can be audited from the account record, which is also why how to choose a BPO partner puts system access and note standards ahead of price.

Classification is decided with counsel

Every statement in this guide about who the rule covers is a statement about the text, not about any particular program. The FDCPA and Regulation F define a debt collector by what a person does and in whose name, and 15 U.S.C. § 1692a(6) draws its exclusions narrowly. Whether a specific engagement is first-party servicing or third-party collection under the FDCPA depends on its structure and is determined with your counsel. TEKS runs every program to Regulation F standards regardless of classification.