FreeCreditReport.com: They was Very Rude & the CUSTOMER SERVICE WAS V...
A FreeCreditReport.com customer review by GetHuman user GetHuman-49503 from November 24th, 2017
Background on GetHuman-49503's case
GetHuman: GetHuman-49503 - can you tell our other FreeCreditReport.com customers when your case took place?
GetHuman-49503: Yup. It was morning, on November 19th.
GetHuman: Did you reach out to FreeCreditReport.com, and if so, how?
GetHuman: And which of these common FreeCreditReport.com customer issues best describes the reason you wanted to talk to them?
(Shows GetHuman-49503 a list of common FreeCreditReport.com problems)
GetHuman-49503: "Question" was why I was trying to call.
GetHuman-49503's review of FreeCreditReport.com customer service
GetHuman: So how would you sum up your experience for GetHuman's FreeCreditReport.com customer community? We'll censor any IDs, numbers, or codes and any inappropriate words here out of respect to the millions of other customers using this resource.
GetHuman-49503: They was Very Rude & the CUSTOMER SERVICE WAS VERY BAD!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
GetHuman: Let's quantify your experience contacting FreeCreditReport.com. On a scale of 1 to 5, how easy is it go get help on a FreeCreditReport.com problem?
GetHuman-49503: I'd give them a five out of five for ease of finding your way to help.
GetHuman: What about quality of communication. How would you rate that on a 1 to 5 scale?
GetHuman-49503: I'd give them a four out of five on communication.
GetHuman: And what about FreeCreditReport.com's ability to quickly and effectively address your problem?
GetHuman-49503: For that I would say one out of five.
GetHuman: And finally- any advice for other FreeCreditReport.com customers?
GetHuman-49503: Call them early in the day or late. Don't forget any personal or account information you might need for FreeCreditReport.com to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from GetHuman-49503 taken from his FreeCreditReport.com customer service problem that occurred on November 19th, 2017.