Malwarebytes: I want to speak to someone you got my $ where...
A Malwarebytes customer review by GetHuman user ~william lussier from November 23rd, 2017
Background on ~william lussier's case
GetHuman: ~william lussier - can you tell our other Malwarebytes customers when your case took place?
~william lussier: Yes. It was morning, on November 22nd.
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 ~william lussier a list of common Malwarebytes problems)
~william lussier: "Change order" was why I was trying to call.
~william lussier'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.
~william lussier: I want to speak to someone you got my $ where is service after the sale? my new emailis *****@***.com phone * if someone can take the time to call me* William lussier at **********
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?
~william lussier: 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?
~william lussier: I'd give them a three out of five on communication.
GetHuman: And what about Malwarebytes's ability to quickly and effectively address your problem?
~william lussier: For that I would say one out of five.
GetHuman: And finally- any advice for other Malwarebytes customers?
~william lussier: 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 ~william lussier taken from his Malwarebytes customer service problem that occurred on November 22nd, 2017.