Annual Free Credit Report: I have a non working printer and was trying to...
A Annual Free Credit Report customer review by GetHuman user ~Mad from November 16th, 2017
Background on ~Mad's case
GetHuman: ~Mad - can you tell our other Annual Free Credit Report customers when your case took place?
~Mad: Yup. It was middle of the night, on November 7th.
GetHuman: Did you reach out to Annual Free Credit Report, and if so, how?
GetHuman: And which of these common Annual Free Credit Report customer issues best describes the reason you wanted to talk to them?
(Shows ~Mad a list of common Annual Free Credit Report problems)
~Mad: "Complaint" was why I was trying to call.
~Mad's review of Annual Free Credit Report customer service
GetHuman: So how would you sum up your experience for GetHuman's Annual Free Credit Report 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.
~Mad: I have a non working printer and was trying to find out how to have a report emailed to me. I can not get an answer or any satisfaction.
GetHuman: Let's quantify your experience contacting Annual Free Credit Report. On a scale of 1 to 5, how easy is it go get help on a Annual Free Credit Report problem?
~Mad: I'd give them a three 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?
~Mad: I'd give them a one out of five on communication.
GetHuman: And what about Annual Free Credit Report's ability to quickly and effectively address your problem?
~Mad: For that I would say five out of five.
GetHuman: And finally- any advice for other Annual Free Credit Report customers?
~Mad: Call them early in the day or late. Don't forget any personal or account information you might need for Annual Free Credit Report to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~Mad taken from his Annual Free Credit Report customer service problem that occurred on November 7th, 2017.