Symantec: FANTASTIC. Diagnosed and fixed my problem in m...
A Symantec customer review by GetHuman user ~Hilliard999999 from November 4th, 2017
Background on ~Hilliard999999's case
GetHuman: ~Hilliard999999 - can you tell our other Symantec customers when your case took place?
~Hilliard999999: Yes I can. It was middle of the night, 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 ~Hilliard999999 a list of common Symantec problems)
~Hilliard999999: "Track order" was why I was trying to call.
~Hilliard999999'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.
~Hilliard999999: FANTASTIC. Diagnosed and fixed my problem in minutes. It was worth the wait. What the Norton guy was able to do in Live Chat was just amazing. I sat there and watched as he solved the problem for me. Thank you Norton.
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?
~Hilliard999999: 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?
~Hilliard999999: I'd give them a four out of five on communication.
GetHuman: And what about Symantec's ability to quickly and effectively address your problem?
~Hilliard999999: For that I would say one out of five.
GetHuman: And finally- any advice for other Symantec customers?
~Hilliard999999: 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 ~Hilliard999999 taken from his Symantec customer service problem that occurred on November 3rd, 2017.