Cerrato v. Solomon

909 F. Supp. 2d 139, 2012 WL 6621339, 2012 U.S. Dist. LEXIS 179132
CourtDistrict Court, D. Connecticut
DecidedDecember 18, 2012
DocketCivil Action No. 3:11-cv-623 (JCH)
StatusPublished
Cited by9 cases

This text of 909 F. Supp. 2d 139 (Cerrato v. Solomon) is published on Counsel Stack Legal Research, covering District Court, D. Connecticut primary law. Counsel Stack provides free access to over 12 million legal documents including statutes, case law, regulations, and constitutions.

Bluebook
Cerrato v. Solomon, 909 F. Supp. 2d 139, 2012 WL 6621339, 2012 U.S. Dist. LEXIS 179132 (D. Conn. 2012).

Opinion

RULING RE: DEFENDANT’S MOTION FOR PARTIAL SUMMARY JUDGMENT (DOC. NO. 66) AND PLAINTIFF’S CROSS-MOTION FOR PARTIAL SUMMARY JUDGMENT (DOC. NO. 71)

JANET C. HALL, District Judge.

I. INTRODUCTION

Plaintiff Judith Cerrato (“Cerrato”) brings this action against defendant Solomon & Solomon (“Solomon”) for violation of the Fair Debt Collection Practices Act, 15 U.S.C. § 1692c (“FDCPA”), and for Connecticut state law invasion of privacy by intrusion upon seclusion.

II. STATEMENT OF FACTS

A. The Debts

Cerrato incurred a financial obligation to Citibank, which was referred to Solomon for collection on August 4, 2010.1 Plaintiffs Local Rule 56(a)(2) Statement (Doc. No.) ¶ 1-2. Solomon assigned account number 23234679 (“account 79”) to that file. Id. at ¶ 2. Citibank previously referred two other files to Solomon involving debts incurred by Cerrato. Id. at ¶ 3. Those files were assigned numbers 21288258 (“account 58”) and 22325563 (“account 63”), and were received for collection on November 7, 2008, and August 31, 2009, respectively. Id; Defendant’s Local Rule 56(a)(2) Statement (Doc. No. 84) at ¶ 4-5. Account 58 went into suit on or before September 21, 2009. Def.’s L.R. 56(a)(2) [141]*141at ¶ 4. Account 63 went into suit on or before March 2, 2010. Id. at ¶ 5. Account 79 went into suit on or before January 1, 2011.2 Id. at ¶ 6.

Solomon began calling Cerrato on account 58 in 2009. Id. at ¶ 7. Cerrato sent a cease and desist letter on September 12, 2009, on account 58.3 Id. at ¶ 8. Solomon received the cease and desist letter on September 12, 2009. Id. at ¶ 9. Despite receiving the notice, Solomon made six more calls to Cerrato before stopping on September 22, 2009. Id. at ¶ 10. In August 2010, Solomon began calling Cerrato again, this time in reference to account 79. Id. at ¶ 11. Between August 16, 2010, and February 2, 2011, Solomon called Cerrato 117 times. Id. at ¶ 12.

