BRIAN M. COGAN, District Judge.
Before me is the motion of Midland Credit Management, Inc. ("MCM") and Midland Funding, LLC's ("MF") (collectively, "defendant") for summary judgment, as well as plaintiff's motion for class certification. Plaintiff alleges that defendant violated the Fair Debt Collection Practices Act ("FDCPA") by attempting to collect a $131 debt plaintiff allegedly owed Verizon. Plaintiff argues that defendant's attempt to seek an explanation from him when it marked his debt as disputed, as well as its failure to report his debt as disputed, were both illegal. However, the undisputed facts show defendant did nothing wrong in attempting to collect this debt, even though, as I have explained in a prior decision, plaintiff attempted to entrap it into committing an FDCPA violation, and that defendant did report the debt as disputed. For those reasons, defendant's motion for summary judgment is granted. Moreover, even if there were issues of fact, I would deny class certification.
In 2010, plaintiff switched his phone service to Verizon. He previously had Verizon service but had changed to another carrier. As a result of his reversion to Verizon, it performed some work on plaintiff's phone line to ensure he had adequate service. Verizon billed him a $131 fee for that work. Plaintiff advised Verizon that he should not have been charged this fee and he never paid the bill.
MCM and MF acquired the debt from Verizon in July 2013. MF purchased the debt and placed it with MCM for servicing.
Defendant's records prove that it sent plaintiff an initial collection letter, dated August 9, 2013, demanding payment for the debt, which was not returned as undeliverable. Plaintiff asserts that he never received this letter until it was produced in discovery, but although there is a factual dispute as to whether plaintiff received the letter, plaintiff cannot genuinely dispute that it was sent.
MCM uses a set of codes to determine how the company will handle an account when a consumer declines or fails to pay. Code 050 is used to document verbal disputes on an account; code 261 indicates a refusal to pay; and code 289 deletes the account, removes it from collection activity, and sends an update to each of the three major Credit Reporting Agencies — TransUnion, Experian, and Equifax (collectively, the "CRAs"). It was also MCM's procedure to label all disputes for accounts located in New York with a 050 code.
On October 17, 2013, plaintiff called MCM. Plaintiff set up a tape recorder before making the call and recorded the entire call. The call is set forth in haec verba and discussed at length in an earlier decision that I wrote in this case,
Defendant's records of plaintiff's account contain the agent's notes of the call, and show that she marked the account as "deleted" following the call. Defendant's records also establish that on the same day, following the call, it sent plaintiff a letter advising him that it had ceased collection efforts and had instructed the CRAs to delete the information MCM had reported regarding the account. The letter stated, in part:
Defendant's internal procedures recognize the options allowed under the FDCPA when it determines that a debt is disputed. Defendant can simply mark and report the debt to the CRAs as disputed, and either leave it in that category or attempt to confirm the validity of the debt and, if it can confirm validity, proceed with collection efforts. Alternatively, upon marking the debt as disputed, defendant can simply delete it, which it will presumably do if it determines that the debt is not worth the trouble of pursuing.
The records show that following the call, defendant coded the account as "289," which, as explained above, meant that the account was disputed and deleted. There is no genuine dispute that within six days after the call, defendant sent multiple requests to Experian, TransUnion, and Equifax, starting on October 23, 2013, asking them to delete the item in question. These requests were reiterated on a monthly basis three times thereafter pursuant to defendant's policy of issuing repeated requests to the CRAs to increase the likelihood that the agencies will comply with requests for deletion.
Plaintiff has failed to produce a credit report from any of the three CRAs showing that, following his telephone call with defendant, his Verizon debt continued to appear, even though those companies are required to produce his credit reports to him on demand. In their place, he has proffered a report from a company called "CreditCheck Total," which is apparently a subsidiary of Experian. This is a commercial subscription service made available to consumers which purports to summarize the reports of the three CRAs, and additionally provide a putative FICO score, all for a fee. Although plaintiff's report from CreditCheck Total continues to show the Verizon debt, it also contains a disclaimer making it clear that it is not to be relied upon as a report from the three recognized CRAs:
Summary judgment is appropriate when "the movant shows that there is no genuine dispute as to any material fact and the movant is entitled to judgment as a matter of law," Fed. R. Civ. P. 56(a), and when "the record taken as a whole could not lead a rational trier of fact to find for the non-moving party."
Plaintiff claims defendant committed four overlapping violations of the FDCPA, all of which stem from a statutory provision that prohibits the use of false or misleading representations in connection with the collection of a debt. First, he contends that defendant violated 15 U.S.C. § 1692e(8) by failing to report to the CRAs that his debt was disputed. Second, he argues that defendant violated § 1692e(10), by falsely representing that he needed to give a reason for his dispute and attempting to obtain more information from him. Third, he contends that the deletion letter, which stated the CRAs had been notified and told to delete the debt, violated § 1692e(2)(A), which prohibits false representations of the character or legal status of a debt, and § 1692e(5), because defendant had not properly notified the CRAs that the debt was disputed. Included in this third claim is also an allegation that by representing that the debt had been reported as disputed, defendant violated § 1692e(10). Finally, plaintiff asserts that defendant violated § 1692e(2)(A) because it falsely represented to him that he had a valid debt owed to Verizon and then it attempted to collect upon that debt by making false representations about the validity of that debt under §§ 1692e(8),(10).
Even construing the facts most favorably to him (like assuming he never received either of the two mailings that defendant sent him), and applying the "least sophisticated consumer" standard (although plaintiff is a lawyer and anything but an unsophisticated consumer),
It is a violation of the FDCPA to communicate "credit information which is known or which should be known to be false, including the failure to communicate that a disputed debt is disputed." 15 U.S.C. § 1692e(8). There is insufficient evidence in this record upon which a reasonable jury could find that, once plaintiff gave it notice of the dispute, defendant failed to communicate that to the CRAs. Defendant's regularly-kept business records clearly show that within six days of plaintiff's telephone call, it contacted each of the three agencies and reported the debt as disputed. Indeed, defendant repeated the notice three times. That is more than the law required it to do. In addition, despite plaintiff's denial of receipt, the records indicate clearly that defendant notified plaintiff of its communication with the CRAs, whether plaintiff received it or not.
Plaintiff's answer to this is to speculate that defendant's records are not what they purport to be, or that the records do not reflect what actually occurred. There are two main pillars upon which this argument rests. The first is the CreditCheck Total report, which continues to list the debt. But it specifically disclaims accuracy in the manner required under the FDCPA. In addition, nothing in the FDCPA required defendant to report the dispute to CreditCheck Total.
More fundamentally, even if the CRAs had continued to report the debt, it would not prove that defendant failed to communicate the dispute. Defendant is not a guarantor of the CRAs' compliance with its request, and it obviously has no control over the CRAs. Thus, if a jury were to conclude that defendant did not mark the debt as disputed because CreditCheck Total continued to list it, I would have to set that verdict aside as speculative and unreasonable.
Plaintiff also contends that there is an issue of fact as to whether defendant really advised the CRAs to delete the account, because the request for deletion also notes that there is a "current balance" and "past due amount" of $131. Apparently, plaintiff believes that when a consumer disputes an account, it exonerates him from the liability, and therefore defendant should have advised the CRAs that there was a zero balance on this account.
That would be a fine kettle of fish indeed. It would obviate the need for the bankruptcy courts, as it would allow a debtor to eliminate debts simply by demanding their deletion by creditors and collection companies. It would obviously turn the consumer credit markets upside down. But that is not the intent of the FDCPA. Rather, the purpose of the FDCPA, inter alia, is to place a halt, whether temporary or permanent, on collection efforts once a debtor alleges that a debt is not valid. It is not a device whereby a debtor can force a collection company to write down his debt to zero. It does not wipe out the debt. The collection company has to maintain the ability to, at least, file a proof of claim in bankruptcy if the debtor later seeks bankruptcy protection, as some do.
The second pillar of plaintiff's argument is to mischaracterize defendant's records and record keeping procedures in several respects. Plaintiff asserts that because his account, following his call, was marked "289" instead of "050," defendant did not, in fact, mark the debt as disputed. That argument ignores the unrebutted testimony of defendant's Rule 30(b)(6) witness, who testified quite clearly that the 050 code is merely a subset of the 289 code. In other words, a 050 code leaves defendant free to investigate the debt and, depending on the results of the investigation, to restore the account to undisputed status. A 289 code, in contrast, identifies a disputed account as to which no further action is going to be taken. As the witness testified, and as the documents confirm, a 289 code is the next step beyond a 050 code, and can be used to signify that no further collection activity should be taken. Defendant in this instance simply skipped the 050-code stage, probably because it was so obvious from the evasive responses that plaintiff gave to the collection agent in his telephone call, that this $131 account was going to be more trouble than it was worth. Defendant's actions following the call — contacting plaintiff and the CRAs and notifying them that the debt was deleted — were completely consistent with the unrebutted testimony.
No matter how plaintiff tries to torture it, the undisputed record shows that following his telephone call, defendant took no further action to collect his debt; it notified him that it was deleting it; and it notified the CRAs to the same effect. That is all that the law required it to do.
Plaintiff argues that defendant violated section 1692e(10) of the FDCPA by asking too many questions of him when he called to dispute his debt. Section 1692e(10) prohibits a debt collector from using "any false representation or deceptive means to collect or attempt to collect any debt." 15 U.S.C. § 1692e(10). The right to dispute a debt is one of the most fundamental rights set forth under the provision of the FDCPA addressing the validation of debts.
Defendant's policies instruct its employees to ask follow-up questions when a consumer advises that he is disputing his debt. I see no problem with that under the law at all. There is nothing unreasonable about allowing a debt collector to ask an individual to explain why he is disputing his debt, as long as it does not interfere with an individual's ability to dispute that debt. Asking follow-up questions enables the debt collector to focus its investigation on what the problem is with the debt, rather than shooting in the dark. It might even allow the collection agency to resolve the dispute on the spot. If the consumer answers the question by saying, "I only owe $120, not $131," the collection agent might well say, "fine, we'll take it." Problem solved.
There may come a point in a verbal exchange where a debt collector is intentionally browbeating a consumer to deter him from disputing his debt. It also might arguably be the case that if a consumer states, "I want to dispute the debt, and I decline to tell you why," the collector might have to stop asking questions and just mark the debt as disputed (although plaintiff has cited no case so holding). But nothing resembling either of those scenarios happened here. Rather, the transcript is quite clear that it was plaintiff who was bobbing and weaving, evading the questions and harassing the collection agent, who was just trying to do her job, find out what the problem was, and perhaps even resolve the dispute. Plaintiff's evasiveness, his cat-andmouse approach, virtually begged for follow-up questions because instead of just refusing to state what the problem was, plaintiff answered with non-sequiturs and put his own questions to her, all in a very obvious attempt to get her to say something improper. I commend the transcript,
What plaintiff did is not what the least sophisticated consumer would do, because the least sophisticated consumer would not be an experienced FDCPA lawyer trying to manufacture an FDCPA claim.
Nothing in MCM's policies, or the phone call with plaintiff, prevented plaintiff from disputing the debt. As I held in an earlier opinion in this case, "[t]he fact that defendant's representative wanted a smidgen of detail about the dispute, when plaintiff was being obviously and intentionally vague, does not amount to a statutory violation."
Finally, and relatedly, plaintiff contends that the October 17, 2013 letter, in which defendant advised him that it was ceasing collection efforts and reporting the debt as deleted to the CRAs, was a false representation under §§ 1692e(2)(A) and 1692e(10) because, in fact, it did not cease collection efforts and did not advise the CRAs to delete the debt. Since, as discussed above, the record demonstrates that defendant properly notified the CRAs that plaintiff's debt was disputed and ceased collection activities, this claim fails.
It is a violation of the FDCPA to falsely represent the legal status of a debt.
Plaintiff's final claim is that defendant violated the FDCPA because it represented that plaintiff had a valid outstanding debt with Verizon and it attempted to collect upon that debt before verifying it was valid. Plaintiff further argues that because he had disputed the debt with debt collectors retained by Verizon prior to the sale of his debt to defendant, which I assume he did, knowledge of that dispute should be imputed to it.
Defendant did not violate the FDCPA by attempting to collect on the debt prior to verifying it. Defendant bought the debt from Verizon which represented that plaintiff owed it $131.21. Defendant's initial letter to plaintiff, even assuming plaintiff never received it, provided adequate notice of how to dispute his debt; that is all defendant had to do. And once plaintiff disputed the debt, defendant was placed on notice that it either needed to cease collection or verify the debt. Defendant had no obligation to independently investigate the debt prior to beginning collection, and there is no reason that plaintiff's prior dispute of the debt with Verizon's debt collectors should have been known to it.
Even if I were not granting defendant's motion for summary judgment, I would deny plaintiff's motion for class certification because he has failed to satisfy the requirements of Rule 23. Rule 23(a) of the Federal Rules of Civil Procedure requires that any proposed class action: "(1) be sufficiently numerous, (2) involve questions of law or fact common to the class, (3) involve class plaintiffs whose claims are typical of those of the class, and (4) involve a class representative or representatives who adequately represent the interests of the class."
In addition to satisfying each of the four prerequisites listed in Rule 23(a), a party seeking class certification must satisfy one of the subsections of Rule 23(b). Plaintiff seeks to certify a class pursuant to subsection 23(b)(3) and therefore must show that "questions of law or fact common to class members predominate over any questions affecting only individual members, and that a class action is superior to other available methods," for adjudicating the controversy. Fed. R. Civ. P. 23(b)(3).
Plaintiff has proposed either a nationwide or New York-only class which he defines as follows: "All persons who, according to Defendants' records (a) have a United States mailing address; (b) within one year before the filing of this action; (c) verbally disputed the debt; and (d) were asked probing questions regarding the reason for the dispute." (Emphasis added). The definition raises numerous problems under Rule 23, but it suffices to note two glaring ones.
The touchstone of ascertainability "is whether the class is sufficiently definite so that it is administratively feasible for the court to determine whether a particular individual is a member."
Plaintiff's proposed class definition would require a two-step process to identify class members. The first step is to cull those consumers to whom defendant assigned a 050 or 261 code within a one year reach-back period.
The second step requires a determination of which of these "050/261" consumers were asked "probing questions." How does plaintiff intend to determine that? I note at the outset that the adjective "probing" is qualitative in nature. One dictionary defines it as "a careful examination or investigation of something."
Defendant itself uses the word "probing" in its procedures manual to give examples of the kinds of questions that a collection agent should ask under certain verbal dispute scenarios, which further illustrates how subjective any determination of the class would be. For example, if a consumer advises the agent that the debt is the product of fraud, one of the suggested "probing" questions for the agent is, "When was the alleged fraud committed?" That hardly seems probing to me, but apparently it does to defendant. Similarly, if a consumer advises the agent that the debt was previously paid, a suggested "probing" question is, "How much did you pay?" Even if one determines that these questions are "probing" within plaintiff's class definition, we encounter the problem that there is nothing illegal about them under the FDCPA; the class definition thus picks up some conduct that might be illegal as deterring the least sophisticated consumer from disputing his debt, and other conduct that plainly would not.
It is apparent what plaintiff is attempting to do by limiting the class to those who were asked "probing" questions. Obviously, he cannot expressly admit that he is seeking a class of those consumers who were asked any questions, as the FDCPA clearly does not prohibit that. So what he really means is to define the class as those who were asked questions "sufficient to deter the least sophisticated consumer from disputing their debt." But he cannot do that either, because it is so obviously qualitative and would so clearly require a case-by-case determination. Therefore, he has seized upon the word used in defendant's procedures manual — "probing" — in the hope of making the inquiry seem less qualitative. But as defendant's procedures manual shows, that inquiry is not less qualitative. It still requires a case-by-case inquiry to determine which questions have an improper deterrent effect and which do not.
Moreover, although defendant's procedures manual gives a few sample questions, the nature of conversation, as plaintiff's exchange with the agent shows, is dynamic. Whether and how topics are covered by a collection agent depends on what she hears from the consumer. A few sample questions may be a starting point, but until artificial intelligence technology increases substantially beyond its current level (at which point collection companies may replace their agents with computers), the particular questions asked will depend on the particular statements that the consumer makes. And yet it is the agent's particular questions that have to be tested under the FDCPA.
But there is more. Despite discovery, plaintiff has given no indication of how we are to ascertain what questions any particular consumer was asked. There is no indication that defendant maintains any recordings of those conversations (unlike plaintiff), and even if it did, as demonstrated above, they would have to be reviewed conversation by conversation. Plaintiff has submitted no written records of any contact between defendant and any consumer, save one — his own. And even that one does not fully disclose what questions he was asked.
Defendant's record of plaintiff's account has a section memorializing contacts with him. One part of that section is a column entitled "Notes," in which the agent summarized the call. In its entirety, she typed in the following:
Because we have the transcript, we know exactly what questions were asked. Without it, we could infer some of them from this note, but not all of them. We would also be misled, because we know from the transcript that the agent did not ask about whether there was fraud; he did not let her get that far. Thus, even putting aside the need to review each of these notes individually to ascertain class membership, I do not see how we can rely on these notes to ascertain whether any particular class member was asked "probing" questions.
Ultimately, although he does not expressly admit it, plaintiff's argument devolves into effectively eliminating the word "probing" from the class definition. His point is that since defendant's policies require the asking of questions, it doesn't matter what questions were asked. But I think any meaningful class would have to distinguish between reasonable, legitimate questions, and questions having an undue, deterrent effect, else we would have class members with no claims under the FDCPA. Plaintiff offers no way to make that distinction because there is none. The class he proposes is utterly unascertainable.
The other glaring defect is that plaintiff is an inadequate representative of his class. Adequacy of representation focuses on the fitness of a purported class representative to competently discharge the responsibility of litigating for the class on behalf of absent class members. Under this prong of Rule 23(a), a court must ensure that the putative representative "possess[es] the same interests and suffer[s] the same injur[y] as the class members."
Whether a plaintiff faces unique defenses is an appropriate factor for the court to consider under the adequacy prong.
Plaintiff faces a defense that is undoubtedly unique to him — it certainly wouldn't be one to which the least sophisticated consumer would be subjected — and which will make it very risky for him to adequately represent the entire class. Plaintiff will be subject to the argument that his FDCPA claims should be rejected because by attempting to entrap the collection agent into violating the statute he will be unable to allege a material violation of the FDCPA.
In
Plaintiff certainly directed his case in a similar fashion. At any trial, plaintiff would be extensively and effectively cross-examined on his attempt to entrap defendant into violating the FDCPA. Specifically, it would be pointed out to the jury that instead of just answering the question of why he was disputing his debt, he engaged in a game of cat-and-mouse. His experience as an FDCPA lawyer would be used to show that he knew exactly what he was doing, and that experience would further differentiate him from the class. It is entirely possible that even if other members of the class had valid claims, plaintiff's behavior would undermine his claim, and would cause him, and therefore the entire class, to suffer an adverse verdict.
Defendant's motion for summary judgment is therefore granted, and the Third Amended Complaint is dismissed. Plaintiff's motion for class certification is denied. The Clerk is directed to enter judgment accordingly.
Second, plaintiff contends that one of defendant's documents showed his account as "open." He nowhere explains the provenance or even the date of this document. In any event, defendant's Rule 30(b)(6) witness made it clear that in defendant's internal terminology, "open" does not mean "undeleted" and "closed" does not mean "deleted."