Skip to content
← Property Operations & PMS

What is the problem you're trying to solve?

'Availibility block shouldn't be released after it's "Confirmed"' has been merged into this idea

Property Operations & PMS: Reservation management

Categories

Availability Block shouldn't be released after it's "Confirmed"

Currently, the system allows a "Confirmed" block to be released unless the "Do not release" toggle is manually selected. This redundancy creates a high risk of manual error, which has recently resulted in an accidental overbooking.

Suppose when we click "Confirmed", it's confirmed and the block should automatically change to "Do not release". Otherwise, it makes the process more complicated and increases the chance of errors.

1 vote

We're glad you're here

Please sign in to leave feedback
Signed in as (Sign out)
Close
Close

We’ll send you updates on this idea

Nguyen Dieu Linh shared this idea  ·   ·  Report…  ·  Admin →
How important is this to you?

We're glad you're here

Please sign in to leave feedback
Signed in as (Sign out)
Close
Close

We're glad you're here

Please sign in to leave feedback
Signed in as (Sign out)
Close
Close
Submitting...
An error occurred while saving the comment
  • Nguyen Dieu Linh commented  ·   ·  Report

    Right now, even after we mark a block as "Confirmed," the system can still release it unless we manually check a second box called "Do not release." Having two separate steps for the same action is confusing and has already caused an accidental overbooking because the second box was missed.

    If a block is confirmed, the system should automatically set it to “Do not release.” Otherwise, confirming the block does not serve its purpose.