Kaspersky Lab: Never got an answer, kept asking to dial extens...
A Kaspersky Lab customer review by GetHuman user GetHuman-36731 from November 21st, 2017
Background on GetHuman-36731's case
GetHuman: GetHuman-36731 - can you tell our other Kaspersky Lab customers when your case took place?
GetHuman-36731: Sure. It was morning, on November 16th.
GetHuman: Did you reach out to Kaspersky Lab, and if so, how?
GetHuman: And which of these common Kaspersky Lab customer issues best describes the reason you wanted to talk to them?
(Shows GetHuman-36731 a list of common Kaspersky Lab problems)
GetHuman-36731: "Overcharge/Strange charge" was why I was trying to call.
GetHuman-36731's review of Kaspersky Lab customer service
GetHuman: So how would you sum up your experience for GetHuman's Kaspersky Lab 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-36731: Never got an answer, kept asking to dial extension when there was no extension to dial. Why is it so hard for you to answer when it comes to refunding someone's money?
GetHuman: Let's quantify your experience contacting Kaspersky Lab. On a scale of 1 to 5, how easy is it go get help on a Kaspersky Lab problem?
GetHuman-36731: 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?
GetHuman-36731: I'd give them a two out of five on communication.
GetHuman: And what about Kaspersky Lab's ability to quickly and effectively address your problem?
GetHuman-36731: For that I would say one out of five.
GetHuman: And finally- any advice for other Kaspersky Lab customers?
GetHuman-36731: Call them early in the day or late. Don't forget any personal or account information you might need for Kaspersky Lab to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from GetHuman-36731 taken from his Kaspersky Lab customer service problem that occurred on November 16th, 2017.