A status change starts it, not the clock
The Appointment Status trigger fires when an appointment is scheduled or when its status changes. It doesn't fire because the start time came and went. If nobody marks the appointment No-show, the follow-up never begins.
So the first question isn't what to send. It's who marks no-shows in your account, and how. A team member might set the status by hand, or another system might set it through the API. We haven't found a source showing HighLevel sets No-show by itself from meeting attendance, so plan as if something has to set it.
An appointment time passing is not a No-show. The status change is.
Building the trigger
The filters do most of the work. Get them right and the workflow enrolls exactly the bookings you mean.
- Go to Automation > Workflows and create a new workflow.
- Click Add New Trigger and choose Appointment Status.
- Filter the status for No-show.
- Narrow it with In Calendar for one calendar, or In Calendar Group for a set of them.
- Set Modified By to match whoever actually changes the status: a user, the customer, the API or a workflow.
- Save the trigger, then mark a test appointment No-show and confirm it enrolls before you publish.
No-show and Cancelled are different statuses
HighLevel lists Cancelled and No-show as separate options in the trigger. Pick both and your recovery messages reach people who cancelled on purpose, which is rarely the message you wrote.
We leave cancellations out unless a cancellation follow-up is part of the plan. If it is, it gets its own copy, so each message says something that fits what happened.
What the recovery sends
Our recovery is three steps with a Wait in front of each: a text, then an email, then a manual task assigned to a person. The task is its own action, separate from the messages, so it lands in someone's task list instead of going out as one more automated message.
The timing is a choice, and HighLevel doesn't set one. We use a short wait before the text and a longer one before the email, then give the task to someone who will actually make the call. Pick delays your team can keep up with.
We build this as its own workflow, not as extra steps in the reminder workflow. Reminders run before the appointment. Recovery starts only after a status change. Kept apart, each one can be tested on its own.
Rather have it set up for you?
We'll build the trigger, the recovery messages and the follow-up task and test it by marking a test booking No-show, and it starts with a 30-minute 1:1 with Rob.
When the follow-up doesn't fire
If a no-show didn't enroll, the trigger filters didn't match. Work back through them against the appointment that was missed.
- Was the status actually set to No-show, or did the appointment just pass?
- Is the appointment on the calendar, or in the calendar group, that the trigger names?
- Does Modified By match who changed the status? A filter set to user won't catch a change made by the API.
- Was the workflow saved and published after the trigger was added?