Hotwire: horrible company to work with for tavel deals.
A Hotwire customer review by GetHuman user GetHuman-amydhum from November 28th, 2017
Background on GetHuman-amydhum's case
GetHuman: GetHuman-amydhum - can you tell our other Hotwire customers when your case took place?
GetHuman-amydhum: Yup. It was morning, on November 25th.
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 GetHuman-amydhum a list of common Hotwire problems)
GetHuman-amydhum: "Account Access" was why I was trying to call.
GetHuman-amydhum'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.
GetHuman-amydhum: horrible company to work with for tavel deals.
GetHuman: Can you tell the rest of us a bit more from what happened on 11/25/17?
GetHuman-amydhum: hotwire's outsouced and untrained employees offer no real solutions to help travelers on a budget.
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?
GetHuman-amydhum: 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?
GetHuman-amydhum: I'd give them a two out of five on communication.
GetHuman: And what about Hotwire's ability to quickly and effectively address your problem?
GetHuman-amydhum: For that I would say one out of five.
GetHuman: And finally- any advice for other Hotwire customers?
GetHuman-amydhum: 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 GetHuman-amydhum taken from his Hotwire customer service problem that occurred on November 25th, 2017.