Auto lead capture, follow-ups and operations on autopilot.
A visual builder for the work nobody should be doing by hand. Lead arrives, assign and acknowledge. Booking confirmed, send the WhatsApp, issue the supplier voucher, create the ops task, schedule the balance reminder — every time, without anyone remembering.
- 410
- Ops hours saved monthly
- 12
- Steps run per booking
- −87%
- Manual errors
Twelve steps, done by hand or not at all.
By hand
- A confirmed booking triggers a checklist someone has to remember to work.
- Vouchers get issued late because ops was busy with a different departure.
- The balance reminder goes out when the traveller has already gone quiet.
- When somebody is on leave, their bookings quietly stop progressing.
On autopilot
- Confirmation fires the WhatsApp, the voucher, the ops task and the reminder.
- Branching, delays and conditions handle the cases that are not standard.
- Escalation catches a step that has not completed, before the traveller notices.
- Leave, illness and turnover stop being operational risk.
Everything Workflow Automation does, in one place.
Visual trigger-action builder
Compose flows on a canvas with branching, delays, conditions and parallel paths. No code, and no waiting on us.
Triggers from every module
Booking confirmed, payment received, deposit overdue, allotment release approaching, document missing, review received.
Actions across the platform
Send a message, create a task, update a record, notify a supplier, call a webhook, generate a document, move a deal stage.
Test before you ship
Dry-run a flow against a real past booking and see exactly what would have happened, before it touches a live traveller.
Full execution log
Every run recorded with inputs, outputs, timing and errors — so when something misfires you can see precisely why.
Guardrails
Rate limits, quiet hours and approval steps stop an automation from messaging two thousand travellers at 3am.
Four steps, and then it keeps doing them.
Choose a trigger
Start from an event, a schedule, or a change in any field across the platform.
Add conditions
Branch by destination, value, market, agent or anything else on the record.
Define actions
Chain the messages, tasks, updates and webhooks that should follow, in order or in parallel.
Test, ship, watch
Dry-run against history, publish, then monitor the execution log and adjust.
“Twelve things used to happen after a booking confirmed, and on a busy week maybe nine of them did. Now all twelve happen, and my ops lead is doing supplier negotiation instead of chasing a checklist.”
- Webhooks
- REST API
- Zapier
- Slack
- Google Sheets
- Every TouringTour module
Asked before every demo.
Do we need a developer to build automations?
No. The builder is visual and most flows are assembled by operations staff. Webhooks and the API are there when you want to go further.
What happens if an automation fails halfway?
The run stops at the failed step, records the error, retries where it is safe to do so, and alerts the flow owner. Completed steps are never silently repeated.
Can we stop an automation that is already running?
Yes. Any flow can be paused instantly, and scheduled runs can be cancelled in bulk before they fire.
Map one of your workflows.
Describe what happens after a booking confirms and we will build that flow on the canvas during the call.
No card · no rebuild of your data · onboarding in 14 days