Builds That Work Get the Daily Build
HighLevel Booking Any local business

Day-before YES or NO confirmation text in its own workflow: confirms, cancels or hands the reply to you

Source-checked YouTube

A trigger-less workflow the reminder sequence drops people into 24 hours before. It asks for a YES or NO, sorts the reply with keyword lists, confirms or cancels the appointment and moves the deal, and sends anything else to the owner.

Source: Aaron Delezenski (ClickLaunch), YouTube, 2026-10-15

1What it does

A trigger-less workflow the reminder sequence drops people into 24 hours before. It asks for a YES or NO, sorts the reply with keyword lists, confirms or cancels the appointment and moves the deal, and sends anything else to the owner.

2Who it is for

Industry
Any local business
Platform
HighLevel
Category
Booking
Tools used
HighLevel WorkflowsWait for replyIf/ElseOpportunitiesInternal notification

3How it works

Every step, in order, is in Workflow at a glance, pinned on the right as you scroll.

Workflow at a glanceHighLevel workflow
  1. 01 Trigger

    No trigger. The main reminder workflow adds the contact 24 hours before the appointment with Add to Workflow and pass input trigger parameters on.

  2. 02 Action

    Send the SMS: 'Hi {{contact.first_name}}, I want to remind you about your appointment tomorrow at {{appointment.only_start_time}} {{appointment.timezone}}. Please reply with a YES or NO if you will be attending tomorrow, so I can best serve you!'

  3. 03 Action + wait

    Wait for a reply to that SMS, with a 1-day timeout. No reply means the contact exits.

  4. 04 Action

    If/Else on the reply message, 'is any of' a YES list or a NO list. Anything else goes to Other.

  5. 05 Action + wait

    YES: add the tags 'appt confirmed' and 'day before confirmed', push the owner with the reply, wait 1.5 minutes (8 AM to 9 PM only), text a thank-you, set the appointment status to confirmed.

  6. 06 Action + wait

    NO: push the owner '{{contact.name}} - NO to appt' with a call-them-to-find-out-why note, wait 1.5 minutes (8 AM to 9 PM only), then text 'Can I ask why you won't be attending your appointment?'

  7. 07 Action + wait

    NO, continued: wait 5 minutes, set the appointment status to cancelled, and move the opportunity to Canceled (or create it there).

  8. 08 Action

    Other: push the owner '{{contact.name}} - 24hr Confirm Reply' with the reply text so a person answers.

Trigger
No trigger. The main reminder workflow adds the contact 24 hours before the appointment with Add to Workflow and pass input trigger parameters on.
AI step
None. Keyword lists replace the HighLevel intent check on purpose.

Every message, in order

Follow the lead, owner and system steps. Select a message to read the full copy. Spacing is not proportional to time.

YES keywords notify the owner and send a thank-you before setting confirmed status.

Default scenario: Replies YES. Expand a step to read its full copy.

On entry from the main workflow · lead · SMS - Day Before Confirmation
Hi {{contact.first_name}}, I want to remind you about your appointment tomorrow at {{appointment.only_start_time}} {{appointment.timezone}}. ➡️ Please reply with a 'YES' or 'NO' if you will be attending tomorrow, so I can best serve you! Thanks, {{appointment.user.first_name}}
Up to 1 day · system · Wait for reply or 1 day
Wait for a reply to the confirmation SMS. The timeout branch is empty: no further messages.
On reply · system · yes
Case-insensitive 'is any of'. YES: yes, yea, yeah, ya, yep, yup, y, sure, sure will, confirmed, 👍, ✅. NO: no, nope, nah, n, can't, cant, cancel, 👎. Anything else goes to Other.
On YES reply, before the owner push · system · Add Tag 'appt confirmed' 'day before confirmed'
Add tags 'appt confirmed' and 'day before confirmed'.
On reply · owner · App Push Notification - YES

Subject: {{contact.name}} Confirmed Appointment!

Confirmed they will be attending their appointment. 😁 Their reply was: {{message.body}}
1.5 minutes, 8 AM to 9 PM, all days · system · Wait 1.5 mins
The reply SMS waits for this sending window.
After the 1.5-minute wait · lead · SMS
Thank you {{contact.first_name}} for confirming your appointment, talk to you soon :-) {{appointment.user.first_name}}
After the reply SMS · system · Update appointment status - Confirmed
Set appointment status confirmed.

Message copy from Aaron Delezenski's HighLevel export. Contact details removed.

4How it went

Unknown. The source shows the build but does not report results.

Only what the source reports. The source did not report numbers.

