Expedia: i got credit for travel insurance - company tol...
A Expedia customer review by GetHuman user ~legaleagle from November 27th, 2017
Background on ~legaleagle's case
GetHuman: ~legaleagle - can you tell our other Expedia customers when your case took place?
~legaleagle: Yeah. It was middle of the night, on November 18th.
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 ~legaleagle a list of common Expedia problems)
~legaleagle: "Change flight" was why I was trying to call.
~legaleagle'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.
~legaleagle: i got credit for travel insurance - company told me they had no such policy number - explained to expedia how serious insurance fraud is and the insurance commissioner takes it seriously what if someone gets injured and their policy is non existent she did not like but i am getting my money bak
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?
~legaleagle: 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?
~legaleagle: 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?
~legaleagle: For that I would say two out of five.
GetHuman: And finally- any advice for other Expedia customers?
~legaleagle: 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 ~legaleagle taken from his Expedia customer service problem that occurred on November 18th, 2017.