Equifax: They answered every question I had and redirect...
A Equifax customer review by GetHuman user GetHuman-48239 from November 17th, 2017
Background on GetHuman-48239's case
GetHuman: GetHuman-48239 - can you tell our other Equifax customers when your case took place?
GetHuman-48239: Yes. It was morning, on November 12th.
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 GetHuman-48239 a list of common Equifax problems)
GetHuman-48239: "Fix credit score" was why I was trying to call.
GetHuman-48239'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.
GetHuman-48239: They answered every question I had and redirected me to other people if needed. The problem wasn't solved so soon, and they have screwed up on my credit. But this number did help connect me to an actual person, especially who knew what they were saying and doing.
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?
GetHuman-48239: 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-48239: 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?
GetHuman-48239: For that I would say one out of five.
GetHuman: And finally- any advice for other Equifax customers?
GetHuman-48239: 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 GetHuman-48239 taken from his Equifax customer service problem that occurred on November 12th, 2017.