Hotwire: I was surprised at how quickly I managed to get...
A Hotwire customer review by GetHuman user ~mmc from November 25th, 2017
Background on ~mmc's case
GetHuman: ~mmc - can you tell our other Hotwire customers when your case took place?
~mmc: Yes. It was afternoon, on November 24th.
GetHuman: Did you reach out to Hotwire, and if so, how?
GetHuman: And which of these common Hotwire customer issues best describes the reason you wanted to talk to them?
(Shows ~mmc a list of common Hotwire problems)
~mmc: "Account Access" was why I was trying to call.
~mmc's review of Hotwire customer service
GetHuman: So how would you sum up your experience for GetHuman's Hotwire 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.
~mmc: I was surprised at how quickly I managed to get through to customer service. I called the listed number and was transferred to the correct department very quickly. The CSR was hard to understand -- though I couldn't place her accent -- and put me on hold twice, but changed my hotel booking w*o penalty. OTOH she wouldn't refund me for a missed night due to a flight cancellation.
GetHuman: Let's quantify your experience contacting Hotwire. On a scale of 1 to 5, how easy is it go get help on a Hotwire problem?
~mmc: 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?
~mmc: I'd give them a one out of five on communication.
GetHuman: And what about Hotwire's ability to quickly and effectively address your problem?
~mmc: For that I would say four out of five.
GetHuman: And finally- any advice for other Hotwire customers?
~mmc: Call them early in the day or late. Don't forget any personal or account information you might need for Hotwire to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~mmc taken from his Hotwire customer service problem that occurred on November 24th, 2017.