Charter Communications: as soon as sign up for ** month set bill, signa...
A Charter Communications customer review by GetHuman user ~unhappy from November 4th, 2017
Background on ~unhappy's case
GetHuman: ~unhappy - can you tell our other Charter Communications customers when your case took place?
~unhappy: Yes. It was evening, on November 1st.
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 ~unhappy a list of common Charter Communications problems)
~unhappy: "Complaint" was why I was trying to call.
~unhappy'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.
~unhappy: as soon as sign up for ** month set bill, signal went to ****, alsways resetting box, having techs come for problem signal weak for Charter to save $
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?
~unhappy: 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?
~unhappy: I'd give them a five out of five on communication.
GetHuman: And what about Charter Communications's ability to quickly and effectively address your problem?
~unhappy: For that I would say two out of five.
GetHuman: And finally- any advice for other Charter Communications customers?
~unhappy: 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 ~unhappy taken from his Charter Communications customer service problem that occurred on November 1st, 2017.