Equifax Freeze Line: Indian call center apparently. Not great Englis...
A Equifax Freeze Line customer review by GetHuman user ~Anonymous from November 14th, 2017
Background on ~Anonymous's case
GetHuman: ~Anonymous - can you tell our other Equifax Freeze Line customers when your case took place?
~Anonymous: Yes I can. It was morning, on November 4th.
GetHuman: Did you reach out to Equifax Freeze Line, and if so, how?
GetHuman: And which of these common Equifax Freeze Line customer issues best describes the reason you wanted to talk to them?
(Shows ~Anonymous a list of common Equifax Freeze Line problems)
~Anonymous: "Activate Freeze" was why I was trying to call.
~Anonymous's review of Equifax Freeze Line customer service
GetHuman: So how would you sum up your experience for GetHuman's Equifax Freeze Line 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.
~Anonymous: Indian call center apparently. Not great English, she had trouble understanding me. I had to repeat a question several times for her to understand me.
GetHuman: Let's quantify your experience contacting Equifax Freeze Line. On a scale of 1 to 5, how easy is it go get help on a Equifax Freeze Line problem?
~Anonymous: 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?
~Anonymous: I'd give them a five out of five on communication.
GetHuman: And what about Equifax Freeze Line's ability to quickly and effectively address your problem?
~Anonymous: For that I would say five out of five.
GetHuman: And finally- any advice for other Equifax Freeze Line customers?
~Anonymous: Call them early in the day or late. Don't forget any personal or account information you might need for Equifax Freeze Line to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~Anonymous taken from his Equifax Freeze Line customer service problem that occurred on November 4th, 2017.