Time Warner: They raised my bill $***.** with no warning. Th...
A Time Warner customer review by GetHuman user ~stanley heavrin from November 22nd, 2017
Background on ~stanley heavrin's case
GetHuman: ~stanley heavrin - can you tell our other Time Warner customers when your case took place?
~stanley heavrin: Yup. It was morning, on November 21st.
GetHuman: Did you reach out to Time Warner, and if so, how?
GetHuman: And which of these common Time Warner customer issues best describes the reason you wanted to talk to them?
(Shows ~stanley heavrin a list of common Time Warner problems)
~stanley heavrin: "Lower my bill" was why I was trying to call.
~stanley heavrin's review of Time Warner customer service
GetHuman: So how would you sum up your experience for GetHuman's Time Warner 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.
~stanley heavrin: They raised my bill $***.** with no warning. They want me to pay $***.** a month. With no special channel. *And trying to talk customer servivmce is mission impossible. *S*****@***.com
GetHuman: Let's quantify your experience contacting Time Warner. On a scale of 1 to 5, how easy is it go get help on a Time Warner problem?
~stanley heavrin: I'd give them a two 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?
~stanley heavrin: I'd give them a five out of five on communication.
GetHuman: And what about Time Warner's ability to quickly and effectively address your problem?
~stanley heavrin: For that I would say four out of five.
GetHuman: And finally- any advice for other Time Warner customers?
~stanley heavrin: Call them early in the day or late. Don't forget any personal or account information you might need for Time Warner to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~stanley heavrin taken from his Time Warner customer service problem that occurred on November 21st, 2017.