Optimum continues to **** me off on a daily bas...
A Optimum customer review by GetHuman user ~Ira Cohen from November 23rd, 2017
Background on ~Ira Cohen's case
GetHuman: ~Ira Cohen - can you tell our other Optimum customers when your case took place?
~Ira Cohen: Yeah. It was afternoon, on November 18th.
GetHuman: Did you reach out to Optimum, and if so, how?
GetHuman: And which of these common Optimum customer issues best describes the reason you wanted to talk to them?
(Shows ~Ira Cohen a list of common Optimum problems)
~Ira Cohen: "Dispute a Charge" was why I was trying to call.
~Ira Cohen's review of Optimum customer service
GetHuman: So how would you sum up your experience for GetHuman's Optimum 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.
~Ira Cohen: Optimum continues to **** me off on a daily basis. Not only did they sneak a rate increase in for my monthly billing, but they told me up front that it is non-negotiable, and they wouldn't charge me anything if I decided to leave for another provider. Their internet service *****, and is really beginning to annoy me.
GetHuman: Let's quantify your experience contacting Optimum. On a scale of 1 to 5, how easy is it go get help on a Optimum problem?
~Ira Cohen: I'd give them a three 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?
~Ira Cohen: I'd give them a five out of five on communication.
GetHuman: And what about Optimum's ability to quickly and effectively address your problem?
~Ira Cohen: For that I would say five out of five.
GetHuman: And finally- any advice for other Optimum customers?
~Ira Cohen: Call them early in the day or late. Don't forget any personal or account information you might need for Optimum to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~Ira Cohen taken from his Optimum customer service problem that occurred on November 18th, 2017.