On February 3, 2011, Cerrato faxed Solomon a notice demanding that it stop calling. Id. at ¶ 13. The four page letter stated that it was “[Regarding all alleged Citibank Accounts” and included a copy of the September 9, 2009 letter. Id. at ¶ 14. The February fax also stated: “[t]he following is a copy of the fax sent on 09-12-2009 and also a new NOTICE TO CEASE COMMUNICATION.” Id.

On February 4, 2010, Tina Collins, an administrative support clerk at Solomon, processed the cease and desist letter from Cerrato.4 Def.’s L.R. 56(a)(2) at ¶ 16. Ms. Collins noted that Solomon should cease and desist communication for account 92, but not the other Citibank accounts. Def.’s L.R. 56(a)(2) at ¶ 21. According to Cerrato, Ms. Collins noted only account 92 because it was the only account number listed on the letter. PI. L.R. 56(a)(2) at ¶ 21.

After receiving the letter, between February 4, 2011 and March 8, 2011, Solomon called Cerrato eight times. Def.’s L.R. 56(a)(2) at ¶ 24. According to Solomon, it utilizes an automatic dialer for outgoing calls to reach customers. A computer generated call log keeps track of all calls. If the consumer answers the telephone, the automatic dialer routes the call to a collection representative. If the call is not answered, and is instead forwarded to an answering machine or voicemail box, the call is terminated by the automatic dialer and recorded in the log as an “attempt.” Def.’s L.R. 56(a)(1) at ¶ 8. According to Solomon, the eight telephone calls made to Cerrato between February 4, and March 8, were listed as “attempts” on the Solomon call logs, and therefore, no Solomon representative spoke to Cerrato. Id. at ¶ 9. However, according to Cerrato, each time Solomon called, its name appeared in the caller identification display of Cerrato’s phone. PI. L.R. 56(a)(1) at ¶ 25. Cerrato knew that Solomon was calling her and that the calls were about a debt, as they had been for the past several years.5 Id.

[142]*142On March 8, 2011, Solomon collector Nicole Esposito called Cerrato about account 79, but Cerrato did not answer. Def.’s L.R. 56(a)(2) at ¶ 26. Ms. Esposito noticed that the February 2, 2011 cease and desist letter had not been applied to account 79. PI. L.R. 56(a)(2) at ¶ 11. As such, Ms. Esposito followed Solomon’s practices and procedures to avoid contact with debtors after receiving a notice to cease and desist.6 Def. L.R. 56(a)(1) at ¶ 11. After Ms. Esposito took such action, the calls ceased. PI. L.R. 56(a)(2) at ¶ 11.

B. Processing Cease and Desist Letters

Solomon designed practices and procedures to avoid violations of the FDCPA, 15 U.S.C. § 1692c. Its employees are trained about the import of a debtor’s request that Solomon cease communications regarding the debt and the manner in which the FDCPA and Solomon protect the debtor’s rights following such requests. PI. 56(a)(2) at ¶ 12. New hires receive in-depth training as to the rules and requirements of the FDCPA as a whole. Thereafter, Solomon provides quarterly training and, depending upon the employee’s function, either quarterly or periodic testing with respect to the FDCPA. Id. at ¶ 13. If a seminar, new decision, or simply a question posed by an employee, arises in between quarterly training, an email advising of any changes in the law, or Solomon’s practices and procedures with respect to the same, is distributed as an update to Solomon’s staff. Id. at ¶ 14. According to Solomon, in order to avoid violations of the FDCPA’s provision preventing debt collectors from contacting debtors, Solomon’s training and testing materials specifically instruct employees as to the meaning and import of a cease and desist letter. Def.’s L.R. 56(a)(1) at ¶ 15. Cerrato contests this claim because Solomon’s testing and literature merely states that employees are allowed to contact a debtor one more time after receiving a cease and desist letter. PI. L.R. 56(a)(2) at ¶ 15.

Solomon’s computer system was designed to include protections to honor cease and desist communications and to avoid violations of the FDCPA. In this regard, Solomon uses a specific code, “ONTC,” to indicate that a debtor has sent a cease and desist letter requesting no further contact with respect to the debt. The ONTC code means to stop action on the account. PI. 56(a)(2) at ¶ 16. According to Solomon, when a cease and desist letter is received, Solomon’s employees are trained to docket the notice and place the “ONTC” code on the account. Def.’s 56(a)(1) at ¶ 16. However, Cerrato claims that employees are not trained to note the [143]*143“ONTO” code on all accounts when a cease and desist letter is received. PI. 56(a)(2) at ¶ 16.

Ms. Collins, who processed Cerrato’s cease and desist letter, has worked at Solomon since approximately 2008. PI. 56(a)(2) at ¶ 17. According to Solomon, Ms. Collins received training with regard to Solomon’s policies for preventing FDCPA violations, and specifically, the import of a cease and desist request as well as the proper method for coding such requests.

Free access — add to your briefcase to read the full text and ask questions with AI

Related

Litt v. Portfolio Recovery Associates LLC
146 F. Supp. 3d 857 (E.D. Michigan, 2015)
Rush v. Portfolio Recovery Associates LLC
977 F. Supp. 2d 414 (D. New Jersey, 2013)
Lee v. Kucker & Bruh, LLP
958 F. Supp. 2d 524 (S.D. New York, 2013)
Sussman v. I.C. System, Inc.
928 F. Supp. 2d 784 (S.D. New York, 2013)

Cite This Page — Counsel Stack

Bluebook (online)
909 F. Supp. 2d 139, 2012 WL 6621339, 2012 U.S. Dist. LEXIS 179132, Counsel Stack Legal Research, https://law.counselstack.com/opinion/cerrato-v-solomon-ctd-2012.