Travelocity: I could not understand the person who helped me...
A Travelocity customer review by GetHuman user ~Kacyloron from November 19th, 2017
Background on ~Kacyloron's case
GetHuman: ~Kacyloron - can you tell our other Travelocity customers when your case took place?
~Kacyloron: Yes I can. It was afternoon, on November 13th.
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 ~Kacyloron a list of common Travelocity problems)
~Kacyloron: "Refund a Charge" was why I was trying to call.
~Kacyloron'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.
~Kacyloron: I could not understand the person who helped me on the phone. Their phones are outsourced to India and it took forever to communicate with her. Finally after an hour on hold and ** minutes talking to her, my problem was eventually solved. I think.
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?
~Kacyloron: 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?
~Kacyloron: I'd give them a one out of five on communication.
GetHuman: And what about Travelocity's ability to quickly and effectively address your problem?
~Kacyloron: For that I would say four out of five.
GetHuman: And finally- any advice for other Travelocity customers?
~Kacyloron: 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 ~Kacyloron taken from his Travelocity customer service problem that occurred on November 13th, 2017.