Orbitz: Waited on hold for ** minutes then hung up and...
A Orbitz customer review by GetHuman user GetHuman-168980 from November 15th, 2017
Background on GetHuman-168980's case
GetHuman: GetHuman-168980 - can you tell our other Orbitz customers when your case took place?
GetHuman-168980: Yes I can. It was evening, on November 13th.
GetHuman: Did you reach out to Orbitz, and if so, how?
GetHuman: And which of these common Orbitz customer issues best describes the reason you wanted to talk to them?
(Shows GetHuman-168980 a list of common Orbitz problems)
GetHuman-168980: "Find Itinerary" was why I was trying to call.
GetHuman-168980's review of Orbitz customer service
GetHuman: So how would you sum up your experience for GetHuman's Orbitz 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-168980: Waited on hold for ** minutes then hung up and tried the hit number one ay each prompt method suggested here and was immediately connected to a woman in a Phillipine call center with a horrible scratchy connection...She was pleasant but I will never use orbitz again.
GetHuman: Let's quantify your experience contacting Orbitz. On a scale of 1 to 5, how easy is it go get help on a Orbitz problem?
GetHuman-168980: 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-168980: I'd give them a two out of five on communication.
GetHuman: And what about Orbitz's ability to quickly and effectively address your problem?
GetHuman-168980: For that I would say three out of five.
GetHuman: And finally- any advice for other Orbitz customers?
GetHuman-168980: Call them early in the day or late. Don't forget any personal or account information you might need for Orbitz to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from GetHuman-168980 taken from his Orbitz customer service problem that occurred on November 13th, 2017.