E-ZPass Virginia: ***-***-**** connects to no one--All I am tryin...
A E-ZPass Virginia customer review by GetHuman user GetHuman-106400 from November 18th, 2017
Background on GetHuman-106400's case
GetHuman: GetHuman-106400 - can you tell our other E-ZPass Virginia customers when your case took place?
GetHuman-106400: Yes I can. It was middle of the night, on November 9th.
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-106400 a list of common E-ZPass Virginia problems)
GetHuman-106400: "Complaint" was why I was trying to call.
GetHuman-106400'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-106400: ***-***-**** connects to no one--All I am trying to do is give E-Z pass my updated Discover card Number
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-106400: I'd give them a four 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-106400: 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-106400: For that I would say five out of five.
GetHuman: And finally- any advice for other E-ZPass Virginia customers?
GetHuman-106400: 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-106400 taken from his E-ZPass Virginia customer service problem that occurred on November 9th, 2017.