Triggers should fire in same order for last minute reservation
The triggers should fire in the same order in which they are usually sent, even for a last-minute booking (instead of all firing at once). This is because when you create the triggers, you define a specific time to send each message
-
Jameson King commented
Agreed! we often have last minute bookings and the confirmation message ends up going out after the check-in details and they often overlook the checkin details and don't know how to get in. Please add this!!!
-
Jenn Eddy commented
Have you used the hour vs day setting for when its sent? Here's an example of our morning after arrival message that goes out at 10am. Our check in time is at 4pm + 18 hours = 10am the next day.
-
Kana Gordon commented
For last minute bookings, it would be really helpful to be able to set the order of when messages go out so it is logical to the guest. Booking Confirmation message should come before the other triggers, for example.
-
Phung Dang commented
Property managers often encounter last-minute bookings where guests check in on the same day the booking is made. In such cases, there are typically two triggers:
1/ An instant trigger for the event of NEW_BOOKING,
2/ A time-based event trigger for BEFORE_STAY_STARTS, which allows to fire after the check-in time.
However, when both events are scheduled for the same time, there is currently no hierarchy or guarantee on the order in which these triggers will fire. As a result, the BEFORE_STAY_STARTS trigger might send a message before the NEW_BOOKING event, leading to confusion and operational inefficiencies.
My request is to improve the handling of last-minute bookings and ensure a logical sequence of events. We propose the following enhancements:
1/ Ordered Trigger Execution:
Implement a mechanism to enforce a hierarchy between triggers, ensuring that the NEW_BOOKING event always fires before the BEFORE_STAY_STARTS event when both are scheduled for the same time.
2/ Condition-Specific Triggers for Last-Minute Bookings.