Booking event triggers
booking.created, booking.cancelled, booking.no_show, booking.completed — each fires a flow you can branch on.
Every booking, no-show, and completed appointment fires a flow. Skip the manual texting. Skip the calendar copy-paste. Skip the review-request emails.
Salons, gyms, mobile detailers, tutors, and similar service operators who want booking events to drive customer communications automatically.
A single operations layer keeps customer experience and back-office workflows aligned.
booking.created, booking.cancelled, booking.no_show, booking.completed — each fires a flow you can branch on.
Branch on customer history, service type, or time-of-day. Send VIPs a different message than first-timers.
Native integrations with Google Calendar, Outlook, Cal.com, Twilio, WhatsApp, and Mailchimp.
When a booking is marked no_show, fire a flow that charges the late fee, sends an SMS, and offers a rebook link.
Sequence operations in a way teams can follow under real volume.
Booking is created in Vertex.
Flow fires: Google Calendar event + SMS confirmation.
24 hours before: reminder SMS, branching on reply.
After completion: review request + loyalty points award.
Customers who get a 24-hour SMS confirmation are 50-70% less likely to no-show. Many service businesses see dropoff from double-digits to single digits within a month.
Yes. On booking.no_show, route through a Vertex action (refund a partial deposit) or a Stripe charge step in the canvas.
Google Calendar, Outlook, and Cal.com are native. Apple Calendar via iCal feeds. The booking trigger fires regardless of which calendar tool you use.
Start with a prefilled signup flow and compare additional buyer guides before rollout.