Priceline: After a half hour of runaround in an automated...
A Priceline customer review by GetHuman user ~Anonymous from November 9th, 2017
Background on ~Anonymous's case
GetHuman: ~Anonymous - can you tell our other Priceline customers when your case took place?
~Anonymous: Yes. It was afternoon, on November 2nd.
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 ~Anonymous a list of common Priceline problems)
~Anonymous: "Cancel or Change Booking" was why I was trying to call.
~Anonymous'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.
~Anonymous: After a half hour of runaround in an automated phonebot ****, I went digging online and found this number. I got a human almost right away. I was transferred twice, but was never put on hold once I was in the system, and I didn't have to repeat myself to each new person I talked to.
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?
~Anonymous: 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?
~Anonymous: I'd give them a five out of five on communication.
GetHuman: And what about Priceline's ability to quickly and effectively address your problem?
~Anonymous: For that I would say two out of five.
GetHuman: And finally- any advice for other Priceline customers?
~Anonymous: 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 ~Anonymous taken from his Priceline customer service problem that occurred on November 2nd, 2017.