Avast! customer service looked at my Event View...
A Avast customer review by GetHuman user ~Grimlet from November 13th, 2017
Background on ~Grimlet's case
GetHuman: ~Grimlet - can you tell our other Avast customers when your case took place?
~Grimlet: Yeah. It was afternoon, on November 7th.
GetHuman: Did you reach out to Avast, and if so, how?
GetHuman: And which of these common Avast customer issues best describes the reason you wanted to talk to them?
(Shows ~Grimlet a list of common Avast problems)
~Grimlet: "Cancel Service" was why I was trying to call.
~Grimlet's review of Avast customer service
GetHuman: So how would you sum up your experience for GetHuman's Avast 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.
~Grimlet: Avast! customer service looked at my Event Viewer in Windows * and told me my system was corrupt and proceeded to try and push a $*** "clean up" on me and never answered my question. Turns out all I had to do was an uninstall*reinstall. Event Viewer is only log entries of errors and has nothing to do with the operation of you computer. Looking into attorney for a nice class action law suit.
GetHuman: Let's quantify your experience contacting Avast. On a scale of 1 to 5, how easy is it go get help on a Avast problem?
~Grimlet: I'd give them a three 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?
~Grimlet: I'd give them a two out of five on communication.
GetHuman: And what about Avast's ability to quickly and effectively address your problem?
~Grimlet: For that I would say three out of five.
GetHuman: And finally- any advice for other Avast customers?
~Grimlet: Call them early in the day or late. Don't forget any personal or account information you might need for Avast to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~Grimlet taken from his Avast customer service problem that occurred on November 7th, 2017.