Equifax: I understood *nd woman. I refused to give my s...
A Equifax customer review by GetHuman user GetHuman-370708 from November 23rd, 2017
Background on GetHuman-370708's case
GetHuman: GetHuman-370708 - can you tell our other Equifax customers when your case took place?
GetHuman-370708: Yup. It was late at night, 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 GetHuman-370708 a list of common Equifax problems)
GetHuman-370708: "Freeze Credit" was why I was trying to call.
GetHuman-370708'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-370708: I understood *nd woman. I refused to give my social sec. * to supervisor (cannot be required except by govt.) and phone is not secure. So she refused to get my file. I gave name, address, birth date and NO ONE ELSE in the US has those. They have NO right to SS *s.
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-370708: 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-370708: I'd give them a one out of five on communication.
GetHuman: And what about Equifax's ability to quickly and effectively address your problem?
GetHuman-370708: For that I would say four out of five.
GetHuman: And finally- any advice for other Equifax customers?
GetHuman-370708: 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-370708 taken from his Equifax customer service problem that occurred on November 18th, 2017.