Symantec: Had all my questions resolved, but took a long...
A Symantec customer review by GetHuman user GetHuman-258816 from November 13th, 2017
Background on GetHuman-258816's case
GetHuman: GetHuman-258816 - can you tell our other Symantec customers when your case took place?
GetHuman-258816: Sure. It was middle of the night, on November 7th.
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 GetHuman-258816 a list of common Symantec problems)
GetHuman-258816: "Technical support" was why I was trying to call.
GetHuman-258816'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.
GetHuman-258816: Had all my questions resolved, but took a long time because this link defaults to the Windows help desk, and I wanted Mac help. It took a looooong time for them to transfer me to the Mac help desk. Is there a similar link for Mac users?
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?
GetHuman-258816: 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?
GetHuman-258816: I'd give them a five out of five on communication.
GetHuman: And what about Symantec's ability to quickly and effectively address your problem?
GetHuman-258816: For that I would say two out of five.
GetHuman: And finally- any advice for other Symantec customers?
GetHuman-258816: 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 GetHuman-258816 taken from his Symantec customer service problem that occurred on November 7th, 2017.