Malwarebytes customer support ***** to put poli...
A Malwarebytes customer review by GetHuman user ~Frustrated from November 26th, 2017
Background on ~Frustrated's case
GetHuman: ~Frustrated - can you tell our other Malwarebytes customers when your case took place?
~Frustrated: Sure. It was morning, on November 21st.
GetHuman: Did you reach out to Malwarebytes, and if so, how?
GetHuman: And which of these common Malwarebytes customer issues best describes the reason you wanted to talk to them?
(Shows ~Frustrated a list of common Malwarebytes problems)
~Frustrated: "Make a purchase" was why I was trying to call.
~Frustrated's review of Malwarebytes customer service
GetHuman: So how would you sum up your experience for GetHuman's Malwarebytes 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.
~Frustrated: Malwarebytes customer support ***** to put politely. There is no way to talk to a person. My support ticket response was that someone would contact me in *-* days! I'm going uninstall and choose another supplier that cares about its customers.
GetHuman: Let's quantify your experience contacting Malwarebytes. On a scale of 1 to 5, how easy is it go get help on a Malwarebytes problem?
~Frustrated: I'd give them a two 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?
~Frustrated: I'd give them a one out of five on communication.
GetHuman: And what about Malwarebytes's ability to quickly and effectively address your problem?
~Frustrated: For that I would say two out of five.
GetHuman: And finally- any advice for other Malwarebytes customers?
~Frustrated: Call them early in the day or late. Don't forget any personal or account information you might need for Malwarebytes to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~Frustrated taken from his Malwarebytes customer service problem that occurred on November 21st, 2017.