Kayak: i made a reservation at Roosevelt hotel in NYC...
A Kayak customer review by GetHuman user ~scotch master from November 23rd, 2017
Background on ~scotch master's case
GetHuman: ~scotch master - can you tell our other Kayak customers when your case took place?
~scotch master: Yes. It was morning, on November 20th.
GetHuman: Did you reach out to Kayak, and if so, how?
GetHuman: And which of these common Kayak customer issues best describes the reason you wanted to talk to them?
(Shows ~scotch master a list of common Kayak problems)
~scotch master: "Find Itinerary" was why I was trying to call.
~scotch master's review of Kayak customer service
GetHuman: So how would you sum up your experience for GetHuman's Kayak 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.
~scotch master: i made a reservation at Roosevelt hotel in NYC, they never sent me a confirmation * to my e mail. the hotel could not provide a receipt because of this * party transaction. then Kayak said i need a Res * in order to get my receipt sent. but never received the * to begin with.. now im out ***$
GetHuman: Let's quantify your experience contacting Kayak. On a scale of 1 to 5, how easy is it go get help on a Kayak problem?
~scotch master: 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?
~scotch master: I'd give them a three out of five on communication.
GetHuman: And what about Kayak's ability to quickly and effectively address your problem?
~scotch master: For that I would say two out of five.
GetHuman: And finally- any advice for other Kayak customers?
~scotch master: Call them early in the day or late. Don't forget any personal or account information you might need for Kayak to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~scotch master taken from his Kayak customer service problem that occurred on November 20th, 2017.