Equifax: Not satisfactory while report is current it is...
Equifax отзыв клиента от пользователя GetHuman ~jazzlover из ноябрь 24-го, 2017
Background on ~jazzlover's case
GetHuman: ~jazzlover - can you tell our other Equifax customers when your case took place?
~jazzlover: Yes I can. It was afternoon, on ноябрь 22-го.
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 ~jazzlover a list of common Equifax problems)
~jazzlover: "Complaint" was why I was trying to call.
~jazzlover'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.
~jazzlover: Not satisfactory while report is current it is not showing very important information. The other * credit agencies are showing correct information and the report from Equifax is now hurting me...I am not a happy person since you should have received the information as it was sent to you
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?
~jazzlover: I'd give them a three 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?
~jazzlover: 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?
~jazzlover: For that I would say one out of five.
GetHuman: And finally- any advice for other Equifax customers?
~jazzlover: Позвоните им рано днем или поздно. Не забывайте личную информацию или информацию об учетной записи, которая может вам понадобиться, чтобы Equifax знал, кто вы.
GetHuman: Well there you have it. Some useful feedback and words from ~jazzlover taken from his Equifax customer service problem that occurred on ноябрь 22-го, 2017.