Documentation /Workflow
Every trigger
A trigger is the thing that happened. Some carry a booking with them, and so know the customer; some carry only the event.
Bookings
These fire once per booking, so the message can be addressed to a person.
| Trigger | Fires when | Filters |
|---|---|---|
| Booking is created | A booking is made, on the site or by hand | Booking status, Payment status |
| Booking status changes | Its status moves | New status, Payment status |
| Attendee is checked in | A code is admitted at the door | — |
| Payment is received | Money is recorded against the order | Payment type, Payment method |
| Booking is refunded | Money goes back | Refund type |
| Event starts — for each booking | Planned, relative to the start | Payment status |
| Event ends — for each booking | Planned, relative to the end | Payment status |
| Event date is canceled — for each booking | A date is called off | — |
| Event date is reopened — for each booking | A cancelled date comes back | — |
Events
These fire once per event or date, not per person. Use them for your own team: there is no customer to address.
| Trigger | Fires when | Filters |
|---|---|---|
| Event starts | Planned, relative to the start | Event status |
| Event ends | Planned, relative to the end | — |
| Event is created | A new event is saved | — |
| Event date is canceled | A date is called off | — |
| Event date is reopened | It comes back | — |
Customers
| Trigger | Fires when |
|---|---|
| Customer is created | Somebody books for the first time |
| A customer gets a sign-in account | Pro and Elite. A WordPress account is made for a customer, with a new password |
The second one is the only moment the new password can be sent: it is never stored anywhere it could be read again. See The customer panel.
Waiting list
A paid feature.
| Trigger | Fires when |
|---|---|
| A waiting list place is offered | A place comes free and is offered to the front of the queue |
This one matters: the offer is useless unless it reaches the person, and this is what sends it, carrying the claim link and its expiry.
Filters
Where a trigger has filters, they narrow it without a second workflow. "Payment is received" filtered to Cash tells the desk about cash and stays quiet about card payments.
Payment status asks how much of the booking has been paid: Not paid, Partially paid, Paid, Partially refunded or Refunded. "Booking is created, 5 days after, Not paid" is a reminder for a bank transfer that has not arrived. "Event starts — for each booking, 14 days before, Not paid" is the same reminder against a deadline before the event. Partially paid finds the bookings that paid a deposit and still owe the rest.
A delayed message checks its filters again when it comes due, against the booking as it is then. Somebody who pays on day three does not get the day-five reminder, and a reminder for each booking is not sent to a booking cancelled in the meantime. Either one shows in the queue as canceled, with the reason.