5Worth knowing

  • Keep it out of the main workflow. A wait-for-reply step there would hold the contact until they answer, and they would miss the 47-minute and 5-minute reminders. In a separate workflow they sit in both at once.
  • Keyword lists, not intent type. In Aaron's earlier test 'Running a few minutes late' scored positive. Matching is not case sensitive, so keep the lists lowercase.
  • Aaron's pipeline puts Canceled and No Show before Appointment Booked, so the update step needs 'allow opportunity to move to any previous stage' on.
  • The main workflow removes the contact and the 'day before confirmed' tag at the start time and on reschedule. A late reply after the call does nothing, and a rescheduled contact gets asked again.
  • The 5-minute wait before cancelling gives someone who replied NO by mistake time to correct it. Add your rebooking link to the NO reply if you want them to pick a new time.
  • Settings: allow re-entry on, stop on response off (the workflow is waiting for that response).

6Recipe

Creator's settings Taken from the source as published.

From Aaron's export.
YES list: yes, yea, yeah, ya, yep, yup, y, sure, sure will, confirmed, 👍, ✅
NO list: no, nope, nah, n, can't, cant, cancel, 👎
If/Else: Contact reply > Replied message > is any of [YES list] | is any of [NO list] | None branch renamed Other.
YES reply SMS: Thank you {{contact.first_name}} for confirming your appointment, talk to you soon :-) {{appointment.user.first_name}}
NO reply SMS: Oh no I'm sorry to hear that. Thanks for the reply btw. Can I ask why you won't be attending your appointment?
Owner push (YES): {{contact.name}} Confirmed Appointment! Their reply was: {{message.body}}
Owner push (Other): {{contact.name}} - 24hr Confirm Reply: "{{message.body}}"

7Source

Open the original YouTube by Aaron Delezenski (ClickLaunch) →

  • Steps checked line by line against Aaron's own HighLevel export of the same sub-account (8 workflows, exported Oct 15, 2026).
  • Chapters: V1 03:20, V2 08:13, V3 12:40, same-day fix 20:16, V4 24:47, pass input trigger parameters 37:00.

Video transcript read on 2026-10-17 (V4 chapters 24:47 to 39:25). Every step checked against Aaron's workflow export for 'Day Before Appt Confirmation'.

Related

More Booking builds

All builds →
HighLevel Booking

Reply intent tested on 13 real replies: why 'Running late' came back positive

A test of HighLevel's AI reply intent (positive/negative) for appointment confirmations. Intent reads the tone of a message, not whether the person answered the question, so it is risky for confirm or cancel logic.

Any local business Adapted from source
HighLevel Booking

Conversation AI booking action inside a workflow, with booked, not booked and timeout branches

Use the Conversation AI appointment booking action in a workflow. The bot fetches open slots, suggests times and books. Three branches let you follow up on each outcome.

Any local business Adapted from source
HighLevel Booking

Appointment confirmation and reminders: reschedule branch, 5 AM morning-of email and a same-day booking guard

Aaron's V4 appointment workflow. It confirms by text and email, sends a reschedule-specific message, reminds 2 days, the morning of, 47 minutes and 5 minutes before, and nudges the rep to log the outcome. A 'tomorrow' check keeps same-day bookers from getting day-before messages after their call.

Any local business Creator's settings

Day-before YES or NO confirmation text in its own workflow: confirms, cancels or hands the reply to you: workflow

  1. 01 Trigger

    No trigger. The main reminder workflow adds the contact 24 hours before the appointment with Add to Workflow and pass input trigger parameters on.

  2. 02 Action

    Send the SMS: 'Hi {{contact.first_name}}, I want to remind you about your appointment tomorrow at {{appointment.only_start_time}} {{appointment.timezone}}. Please reply with a YES or NO if you will be attending tomorrow, so I can best serve you!'

  3. 03 Action + wait

    Wait for a reply to that SMS, with a 1-day timeout. No reply means the contact exits.

  4. 04 Action

    If/Else on the reply message, 'is any of' a YES list or a NO list. Anything else goes to Other.

  5. 05 Action + wait

    YES: add the tags 'appt confirmed' and 'day before confirmed', push the owner with the reply, wait 1.5 minutes (8 AM to 9 PM only), text a thank-you, set the appointment status to confirmed.

  6. 06 Action + wait

    NO: push the owner '{{contact.name}} - NO to appt' with a call-them-to-find-out-why note, wait 1.5 minutes (8 AM to 9 PM only), then text 'Can I ask why you won't be attending your appointment?'

  7. 07 Action + wait

    NO, continued: wait 5 minutes, set the appointment status to cancelled, and move the opportunity to Canceled (or create it there).

  8. 08 Action

    Other: push the owner '{{contact.name}} - 24hr Confirm Reply' with the reply text so a person answers.