The Strict Liability Trap: Litigating Ignored 'Cease and Desist' Notices Under the FDCPA

If you sent a written request asking a debt collector to stop contacting you, and the calls or letters kept coming, federal law may have been violated the moment the next communication arrived. The Fair Debt Collection Practices Act gives consumers a powerful tool to shut down most debt collection communications by written notice — and it holds collectors accountable when their systems fail to honor that notice. The analysis below explains how cease-and-desist notices work under federal law, why collection agencies systematically fail to process them, and what evidence makes a § 1692c(c) claim enforceable. For a broader overview of your rights under the FDCPA and a tool to track collector communications against federal limits, see our Know Your Rights: Debt Collection Harassment page.

Third-party debt collection is a volume business heavily reliant on automated predictive dialers. When an account moves into default, agencies deploy software designed to call consumers repeatedly, banking on persistence to drive a payment. Federal law, however, provides consumers with a clear right to terminate most of this communication by written notice. When a debt collector ignores that notice, the calls and letters that follow may give rise to federal claims.

What Triggers a Communication Ban Under 15 U.S.C. § 1692c(c)?

The Fair Debt Collection Practices Act (FDCPA) restricts how and when a debt collector may communicate with a consumer. Under 15 U.S.C. § 1692c(c), a consumer can unilaterally terminate almost all communications from a third-party debt collector by providing written notice.

To trigger this protection, the consumer must notify the debt collector in writing that:

• The consumer refuses to pay the debt; OR
• The consumer wishes the debt collector to cease further communication.

Once that written notice is received, the collector's automated dialers must stop. The letters must stop. A single demand call placed after receipt of the notice — outside the narrow exceptions discussed below — can violate federal law.

The FDCPA is widely characterized as a strict liability statute, and many of its provisions impose liability without requiring proof of intent. The statute provides a narrow safety valve at 15 U.S.C. § 1692k(c): the "bona fide error" defense, which a collector may invoke if it proves the violation was unintentional and resulted from a bona fide error notwithstanding the maintenance of procedures reasonably adapted to avoid such error. Federal courts have generally interpreted this defense narrowly, and the Eighth Circuit requires defendants to prove they maintained procedures reasonably adapted to avoid the specific error that occurred — meaning the defense fails where a procedural or systemic gap allowed the violation rather than an isolated clerical mistake.

Why Compliance Departments Fail: The "Left Hand, Right Hand" Problem

Sophisticated collection agencies typically operate large, segmented call centers. When a consumer sends a written cease-and-desist letter via certified mail, the letter usually routes to a compliance or mailroom department. If the agency fails to promptly update the consumer's file in its central database, the automated predictive dialer — the "right hand" — simply continues calling.

In federal court, administrative delay and systemic software failures are typically not viable defenses for FDCPA violations, and they are often the precise circumstances in which the bona fide error defense fails — because a procedure that allows a cease-and-desist notice to sit unprocessed while the dialer continues is not, by definition, a procedure reasonably adapted to avoid the violation.

The Three Statutory Exceptions

To evaluate a potential FDCPA claim, it is critical to understand the boundaries of the law. After receiving a cease-and-desist notice, a collector is legally permitted to contact the consumer for only three specific reasons:

• To advise of termination: to notify the consumer that further efforts to collect are being terminated.
• To notify of ordinary remedies: to notify the consumer that the debt collector or creditor may invoke specified remedies ordinarily invoked by such collector or creditor.
• To notify of specific action: to notify the consumer that the debt collector or creditor intends to invoke a specified remedy (such as filing a lawsuit).

A post-notice communication that demands payment or attempts to negotiate a settlement falls outside these exceptions and constitutes a statutory violation.

What Evidence Establishes a § 1692c(c) Claim?

Effective FDCPA cease-and-desist claims rest on a clear evidentiary record. Two pieces of evidence carry most of the case:

• Proof of delivery of the written notice — typically a certified mail return receipt establishing the date the collector received the cease-and-desist letter.
• A record of post-notice communications — call logs, voicemails, screenshots of text messages, and copies of subsequent letters, each timestamped after the date of delivery.

With this record in hand, a well-documented pre-litigation demand outlines the specific notice, the proof of delivery, and the subsequent violations. The FDCPA provides for actual damages, statutory damages, and fee-shifting under 15 U.S.C. § 1692k — making early resolution a common outcome where the evidentiary record is clean.

Midwest Consumer Law PLLC handles FDCPA cease-and-desist matters in federal court.