Equifax: Spoke to "John". He had an accent, but VERY hel...
A Equifax customer review by GetHuman user ~CharlieChainsaw from November 15th, 2017
Background on ~CharlieChainsaw's case
GetHuman: ~CharlieChainsaw - can you tell our other Equifax customers when your case took place?
~CharlieChainsaw: Yes. It was afternoon, on November 6th.
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 ~CharlieChainsaw a list of common Equifax problems)
~CharlieChainsaw: "Check credit score" was why I was trying to call.
~CharlieChainsaw'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.
~CharlieChainsaw: Spoke to "John". He had an accent, but VERY helpful and courteous. Answered every single one of my questions. Told me why I was having difficulty viewing my report online, and is mailing it to me directly. Great phone number resource! Thanks!
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?
~CharlieChainsaw: I'd give them a four 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?
~CharlieChainsaw: I'd give them a five out of five on communication.
GetHuman: And what about Equifax's ability to quickly and effectively address your problem?
~CharlieChainsaw: For that I would say two out of five.
GetHuman: And finally- any advice for other Equifax customers?
~CharlieChainsaw: 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 ~CharlieChainsaw taken from his Equifax customer service problem that occurred on November 6th, 2017.