Zipcar: I was on hold at the *** number for over ** min...
A Zipcar customer review by GetHuman user ~ekkc10753 from November 9th, 2017
Background on ~ekkc10753's case
GetHuman: ~ekkc10753 - can you tell our other Zipcar customers when your case took place?
~ekkc10753: Yes I can. It was morning, on November 5th.
GetHuman: Did you reach out to Zipcar, and if so, how?
GetHuman: And which of these common Zipcar customer issues best describes the reason you wanted to talk to them?
(Shows ~ekkc10753 a list of common Zipcar problems)
~ekkc10753: "Loyalty program" was why I was trying to call.
~ekkc10753's review of Zipcar customer service
GetHuman: So how would you sum up your experience for GetHuman's Zipcar 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.
~ekkc10753: I was on hold at the *** number for over ** min, saying "customer service, customer service" over and over (zipcard is lost, no account number). Then I used one of those "they'll call you" Apps and punted after * minutes. Called the *** number and a nice woman answered on the second ring!!!*Took care of everything!!
GetHuman: Let's quantify your experience contacting Zipcar. On a scale of 1 to 5, how easy is it go get help on a Zipcar problem?
~ekkc10753: I'd give them a two 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?
~ekkc10753: I'd give them a three out of five on communication.
GetHuman: And what about Zipcar's ability to quickly and effectively address your problem?
~ekkc10753: For that I would say five out of five.
GetHuman: And finally- any advice for other Zipcar customers?
~ekkc10753: Call them early in the day or late. Don't forget any personal or account information you might need for Zipcar to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~ekkc10753 taken from his Zipcar customer service problem that occurred on November 5th, 2017.