Cox Communications: Fixed the ridiculous problem that should not ha...
A Cox Communications customer review by GetHuman user GetHuman-319997 from November 26th, 2017
Background on GetHuman-319997's case
GetHuman: GetHuman-319997 - can you tell our other Cox Communications customers when your case took place?
GetHuman-319997: Yeah. It was afternoon, on November 16th.
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 GetHuman-319997 a list of common Cox Communications problems)
GetHuman-319997: "Complaint" was why I was trying to call.
GetHuman-319997'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.
GetHuman-319997: Fixed the ridiculous problem that should not have existed in the first place. This number was Great!
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?
GetHuman-319997: 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-319997: I'd give them a two out of five on communication.
GetHuman: And what about Cox Communications's ability to quickly and effectively address your problem?
GetHuman-319997: For that I would say one out of five.
GetHuman: And finally- any advice for other Cox Communications customers?
GetHuman-319997: 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 GetHuman-319997 taken from his Cox Communications customer service problem that occurred on November 16th, 2017.