Changes

Jump to navigation Jump to search

Auto Actions

1,443 bytes added, 10:17, 24 April 2019
no edit summary
''This page is about the menu SETTINGS -> GUEST MANAGEMENT -> AUTO ACTIONS''
An Auto Action is an action which can be programmed to occur at a time relative to the time the booking being was made, to the check in date or to the check out date.
The action can be a pre-canned email sent to the guest or to a fixed email address or a change , and it can also make changes to the booking information. Click on "Edit" to modify an existing auto action or on "Create New Action" to set up a new auto action:
The auto actions will appear on the MAIL 'Mail & Actions' tab of each booking where you manually can send the email can be sent manuallytrigger the changes to the booking. If you are using your own mail server for outgoing mail the Booking and Invoice actions will also be applied before sending the mail.   Note: Confirmation message will send automatically to the guest. You can customize them in SETTINGS ->GUEST MANAGEMENT->CONFIRMATION MESSAGES.
Note: Confirmation messages will send automatically to the guest. You can customize them in SETTINGS ->GUEST MANAGEMENT->CONFIRMATION MESSAGES.
Email sending works per account.
Auto Action Emails which are sent automatically by the system are sent from the EMail address of the account that created the Auto Action. This is the account set up in in SETTINGS-ACCOUNT-OUTGOING EMAIL.
 
Automatic actions will trigger every 15 minutes.
'''Manual sending:'''
When sending manual by clicking on the 'Send' button you will need to make sure you are logged into the account which uses the EMail address you want to send from.
 
__TOC__
== Trigger ==
== Examples ==
'''Example 1''' - ===Automatically change the status of all "Request" bookings to "Cancelled" after three days:===
Trigger tab
*Booking Status = Cancelled
'''Example 2''' - ===Automatically change the status of all bookings which have been imported from Ical to "Request" :===
Trigger tab:
Booking changes are applied before the mail is sent.
'''Example 3''' - ===Automatically set a flag /colour for a booking coming from a certain channel :===
Trigger tab:
*Flag Colour - choose the flag colour
Booking changes are applied before the mail is sent so that the flag template variable can be reflected in the email.
'''Example 4''' - ===Automatically send an Email to the guest when the status of a booking changes to "Cancelled" :===
Trigger tab:
'''Example 5''' - ===Automatically add a fee to all bookings from a channel:===
Trigger tab:
*Trigger Event = After Booking
'''Example 6''' - ===Apply a flag when a payment was made:===
Also see Example 14 for payments/deposits prior to Check-in
*Flag Colour - choose the flag colour
===Apply an info code and and/or icon when a payment was made===
'''Example 7''' Trigger tab:*Trigger Event = After Booking*Trigger Time = Immediate*Trigger Window = 365*Booking Source = All*Booking Status = All but not cancelled*Invoice Balance = Any Payment made Booking Info tab:*Execution = One time only*Info Code = Enter the preset code for the icon or info code which you have created in SETTINGS- >ACCOUNT->PREFERENCES. ===Apply a flag when a booking is cancelled:===
Trigger tab
*Trigger Event = After Booking
*Trigger Time = 1 Hour
*Trigger Window = 365 days
*Flag Colour = Set as required
 '''Example 8''' - ===Send an email or SMS to Guest when booking made more than 10 days in advance:===
Trigger tab:
'''Example 9''' - ===Send an email with a key code for a specific unit one day before check-in:===
Trigger tab:
'''Example 10''' - ===Send an email to guests from Channels:===
Trigger tab:
'''Example 11''' - ===Automatically set a flag for a bookings from a a channel which have breakfast included :===
Trigger tab:
'''Example 12''' - ===Automatically send a message (email or sms) to guests that have Checked-out 30 days or more :===
Trigger tab:
'''Example 13''' - ===Automatically send a Request for payment to your guests for all bookings :===
Trigger tab:
Booking changes are applied before the mail is sent so that the flag template variable can be reflected in the email.
'''Example 14''' - ===Automatically send a Request for payment to your guests XX days before arrival :===
Trigger tab:
'''Example 15''' - ===Apply a flag when deposit is was made prior to Check-in :===
Trigger tab:
Setting details with the Booking tab and Booking info tab allows you to trigger additional (follow on) Auto Actions and Reports.
 '''Example 16''' - ===Apply a flag when booking is fully paid :===
Trigger tab:
'''Example 17''' - ===Send SMS in a certain language (if it is the language of the booking) or a default language===
This uses a smart template variable. In this example we check whether the guest booked in French. If yes, then we send a French text. If no, we send an English text.
*Phone Number = [GUESTMOBILE]
*SMS Message = [IF=:[GUESTLANGUAGE]:fr:French_text|English_text]
 
===Automatically assign invoice numbers===
Trigger tab:
*Trigger Event = Check-out
*Trigger Time = Immediate
*Any Booking Info Code = CHECKOUT (optional only if you use the check-out function, if not leave blank)
 
Invoice tab:
*Assign Invoice Number = yes
 
===Group check-in ===
This requires the master booking to be checked-in via the check-in function.
 
Trigger tab:
 
*Trigger Event = After Booking
*Trigger Time = immediately
*Trigger Window = 365
*Booking Source = All
*Booking Status = All but not cancelled
*Group bookings" = Trigger all on master
*Info Code = CHECKIN
 
Booking info tab :
*Info Code = CHECKIN
 
 
===Send Remotelock/Lockstate PIN ===
Trigger tab:
*Trigger Event = Check-in
*Trigger Time = -2 (the number of days before check-in you want to sent the code)
*Trigger Window = 2
*Booking Source = All
*Booking Status = All but not cancelled
*Group bookings" = Trigger all on master
*Info Code = LOCKSTATE_PIN
 
Email tab :
*Send Email = Guest and cc
*EMail Subject = Your access code (your text)
*Email Text = Your text which includes the template variable [BOOKINGINFOCODETEXT:LOCKSTATE_PIN]
== Troubleshooting ==
'''If Auto Actions do not send:'''
In The list in the "TestMail" tab of the Auto Action booking will tell you can check why an Auto Action was not executed. Common causes are:
*Is your outgoing Email address working? Go to SETTINGS->ACCOUNT->OUTGOING EMAIL and click on "Send Test Email".
*Is your Auto Action set to send automatically?
*Is the guests Email address valid ("Mails" tab of the booking)?
*Is the booking set to allow automatic Emails Allow Auto Actions ("Mails" tab of the booking)?
*Do all trigger events apply to the booking?
770

edits

Navigation menu