Time Warner: Everything was checked out before the end of su...
A Time Warner customer review by GetHuman user GetHuman-404064 from November 27th, 2017
Background on GetHuman-404064's case
GetHuman: GetHuman-404064 - can you tell our other Time Warner customers when your case took place?
GetHuman-404064: Yes. It was morning, on November 25th.
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-404064 a list of common Time Warner problems)
GetHuman-404064: "Lower my bill" was why I was trying to call.
GetHuman-404064'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-404064: Everything was checked out before the end of support call. *Now about*** hour later, I can't get out of Prime or On Demand. I didn't do anything to go to those two. So now back to other problems.
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-404064: 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?
GetHuman-404064: I'd give them a three out of five on communication.
GetHuman: And what about Time Warner's ability to quickly and effectively address your problem?
GetHuman-404064: For that I would say four out of five.
GetHuman: And finally- any advice for other Time Warner customers?
GetHuman-404064: 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-404064 taken from his Time Warner customer service problem that occurred on November 25th, 2017.