FreeCreditReport.com: Wow just like the person below, they offered a...
A FreeCreditReport.com customer review by GetHuman user ~anonymous from November 22nd, 2017
Background on ~anonymous's case
GetHuman: ~anonymous - can you tell our other FreeCreditReport.com customers when your case took place?
~anonymous: Sure. It was middle of the night, on November 14th.
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 ~anonymous a list of common FreeCreditReport.com problems)
~anonymous: "Question" was why I was trying to call.
~anonymous'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.
~anonymous: Wow just like the person below, they offered a discount to keep service, the rate was guaranteed for * years but i still canceled
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?
~anonymous: 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?
~anonymous: I'd give them a two out of five on communication.
GetHuman: And what about FreeCreditReport.com's ability to quickly and effectively address your problem?
~anonymous: For that I would say one out of five.
GetHuman: And finally- any advice for other FreeCreditReport.com customers?
~anonymous: 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 ~anonymous taken from his FreeCreditReport.com customer service problem that occurred on November 14th, 2017.