Cable One: Our internet was having connection issues when...
A Cable One customer review by GetHuman user ~Richard A from November 24th, 2017
Background on ~Richard A's case
GetHuman: ~Richard A - can you tell our other Cable One customers when your case took place?
~Richard A: Sure. It was morning, on November 21st.
GetHuman: Did you reach out to Cable One, and if so, how?
GetHuman: And which of these common Cable One customer issues best describes the reason you wanted to talk to them?
(Shows ~Richard A a list of common Cable One problems)
~Richard A: "None of those really matches why I wanted to contact Cable One that day." was why I was trying to contact.
~Richard A's review of Cable One customer service
GetHuman: So how would you sum up your experience for GetHuman's Cable One 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.
~Richard A: Our internet was having connection issues when we called, after ** minutes of the tech blaming our computers and web browsers he talked to another tech. After he came back he informed us that they were having issues on their end.
GetHuman: Let's quantify your experience contacting Cable One. On a scale of 1 to 5, how easy is it go get help on a Cable One problem?
~Richard A: I'd give them a one 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?
~Richard A: I'd give them a one out of five on communication.
GetHuman: And what about Cable One's ability to quickly and effectively address your problem?
~Richard A: For that I would say four out of five.
GetHuman: And finally- any advice for other Cable One customers?
~Richard A: Call them early in the day or late. Don't forget any personal or account information you might need for Cable One to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~Richard A taken from his Cable One customer service problem that occurred on November 21st, 2017.