Razer: Great customer support and great experience! Ra...
A Razer customer review by GetHuman user ~Phantomish from November 18th, 2017
Background on ~Phantomish's case
GetHuman: ~Phantomish - can you tell our other Razer customers when your case took place?
~Phantomish: Yes I can. It was morning, on November 12th.
GetHuman: Did you reach out to Razer, and if so, how?
GetHuman: And which of these common Razer customer issues best describes the reason you wanted to talk to them?
(Shows ~Phantomish a list of common Razer problems)
~Phantomish: "Complaint" was why I was trying to call.
~Phantomish's review of Razer customer service
GetHuman: So how would you sum up your experience for GetHuman's Razer 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.
~Phantomish: Great customer support and great experience! Raymond spoke plain English and was very easy to understand. Also, when he learned I had already tried the troubleshooting tips he had recommended, he did not insist that I go through them again for the sake of protocol and got right to the RMA. * stars for the Razer phone support line!
GetHuman: Let's quantify your experience contacting Razer. On a scale of 1 to 5, how easy is it go get help on a Razer problem?
~Phantomish: 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?
~Phantomish: I'd give them a one out of five on communication.
GetHuman: And what about Razer's ability to quickly and effectively address your problem?
~Phantomish: For that I would say four out of five.
GetHuman: And finally- any advice for other Razer customers?
~Phantomish: Call them early in the day or late. Don't forget any personal or account information you might need for Razer to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~Phantomish taken from his Razer customer service problem that occurred on November 12th, 2017.