E-ZPass New York: Worked great. Gethuman saves the day again sin...
A E-ZPass New York customer review by GetHuman user GetHuman-313922 from November 27th, 2017
Background on GetHuman-313922's case
GetHuman: GetHuman-313922 - can you tell our other E-ZPass New York customers when your case took place?
GetHuman-313922: Yeah. It was afternoon, on November 21st.
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 GetHuman-313922 a list of common E-ZPass New York problems)
GetHuman-313922: "Overcharge/Strange charge" was why I was trying to call.
GetHuman-313922'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.
GetHuman-313922: Worked great. Gethuman saves the day again since EZ Pass NY doesn't transparently post customer service numbers.
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?
GetHuman-313922: 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?
GetHuman-313922: 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?
GetHuman-313922: For that I would say five out of five.
GetHuman: And finally- any advice for other E-ZPass New York customers?
GetHuman-313922: 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 GetHuman-313922 taken from his E-ZPass New York customer service problem that occurred on November 21st, 2017.