Equifax: I went through hoops before I got back on gethu...
A Equifax customer review by GetHuman user ~stressless from November 21st, 2017
Background on ~stressless's case
GetHuman: ~stressless - can you tell our other Equifax customers when your case took place?
~stressless: Yeah. It was evening, on November 18th.
GetHuman: Did you reach out to Equifax, and if so, how?
GetHuman: And which of these common Equifax customer issues best describes the reason you wanted to talk to them?
(Shows ~stressless a list of common Equifax problems)
~stressless: "Unfreeze Credit" was why I was trying to call.
~stressless's review of Equifax customer service
GetHuman: So how would you sum up your experience for GetHuman's Equifax 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.
~stressless: I went through hoops before I got back on gethuman for this number. I couldn't get my credit report from annualcreditreport.com, so someone here accessed it and told me everything looks fine, and offered to send me my free credit report in the mail. I waited for him for *-* mins more and I was done! Whew!
GetHuman: Let's quantify your experience contacting Equifax. On a scale of 1 to 5, how easy is it go get help on a Equifax problem?
~stressless: 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?
~stressless: I'd give them a four out of five on communication.
GetHuman: And what about Equifax's ability to quickly and effectively address your problem?
~stressless: For that I would say three out of five.
GetHuman: And finally- any advice for other Equifax customers?
~stressless: Call them early in the day or late. Don't forget any personal or account information you might need for Equifax to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~stressless taken from his Equifax customer service problem that occurred on November 18th, 2017.