Charter Communications: Do not push * of you do not want sales. They do...
A Charter Communications customer review by GetHuman user ~Keri from November 26th, 2017
Background on ~Keri's case
GetHuman: ~Keri - can you tell our other Charter Communications customers when your case took place?
~Keri: Sure. It was morning, on November 22nd.
GetHuman: Did you reach out to Charter Communications, and if so, how?
GetHuman: And which of these common Charter Communications customer issues best describes the reason you wanted to talk to them?
(Shows ~Keri a list of common Charter Communications problems)
~Keri: "Change Plan" was why I was trying to call.
~Keri's review of Charter Communications customer service
GetHuman: So how would you sum up your experience for GetHuman's Charter 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.
~Keri: Do not push * of you do not want sales. They do not have a customer service dept. * always takes you to sales. If you need repair, push * and it takes you straight to repair.
GetHuman: Let's quantify your experience contacting Charter Communications. On a scale of 1 to 5, how easy is it go get help on a Charter Communications problem?
~Keri: 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?
~Keri: I'd give them a four out of five on communication.
GetHuman: And what about Charter Communications's ability to quickly and effectively address your problem?
~Keri: For that I would say five out of five.
GetHuman: And finally- any advice for other Charter Communications customers?
~Keri: Call them early in the day or late. Don't forget any personal or account information you might need for Charter Communications to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~Keri taken from his Charter Communications customer service problem that occurred on November 22nd, 2017.