Enterprise Rent-A-Car: Even though I got an erroneous bill there was n...
A Enterprise Rent-A-Car customer review by GetHuman user ~ddd from November 15th, 2017
Background on ~ddd's case
GetHuman: ~ddd - can you tell our other Enterprise Rent-A-Car customers when your case took place?
~ddd: Yes I can. It was morning, on November 8th.
GetHuman: Did you reach out to Enterprise Rent-A-Car, and if so, how?
GetHuman: And which of these common Enterprise Rent-A-Car customer issues best describes the reason you wanted to talk to them?
(Shows ~ddd a list of common Enterprise Rent-A-Car problems)
~ddd: "Complaint" was why I was trying to call.
~ddd's review of Enterprise Rent-A-Car customer service
GetHuman: So how would you sum up your experience for GetHuman's Enterprise Rent-A-Car 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.
~ddd: Even though I got an erroneous bill there was no central customer support to resolve it and the branch which rented the car out was content to just brush me off. Horrible support after they send you the bill.
GetHuman: Let's quantify your experience contacting Enterprise Rent-A-Car. On a scale of 1 to 5, how easy is it go get help on a Enterprise Rent-A-Car problem?
~ddd: I'd give them a one 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?
~ddd: I'd give them a one out of five on communication.
GetHuman: And what about Enterprise Rent-A-Car's ability to quickly and effectively address your problem?
~ddd: For that I would say five out of five.
GetHuman: And finally- any advice for other Enterprise Rent-A-Car customers?
~ddd: Call them early in the day or late. Don't forget any personal or account information you might need for Enterprise Rent-A-Car to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~ddd taken from his Enterprise Rent-A-Car customer service problem that occurred on November 8th, 2017.