Skip to content
Julius Dela Peña

Selected WorkProject 03CRM / Operations

GoHighLevel Appointment Lifecycle

Appointment status automation for booking, reminder, cancellation and no-show workflows.

An operational workflow built in GoHighLevel to manage the appointment lifecycle, including confirmations, reminders, cancellations, no-shows and follow-up logic.

GoHighLevel workflow branching appointment status and pipeline triggers into cancellation, no-show and follow-up pathsOpen the full GoHighLevel Appointment Lifecycle workflow capture (opens in a new tab)
Appointment status workflow in the GoHighLevel builder — triggers and branches. Select to open the full capture.

01Context

01Project type
Automation project
02Tools
  • GoHighLevel

02Problem

Appointment-based pipelines depend on what happens around the booking. Confirmations, reminders and responses to cancelled or missed appointments were easy to miss when status changes were handled by hand.

03Appointment Lifecycle

Every status change has a defined next step.

The workflows follow an appointment from booking to the outcome. Each change of status moves the contact to the matching pipeline stage and sends the right message.

Cancellations and no-shows leave the main path into a recovery sequence, which ends as soon as the contact rebooks.

  1. 01Booked

    Moved to the booked pipeline stage.

  2. 02Confirmed

    Email and SMS confirmation.

    • Cancelled

      Tags and stage updated.

    • Follow-up sequence

      Email, wait, then a rebooking check.

  3. 03Reminded

    Reminders 24 hours and 2 hours before.

    • No-show

      Tags and stage updated.

    • Follow-up sequence

      Email, wait, then a rebooking check.

  4. 04Showed

    Tags and pipeline stage updated.

Contacts who rebook exit the recovery path, so nobody keeps receiving follow-up after booking again.

03Workflow Logic

One workflow, five triggers, separate paths.

The status workflow listens for five triggers — changes to appointment status and to pipeline stage. A condition routes each one to its own branch.

03 stages09 steps

  1. 3 steps

    01Trigger

    1. Appointment status changes
    2. Pipeline stage changes
    3. Five triggers in one workflow
  2. 3 steps

    02Logic

    1. Condition routes each trigger to its branch
    2. Cancelled, no-show or showed
    3. Wait, then check for a rebooking
  3. Output

    03Outcome

    1. Tags and pipeline stage updated
    2. Follow-up email sent
    3. Rebooked contacts exit the workflow

04Build highlights

A GoHighLevel workflow set that reacts to every appointment status and pipeline change, keeping contact tags, pipeline stages and follow-up messages in step.

04The Workflow

The full status workflow.

Each branch updates the contact’s tags and pipeline stage, then sends the appropriate email. Recovery paths wait, check whether the contact has rebooked, and only continue the follow-up if they have not.

GoHighLevel workflow branching appointment status and pipeline triggers into cancellation, no-show and follow-up pathsOpen full-size image: GoHighLevel workflow branching appointment status and pipeline triggers into cancellation, no-show and follow-up paths (opens in a new tab)
Appointment status workflow: five triggers, a routing condition and separate recovery branches.

04What It Automates

Across the appointment lifecycle.

  • Booking

    Confirmation and reminders

    Moves booked contacts to the right stage, sends confirmations and delivers timed reminders before the appointment.

  • Status

    Cancellations and no-shows

    Reacts to cancelled and no-show appointments with tag and pipeline updates and a follow-up sequence.

  • Follow-up

    Re-engagement

    Delayed follow-ups with checks in between, so contacts who rebook stop receiving recovery messages.

  • Nurture

    Lead nurture and reactivation

    Multi-touch email and SMS sequences for leads who have not booked, and longer-term reactivation for inactive contacts.

04Related Workflows

Two companion workflows.

GoHighLevel workflow branching on appointment and pipeline triggers into confirmation and reminder stepsOpen full-size image: GoHighLevel workflow branching on appointment and pipeline triggers into confirmation and reminder steps (opens in a new tab)
Appointment booked — Stage updates, confirmation and timed reminders.
GoHighLevel workflow sending email and SMS confirmations followed by timed remindersOpen full-size image: GoHighLevel workflow sending email and SMS confirmations followed by timed reminders (opens in a new tab)
Booking confirmation — Email and SMS confirmations, then 24-hour and 2-hour reminders.

04Platform

Built entirely in GoHighLevel.

  • Workflows

    Workflow builder

    Triggers, conditions, waits and go-to steps.

  • Pipelines

    Pipeline stages

    Each appointment status reflected in the pipeline.

  • Tags

    Contact tags

    Tracks status and gates follow-up.

  • Messaging

    Email and SMS

    Confirmations, reminders and follow-up messages.

05Result

Consistent follow-up for every appointment status, reminders on schedule, and recovery sequences that stop as soon as a contact rebooks.

Operational value

Follow-up
Consistent
Every appointment status change triggers the matching tags, stage and messages.
Reminders
Automated
Confirmations and reminders go out by email and SMS on schedule.
Cancellations & no-shows
Followed up
A re-engagement sequence runs and stops once the contact rebooks.

06My role

What I was responsible for.

  1. Workflow Design
  2. Trigger & Branch Logic
  3. Pipeline & Tag Structure
  4. Follow-up Sequences
Tools
  • GoHighLevel

Contact

Have a workflow, dashboard or CRM that needs fixing? Let’s talk.

Available for new projects

Tell me about the operation, the systems involved and where the work gets stuck. A short call is usually enough to see whether I can help.

Book a call (opens in a new tab)Email me