Builds That Work Get the Daily Build

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

Source-checked YouTube

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.

Source: Aaron Delz (ClickLaunch), YouTube, 2026-10-08

1What it does

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.

2Who it is for

Industry
Any local business
Platform
HighLevel
Category
Booking
Tools used
HighLevel WorkflowsIf/ElseInternal 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

    Customer replied to an appointment confirmation text.

  2. 02 Action

    Send a confirmation text asking for a yes or no.

  3. 03 Action

    Branch with If/Else on Contact reply > Reply message > 'is any of' a hand-built YES list.

  4. 04 Action

    Second branch with a NO list.

  5. 05 Action

    Everything else goes to an internal notification so a human reads it.

Trigger
Customer replied to an appointment confirmation text.
AI step
None. The point of the build is to replace the AI intent check with explicit keyword lists.

4How it went

Tested 13 real replies. 'Running a few minutes late' came back POSITIVE. 'No problem, see you then' came back NEGATIVE. Matching was not case sensitive.

Only what the source reports. Numbers above come from the source.

5Worth knowing

  • AI intent is fine for sorting nurture replies, not for confirming or cancelling appointments.
  • 'Yes, but can we move it to Thursday?' is a reschedule, not a yes. Route unknowns to a human.

6Recipe

Adapted from source Reworded or reconstructed from what the source shows.

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 > Reply message > is any of [YES list] -> mark confirmed. Is any of [NO list] -> cancel flow. Else -> internal notification to the assigned user.

7Source

Open the original YouTube by Aaron Delz (ClickLaunch) →

Source opened and read on 2026-10-11.

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

  1. 01 Trigger

    Customer replied to an appointment confirmation text.

  2. 02 Action

    Send a confirmation text asking for a yes or no.

  3. 03 Action

    Branch with If/Else on Contact reply > Reply message > 'is any of' a hand-built YES list.

  4. 04 Action

    Second branch with a NO list.

  5. 05 Action

    Everything else goes to an internal notification so a human reads it.