Symantec: My initial call to this number was answered pol...
A Symantec customer review by GetHuman user ~Nema46 from November 12th, 2017
Background on ~Nema46's case
GetHuman: ~Nema46 - can you tell our other Symantec customers when your case took place?
~Nema46: Yeah. It was morning, on November 3rd.
GetHuman: Did you reach out to Symantec, and if so, how?
GetHuman: And which of these common Symantec customer issues best describes the reason you wanted to talk to them?
(Shows ~Nema46 a list of common Symantec problems)
~Nema46: "Technical support" was why I was trying to call.
~Nema46's review of Symantec customer service
GetHuman: So how would you sum up your experience for GetHuman's Symantec 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.
~Nema46: My initial call to this number was answered politely, but I was transferred immediately to another department* put on hold for *** minutes with loud, cacaphonous, mind-numbing music clearky played to discourage anyone from staying on the phone. This same thing has happened to me over *** times in dealing with Symantec*Norton. My advice is to NOT get involved with any of their products.
GetHuman: Let's quantify your experience contacting Symantec. On a scale of 1 to 5, how easy is it go get help on a Symantec problem?
~Nema46: 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?
~Nema46: I'd give them a three out of five on communication.
GetHuman: And what about Symantec's ability to quickly and effectively address your problem?
~Nema46: For that I would say five out of five.
GetHuman: And finally- any advice for other Symantec customers?
~Nema46: Call them early in the day or late. Don't forget any personal or account information you might need for Symantec to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~Nema46 taken from his Symantec customer service problem that occurred on November 3rd, 2017.