Auto Actions: Difference between revisions
Jump to navigation
Jump to search
| Line 181: | Line 181: | ||
=== Booking Info === | === Booking Info === | ||
Set up auto actions which automatically add or remove info codes. This is good practice for reporting and also to trigger/exclude bookings from other auto actions. | Set up auto actions which automatically add or remove info codes. This is good practice for reporting and also to trigger/exclude bookings from other auto actions. | ||
Booking info codes can be used to 'sequence' your auto actions. | |||
For example, you have an auto action that sends a message to the guest, but only after another action has already triggered. | |||
Consider the auto action to add a pending payment to a booking for the Security deposit authorisation, this should only be triggered when the Booking info code = STRIPEPAYEMNT or CARDTOSTRIPE, both confirm the guest credit card is in the booking. | |||
=== Invoice === | === Invoice === | ||