Blizzard: No human being. Just a recording telling me to...
A Blizzard customer review by GetHuman user ~Sunami from November 27th, 2017
Background on ~Sunami's case
GetHuman: ~Sunami - can you tell our other Blizzard customers when your case took place?
~Sunami: Yes I can. It was morning, on November 20th.
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 ~Sunami a list of common Blizzard problems)
~Sunami: "Overcharge/Strange charge" was why I was trying to contact.
~Sunami'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.
~Sunami: No human being. Just a recording telling me to go to their site which only gives pre-guessed choices of what you might need help with. Sorry my question doesn't fall into any of their pre-supposed categories. I pay MONEY to play this game and I should be able to get ahold of one human being to ask a simple question.
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?
~Sunami: 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?
~Sunami: I'd give them a one out of five on communication.
GetHuman: And what about Blizzard's ability to quickly and effectively address your problem?
~Sunami: For that I would say two out of five.
GetHuman: And finally- any advice for other Blizzard customers?
~Sunami: 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 ~Sunami taken from his Blizzard customer service problem that occurred on November 20th, 2017.