They would like for the confirmation email message trigger from SNT to GMS to be delayed until the user select "confirm reservation" in Rover.
Currently, confirmation email is being triggered even when the reservation is deemed not completed. For example: during reservation creation, before confirming or adding payment, the dates were incorrect, user went back to the dashboard to change the dates but the reservation was shown as "confirmed" and an email reservation confirmation was sent to the guest.
This also triggers multiple confirmation emails being sent to the guests.
On the GMS end - they are able to set the delay timer to delay sending of the confirmation email. Other option is a manual trigger of the confirmation email but would require additional resource to monitor email confirmation being sent to guests.
This is a request from Belvedere Hotel.
They would like for the confirmation email message trigger from SNT to GMS to be delayed until the user select "confirm reservation" in Rover.
Currently, confirmation email is being triggered even when the reservation is deemed not completed. For example: during reservation creation, before confirming or adding payment, the dates were incorrect, user went back to the dashboard to change the dates but the reservation was shown as "confirmed" and an email reservation confirmation was sent to the guest.
This also triggers multiple confirmation emails being sent to the guests.
On the GMS end - they are able to set the delay timer to delay sending of the confirmation email. Other option is a manual trigger of the confirmation email but would require additional resource to monitor email confirmation being sent to guests.