Blizzard: I have a serious issue involving a false report...
A Blizzard customer review by GetHuman user GetHuman-310911 from November 23rd, 2017
Background on GetHuman-310911's case
GetHuman: GetHuman-310911 - can you tell our other Blizzard customers when your case took place?
GetHuman-310911: Sure. It was middle of the night, on November 19th.
GetHuman: Did you reach out to Blizzard, and if so, how?
GetHuman: And which of these common Blizzard customer issues best describes the reason you wanted to talk to them?
(Shows GetHuman-310911 a list of common Blizzard problems)
GetHuman-310911: "Cancel order" was why I was trying to contact.
GetHuman-310911's review of Blizzard customer service
GetHuman: So how would you sum up your experience for GetHuman's Blizzard 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-310911: I have a serious issue involving a false report on myself and the operator just referred me to the website and the website has jack on this particular subject. Wtf, why is hard to contact Blizzard on important cases like this
GetHuman: Let's quantify your experience contacting Blizzard. On a scale of 1 to 5, how easy is it go get help on a Blizzard problem?
GetHuman-310911: I'd give them a one 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-310911: I'd give them a four out of five on communication.
GetHuman: And what about Blizzard's ability to quickly and effectively address your problem?
GetHuman-310911: For that I would say one out of five.
GetHuman: And finally- any advice for other Blizzard customers?
GetHuman-310911: Try to deal with them early in the day or later. Don't forget any personal or account information you might need for Blizzard to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from GetHuman-310911 taken from his Blizzard customer service problem that occurred on November 19th, 2017.