****o, why suddenly Cancel my Booking ********* Check-in December **, ****. I not cance...

GetHuman821150's customer service issue with Agoda from June 2018

23 views
 | 
2130 similar
 | 
0 following
Help with my Agoda issue
How did GetHuman821150 do it?
Waiting to hear how GetHuman821150 fixed the problem to share with other customers.
****o, why suddenly Cancel my Booking ********* Check-in December **, ****. I not cancel my booking, please don't charge to my credit card.
I trust that Agoda will make this right and come up with a resolution that is fair.
Help with my Agoda issue
Follow this to see how it gets fixed
Do you have a customer issue as well?
We can help you get Agoda's attention and get better help faster. Tap below to get started.
Having Agoda issues too?
Get tips from pros & other customers, and get it handled faster:
For better results, write at least 100 characters
How would Agoda email you?
This email address isn't valid
Follow this issue
See how GetHuman821150 fixes it.
This email address isn't valid

Agoda

Customer service issue
Reported by GetHuman821150
Jun 26th, 2018 - 2 mons ago
I have an issue with Agoda too
Fixed
Seen by 23 customers so far
Similar issue to 2130 others
0 customers following this
Follow this issue to see how it gets fixed
Items needed
Email address on the account
Last 4 digits of the payment card
Phone number on the booking
Booking ID
Timeline
GetHuman821150 started working on this issue
Jun 26th 3:49am
GetHuman821150 indicated the issue is not fixed yet.
Jun 26th 5:23am
GetHuman821150 indicated the issue is not fixed yet.
Jun 26th 5:24am
GetHuman821150 indicated the issue is not fixed yet.
Jun 26th 5:27am
GetHuman821150 indicated the issue is not fixed yet.
Jun 26th 5:31am
GetHuman821150 indicated the issue is not fixed yet.
Jun 26th 5:48am
GetHuman821150 indicated the issue is not fixed yet.
Jun 26th 5:52am
GetHuman821150 indicated the issue is not fixed yet.
Jun 26th 6:21am
GetHuman821150 confirmed the issue is fixed. Hooray!
Jun 26th 11:41am
GetHuman821150 confirmed the issue is fixed. Hooray!
Jun 26th 11:42am