Cisco Systems: she waited until the end of all the work ** ins...
A Cisco Systems customer review by GetHuman user ~martib43 from November 12th, 2017
Background on ~martib43's case
GetHuman: ~martib43 - can you tell our other Cisco Systems customers when your case took place?
~martib43: Yes I can. It was evening, on November 3rd.
GetHuman: Did you reach out to Cisco Systems, and if so, how?
GetHuman: And which of these common Cisco Systems customer issues best describes the reason you wanted to talk to them?
(Shows ~martib43 a list of common Cisco Systems problems)
~martib43: "Complaint" was why I was trying to call.
~martib43's review of Cisco Systems customer service
GetHuman: So how would you sum up your experience for GetHuman's Cisco Systems 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.
~martib43: she waited until the end of all the work ** instructions of 'checks' to inform me that it would cost me $** for * computer, $*** for both my laptop & desktop: something about all 'the settings would have to be changed' what ever that means. Too Expensive
GetHuman: Let's quantify your experience contacting Cisco Systems. On a scale of 1 to 5, how easy is it go get help on a Cisco Systems problem?
~martib43: I'd give them a four 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?
~martib43: I'd give them a three out of five on communication.
GetHuman: And what about Cisco Systems's ability to quickly and effectively address your problem?
~martib43: For that I would say five out of five.
GetHuman: And finally- any advice for other Cisco Systems customers?
~martib43: Call them early in the day or late. Don't forget any personal or account information you might need for Cisco Systems to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~martib43 taken from his Cisco Systems customer service problem that occurred on November 3rd, 2017.