How Workflows Handle Appointment Changes

Appointment-based workflows react when a booking is made, canceled, or moved. Understanding these behaviors helps you build reminder sequences that behave correctly.

Multiple bookings

A contact can book several appointments, so appointment triggers always allow a new entry for each booking, even if the person is still in the workflow from an earlier one and even if Allow Re-entry is off.

Canceled appointments

An appointment counts as canceled when its status changes from New, Confirmed, or Showed to Canceled, Invalid, or No Show.

Result: the contact is pulled out of the workflow and no further steps run. For example, if someone waiting five days before a reminder cancels, the reminder never sends.

Rescheduled appointments

An appointment counts as rescheduled when its start or end time changes.

Result: the contact is removed from the current run. If another workflow (or the same one) uses an Appointment Status trigger set to Rescheduled, and the new booking matches its filters such as calendar and assigned user, the contact enters it again and gets a fresh sequence based on the new time.

To restart reminders after a reschedule, build a workflow with the Rescheduled status trigger and allow re-entry.

Recurring appointments

Recurring series do not start workflows through the Customer Booked Appointment trigger. Use other triggers or an approach based on status changes if you need automation for repeating bookings.

Design tips

• Keep reminder workflows on the Appointment Status trigger so you can respond to specific changes.
• Match filters (calendar, user) between booking and rescheduling workflows.
• Use Wait Until steps tied to the appointment time rather than fixed delays.
• Test by booking, rescheduling, and canceling with a test contact.

Good to know: Cancellations remove contacts automatically, so you don't need a separate cleanup step.