Ubisoft: Your game is a pile of ****, and your servers s...
A Ubisoft customer review by GetHuman user GetHuman-schraale from December 1st, 2017
Background on GetHuman-schraale's case
GetHuman: GetHuman-schraale - can you tell our other Ubisoft customers when your case took place?
GetHuman-schraale: Yes. It was middle of the night, on November 30th.
GetHuman: Did you reach out to Ubisoft, and if so, how?
GetHuman: And which of these common Ubisoft customer issues best describes the reason you wanted to talk to them?
(Shows GetHuman-schraale a list of common Ubisoft problems)
GetHuman-schraale: "Missing Items" was why I was trying to call.
GetHuman-schraale's review of Ubisoft customer service
GetHuman: So how would you sum up your experience for GetHuman's Ubisoft 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-schraale: Your game is a pile of ****, and your servers **** ***, please help.
GetHuman: Can you tell the rest of us a bit more from what happened on 11/30/17?
GetHuman-schraale: what the **** were your developers thinking?
GetHuman: Let's quantify your experience contacting Ubisoft. On a scale of 1 to 5, how easy is it go get help on a Ubisoft problem?
GetHuman-schraale: 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?
GetHuman-schraale: I'd give them a three out of five on communication.
GetHuman: And what about Ubisoft's ability to quickly and effectively address your problem?
GetHuman-schraale: For that I would say five out of five.
GetHuman: And finally- any advice for other Ubisoft customers?
GetHuman-schraale: Call them early in the day or late. Don't forget any personal or account information you might need for Ubisoft to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from GetHuman-schraale taken from his Ubisoft customer service problem that occurred on November 30th, 2017.