Expedia (UK): Absolute terrible service, I spoke to * members...
A Expedia (UK) customer review by GetHuman user ~Anonymous from November 23rd, 2017
Background on ~Anonymous's case
GetHuman: ~Anonymous - can you tell our other Expedia (UK) customers when your case took place?
~Anonymous: Sure. It was morning, on November 21st.
GetHuman: Did you reach out to Expedia (UK), and if so, how?
GetHuman: And which of these common Expedia (UK) customer issues best describes the reason you wanted to talk to them?
(Shows ~Anonymous a list of common Expedia (UK) problems)
~Anonymous: "None of those really matches why I wanted to call Expedia (UK) that day." was why I was trying to call.
~Anonymous's review of Expedia (UK) customer service
GetHuman: So how would you sum up your experience for GetHuman's Expedia (UK) 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.
~Anonymous: Absolute terrible service, I spoke to * members of staff and nobody seemed to know what they were doing in the end i had to demand to speak to a manager, who managed to sort out my problem.
GetHuman: Let's quantify your experience contacting Expedia (UK). On a scale of 1 to 5, how easy is it go get help on a Expedia (UK) problem?
~Anonymous: I'd give them a three 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?
~Anonymous: I'd give them a two out of five on communication.
GetHuman: And what about Expedia (UK)'s ability to quickly and effectively address your problem?
~Anonymous: For that I would say one out of five.
GetHuman: And finally- any advice for other Expedia (UK) customers?
~Anonymous: Call them early in the day or late. Don't forget any personal or account information you might need for Expedia (UK) to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~Anonymous taken from his Expedia (UK) customer service problem that occurred on November 21st, 2017.