Symantec: They owe me a refund for over * months due to t...
A Symantec customer review by GetHuman user ~law1 from November 19th, 2017
Background on ~law1's case
GetHuman: ~law1 - can you tell our other Symantec customers when your case took place?
~law1: Yup. It was evening, on November 13th.
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 ~law1 a list of common Symantec problems)
~law1: "Overcharge/Strange charge" was why I was trying to call.
~law1'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.
~law1: They owe me a refund for over * months due to the cancelation of a product. I have * case numbers and every time I finally speak to a human after being on hold for hours, they say that the problem will be resolved. They are liars and apparently thieves. At this point,it's about principal. Will take legal action even if the refund is for * cents. It's actually for $**.**.
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?
~law1: 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?
~law1: 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?
~law1: For that I would say one out of five.
GetHuman: And finally- any advice for other Symantec customers?
~law1: 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 ~law1 taken from his Symantec customer service problem that occurred on November 13th, 2017.