By the end of this training article you will be able to:
- Understand the process for dining cancellations
- Set up the links and templates required
Cancellations Process
There are two ways to set up the cancellation process. The first is to set up a cancellation link directly in the confirmation, and the second is to use a link on your website whereby the guest can put in their email address and receive a cancellation prompt which lists out all their bookings.
Currently, there is no mechanism for setting cancellation deposit policies, and any deposit on the booking will default to the unprocessed deposits folio if the booking is cancelled.
Setting Up Links & Cancellation Templates
Step 1.
In cloud reservations, navigate to Facilities > F&B > Templates. Select the restaurant you are setting up cancellations for, and then choose the Cancellation Prompt template.
Create the template of your choice, and put a link with the tag $$Link$$ behind a button prompting them to view or cancel bookings.
Save your template.
Step 2.
Staying in the same place, select the Cancellation Confirmation template.
Create your template which the guest will be sent once they have cancelled the booking.
Step 3.
For step 3 you have two options depending on how you are setting up your cancellations.
Option 1 - Direct link for a specific booking.
Include the tag $$CancelLink$$ in your booking confirmation. This will take the guest to the specific booking and allow them to cancel.
Option 2 - Generate a list of guest bookings.
Include the following link in your booking confirmations. You will need to use the hotelID and RestID from your corresponding dining engine.
https://cloud-reservations.net/Cancel/Meals?hotelID=XXXX&restID=XX
This will then prompt the guest to put in the email address associated with the bookings, and then they will get emailed a full list off all upcoming bookings to cancel.
Online cancellations are now up and running without any further action required.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article