TransUnion: Terrible. they had three different phone number...
Una recensione del cliente TransUnion da parte dell'utente GetHuman ~Guillermo da novembre 23º, 2017
Background on ~Guillermo's case
GetHuman: ~Guillermo - can you tell our other TransUnion customers when your case took place?
~Guillermo: Yes. It was morning, on novembre 16º.
GetHuman: Did you reach out to TransUnion, and if so, how?
GetHuman: And which of these common TransUnion customer issues best describes the reason you wanted to talk to them?
(Shows ~Guillermo a list of common TransUnion problems)
~Guillermo: "Cancel Subscription" was why I was trying to call.
~Guillermo's review of TransUnion customer service
GetHuman: So how would you sum up your experience for GetHuman's TransUnion 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.
~Guillermo: Terrible. they had three different phone numbers for each thing I wanted to do do. They ask you a ton of questions to verify who thou are ( i understand the need for security but this is ridiculous) on top of that the accent was terrible.
GetHuman: Let's quantify your experience contacting TransUnion. On a scale of 1 to 5, how easy is it go get help on a TransUnion problem?
~Guillermo: 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?
~Guillermo: I'd give them a two out of five on communication.
GetHuman: And what about TransUnion's ability to quickly and effectively address your problem?
~Guillermo: For that I would say one out of five.
GetHuman: And finally- any advice for other TransUnion customers?
~Guillermo: Chiamali presto o tardi. Non dimenticare le informazioni personali o relative all'account di cui potresti aver bisogno per TransUnion sapere chi sei.
GetHuman: Well there you have it. Some useful feedback and words from ~Guillermo taken from his TransUnion customer service problem that occurred on novembre 16º, 2017.