Agoda: Cancel booking
A Agoda customer review by GetHuman user GetHuman-ufukkaba from December 8th, 2017
Background on GetHuman-ufukkaba's case
GetHuman: GetHuman-ufukkaba - can you tell our other Agoda customers when your case took place?
GetHuman-ufukkaba: Yes I can. It was evening, on December 5th.
GetHuman: Did you reach out to Agoda, and if so, how?
GetHuman: And which of these common Agoda customer issues best describes the reason you wanted to talk to them?
(Shows GetHuman-ufukkaba a list of common Agoda problems)
GetHuman-ufukkaba: "Make a booking" was why I was trying to call.
GetHuman-ufukkaba's review of Agoda customer service
GetHuman: So how would you sum up your experience for GetHuman's Agoda 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-ufukkaba: Cancel booking
GetHuman: Can you tell the rest of us a bit more from what happened on 12/05/17?
GetHuman-ufukkaba: I went to the accommodation to check in, but they told me they are not working together with Agoda so we had to leave that place, while my money was taken from my creditcard.
GetHuman: Let's quantify your experience contacting Agoda. On a scale of 1 to 5, how easy is it go get help on a Agoda problem?
GetHuman-ufukkaba: 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-ufukkaba: I'd give them a one out of five on communication.
GetHuman: And what about Agoda's ability to quickly and effectively address your problem?
GetHuman-ufukkaba: For that I would say one out of five.
GetHuman: And finally- any advice for other Agoda customers?
GetHuman-ufukkaba: Call them early in the day or late. Don't forget any personal or account information you might need for Agoda to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from GetHuman-ufukkaba taken from his Agoda customer service problem that occurred on December 5th, 2017.