Equifax: I wanted to unfreeze my account to buy a new ca...
A Equifax customer review by GetHuman user GetHuman-404440 from November 28th, 2017
Background on GetHuman-404440's case
GetHuman: GetHuman-404440 - can you tell our other Equifax customers when your case took place?
GetHuman-404440: Yes I can. It was middle of the night, on November 27th.
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-404440 a list of common Equifax problems)
GetHuman-404440: "Check credit score" was why I was trying to call.
GetHuman-404440'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-404440: I wanted to unfreeze my account to buy a new car tomorrow. Have to wait *-** days for a * digit number. The internet was very hard to use as well as the phone prompts to get me where I needed to go. These guys some more work to do.
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-404440: I'd give them a two 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-404440: I'd give them a three out of five on communication.
GetHuman: And what about Equifax's ability to quickly and effectively address your problem?
GetHuman-404440: For that I would say two out of five.
GetHuman: And finally- any advice for other Equifax customers?
GetHuman-404440: 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-404440 taken from his Equifax customer service problem that occurred on November 27th, 2017.