E-ZPass Virginia: VERY PLEASANT LADY. GAVE ME INFORMATION THAT I...
A E-ZPass Virginia customer review by GetHuman user GetHuman-43052 from November 22nd, 2017
Background on GetHuman-43052's case
GetHuman: GetHuman-43052 - can you tell our other E-ZPass Virginia customers when your case took place?
GetHuman-43052: Yeah. It was middle of the night, on November 16th.
GetHuman: Did you reach out to E-ZPass Virginia, and if so, how?
GetHuman: And which of these common E-ZPass Virginia customer issues best describes the reason you wanted to talk to them?
(Shows GetHuman-43052 a list of common E-ZPass Virginia problems)
GetHuman-43052: "Complaint" was why I was trying to call.
GetHuman-43052's review of E-ZPass Virginia customer service
GetHuman: So how would you sum up your experience for GetHuman's E-ZPass Virginia 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-43052: VERY PLEASANT LADY. GAVE ME INFORMATION THAT I NEEDED. THANK GOD!!! FOR A LIVE HUMAN BEING THAT YOU ACTUALLY GET TO TALK TOO.
GetHuman: Let's quantify your experience contacting E-ZPass Virginia. On a scale of 1 to 5, how easy is it go get help on a E-ZPass Virginia problem?
GetHuman-43052: 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-43052: I'd give them a five out of five on communication.
GetHuman: And what about E-ZPass Virginia's ability to quickly and effectively address your problem?
GetHuman-43052: For that I would say five out of five.
GetHuman: And finally- any advice for other E-ZPass Virginia customers?
GetHuman-43052: Call them early in the day or late. Don't forget any personal or account information you might need for E-ZPass Virginia to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from GetHuman-43052 taken from his E-ZPass Virginia customer service problem that occurred on November 16th, 2017.