McAfee: The person i had followed a script and when the...
A McAfee customer review by GetHuman user ~catfish182 from October 27th, 2017
Background on ~catfish182's case
GetHuman: ~catfish182 - can you tell our other McAfee customers when your case took place?
~catfish182: Yes I can. It was evening, on October 19th.
GetHuman: Did you reach out to McAfee, and if so, how?
GetHuman: And which of these common McAfee customer issues best describes the reason you wanted to talk to them?
(Shows ~catfish182 a list of common McAfee problems)
~catfish182: "Overcharge/Strange charge" was why I was trying to call.
~catfish182's review of McAfee customer service
GetHuman: So how would you sum up your experience for GetHuman's McAfee 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.
~catfish182: The person i had followed a script and when the script failed he kept going back to the script over and over. He refused to let me speak to a manager or to transfer me to tier two support. He mocked me and refused to listen to anything i said. The software is nice but i weep for who ever has to call "support"
GetHuman: Let's quantify your experience contacting McAfee. On a scale of 1 to 5, how easy is it go get help on a McAfee problem?
~catfish182: I'd give them a five 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?
~catfish182: I'd give them a two out of five on communication.
GetHuman: And what about McAfee's ability to quickly and effectively address your problem?
~catfish182: For that I would say five out of five.
GetHuman: And finally- any advice for other McAfee customers?
~catfish182: Call them early in the day or late. Don't forget any personal or account information you might need for McAfee to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~catfish182 taken from his McAfee customer service problem that occurred on October 19th, 2017.