Automations
Automations that start when a guest does something
Automations, also called journeys, start when a guest joins your WiFi, buys, books or checks out, then wait for their next move and send emails, texts or offers. Editing one live moves nobody in it.
What can start an automation?
Things guests do and dates that matter to them, 36 triggers in all. Retail ones (product views, checkouts started, price drops, back in stock) are a pilot. Each takes a segment-style entry filter, and an automation can have several.
- Joins the WiFi
- Makes a purchase, with an optional venue and minimum spend
- Books, completes, cancels or misses a booking
- Books, checks in to or checks out of a stay
- Redeems an offer, or is issued a voucher
- Submits a form or a survey
- Has a tag added or removed, or a property changed
- Joins or leaves a segment
- Birthday, anniversary, sign-up anniversary or a set date
- An API call
- Before launch, an estimate of how many guests a week would have started it, from the last 30 days, for triggers that read guest activity
Purple Engage screens shown with sample data for a fictional pub group. Every name and figure is invented.
What can an automation wait for?
The guest's next move, for up to 90 days, with a path for "did it" and one for "ran out of time". Only the guest's own actions count, not machine opens or staff opt-ins. Exit goals stop it early.
- Wait for a visit, redemption, purchase, booking, open or click
- Waits of up to 90 days, with a path for each outcome
- Up to 10 exit goals, such as stopping when a guest redeems or books
What can each step of an automation do?
Send messages, change tags or properties, issue offers, alert your team or post guest details to your own system. The opt-in check on every message step cannot be removed, and an email opt-in never counts as consent to text.
- Send an email
- Send a text
- Add or remove tags
- Update a property
- Issue an offer, reusing a live code rather than doubling it
- Alert 1 to 20 team members in the app, and by email if you choose
- Post up to 30 fields to your own endpoint through a signed webhook
Can I test one path against another?
Yes. Split guests down two to five paths in shares you set. A path's rate shows once 100 people take it and 10 meet the goal; a leader is called only when the 95% range on its lead clears zero.
- Splits into two to five paths, with each guest always on the same one
- A path wired to the end acts as a held-back group
Purple Engage screens shown with sample data for a fictional pub group. Every name and figure is invented.
What happens if I edit a running automation?
Every activation is a numbered version. Guests already inside finish on the version they joined, including the email they were due, and new guests get the new one. If publishing fails, the live version stays live.
- A review screen before you publish: what changed, how many people sit at each changed step and which live automations it could set off
- Loop protection: automations that could start each other are flagged, and one guest enters from an activity at most 10 times in 24 hours
Questions
How long can an automation wait?
Up to 90 days for each wait, and an automation can hold up to 10 waits.
Will importing old orders send "thanks for your visit" emails?
No. Activity older than 24 hours, or a connector's history load, never starts an automation, so connecting a POS with two years of orders does not send two years of thank-you emails. The history still shows on each guest's timeline.
Set up your first automation
The free plan is listed at 500 credits a month, with unlimited* contacts and no card needed.