Priceline: DO NOT SELECT * FOR CUSTOMER SERVICE! WAIT ON T...
A Priceline customer review by GetHuman user ~happylizz from November 7th, 2017
Background on ~happylizz's case
GetHuman: ~happylizz - can you tell our other Priceline customers when your case took place?
~happylizz: Yeah. It was middle of the night, on October 31st.
GetHuman: Did you reach out to Priceline, and if so, how?
GetHuman: And which of these common Priceline customer issues best describes the reason you wanted to talk to them?
(Shows ~happylizz a list of common Priceline problems)
~happylizz: "Make a booking" was why I was trying to call.
~happylizz's review of Priceline customer service
GetHuman: So how would you sum up your experience for GetHuman's Priceline 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.
~happylizz: DO NOT SELECT * FOR CUSTOMER SERVICE! WAIT ON THE LINE! I tried selecting * a couple of times and got the run around. Just wait for an operator to transfer your call and then tell them what you need to speak to someone about. They will direct you to AN ACTUAL PERSON. This works!
GetHuman: Let's quantify your experience contacting Priceline. On a scale of 1 to 5, how easy is it go get help on a Priceline problem?
~happylizz: 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?
~happylizz: I'd give them a one out of five on communication.
GetHuman: And what about Priceline's ability to quickly and effectively address your problem?
~happylizz: For that I would say three out of five.
GetHuman: And finally- any advice for other Priceline customers?
~happylizz: Call them early in the day or late. Don't forget any personal or account information you might need for Priceline to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~happylizz taken from his Priceline customer service problem that occurred on October 31st, 2017.