Expedia: I have waited for over an hour four times in th...
A Expedia customer review by GetHuman user GetHuman-405434 from November 26th, 2017
Background on GetHuman-405434's case
GetHuman: GetHuman-405434 - can you tell our other Expedia customers when your case took place?
GetHuman-405434: Yes. It was afternoon, on November 24th.
GetHuman: Did you reach out to Expedia, and if so, how?
GetHuman: And which of these common Expedia customer issues best describes the reason you wanted to talk to them?
(Shows GetHuman-405434 a list of common Expedia problems)
GetHuman-405434: "Dispute a Charge" was why I was trying to call.
GetHuman-405434's review of Expedia customer service
GetHuman: So how would you sum up your experience for GetHuman's Expedia 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-405434: I have waited for over an hour four times in the last ** hours. Each time, I have been disconnected by Expedia's system. Not once, have they tried to call me back. Unfortunately, I'm at their mercy as I have to change an international flight within the next ** hours.
GetHuman: Let's quantify your experience contacting Expedia. On a scale of 1 to 5, how easy is it go get help on a Expedia problem?
GetHuman-405434: 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-405434: I'd give them a one out of five on communication.
GetHuman: And what about Expedia's ability to quickly and effectively address your problem?
GetHuman-405434: For that I would say one out of five.
GetHuman: And finally- any advice for other Expedia customers?
GetHuman-405434: Call them early in the day or late. Don't forget any personal or account information you might need for Expedia to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from GetHuman-405434 taken from his Expedia customer service problem that occurred on November 24th, 2017.