Travelocity: I waited almost half an hour and gave up. Trie...
A Travelocity customer review by GetHuman user GetHuman-348087 from November 26th, 2017
Background on GetHuman-348087's case
GetHuman: GetHuman-348087 - can you tell our other Travelocity customers when your case took place?
GetHuman-348087: Yeah. It was morning, on November 22nd.
GetHuman: Did you reach out to Travelocity, and if so, how?
GetHuman: And which of these common Travelocity customer issues best describes the reason you wanted to talk to them?
(Shows GetHuman-348087 a list of common Travelocity problems)
GetHuman-348087: "Make a Booking" was why I was trying to call.
GetHuman-348087's review of Travelocity customer service
GetHuman: So how would you sum up your experience for GetHuman's Travelocity 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-348087: I waited almost half an hour and gave up. Tried to call back choosing different options. Got the same waiting music. I didn't see this page until now, and just realized that I should have kept waiting.
GetHuman: Let's quantify your experience contacting Travelocity. On a scale of 1 to 5, how easy is it go get help on a Travelocity problem?
GetHuman-348087: 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?
GetHuman-348087: I'd give them a five out of five on communication.
GetHuman: And what about Travelocity's ability to quickly and effectively address your problem?
GetHuman-348087: For that I would say four out of five.
GetHuman: And finally- any advice for other Travelocity customers?
GetHuman-348087: Call them early in the day or late. Don't forget any personal or account information you might need for Travelocity to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from GetHuman-348087 taken from his Travelocity customer service problem that occurred on November 22nd, 2017.