How workflows work
A workflow automates a multi-step guest journey: started by an event, branched by what the guest does, and measured end to end.
An event starts it.
A workflow fires off something that actually happened, not a date in a calendar someone has to remember.
It waits, then splits.
Steps wait so messages land at sensible moments, then the journey branches on what the guest does.
You see the drop-off.
Step-by-step metrics show where guests convert and where they leave, so the journey can be tightened.
When you'd use it
Read this first to see how a journey is triggered, shaped and measured before you build one.
How it behaves
A workflow starts automatically when something happens, sends emails as part of the sequence, and waits between steps so messages arrive at sensible moments. It branches on what the guest does, tags guests along the way, and can add loyalty points to an account.
Because it lives on the same platform as bookings, Wi-Fi, loyalty and reviews, a workflow fires off a real event, not a date in a calendar you have to remember. Build the journey once and it works in the background, evergreen, doing the heavy lifting so the team can focus on service.
It runs as a visual, drag-and-drop flow the venue can build, pause and edit itself, with step-by-step metrics showing where guests convert or drop out, and an AI read that explains a flow in plain English.
Configuration and options
- Trigger
- A real event that starts the journey.
- Steps
- Emails, waits, branches, tags and loyalty points.
- Visual builder
- A drag-and-drop canvas the venue owns.
- Metrics
- Step-by-step conversion, plus an AI explanation.
Good to know
A workflow only messages guests opted in to the relevant channel.
A win-back can watch for a rebooking and exit the moment it happens, so you never nudge someone to do a thing they have already done.
Sending SMS and inbox handoff from a workflow are rolling out; email send is available today.