FDCPA communication and recordkeeping requirements

Debt collection compliance depends on more than knowing the rules.

A debt collector also needs to show what happened. Which channel was used? When did contact take place? Did the consumer opt out of a specific email address or text number? Was the right validation information provided? What happened after the account was disputed?

Those questions are difficult to answer when communication data is spread across dialers, message platforms, customer service tools, spreadsheets, agency portals, and agent notes.

For debt collectors covered by the FDCPA and Regulation F, communication and recordkeeping controls are a practical part of the compliance program. They help teams manage customer contact, respond to account changes, and retain the records needed to show how an account was handled.

Remember: This article provides general information only and isn’t legal advice. FDCPA and Regulation F obligations can depend on the collector, debt, communication method, state law, and the facts of a particular case. Always review your requirements with qualified legal and compliance advisors.

What does Regulation F cover?

Regulation F is the CFPB’s debt collection rule under 12 CFR Part 1006. It implements the FDCPA for covered debt collectors and includes requirements and official interpretations for communications, validation notices, electronic opt-outs, and record retention.

For a broader explanation of the FDCPA, who it covers, and how Regulation F fits into the federal framework, read our guide to FDCPA compliance for debt collectors.

This article focuses on the day-to-day operational work behind communications and evidence.

Managing telephone contact rules

Telephone contact rules are often reduced to “seven calls in seven days.” This shorthand misses important context.

Regulation F prohibits debt collectors from placing telephone calls or engaging a person in telephone conversation repeatedly or continuously with intent to annoy, abuse, or harass. It also creates a rebuttable presumption of a violation in specified circumstances if a debt collector:

• Places telephone calls to a particular person in connection with collecting a particular debt more than seven times within seven consecutive days, or
• Places a telephone call to a particular person within seven consecutive days after having a telephone conversation with that person about the same debt.

This isn’t a universal, unconditional call limit. The regulation includes exceptions, and the application of the rule can depend on the facts. Teams should work from an approved legal interpretation rather than rely on a simple call counter.

From an operations perspective, this means teams need a reliable way to:

• Track contact attempts and telephone conversations by person and debt
• Record the date and outcome of relevant calls
• Apply the organization’s approved contact strategy
• Suppress or adjust future calls when a rule or customer event applies
• Surface exceptions for review
• Keep a usable account level contact history

The goal is to connect the contact policy to the actual workflow. A policy that lives in a training document won’t help if the dialer, collections system, and agent view don’t reflect the same information.

Electronic communications and opt-outs

Email and text messaging can give customers more ways to engage with collections teams. They also create more moving parts.

Under Regulation F, when a debt collector communicates or attempts to communicate electronically in connection with debt collection using a specific email address, text message number, or other electronic medium address, the collector generally needs 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.

This matters because an opt-out needs to affect future activity.

A workable process should help teams:

• Use approved templates with the required opt-out information
• Capture the opt-out against the specific email address or phone number involved
• Update future communication workflows after the opt-out is received
• Suppress queued or scheduled messages to that address or number
• Keep a record of the request and the action taken
• Flag unclear, incomplete, or conflicting instructions for review

Regulation F also affects how required disclosures can be sent. For example, if a consumer has opted out of debt collection communications to a particular electronic address or number, a debt collector can't use that address or number to send required disclosures.

Electronic communication may also raise issues under other laws, including the TCPA, as well as state law and organization-specific policies. Don’t assume one set of rules answers every channel or use case.

Validation notices and debt information

Validation information is a central part of FDCPA compliance.

Under the FDCPA, debt collectors need to provide consumers with certain basic information about the debt and their dispute rights. The statute provides that consumers generally have 30 days to dispute a debt, and it identifies information that needs to be included in the notice process, including the amount of the debt and the name of the creditor.

Regulation F adds detail around validation information and provides model form notices. The important operational issue is accuracy and consistency.

Teams need a process that can:

• Pull the right debt and creditor information
• Use an approved notice version
• Record when and how the notice was delivered
• Track disputes and requests for additional information
• Update the account workflow when a response is received
• Keep the relevant evidence available for review

A validation notice isn't just a document generation task. It depends on accurate account data, controlled templates, connected workflows, and clear ownership when a consumer responds.

Record retention under Regulation F

Recordkeeping is where policy becomes evidence.

Under § 1006.100, a debt collector generally needs to retain records that are evidence of compliance or noncompliance with the FDCPA and Regulation F from the date collection activity begins until three years after the debt collector’s last collection activity on the debt. The rule includes specific provisions and exceptions, so organizations should review the regulation and legal guidance that applies to their circumstances.

If a debt collector records telephone calls made in connection with debt collection, the collector also needs to retain each recording for three years after the call date.

For collections teams, relevant records may include:

• Telephone contact attempts and outcomes
• Call recordings, where calls are recorded
• Text messages, emails, and other electronic communications
• Consumer opt-out requests and preference updates
• Validation notices and associated account information
• Account status and workflow history
• Disputes, complaints, and escalation records
• User activity or account changes relevant to the collection process
• Records from third party agencies or service providers, where applicable

The exact records an organization needs to retain will depend on its legal obligations, systems, policies, and business model. The point is to make sure relevant evidence isn’t scattered across disconnected tools or lost when an account moves between teams.

Why fragmented systems make recordkeeping harder

Many collections operations use more than one system to manage customer contact and account activity.

This may include:

• A collections platform
• A dialer
• Email, SMS, or messaging tools
• A customer service platform
• Payment systems
• Document management tools
• Spreadsheets and shared inboxes
• Third party agency portals

Each system may hold part of the story. The problem comes when teams can’t bring that information together quickly enough.

This can lead to:

• Incomplete contact histories
• Preferences that don’t reach message scheduling systems
• Difficulty showing which workflow applied to an account
• Delays responding to a dispute, complaint, audit, or legal request
• Different teams working from different versions of the account history
• Too much reliance on manual data searches

Read more about how legacy collections systems create compliance risk.

Build a process that holds up

Strong communication and recordkeeping controls don’t come from one feature or one policy. They come from connecting people, processes, and systems.

Use this checklist to review your approach:

1. Define the approved process for each communication channel.
   Cover phone, email, text, mail, and any other channels your organization uses.
2. Keep contact history, preferences, and account status connected.
   The next action should reflect the most current information available.
3. Use controlled templates and version management.
   Teams should know which messages and notices are approved for use.
4. Set clear ownership for opt-outs, disputes, complaints, and exceptions.
   A customer request shouldn’t sit in an inbox without changing the account workflow.
5. Retain records in a secure, accessible system of record.
   Make it possible to retrieve relevant evidence when it is needed.
6. Train internal teams and third party partners.
   The process only works if people know how to follow it and when to escalate.
7. Test the process after a policy, system, vendor, or regulatory change.
   Check standard scenarios as well as missing data, conflicting instructions, and exception paths.
8. Review outcomes regularly.
   Look at complaints, overrides, failed communications, manual workarounds, and recurring exceptions.

Technology supports the process. It doesn’t own it.

Collections technology can help teams manage workflows, records, permissions, communication history, and customer context. It can make it easier to apply approved policies consistently and retrieve information when it matters.

It can’t interpret the law, decide whether an exception applies, or guarantee a compliant outcome.

Those responsibilities stay with the organization and its legal, compliance, operations, and risk teams.

For a closer look at how configurable workflows and controls can support collections operations, check out our guide to Configuring Collections Systems for Compliance Advantage.