I accidentally booked a hotel in Indianapolis IN, and immediately cancelled it. I then...

GetHuman653090's Refund a booking issue with Agoda from May 2018

Help with my Agoda issue
The issue in GetHuman653090's own words
I accidentally booked a hotel in Indianapolis IN, and immediately cancelled it. I then booked the correct hotel, which is same chain but different location. I am being charged for both locations. I called the one that was cancelled and spoke with manager and he said he was unable to help. could I get some help please to get my money back that I cancelled within minutes due to accidentally hitting the wrong button. Please help me.. Confirmation number for one cancelled was *********. The manage at Comfort Suites Indianapolis states that I have to get reimbursement from you. Please help! Thank you
GetHuman653090 did not yet indicate what Agoda should do to make this right.
I have an issue with Agoda too
How GetHuman653090 fixed the problem
We are waiting for GetHuman653090 to fix the problem and share the solution with the rest of us customers.
Please help with my Agoda issue
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
This email address isn't valid

Agoda

Refund a booking issue
Reported by GetHuman653090
May 3rd, 2018 - a yr ago
I have an issue with Agoda too
Not resolved
Seen by 5 customers so far
Similar issue to 29214 others
0 customers following this
Items needed
Email address on the account
Last 4 digits of the payment card
Phone number on the booking
Booking ID
Timeline
GetHuman653090 started working on this issue
May 3rd, 2018 4:09pm
GetHuman653090 indicated the issue is not fixed yet.
May 3rd, 2018 9:19pm
GetHuman653090 indicated the issue is not fixed yet.
May 3rd, 2018 9:22pm
GetHuman653090 indicated the issue is not fixed yet.
May 3rd, 2018 9:22pm
GetHuman653090 indicated the issue is not fixed yet.
May 5th, 2018 2:04am