Orbitz: Talked to * reps and could not understand any o...
A Orbitz customer review by GetHuman user GetHuman-399910 from November 22nd, 2017
Background on GetHuman-399910's case
GetHuman: GetHuman-399910 - can you tell our other Orbitz customers when your case took place?
GetHuman-399910: Yes I can. It was afternoon, on November 16th.
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-399910 a list of common Orbitz problems)
GetHuman-399910: "Refund a Charge" was why I was trying to call.
GetHuman-399910'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-399910: Talked to * reps and could not understand any of them, except that they were incapable of fixing a problem that was due to Orbitz. And, the information they provided was incorrect because I then called Delta and found out what Orbitz was telling me was not in fact correct.
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-399910: 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-399910: I'd give them a one out of five on communication.
GetHuman: And what about Orbitz's ability to quickly and effectively address your problem?
GetHuman-399910: For that I would say five out of five.
GetHuman: And finally- any advice for other Orbitz customers?
GetHuman-399910: 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-399910 taken from his Orbitz customer service problem that occurred on November 16th, 2017.