Difference between revisions of "Auto Actions"

From Beds24 Wiki
Jump to navigation Jump to search
(15 intermediate revisions by 4 users not shown)
Line 4: Line 4:
 
[[Category:Troubleshooting]]
 
[[Category:Troubleshooting]]
 
[[Category:Automation]]
 
[[Category:Automation]]
 +
[[Category:Webhooks]]
 
<div class="heading">Auto Actions</div>
 
<div class="heading">Auto Actions</div>
  
  This page is about the menu SETTINGS -> GUEST MANAGEMENT -> AUTO ACTIONS and explains how to set up and use Auto Actions.
+
  This page is about the menu {{#fas:cog}} (SETTINGS) GUEST MANAGEMENT > AUTO ACTIONS and explains how to set up and use Auto Actions.
  
 
An Auto Action is an action which can be programmed to occur at a time relative to the time the booking was made, to the check in date or to the check out date. To use this function you need to set the system to use you own Email address for sending in SETTINGS->ACCOUNT->OUTGOING EMAIL.  
 
An Auto Action is an action which can be programmed to occur at a time relative to the time the booking was made, to the check in date or to the check out date. To use this function you need to set the system to use you own Email address for sending in SETTINGS->ACCOUNT->OUTGOING EMAIL.  
Line 89: Line 90:
 
Test why an auto action did not trigger.
 
Test why an auto action did not trigger.
  
<div class="NavFrame">
+
== Troubleshooting ==
<div class="NavHead">'''Examples'''</div>
+
'''If Auto Actions do not send:'''
<div class="NavContent" style="display: none;">
+
The list in the "Mail" tab of the booking will tell you why. 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 Allow Auto Actions ("Mails" tab of the booking)?
 +
*Do all trigger events apply to the booking?
 +
 
 +
 +
'''Auto Action is not editable'''
 +
To have write access to an auto action an account needs to have write access to all properties to which the auto action applies. This might not be the case if you use sub accounts and the Auto Action is set to trigger for "All Properties".
 +
 
 +
'''You don't have permission to access control2.php on this server''' error message, when the save button is clicked
 +
It is most likely something in your content triggering the firewall.
 +
Try adding the content bit by bit until you find the item causing the problem.
 +
Often it is a script or HTML item that appears to the firewall as a possible hacking attack.
 +
It can also be something that looks innocent like a combination of numbers and words like "and" or "or" that hackers often use in sql injection attacks.
 +
Once you find the item causing the problem, try rewording it.
 +
 
  
 
== Examples ==
 
== Examples ==
===Automatically change the status of all "Request" bookings to "Cancelled" after three days ===
+
<div class="mw-collapsible mw-collapsed">
 +
<div  class="headline-collapse" >
 +
=== Automatically change the status of all "Request" bookings to "Cancelled" after three days ===
 +
</div>
 +
<div class="mw-collapsible-content">
 
Trigger tab
 
Trigger tab
 
*Trigger Event = After Booking
 
*Trigger Event = After Booking
Line 103: Line 125:
 
*Execution = One time only
 
*Execution = One time only
 
*Booking Status = Cancelled
 
*Booking Status = Cancelled
 +
</div>
 +
</div>
 +
 +
<div class="mw-collapsible mw-collapsed">
 +
<div  class="headline-collapse" >
  
===Automatically change the status of all bookings which have been imported from Ical to "Request"===
+
=== Automatically change the status of all bookings which have been imported from Ical to "Request" ===
 +
</div>
 +
<div class="mw-collapsible-content">
 
Trigger tab:
 
Trigger tab:
 
*Trigger Event = After Booking
 
*Trigger Event = After Booking
Line 115: Line 144:
  
 
Booking changes are applied before the mail is sent.
 
Booking changes are applied before the mail is sent.
 +
</div>
 +
</div>
 +
 +
<div class="mw-collapsible mw-collapsed">
 +
<div  class="headline-collapse" >
  
 
===Automatically set a flag/colour for a booking coming from a certain channel===
 
===Automatically set a flag/colour for a booking coming from a certain channel===
 +
</div>
 +
<div class="mw-collapsible-content">
 +
 
Trigger tab:
 
Trigger tab:
 
*Trigger Event = After Booking
 
*Trigger Event = After Booking
Line 128: Line 165:
  
 
Booking changes are applied before the mail is sent so that the flag template variable can be reflected in the email.
 
Booking changes are applied before the mail is sent so that the flag template variable can be reflected in the email.
 +
</div>
 +
</div>
  
 +
<div class="mw-collapsible mw-collapsed">
 +
<div  class="headline-collapse" >
 
===Automatically send an Email to the guest when the status of a booking changes to  "Cancelled"===
 
===Automatically send an Email to the guest when the status of a booking changes to  "Cancelled"===
 +
</div>
 +
<div class="mw-collapsible-content">
 +
 
Trigger tab:
 
Trigger tab:
 
*Trigger Event = Check-in
 
*Trigger Event = Check-in
Line 143: Line 187:
 
<span style="color:#fe746c;“ >{{#fas:exclamation-triangle}}  </span> If you are using deposit collection make sure you set SETTINGS->PAYMENTS->PAYMENT COLLECTION "Non Payment Booking Status" = Request.
 
<span style="color:#fe746c;“ >{{#fas:exclamation-triangle}}  </span> If you are using deposit collection make sure you set SETTINGS->PAYMENTS->PAYMENT COLLECTION "Non Payment Booking Status" = Request.
  
 +
</div>
 +
</div>
 +
 +
<div class="mw-collapsible mw-collapsed">
 +
<div  class="headline-collapse" >
 
===Automatically change the status of all upcoming direct bookings to "Cancelled"  and send an Email to the guest ===
 
===Automatically change the status of all upcoming direct bookings to "Cancelled"  and send an Email to the guest ===
 +
</div>
 +
<div class="mw-collapsible-content">
 
Trigger tab:
 
Trigger tab:
 
*Trigger Event = Check-in
 
*Trigger Event = Check-in
Line 157: Line 208:
 
*Trigger Action = Auto
 
*Trigger Action = Auto
 
*Send Email = Guest
 
*Send Email = Guest
 +
</div>
 +
</div>
  
 +
<div class="mw-collapsible mw-collapsed">
 +
<div  class="headline-collapse" >
 
===Automatically add a fee to all bookings from a channel===
 
===Automatically add a fee to all bookings from a channel===
 +
</div>
 +
<div class="mw-collapsible-content">
 
Trigger tab:
 
Trigger tab:
 
*Trigger Event = After Booking
 
*Trigger Event = After Booking
Line 173: Line 230:
  
 
The fee will be added the next time the auto actions run.  
 
The fee will be added the next time the auto actions run.  
 +
</div>
 +
</div>
  
 +
<div class="mw-collapsible mw-collapsed">
 +
<div  class="headline-collapse" >
 
===Add a pending payment===
 
===Add a pending payment===
 +
</div>
 +
<div class="mw-collapsible-content">
 
Trigger tab:
 
Trigger tab:
 
*Trigger Event = After Booking or Before Check-in
 
*Trigger Event = After Booking or Before Check-in
Line 194: Line 257:
 
*Payment Rule = use auto or manual  - if you have set up payment rules in SETTINGS->GUEST MANAGEMENT->PAYMENT COLLECTION they will be available here  
 
*Payment Rule = use auto or manual  - if you have set up payment rules in SETTINGS->GUEST MANAGEMENT->PAYMENT COLLECTION they will be available here  
 
*Payment Due = Set when the payment is due
 
*Payment Due = Set when the payment is due
 +
</div>
 +
</div>
  
 
+
<div class="mw-collapsible mw-collapsed">
====Example: Credit card is collected at time of booking and full payment is due 3 days prior to arrival.====
+
<div  class="headline-collapse" >
 +
===Credit card is collected at time of booking and full payment is due 3 days prior to arrival.===
 +
</div>
 +
<div class="mw-collapsible-content">
  
 
Trigger tab:
 
Trigger tab:
Line 213: Line 281:
  
 
<span style="color:#fe746c;“ >{{#fas:exclamation-triangle}}  </span> Automatic collection is only available for customer who use [[Stripe]].
 
<span style="color:#fe746c;“ >{{#fas:exclamation-triangle}}  </span> Automatic collection is only available for customer who use [[Stripe]].
 +
</div>
 +
</div>
  
====Example: Credit card is collected at time of booking and you want to 'Capture' a Security Deposit.====
+
<div class="mw-collapsible mw-collapsed">
 +
<div  class="headline-collapse" >
 +
===Credit card is collected at time of booking and you want to 'Capture' a Security Deposit.===
 +
</div>
 +
<div class="mw-collapsible-content">
  
 
Trigger tab:
 
Trigger tab:
Line 250: Line 324:
 
*Add info code on success = add a Booking Info item to the booking on success
 
*Add info code on success = add a Booking Info item to the booking on success
 
*Add info code on failure = add a Booking Info item to the booking on failure
 
*Add info code on failure = add a Booking Info item to the booking on failure
 +
</div>
 +
</div>
  
 +
<div class="mw-collapsible mw-collapsed">
 +
<div  class="headline-collapse" >
 
===Apply a flag when a payment was made===
 
===Apply a flag when a payment was made===
 +
</div>
 +
<div class="mw-collapsible-content">
 
<span style="color: #f3e504; font-size: 250%;" >{{#fas:lightbulb}} </span>  Also see Example : " Apply a flag when deposit was made prior to Check-in AND/OR Apply a flag when booking is fully paid".
 
<span style="color: #f3e504; font-size: 250%;" >{{#fas:lightbulb}} </span>  Also see Example : " Apply a flag when deposit was made prior to Check-in AND/OR Apply a flag when booking is fully paid".
  
Line 266: Line 346:
 
*Flag Text = The text you want to display
 
*Flag Text = The text you want to display
 
*Flag Colour - choose the flag colour
 
*Flag Colour - choose the flag colour
 +
</div>
 +
</div>
  
 +
<div class="mw-collapsible mw-collapsed">
 +
<div  class="headline-collapse" >
 
===Apply a flag when a payment FAILS at Stripe===
 
===Apply a flag when a payment FAILS at Stripe===
 +
</div>
 +
<div class="mw-collapsible-content">
 
   
 
   
 
Trigger tab:
 
Trigger tab:
Line 281: Line 367:
 
*Flag Text = Stripe Payment Failed
 
*Flag Text = Stripe Payment Failed
 
*Flag Colour - choose the flag colour
 
*Flag Colour - choose the flag colour
 +
</div>
 +
</div>
  
 +
<div class="mw-collapsible mw-collapsed">
 +
<div  class="headline-collapse" >
 
===Apply a flag to Booking.com bookings and auto report the Credit Card when a payment FAILS at Stripe===
 
===Apply a flag to Booking.com bookings and auto report the Credit Card when a payment FAILS at Stripe===
 +
</div>
 +
<div class="mw-collapsible-content">
  
 
Go to Settings > Channel Manager > Preferences and set Auto report failed cards = Yes
 
Go to Settings > Channel Manager > Preferences and set Auto report failed cards = Yes
Line 298: Line 390:
 
*Flag Text = Failed CC reported to Booking.com  
 
*Flag Text = Failed CC reported to Booking.com  
 
*Flag Colour - choose the flag colour
 
*Flag Colour - choose the flag colour
 +
</div>
 +
</div>
  
 +
<div class="mw-collapsible mw-collapsed">
 +
<div  class="headline-collapse" >
 
===Apply an info code and and/or icon when a payment was made===
 
===Apply an info code and and/or icon when a payment was made===
 +
</div>
 +
<div class="mw-collapsible-content">
 
Trigger tab:
 
Trigger tab:
 
*Trigger Event = After Booking
 
*Trigger Event = After Booking
Line 311: Line 409:
 
*Execution = One time only
 
*Execution = One time only
 
*Info Code = Enter the preset code for the icon or info code which you have created in SETTINGS->ACCOUNT->PREFERENCES.
 
*Info Code = Enter the preset code for the icon or info code which you have created in SETTINGS->ACCOUNT->PREFERENCES.
 +
</div>
 +
</div>
  
 +
<div class="mw-collapsible mw-collapsed">
 +
<div  class="headline-collapse" >
 
===Apply a flag when a booking is cancelled===
 
===Apply a flag when a booking is cancelled===
 +
</div>
 +
<div class="mw-collapsible-content">
 
Trigger tab
 
Trigger tab
 
*Trigger Event = After Booking
 
*Trigger Event = After Booking
Line 324: Line 428:
 
*Flag text = (enter the text you require)
 
*Flag text = (enter the text you require)
 
*Flag Colour = Set as required
 
*Flag Colour = Set as required
 +
</div>
 +
</div>
  
 +
<div class="mw-collapsible mw-collapsed">
 +
<div  class="headline-collapse" >
 
===Send an message or SMS to Guest when booking made more than 10 days in advance===
 
===Send an message or SMS to Guest when booking made more than 10 days in advance===
 +
</div>
 +
<div class="mw-collapsible-content">
 
Trigger tab:
 
Trigger tab:
 
*Trigger Event = Check-in
 
*Trigger Event = Check-in
Line 338: Line 448:
 
Message tab or SMS tab:
 
Message tab or SMS tab:
 
*Update details as appropriate
 
*Update details as appropriate
 +
</div>
 +
</div>
  
 
+
<div class="mw-collapsible mw-collapsed">
 +
<div  class="headline-collapse" >
 
===Send an message or SMS to Guest when booking made more than 7 days in advance===
 
===Send an message or SMS to Guest when booking made more than 7 days in advance===
 +
</div>
 +
<div class="mw-collapsible-content">
 
Alternatively you an use Between Booking and Check in
 
Alternatively you an use Between Booking and Check in
  
Line 356: Line 471:
 
Message tab or SMS tab:
 
Message tab or SMS tab:
 
*Update details as appropriate
 
*Update details as appropriate
 +
</div>
 +
</div>
  
 +
<div class="mw-collapsible mw-collapsed">
 +
<div  class="headline-collapse" >
 
===Send an message or SMS to Guest when booking made more last minute booking - 6 days or less===
 
===Send an message or SMS to Guest when booking made more last minute booking - 6 days or less===
 
+
</div>
 +
<div class="mw-collapsible-content">
  
 
Trigger tab:
 
Trigger tab:
Line 373: Line 493:
 
Message tab or SMS tab:
 
Message tab or SMS tab:
 
*Update details as appropriate
 
*Update details as appropriate
 +
</div>
 +
</div>
  
 +
<div class="mw-collapsible mw-collapsed">
 +
<div  class="headline-collapse" >
 
===Send an Email with a key code for a specific unit one day before check-in===
 
===Send an Email with a key code for a specific unit one day before check-in===
 +
</div>
 +
<div class="mw-collapsible-content">
 
Trigger tab:
 
Trigger tab:
 
*Trigger Event = Check-in
 
*Trigger Event = Check-in
Line 392: Line 518:
  
 
The template variables will only work if you have entered text in SETTINGS->PROPERTIES->ROOMS->SET UP "Unit Names". The context help for this setting will explain how to do this.
 
The template variables will only work if you have entered text in SETTINGS->PROPERTIES->ROOMS->SET UP "Unit Names". The context help for this setting will explain how to do this.
 +
</div>
 +
</div>
  
 +
<div class="mw-collapsible mw-collapsed">
 +
<div  class="headline-collapse" >
 
===Send an Email to the guest when a payment is made===
 
===Send an Email to the guest when a payment is made===
 +
</div>
 +
<div class="mw-collapsible-content">
 
Trigger tab:
 
Trigger tab:
 
*Trigger Event = After Booking
 
*Trigger Event = After Booking
Line 404: Line 536:
 
*Enter your text.  
 
*Enter your text.  
 
You can use Invoice Template variables showing the booking charges/payments.
 
You can use Invoice Template variables showing the booking charges/payments.
 +
</div>
 +
</div>
  
 +
<div class="mw-collapsible mw-collapsed">
 +
<div  class="headline-collapse" >
 
===Send an Email to guests from Channels===
 
===Send an Email to guests from Channels===
 +
</div>
 +
<div class="mw-collapsible-content">
 
Trigger tab:
 
Trigger tab:
 
*Trigger Event = After Booking
 
*Trigger Event = After Booking
Line 423: Line 561:
  
 
The template variables will only work if you have entered text in SETTINGS->PROPERTIES->ROOMS->SET UP "Unit Names". The context help for this setting will explain how to do this.
 
The template variables will only work if you have entered text in SETTINGS->PROPERTIES->ROOMS->SET UP "Unit Names". The context help for this setting will explain how to do this.
 +
</div>
 +
</div>
  
 
+
<div class="mw-collapsible mw-collapsed">
 +
<div  class="headline-collapse" >
 
===Automatically set a flag for a bookings from a channel which have breakfast included===
 
===Automatically set a flag for a bookings from a channel which have breakfast included===
 +
</div>
 +
<div class="mw-collapsible-content">
 
Trigger tab:
 
Trigger tab:
 
*Trigger Event = After Booking
 
*Trigger Event = After Booking
Line 438: Line 581:
  
 
Booking changes are applied before the mail is sent so that the flag template variable can be reflected in the Email.
 
Booking changes are applied before the mail is sent so that the flag template variable can be reflected in the Email.
 +
</div>
 +
</div>
  
 +
<div class="mw-collapsible mw-collapsed">
 +
<div  class="headline-collapse" >
 
===Automatically send a message (Email or sms) to guests that have Checked-out 30 days or more===
 
===Automatically send a message (Email or sms) to guests that have Checked-out 30 days or more===
 +
</div>
 +
<div class="mw-collapsible-content">
 
Trigger tab:
 
Trigger tab:
 
*Trigger Event = After Check-out
 
*Trigger Event = After Check-out
Line 452: Line 601:
 
*Flag Text = The text you want to display
 
*Flag Text = The text you want to display
 
*Flag Colour - choose the flag colour
 
*Flag Colour - choose the flag colour
 +
</div>
 +
</div>
  
 
+
<div class="mw-collapsible mw-collapsed">
 +
<div  class="headline-collapse" >
 
===Automatically send a Request for payment to your guests for all bookings===
 
===Automatically send a Request for payment to your guests for all bookings===
 +
</div>
 +
<div class="mw-collapsible-content">
 
Trigger tab:
 
Trigger tab:
  
Line 476: Line 630:
 
*Flag Colour - choose the flag colour
 
*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.
 
Booking changes are applied before the mail is sent so that the flag template variable can be reflected in the Email.
 +
</div>
 +
</div>
  
 +
<div class="mw-collapsible mw-collapsed">
 +
<div  class="headline-collapse" >
 
===Automatically send a Request for payment to your guests XX days before arrival===
 
===Automatically send a Request for payment to your guests XX days before arrival===
 +
</div>
 +
<div class="mw-collapsible-content">
 
Trigger tab:
 
Trigger tab:
  
Line 499: Line 659:
 
*Flag Colour - choose the flag colour
 
*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.
 
Booking changes are applied before the mail is sent so that the flag template variable can be reflected in the Email.
 +
</div>
 +
</div>
  
 +
<div class="mw-collapsible mw-collapsed">
 +
<div  class="headline-collapse" >
 
===Automatically send a Request for payment to your guests XX days after booking===
 
===Automatically send a Request for payment to your guests XX days after booking===
 +
</div>
 +
<div class="mw-collapsible-content">
  
 
You allow your guests to make X number of payments for their booking.  
 
You allow your guests to make X number of payments for their booking.  
Line 548: Line 714:
 
**Go to Booking Info Tab and from the drop down list  
 
**Go to Booking Info Tab and from the drop down list  
 
**Select the value 'MULTIPLE' (or the value you want to use to trigger)
 
**Select the value 'MULTIPLE' (or the value you want to use to trigger)
 +
</div>
 +
</div>
  
 +
<div class="mw-collapsible mw-collapsed">
 +
<div  class="headline-collapse" >
 
===Apply a flag when deposit was made prior to Check-in===
 
===Apply a flag when deposit was made prior to Check-in===
 +
</div>
 +
<div class="mw-collapsible-content">
 
Trigger tab:
 
Trigger tab:
  
Line 576: Line 748:
  
 
Setting details with the Booking tab and Booking info tab allows you to trigger additional (follow on) Auto Actions and Reports.
 
Setting details with the Booking tab and Booking info tab allows you to trigger additional (follow on) Auto Actions and Reports.
 +
</div>
 +
</div>
  
 +
<div class="mw-collapsible mw-collapsed">
 +
<div  class="headline-collapse" >
 
===Apply a flag when booking is fully paid===
 
===Apply a flag when booking is fully paid===
 +
</div>
 +
<div class="mw-collapsible-content">
 
Trigger tab:
 
Trigger tab:
 
*Trigger Event = After Booking
 
*Trigger Event = After Booking
Line 590: Line 768:
 
*Flag Text = The text you want to display
 
*Flag Text = The text you want to display
 
*Flag Colour - choose the flag colour
 
*Flag Colour - choose the flag colour
 +
</div>
 +
</div>
  
 +
<div class="mw-collapsible mw-collapsed">
 +
<div  class="headline-collapse" >
 
===Send Email in a the guests language to an internal Email address ===
 
===Send Email in a the guests language to an internal Email address ===
 +
</div>
 +
<div class="mw-collapsible-content">
 
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.
 
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.
  
Line 599: Line 783:
 
Email tab:
 
Email tab:
 
*Enter the message in the appropriate language under your default language.
 
*Enter the message in the appropriate language under your default language.
 +
</div>
 +
</div>
  
 +
<div class="mw-collapsible mw-collapsed">
 +
<div  class="headline-collapse" >
 
===Send SMS in a certain language (if it is the language of the booking) or a default language===
 
===Send SMS in a certain language (if it is the language of the booking) or a default language===
 +
</div>
 +
<div class="mw-collapsible-content">
 
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.
 
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.
  
Line 610: Line 800:
 
*Phone Number = [GUESTMOBILE]
 
*Phone Number = [GUESTMOBILE]
 
*SMS Message = [IF=:[GUESTLANGUAGE]:fr:French_text|English_text]
 
*SMS Message = [IF=:[GUESTLANGUAGE]:fr:French_text|English_text]
 +
</div>
 +
</div>
  
 +
<div class="mw-collapsible mw-collapsed">
 +
<div  class="headline-collapse" >
 
===Automatically assign invoice numbers===
 
===Automatically assign invoice numbers===
 +
</div>
 +
<div class="mw-collapsible-content">
 
Trigger tab:
 
Trigger tab:
 
*Trigger Event = Check-out
 
*Trigger Event = Check-out
Line 619: Line 815:
 
Invoice tab:
 
Invoice tab:
 
*Assign Invoice Number = yes
 
*Assign Invoice Number = yes
 +
</div>
 +
</div>
  
 +
<div class="mw-collapsible mw-collapsed">
 +
<div  class="headline-collapse" >
 
===Group check-in ===
 
===Group check-in ===
 +
</div>
 +
<div class="mw-collapsible-content">
 
This requires the master booking to be checked-in via the check-in function.  
 
This requires the master booking to be checked-in via the check-in function.  
  
Line 635: Line 837:
 
Booking info tab :  
 
Booking info tab :  
 
*Info Code = CHECKIN
 
*Info Code = CHECKIN
 +
</div>
 +
</div>
  
 
+
<div class="mw-collapsible mw-collapsed">
 +
<div  class="headline-collapse" >
 
===Send Remotelock/Lockstate PIN ===
 
===Send Remotelock/Lockstate PIN ===
 +
</div>
 +
<div class="mw-collapsible-content">
 
Trigger tab:
 
Trigger tab:
 
*Trigger Event = Check-in
 
*Trigger Event = Check-in
Line 651: Line 858:
 
*EMail Subject = Your access code (your text)
 
*EMail Subject = Your access code (your text)
 
*Email Text = Your text which includes the template variable  [BOOKINGINFOCODETEXT:LOCKSTATE_PIN]
 
*Email Text = Your text which includes the template variable  [BOOKINGINFOCODETEXT:LOCKSTATE_PIN]
 +
</div>
 +
</div>
  
 +
<div class="mw-collapsible mw-collapsed">
 +
<div  class="headline-collapse" >
 
===Send Email to all current guest ===
 
===Send Email to all current guest ===
 +
</div>
 +
<div class="mw-collapsible-content">
 
Trigger tab:
 
Trigger tab:
 
*Trigger Event = Check-in
 
*Trigger Event = Check-in
Line 669: Line 882:
  
 
It is assumed you use the Checkin/Checkout feature in the Dashboard, if not you can either manually add Checkin to your bookings (Booking info tab) or create an auto action to add the Booking Info Codes to the bookings.
 
It is assumed you use the Checkin/Checkout feature in the Dashboard, if not you can either manually add Checkin to your bookings (Booking info tab) or create an auto action to add the Booking Info Codes to the bookings.
 +
</div>
 +
</div>
  
 +
<div class="mw-collapsible mw-collapsed">
 +
<div  class="headline-collapse" >
 
===Send Email with a PDF attachment===
 
===Send Email with a PDF attachment===
 +
</div>
 +
<div class="mw-collapsible-content">
  
 
You can send Invoice or Booking Template attachments to your Guests.  
 
You can send Invoice or Booking Template attachments to your Guests.  
Line 696: Line 915:
  
 
Other files can not be attached. We recommend you use a link to a file you upload to your web site.
 
Other files can not be attached. We recommend you use a link to a file you upload to your web site.
 +
</div>
 +
</div>
  
 +
<div class="mw-collapsible mw-collapsed">
 +
<div  class="headline-collapse" >
 
===Add CHECKIN Booking info code to bookings ===
 
===Add CHECKIN Booking info code to bookings ===
 +
</div>
 +
<div class="mw-collapsible-content">
  
 
If you need to use the Booking info code CHECKIN/CHECKOUT for reporting/other auto actions, you can set the Booking info code rather than use the Current guest module in the dashboard.  
 
If you need to use the Booking info code CHECKIN/CHECKOUT for reporting/other auto actions, you can set the Booking info code rather than use the Current guest module in the dashboard.  
Line 712: Line 937:
 
*Booking Info Code = CHECKIN
 
*Booking Info Code = CHECKIN
 
*Booking Info Text = Auto Checkin
 
*Booking Info Text = Auto Checkin
 +
</div>
 +
</div>
  
 +
<div class="mw-collapsible mw-collapsed">
 +
<div  class="headline-collapse" >
 
===Add CHECKOUT Booking info code to bookings ===
 
===Add CHECKOUT Booking info code to bookings ===
 +
</div>
 +
<div class="mw-collapsible-content">
  
 
If you need to use the Booking info code CHECKIN/CHECKOUT for reporting/other auto actions, you can set the Booking info code rather than use the Current guest module in the dashboard.  
 
If you need to use the Booking info code CHECKIN/CHECKOUT for reporting/other auto actions, you can set the Booking info code rather than use the Current guest module in the dashboard.  
Line 728: Line 959:
 
*Booking Info Code = CHECKOUT
 
*Booking Info Code = CHECKOUT
 
*Booking Info Text = Auto Checkout
 
*Booking Info Text = Auto Checkout
 +
</div>
 +
</div>
  
 +
<div class="mw-collapsible mw-collapsed">
 +
<div  class="headline-collapse" >
 
===Use API/Webhook to write to the field 'Message'===
 
===Use API/Webhook to write to the field 'Message'===
 +
</div>
 +
<div class="mw-collapsible-content">
  
 
You can use a webhook in conjunction with the API JSON function '''setBooking''' to write to any field in the booking. First you have to configure access to the API:
 
You can use a webhook in conjunction with the API JSON function '''setBooking''' to write to any field in the booking. First you have to configure access to the API:
Line 763: Line 1,000:
 
::"message": "[MESSAGE] - Append this message"
 
::"message": "[MESSAGE] - Append this message"
 
:}
 
:}
 +
</div>
 +
</div>
  
 +
<div class="mw-collapsible mw-collapsed">
 +
<div  class="headline-collapse" >
 
===Use API/Webhook to write the value of the 'commission' field to a new invoice item===
 
===Use API/Webhook to write the value of the 'commission' field to a new invoice item===
 +
</div>
 +
<div class="mw-collapsible-content">
 
You can create a new invoice item that contains the price of the channel's commission as a negative value to subtract it from the room price. You use the API JSON function '''setBooking''' for this. First you need to configure access to the API:
 
You can create a new invoice item that contains the price of the channel's commission as a negative value to subtract it from the room price. You use the API JSON function '''setBooking''' for this. First you need to configure access to the API:
  
Line 808: Line 1,051:
 
::]
 
::]
 
:}
 
:}
 
 
 
</div>
 
</div>
 
</div>
 
</div>
 
== Troubleshooting ==
 
'''If Auto Actions do not send:'''
 
The list in the "Mail" tab of the booking will tell you why. 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 Allow Auto Actions ("Mails" tab of the booking)?
 
*Do all trigger events apply to the booking?
 
 
 
'''Auto Action is not editable'''
 
To have write access to an auto action an account needs to have write access to all properties to which the auto action applies. This might not be the case if you use sub accounts and the Auto Action is set to trigger for "All Properties".
 
 
'''You don't have permission to access control2.php on this server''' error message, when the save button is clicked
 
It is most likely something in your content triggering the firewall.
 
Try adding the content bit by bit until you find the item causing the problem.
 
Often it is a script or HTML item that appears to the firewall as a possible hacking attack.
 
It can also be something that looks innocent like a combination of numbers and words like "and" or "or" that hackers often use in sql injection attacks.
 
Once you find the item causing the problem, try rewording it.
 

Revision as of 07:40, 23 May 2020

Auto Actions
This page is about the menu  (SETTINGS) GUEST MANAGEMENT > AUTO ACTIONS and explains how to set up and use Auto Actions.

An Auto Action is an action which can be programmed to occur at a time relative to the time the booking was made, to the check in date or to the check out date. To use this function you need to set the system to use you own Email address for sending in SETTINGS->ACCOUNT->OUTGOING EMAIL.

The action can be a pre-canned email sent to the guest or to a fixed email address, 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 & Actions' tab of each booking where you manually can send the email trigger 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.

Confirmation messages will send automatically to the guest. You can customize them in SETTINGS ->GUEST MANAGEMENT->CONFIRMATION MESSAGES.

Email sending works per account.

If you have sub accounts and need an auto action to be used across multiple accounts/properties, then create the auto action at the Master Account Level and set Property = 'All visible in account' and ensure the Master account has access to the properties.

Auto sending:

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.


Contents

1 Trigger

Sets the criteria which have to be fulfilled to start the Auto Action.

"Booking Source" = "Direct" applies the Auto Actions only to bookings from your own web site, manually added bookings and bookings imported though the API (not the channel manager). If you want to apply and Auto Action only to manually added bookings add your username in the "Referrer" field.

"Trigger Time" defines when the action is allowed to start. Once it has started it is allowed to go for the "Time Window" period. When the "Time Window" period has elapsed the auto action stops.

Both "Trigger Time" and "Time Window" are relative to a "Trigger Event" i.e. check-in, check-out, time of booking.

2 Email

Go to Email to create or modify a prepared Email template. Templates can contain Template Variables to include information specific to the booking in the Email, for example the guests name or the arrival date.

  • To send Emails automatically you need to set up your outgoing Email address in SETTINGS -> ACCOUNT -> OUTGOING EMAIL.
  • To send Emails manually open a booking and go to the MAIL tab. Manual Emails will open in a window, you may send it as is or edit it before sending.

Some systems have a limit of about 2000 characters for this form of email generation. If the email will not open try reducing the amount of text.

If Auto Action Emails are send automatically they are send through your Email server. You should see this on your server. Whether you see it in your Sent box or not depends on your Email program.

If Auto Action Emails are sent manually via a link in the "Email Templates" list in the booking Beds24 will first try to send through your Email server. You should see this on your server. Whether you see it in your Sent box or not depends on your Email program.

If this does not work it will pop and send through your desktop. In this case you will see it in your Sent box.

2.1 Email Attachments

You can choose to attach an invoice or a booking template as a PDF file to emails sent by Auto Actions.

If you send Emails with pdf attachment (invoice, booking template) to Alias-Email addresses created by channels the channel might block the attachment so it is not delivered to the guest. Ask your channel about their policy regarding this.

Other files can not be attached. We recommend you use a link to a file you upload to your web site.

3 SMS

You can automatically send SMS messages. Please note that a fee per SMS message applies if this function is activated.

The SMS will send in the language of the account, not the language of the booking. Read Example 17 for a way to control the language of the SMS.

4 Booking

Go to the tab 'Booking' to set up an auto action which modifies something in the booking.

5 Booking Info

Set up auto actions which automatically add or remove info codes.

6 Invoice

Automatically add invoice items or pending payments.

Invoice changes are applied before the mail is sent.

7 API

Create auto actions which trigger HTTP POST notifications.

8 Webhook

Create auto actions which trigger a web hook when the trigger conditions are met.

9 Test

Test why an auto action did not trigger.

10 Troubleshooting

If Auto Actions do not send:
The list in the "Mail" tab of the booking will tell you why. 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 Allow Auto Actions ("Mails" tab of the booking)?
*Do all trigger events apply to the booking?


Auto Action is not editable
To have write access to an auto action an account needs to have write access to all properties to which the auto action applies. This might not be the case if you use sub accounts and the Auto Action is set to trigger for "All Properties". 
You don't have permission to access control2.php on this server error message, when the save button is clicked
It is most likely something in your content triggering the firewall.
Try adding the content bit by bit until you find the item causing the problem.
Often it is a script or HTML item that appears to the firewall as a possible hacking attack.
It can also be something that looks innocent like a combination of numbers and words like "and" or "or" that hackers often use in sql injection attacks.
Once you find the item causing the problem, try rewording it.


11 Examples

11.1 Automatically change the status of all "Request" bookings to "Cancelled" after three days

Trigger tab

  • Trigger Event = After Booking
  • Trigger Time = 3 days
  • Booking Status = Request

Booking tab:

  • Execution = One time only
  • Booking Status = Cancelled

11.2 Automatically change the status of all bookings which have been imported from Ical to "Request"

Trigger tab:

  • Trigger Event = After Booking
  • Trigger Time = Immediate
  • Booking Source = Ical Import (1, 2, 3)

Booking tab:

  • Execution = One time only
  • Booking Status = Request

Booking changes are applied before the mail is sent.

11.3 Automatically set a flag/colour for a booking coming from a certain channel

Trigger tab:

  • Trigger Event = After Booking
  • Trigger Time = Immediate
  • Booking Source = Booking.com (for example)

Booking tab:

  • Execution = One time only
  • Flag Text = The text you want to display
  • 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.

11.4 Automatically send an Email to the guest when the status of a booking changes to "Cancelled"

Trigger tab:

  • Trigger Event = Check-in
  • Trigger Time = -365
  • Trigger Window = 365
  • Booking Source = All (for example)
  • Booking Status = Cancelled

Message tab:

  • Trigger Action = Auto
  • Send Email = Guest

If you are using deposit collection make sure you set SETTINGS->PAYMENTS->PAYMENT COLLECTION "Non Payment Booking Status" = Request.

11.5 Automatically change the status of all upcoming direct bookings to "Cancelled" and send an Email to the guest

Trigger tab:

  • Trigger Event = Check-in
  • Trigger Time = -14 (for example to cancel the bookings for the next two weeks)
  • Trigger Window = 14
  • Booking Source = Direct
  • Booking Status = All Not Cancelled

Booking tab:

  • Booking Status = Cancelled

Message tab:

  • Trigger Action = Auto
  • Send Email = Guest

11.6 Automatically add a fee to all bookings from a channel

Trigger tab:

  • Trigger Event = After Booking
  • Trigger Time = Immediate
  • Booking Source = Expedia (for example)

Invoice tab:

  • Type = Amount
  • Description = Cleaning fee (for example)
  • Amount = 50 (for example - the amount of your cleaning fee)
  • per = Room
  • Period = one time
  • VAT = 19% (for example - enter the VAT amount if applicable)

The fee will be added the next time the auto actions run.

11.7 Add a pending payment

Trigger tab:

  • Trigger Event = After Booking or Before Check-in
  • Trigger Time = set the time you want to collect the payment
  • Booking Source =All (for example, you can also set different rules for different channels)

Booking Info tab:

  • Optional, add a booking info tab for information and reporting

Booking tab: Optional

  • Flag Text = Pending payment added (for example)
  • Flag Colour = select the colour as this will be visible in the Calendar/Bookings list

Invoice tab:

  • Payment Type = select on what the payment is calculated
  • Description = the text you will see in the "Charges and Payments" tab
  • Status = if you use the status function add the status you want to apply to the pending payment (optional)
  • Amount = enter the amount or percentage you want to collect
  • Payment Rule = use auto or manual - if you have set up payment rules in SETTINGS->GUEST MANAGEMENT->PAYMENT COLLECTION they will be available here
  • Payment Due = Set when the payment is due

11.8 Credit card is collected at time of booking and full payment is due 3 days prior to arrival.

Trigger tab:

  • Trigger Event = After Booking
  • Trigger Time = immediate
  • Booking Source =All (for example, you can also set different rules for different channels)

Invoice tab:

  • Payment Type = Percent of balance due
  • Description = the text you will see in the "Charges and Payments" tab (Payment Balance)
  • Status = if you use the status function add the status you want to apply to the pending payment (optional)
  • Amount = 100 (balance is full price so 100% of the balance)
  • Payment Rule = Auto
  • Payment Due = check in -3


Automatic collection is only available for customer who use Stripe.

11.9 Credit card is collected at time of booking and you want to 'Capture' a Security Deposit.

Trigger tab:

  • Trigger Event = After Booking
  • Trigger Time = immediate
  • Booking Source =All (for example, you can also set different rules for different channels)

Invoice tab:

  • Payment Type = Fixed amount
  • Description = Security Deposit (the text you will see in the "Charges and Payments" tab)
  • Status = if you use the status function add the status you want to apply to the pending payment (optional)
  • Amount = 100 (balance is full price so 100% of the balance)
  • Payment Rule = Security Deposit (Create a Payment Rule, see below)
  • Payment Due = check in


Automatic collection is only available for customer who use Stripe.

Create a Payment Rule to 'Capture' a payment only. Captured payments will only be valid for 7 days, then it will expire, if the booking is for a longer period, then you can create a second Capture, you will need to create another auto action for this.

Go to Settings > Payments > Payment Rules

Payment Rule :

  • Name = Enter your title - Security Deposit (for example)
  • Action = Auto

Payment Trigger :

  • Booking Status = select from the drop down list
  • Any Booking Info Code = optional
  • All Booking Info Codes = optional
  • Exclude Booking Info Code = optional (can exclude Virtual Credit cards, find the Booking info code in the booking)

Payment Action :

  • Capture = Yes/No - immediately charged (Capture=Yes), if you want to make sure that the amount is available for later capture (Capture=No)
  • Add info code on success = add a Booking Info item to the booking on success
  • Add info code on failure = add a Booking Info item to the booking on failure

11.10 Apply a flag when a payment was made

Also see Example : " Apply a flag when deposit was made prior to Check-in AND/OR Apply a flag when booking is fully paid".

Trigger tab:

  • Trigger Event = After Booking
  • Trigger Time = Immediate
  • Trigger Window = 365
  • Booking Source = All
  • Booking Status = All not cancelled
  • Invoice Balance = Any Payment made

Booking tab:

  • Execution = One time only
  • Flag Text = The text you want to display
  • Flag Colour - choose the flag colour

11.11 Apply a flag when a payment FAILS at Stripe

Trigger tab:

  • Trigger Event = After Booking
  • Trigger Time = Immediate
  • Trigger Window = 365
  • Booking Source = All
  • Booking Status = All but not cancelled
  • Booking Info Code = STRIPEFAIL

Booking tab:

  • Execution = One time only
  • Flag Text = Stripe Payment Failed
  • Flag Colour - choose the flag colour

11.12 Apply a flag to Booking.com bookings and auto report the Credit Card when a payment FAILS at Stripe

Go to Settings > Channel Manager > Preferences and set Auto report failed cards = Yes

Trigger tab:

  • Trigger Event = After Booking
  • Trigger Time = Immediate
  • Trigger Window = 365
  • Booking Source = All
  • Booking Status = All but not cancelled
  • Booking Info Code = BOOKINGCOMCARD

Booking tab:

  • Execution = One time only
  • Flag Text = Failed CC reported to Booking.com
  • Flag Colour - choose the flag colour

11.13 Apply an info code and and/or icon when a payment was made

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.

11.14 Apply a flag when a booking is cancelled

Trigger tab

  • Trigger Event = After Booking
  • Trigger Time = 1 Hour
  • Trigger Window = 365 days
  • Booking Status = Cancelled

Booking tab:

  • Execution = One time only
  • Booking Status = No Change
  • Flag text = (enter the text you require)
  • Flag Colour = Set as required

11.15 Send an message or SMS to Guest when booking made more than 10 days in advance

Trigger tab:

  • Trigger Event = Check-in
  • Trigger Time = -365 days
  • Trigger Window = 355 days
  • Booking Status = All not cancelled

Booking tab:

  • Execution = One time only
  • Booking Status = No Change

Message tab or SMS tab:

  • Update details as appropriate

11.16 Send an message or SMS to Guest when booking made more than 7 days in advance

Alternatively you an use Between Booking and Check in

Trigger tab:

  • Trigger Event = Booking (but not after check-in)
  • Trigger Time = Immediate
  • Trigger Window = 1 day

Between Booking and Check in = 7 to 999

  • Booking Status = All not cancelled

Booking tab:

  • Execution = One time only
  • Booking Status = No Change

Message tab or SMS tab:

  • Update details as appropriate

11.17 Send an message or SMS to Guest when booking made more last minute booking - 6 days or less

Trigger tab:

  • Trigger Event = Booking (but not after check-in)
  • Trigger Time = Immediate
  • Trigger Window = 1 day

Between Booking and Check in = 0 to 6

  • Booking Status = All not cancelled

Booking tab:

  • Execution = One time only
  • Booking Status = No Change

Message tab or SMS tab:

  • Update details as appropriate

11.18 Send an Email with a key code for a specific unit one day before check-in

Trigger tab:

  • Trigger Event = Check-in
  • Trigger Time = -1 day
  • Trigger Window = 1 day
  • Booking Status = All not cancelled
  • Unit = Select the number of the unit you want to send this message to. Note that the number represents the index of the unit not its name.

Booking tab:

  • Execution = One time only
  • Booking Status = No Change

Message tab:

  • Enter your text. If you are using the "Additional Information" function SETTINGS->PROPERTIES->ROOMS->SET UP "Unit Names" you can use template variables

Example: Your room is [UNITNAME]. Check-in from: [UNITNAME:1] . The key code is: [UNITNAME:2]

The template variables will only work if you have entered text in SETTINGS->PROPERTIES->ROOMS->SET UP "Unit Names". The context help for this setting will explain how to do this.

11.19 Send an Email to the guest when a payment is made

Trigger tab:

  • Trigger Event = After Booking
  • Trigger Time = Immediate
  • Trigger Window = 365 day
  • Booking Status = All not cancelled
  • Invoice Balance = Any Payment made OR Invoice Balance = Zero (payment in full)

Message tab:

  • Enter your text.

You can use Invoice Template variables showing the booking charges/payments.

11.20 Send an Email to guests from Channels

Trigger tab:

  • Trigger Event = After Booking
  • Trigger Time = Immediate
  • Trigger Window = 1 day
  • Booking Source = Channel Manager

Booking tab:

  • Execution = One time only
  • Booking Status = No Change

Message tab:

  • Send Email = Guest
  • Enter you text. If you are using the "Additional Information" function SETTINGS->PROPERTIES->ROOMS->SET UP "Unit Names" you can use template variables

Example: Your room is [UNITNAME]. Check-in from: [UNITNAME:1] . The key code is: [UNITNAME:2]

The template variables will only work if you have entered text in SETTINGS->PROPERTIES->ROOMS->SET UP "Unit Names". The context help for this setting will explain how to do this.

11.21 Automatically set a flag for a bookings from a channel which have breakfast included

Trigger tab:

  • Trigger Event = After Booking
  • Trigger Time = Immediate
  • Booking Source = Booking.com (for example)
  • Booking Field Contains - select "API Message" in the next field enter: meal_plan=Breakfast (or Extra Breakfast - use the text the channel uses)

Booking tab:

  • Execution = One time only
  • Flag Text = The text you want to display
  • 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.

11.22 Automatically send a message (Email or sms) to guests that have Checked-out 30 days or more

Trigger tab:

  • Trigger Event = After Check-out
  • Trigger Time = 30 days
  • Trigger Window = 365 days

Message or SMS tab: Enter the details you want to send.

Booking tab: (optional)

  • Execution = One time only
  • Flag Text = The text you want to display
  • Flag Colour - choose the flag colour

11.23 Automatically send a Request for payment to your guests for all bookings

Trigger tab:

  • Trigger Event = After Booking
  • Trigger Time = Immediate
  • Trigger Window = 1 day

Booking Source = ALL (or select the booking source/Channel)

Message tab:

Send Email : select the appropriate option

  • Edit Email Subject - enter the subject for your Guests
  • Edit Email Text :- enter the Email text you wish to send to your guests include template variable

[PAYLINK] this creates a payment link (HTML A tag) for the payment request for the amount in the booking deposit field if non zero, otherwise the outstanding balance. Check the template variables for other options.

Booking tab:

  • Execution = One time only
  • Flag Text = The text you want to display
  • 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.

11.24 Automatically send a Request for payment to your guests XX days before arrival

Trigger tab:

  • Trigger Event = Check-in
  • Trigger Time = -42
  • Trigger Window = 1 day

Booking Source = ALL (or select the booking source/Channel)

Message tab:

Send Email : select the appropriate option

  • Edit Email Subject - enter the subject for your Guests
  • Edit Email Text :- enter the Email text you wish to send to your guests include template variable

[PAYLINK] this creates a payment link (HTML A tag) for the payment request for the amount in the booking deposit field if non zero, otherwise the outstanding balance. Check the template variables for other options.

Booking tab:

  • Execution = One time only
  • Flag Text = The text you want to display
  • 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.

11.25 Automatically send a Request for payment to your guests XX days after booking

You allow your guests to make X number of payments for their booking.

You can not trigger the auto action multiple times, unless you manage this manually, therefore you need to create multiple auto actions, so if you allow 3 payments for their booking, then you will need 3 auto actions.

You will need to manually add a Booking Info Code to each booking that you have agreed to allow X payments.

Create Auto Action one Trigger tab:

  • Trigger Event = Booking (but not after check-in)
  • Trigger Time = +7 days
  • Trigger Window = 1 day
  • Booking Source = ALL (or select the booking source/Channel)
  • Invoice Balance = Not Zero
  • Any Booking Info Code = MULTIPLE (for example) this can be used if you only allow some guests to make multiple payments.

Message tab:

Send Email : select the appropriate option

  • Edit Email Subject - enter the subject for your Guests
  • Edit Email Text :- enter the Email text you wish to send to your guests include template variable

[PAYLINK] this creates a payment link (HTML A tag) for the payment request for the amount in the booking deposit field if non zero, otherwise the outstanding balance. Check the template variables for other options.

Booking tab:

  • Execution = One time only
  • Flag Text = The text you want to display
  • 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.

Create additional Auto Actions for each period you want to trigger

Create Auto Action 2 (and 3, 4, 5 - how may you need)

  • Trigger Time = +14 days (days you want to collect the payments)
  • Trigger Window = 1 day

Setup booking info code

Go to SETTINGS -> ACCOUNT -> PREFERENCES -> BOOKINGS -> Booking Info Code Values and enter MULTIPLE (or the value you want to use to trigger)

Update Booking to allow Multiple payments

  • Open the booking
    • Go to Booking Info Tab and from the drop down list
    • Select the value 'MULTIPLE' (or the value you want to use to trigger)

11.26 Apply a flag when deposit was made prior to Check-in

Trigger tab:

  • Trigger Event = Check-in
  • Trigger Time = -365 (for example : must be a negative value and the same as the value in Trigger window)
  • Trigger Window = 365
  • Booking Source = All
  • Booking Status = All but not cancelled
  • Invoice Balance = Any Payment made

Message tab:

  • Send Email : select appropriate option
  • Enter : Subject and Email content

Booking tab: (optional)

  • Execution = One time only
  • Flag Text = The text you want to display
  • Flag Colour - choose the flag colour

Booking info tab : (optional)

  • Booking Info Code : DEPOSITPAID (for example)
  • Booking Info Text : additional text if required.

Setting details with the Booking tab and Booking info tab allows you to trigger additional (follow on) Auto Actions and Reports.

11.27 Apply a flag when booking is fully paid

Trigger tab:

  • Trigger Event = After Booking
  • Trigger Time = Immediate
  • Trigger Window = 365
  • Booking Source = All
  • Booking Status = All not cancelled
  • Invoice Balance = ZERO

Booking tab:

  • Execution = One time only
  • Flag Text = The text you want to display
  • Flag Colour - choose the flag colour

11.28 Send Email in a the guests language to an internal Email address

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.

Trigger tab:

  • Booking Field Contains - select "Language" in the next field enter: the short code for the language this Auto Action is for.

Email tab:

  • Enter the message in the appropriate language under your default language.

11.29 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.

Trigger tab: Whatever you want

Booking tab: Whatever you want

SMS tab:

  • Phone Number = [GUESTMOBILE]
  • SMS Message = [IF=:[GUESTLANGUAGE]:fr:French_text|English_text]

11.30 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

11.31 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

11.32 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

Message 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]

11.33 Send Email to all current guest

Trigger tab:

  • Trigger Event = Check-in
  • Trigger Time = Immediate
  • Trigger Window = 14(the max number of days your guests can stay)
  • Booking Source = All
  • Booking Status = All but not cancelled
  • Group bookings = Trigger all on master
  • Any Booking Info Code = CHECKIN
  • Exclude Booking Info Code = CHECKOUT

Message tab:

  • Send Email = Guest
  • EMail Subject = Enter the appropriate details
  • Email Text = Your text which includes the details for your current guests.

It is assumed you use the Checkin/Checkout feature in the Dashboard, if not you can either manually add Checkin to your bookings (Booking info tab) or create an auto action to add the Booking Info Codes to the bookings.

11.34 Send Email with a PDF attachment

You can send Invoice or Booking Template attachments to your Guests.

Setup your Invoice or Booking Template, go to SETTINGS -> GUEST MANAGEMENT -> INVOICING or SETTINGS -> GUEST MANAGEMENT -> BOOKING TEMPLATES

Trigger tab:

  • Trigger Event = Checkout
  • Trigger Time = Immediate
  • Trigger Window = 1
  • Booking Source = All (or select the appropriate channel/Direct)
  • Booking Status = All but not cancelled
  • Group bookings = Trigger all on master
  • Any Booking Info Code = CHECKOUT

Message tab:

  • Send Email = Guest API/Smart Email (or one of the other options)
  • Attachment = Select an option from the drop down list.
  • EMail Subject = Enter the appropriate details
  • Email Text = Your text which includes the details for your current guests.

It is assumed you use the Checkin/Checkout feature in the Dashboard, if not you can either manually add Checkout to your bookings (Booking info tab) or create an auto action to add the Booking Info Codes to the bookings.

If you send Emails with pdf attachment (invoice, booking template) to Alias-Email addresses created by channels the channel might block the attachment so it is not delivered to the guest. Ask your channel about their policy regarding this.

Other files can not be attached. We recommend you use a link to a file you upload to your web site.

11.35 Add CHECKIN Booking info code to bookings

If you need to use the Booking info code CHECKIN/CHECKOUT for reporting/other auto actions, you can set the Booking info code rather than use the Current guest module in the dashboard.

Trigger tab:

  • Trigger Event = Check-in
  • Trigger Time = Immediate
  • Trigger Window = 1 day
  • Booking Source = All
  • Booking Status = All but not cancelled
  • Group bookings = Trigger all on master

Booking Info tab:

  • Booking Info Code = CHECKIN
  • Booking Info Text = Auto Checkin

11.36 Add CHECKOUT Booking info code to bookings

If you need to use the Booking info code CHECKIN/CHECKOUT for reporting/other auto actions, you can set the Booking info code rather than use the Current guest module in the dashboard.

Trigger tab:

  • Trigger Event = Check-out
  • Trigger Time = Immediate
  • Trigger Window = 1 day
  • Booking Source = All
  • Booking Status = All but not cancelled
  • Group bookings = Trigger all on master

Booking Info tab:

  • Booking Info Code = CHECKOUT
  • Booking Info Text = Auto Checkout

11.37 Use API/Webhook to write to the field 'Message'

You can use a webhook in conjunction with the API JSON function setBooking to write to any field in the booking. First you have to configure access to the API:

You need two keys to use our API JSON functions - one for the API itself and one for the property. The keys have to consist of 16 characters of your choosing.
API key:
  • SETTINGS -> ACCOUNT -> ACCOUNT->ACCESS "API Key 1"
  • API Key = my_very_secret_api_key
  • API Key Access = allow any IP
  • IP Whitelist = [leave empty]
  • Allow Writes = Yes
  • Property Access = Owned by this account only
  • Property key:
  • Settings > Properties > Access > propKey = secret_key_for_prop_XXXXXX

Set the triggers you need, for example:

Booking Field Contains: Message = XXX

Set the webhook like this:

  • URL = https://api.beds24.com/json/setBooking
  • Custom Header = [leave empty]

Body Data:

{
"authentication":
{
"apiKey": "my_very_secret_api_key",
"propKey": "secret_key_for_prop_XXXXXX"
},
"bookId": "[BOOKID]",
"message": "[MESSAGE] - Append this message"
}

11.38 Use API/Webhook to write the value of the 'commission' field to a new invoice item

You can create a new invoice item that contains the price of the channel's commission as a negative value to subtract it from the room price. You use the API JSON function setBooking for this. First you need to configure access to the API:

You need two keys to use our API JSON functions - one for the API itself and one for the property. The keys have to consist of 16 characters of your choosing.
API key:

  • SETTINGS -> ACCOUNT -> ACCOUNT->ACCESS "API Key 1"
  • API Key = my_very_secret_api_key
  • API Key Access = allow any IP
  • IP Whitelist = [leave empty]
  • Allow Writes = Yes
  • Property Access = Owned by this account only
  • Property key:
  • Settings > Properties > Access > propKey = secret_key_for_prop_XXXXXX

Set the triggers you need, for example:

Booking Source = Booking.com

Set the webhook like this:

  • URL = https://api.beds24.com/json/setBooking
  • Custom Header = [leave empty]
  • Body Data =
{
"authentication":
{
"apiKey": "my_very_secret_api_key",
"propKey": "secret_key_for_prop_XXXXXX"
},
"bookId": "[BOOKID]",
"invoice":
[
{
"description": "Booking.com Commission",
"status": "",
"qty": "1",
"price": "-[COMMISSIONNUM]",
"vatRate": "7.00",
"type": "0",
"invoiceeId": ""
}
]
}