Time Warner: I agreed with a ***.** a month deal. N got char...
A Time Warner customer review by GetHuman user ~nikornelas from November 23rd, 2017
Background on ~nikornelas's case
GetHuman: ~nikornelas - can you tell our other Time Warner customers when your case took place?
~nikornelas: Yes I can. It was middle of the night, on November 16th.
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 ~nikornelas a list of common Time Warner problems)
~nikornelas: "Upgrade Account" was why I was trying to call.
~nikornelas'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.
~nikornelas: I agreed with a ***.** a month deal. N got charged ***.** n when i tried to correct this, got transferred *-* times, basically got the run around. No one knows what they're doing, horrible c.s, i wouldnt recommend this service to anyone.
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?
~nikornelas: I'd give them a five 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?
~nikornelas: I'd give them a two out of five on communication.
GetHuman: And what about Time Warner's ability to quickly and effectively address your problem?
~nikornelas: For that I would say three out of five.
GetHuman: And finally- any advice for other Time Warner customers?
~nikornelas: 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 ~nikornelas taken from his Time Warner customer service problem that occurred on November 16th, 2017.