A guest on a non-refundable Agoda booking is asking for a free cancellation. Here is how that request actually gets decided, what the property's role is, and how to respond without guessing.
A guest asking for a free cancellation on a booking they made under a non-refundable rate puts you in an awkward spot, because the rate plan and the actual outcome of the request are not always the same thing. This article walks through how these requests get handled and what you can control.
A guest booked a room under a non-refundable rate, knowing, at least in principle, that cancelling would not normally entitle them to a refund. Later, they ask for an exception, sometimes through Agoda's guest support channel, sometimes by contacting the property directly, citing a reason they consider reasonable for being let out of the booking without the usual charge.
The rate plan itself doesn't change just because a request is made. What determines the outcome is whether the property agrees to the exception, whether Agoda's own policies for the circumstance apply, or some combination of both, depending on how the request was raised and what it's based on.
A non-refundable rate plan exists specifically so that a property can price more aggressively in exchange for certainty of revenue if the guest cancels. Honoring a free cancellation request on that rate, even once, sets aside the reason the rate plan was offered at that price in the first place, which is why it is not something that happens by default just because a guest asks.
At the same time, some requests are raised through processes where Agoda itself reviews specific circumstances, separate from the property simply agreeing out of goodwill, so the path a request takes can affect who ultimately decides it.
Work through the specifics of the booking and the request before deciding anything, rather than replying based on the guest's tone or urgency alone.
Whatever the final decision on a cancellation request, the calendar needs to reflect it correctly and quickly, including per-room no-show marking, date shifts, and early checkout where relevant, so the room is either reopened for sale or correctly held, matching the actual outcome rather than an assumption.
Activity history keeps a record of who made the decision and when, which is useful if the same request is raised again or reviewed later. You can see the calendar and history views on the public demo at try.primehostpartners.com, open without signing up.