E-ZPass New York: Guy on the phone was rude and acts like he just...
A E-ZPass New York customer review by GetHuman user ~Jackinthebox from November 20th, 2017
Background on ~Jackinthebox's case
GetHuman: ~Jackinthebox - can you tell our other E-ZPass New York customers when your case took place?
~Jackinthebox: Yeah. It was morning, on November 17th.
GetHuman: Did you reach out to E-ZPass New York, and if so, how?
GetHuman: And which of these common E-ZPass New York customer issues best describes the reason you wanted to talk to them?
(Shows ~Jackinthebox a list of common E-ZPass New York problems)
~Jackinthebox: "Overcharge/Strange charge" was why I was trying to call.
~Jackinthebox's review of E-ZPass New York customer service
GetHuman: So how would you sum up your experience for GetHuman's E-ZPass New York 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.
~Jackinthebox: Guy on the phone was rude and acts like he just turned the Earth off its axis taking my call. Hope he gets run over by a car in front of his family
GetHuman: Let's quantify your experience contacting E-ZPass New York. On a scale of 1 to 5, how easy is it go get help on a E-ZPass New York problem?
~Jackinthebox: 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?
~Jackinthebox: I'd give them a four out of five on communication.
GetHuman: And what about E-ZPass New York's ability to quickly and effectively address your problem?
~Jackinthebox: For that I would say five out of five.
GetHuman: And finally- any advice for other E-ZPass New York customers?
~Jackinthebox: Call them early in the day or late. Don't forget any personal or account information you might need for E-ZPass New York to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~Jackinthebox taken from his E-ZPass New York customer service problem that occurred on November 17th, 2017.