Experian: after bashing my head repeatedly trying the exp...
Una recensione del cliente Experian da parte dell'utente GetHuman GetHuman-108150 da novembre 24º, 2017
Background on GetHuman-108150's case
GetHuman: GetHuman-108150 - can you tell our other Experian customers when your case took place?
GetHuman-108150: Yes I can. It was afternoon, on novembre 21º.
GetHuman: Did you reach out to Experian, and if so, how?
GetHuman: And which of these common Experian customer issues best describes the reason you wanted to talk to them?
(Shows GetHuman-108150 a list of common Experian problems)
GetHuman-108150: "Check credit score" was why I was trying to call.
GetHuman-108150's review of Experian customer service
GetHuman: So how would you sum up your experience for GetHuman's Experian 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-108150: after bashing my head repeatedly trying the experian provided *** *, I finally got smart and asked gethuman. Thanks for giving a direct number to an actual person who speaks a common language.
GetHuman: Let's quantify your experience contacting Experian. On a scale of 1 to 5, how easy is it go get help on a Experian problem?
GetHuman-108150: 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?
GetHuman-108150: I'd give them a five out of five on communication.
GetHuman: And what about Experian's ability to quickly and effectively address your problem?
GetHuman-108150: For that I would say five out of five.
GetHuman: And finally- any advice for other Experian customers?
GetHuman-108150: Chiamali presto o tardi. Non dimenticare le informazioni personali o relative all'account di cui potresti aver bisogno per Experian sapere chi sei.
GetHuman: Well there you have it. Some useful feedback and words from GetHuman-108150 taken from his Experian customer service problem that occurred on novembre 21º, 2017.