Cox Communications: Wouldn't help with my issues and I would have t...
A Cox Communications customer review by GetHuman user ~R.S. from November 15th, 2017
Background on ~R.S.'s case
GetHuman: ~R.S. - can you tell our other Cox Communications customers when your case took place?
~R.S.: Yes I can. It was evening, on November 13th.
GetHuman: Did you reach out to Cox Communications, and if so, how?
GetHuman: And which of these common Cox Communications customer issues best describes the reason you wanted to talk to them?
(Shows ~R.S. a list of common Cox Communications problems)
~R.S.: "Service or technical issues" was why I was trying to call.
~R.S.'s review of Cox Communications customer service
GetHuman: So how would you sum up your experience for GetHuman's Cox Communications 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.
~R.S.: Wouldn't help with my issues and I would have to repeat myself constantly only to be told to do*submit something I've already done. Completely useless though the rep was overall polite but still not helpful.
GetHuman: Let's quantify your experience contacting Cox Communications. On a scale of 1 to 5, how easy is it go get help on a Cox Communications problem?
~R.S.: 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?
~R.S.: I'd give them a five out of five on communication.
GetHuman: And what about Cox Communications's ability to quickly and effectively address your problem?
~R.S.: For that I would say five out of five.
GetHuman: And finally- any advice for other Cox Communications customers?
~R.S.: Call them early in the day or late. Don't forget any personal or account information you might need for Cox Communications to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~R.S. taken from his Cox Communications customer service problem that occurred on November 13th, 2017.