Equifax: I called * times *st time call back after ** mi...
Equifax Ulasan pelanggan oleh pengguna GetHuman ~marinerbill31 dari November 26, 2017
Background on ~marinerbill31's case
GetHuman: ~marinerbill31 - can you tell our other Equifax customers when your case took place?
~marinerbill31: Yes. It was morning, on November 21.
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 ~marinerbill31 a list of common Equifax problems)
~marinerbill31: "Check credit score" was why I was trying to call.
~marinerbill31'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.
~marinerbill31: I called * times *st time call back after ** minutes, *nd time waited ** minutes told to call back in * hour *rd time I called back told to call back in * hour. Finally drove from charlotte to Atlanta and filed small claims suit to have errors removed.
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?
~marinerbill31: 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?
~marinerbill31: 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?
~marinerbill31: For that I would say two out of five.
GetHuman: And finally- any advice for other Equifax customers?
~marinerbill31: Hubungi mereka pada awal atau lewat. Jangan lupa maklumat peribadi atau akaun yang mungkin anda perlukan untuk Equifax mengetahui siapa anda.
GetHuman: Well there you have it. Some useful feedback and words from ~marinerbill31 taken from his Equifax customer service problem that occurred on November 21, 2017.