Time Warner: TERRIBLE CUSTOMER SERVICE. can't get a human on...
A Time Warner customer review by GetHuman user GetHuman-230888 from November 13th, 2017
Background on GetHuman-230888's case
GetHuman: GetHuman-230888 - can you tell our other Time Warner customers when your case took place?
GetHuman-230888: Yup. It was late at night, on November 11th.
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 GetHuman-230888 a list of common Time Warner problems)
GetHuman-230888: "Make a payment" was why I was trying to call.
GetHuman-230888'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.
GetHuman-230888: TERRIBLE CUSTOMER SERVICE. can't get a human on the phone, and chat ends up escalating until no one responds even for a simple question. would love to switch away from this horrible company.
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?
GetHuman-230888: 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?
GetHuman-230888: 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?
GetHuman-230888: For that I would say four out of five.
GetHuman: And finally- any advice for other Time Warner customers?
GetHuman-230888: 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 GetHuman-230888 taken from his Time Warner customer service problem that occurred on November 11th, 2017.