Malwarebytes: I need to talk to someone about my service*I pa...
A Malwarebytes customer review by GetHuman user ~Carolyn Wilson from November 19th, 2017
Background on ~Carolyn Wilson's case
GetHuman: ~Carolyn Wilson - can you tell our other Malwarebytes customers when your case took place?
~Carolyn Wilson: Sure. It was middle of the night, on November 17th.
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 ~Carolyn Wilson a list of common Malwarebytes problems)
~Carolyn Wilson: "Account Access" was why I was trying to call.
~Carolyn Wilson'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.
~Carolyn Wilson: I need to talk to someone about my service*I pay for one year service I only got one month service now on have no service please contact me at ***-***-**** thank you
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?
~Carolyn Wilson: 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?
~Carolyn Wilson: I'd give them a two out of five on communication.
GetHuman: And what about Malwarebytes's ability to quickly and effectively address your problem?
~Carolyn Wilson: For that I would say one out of five.
GetHuman: And finally- any advice for other Malwarebytes customers?
~Carolyn Wilson: 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 ~Carolyn Wilson taken from his Malwarebytes customer service problem that occurred on November 17th, 2017.