Skip to content
Julius Dela Peña

Selected WorkProject 03CRM / Operations

GoHighLevelAppointmentLifecycle.

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

03Project
of 15

Project overview
GoHighLevel workflow branching on appointment and pipeline triggers into confirmation and reminder stepsOpen the full Appointment booked (opens in a new tab)
02Appointment booked
GoHighLevel workflow sending email and SMS confirmations followed by timed remindersOpen the full Booking confirmation (opens in a new tab)
03Booking confirmation
GoHighLevel workflow branching appointment status and pipeline triggers into cancellation, no-show and follow-up pathsOpen the full GoHighLevel Appointment Lifecycle (opens in a new tab)
01Status workflow
Context
Appointment-based pipelines in GoHighLevel
Domain
CRM automation
Scope
Booking through follow-up
Status
Workflows built in GoHighLevel

01The Challenge

What happens around every booking.

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.

The goal

Give every appointment status change its next step, automatically.

GoHighLevel workflow branching appointment status and pipeline triggers into cancellation, no-show and follow-up pathsOpen the full Status workflow · GoHighLevel capture (opens in a new tab)

The status workflow in the GoHighLevel builder: five triggers, one routing condition and separate recovery branches.

02The Workflow

One workflow. Five triggers. Separate paths.

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

Workflow spec

Trigger
Appointment status or pipeline stage changes
Routing
One condition sends each trigger to its branch
Output
Tags, pipeline stage and messages updated

03How It Works

From booked to showed — or recovered.

The appointment’s main path, step by step.

  1. Booked

    Moved to the booked pipeline stage.

    Pipeline

  2. Confirmed

    Email and SMS confirmation.

    Email + SMS

  3. Reminded

    Reminders 24 hours and 2 hours before.

    Timed

  4. Showed

    Tags and pipeline stage updated.

    Status

Companion workflows

04Architecture

Every status change has a defined next step.

Five triggers in one workflow, routed by condition into the main path or a recovery path.

  1. 01Trigger

    • TriggerAppointment status changes
    • TriggerPipeline stage changes

  2. 02Route

    • RulesCondition routes each trigger

  3. 03Main path

    • Pipeline stageBooked
    • Email + SMSConfirmed
    • 24h and 2h beforeReminded
    • Tags + stageShowed

  4. 04Recovery

    • Tags + stageCancelled
      Tags + stageNo-show
    • Email, wait, rebooking checkFollow-up sequence
    • OutcomeRebooked contacts exit
  • Workflow step

Rules route every trigger. Cancellations and no-shows leave the main path for a recovery sequence that ends as soon as the contact rebooks.

05Validation & Controls

Nobody is followed up after they rebook.

Recovery waits, checks for a rebooking, and only then continues.

Implementation statusBuilt in GoHighLevel

  • Confirmation and remindersBuilt
  • Cancellations and no-showsBuilt
  • Re-engagement with rebooking checkBuilt
  • Lead nurture and reactivationBuilt

Workflow checks

Routing
A condition sends each of the five triggers down its own branch.
Waits
Recovery branches wait before following up.
Rebooking
Contacts who rebook exit the recovery path, so nobody keeps receiving follow-up.
Tags
Contact tags record each status and gate the follow-up.

06The Stack

Built entirely in GoHighLevel.

Only GoHighLevel’s own features are used.

  • Workflow builder

    Triggers, conditions, waits and go-to steps

  • Pipeline stages

    Each appointment status reflected in the pipeline

  • Contact tags

    Tracks status and gates follow-up

  • Email and SMS

    Confirmations, reminders and follow-up messages

07The Outcome

What the workflows do.

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

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

My role

  • Workflow Design
  • Trigger & Branch Logic
  • Pipeline & Tag Structure
  • Follow-up Sequences

Delivered capability

  • Moves every appointment to the matching pipeline stage
  • Sends confirmations and timed reminders by email and SMS
  • Follows up cancellations and no-shows with a recovery sequence
  • Stops recovery as soon as a contact rebooks

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