HighLevel: Wait Step: Now with Support for User Replies!

HighLevel published a changelog update for Wait Step: Now with Support for User Replies!. The Wait action now supports User Replied as a wait condition.

What changed

The Wait action now supports User Replied as a wait condition.

In addition to waiting for a contact to reply, you can now keep the contact waiting until a team member responds to the conversation before continuing to the next step.

Why it matters for agencies and VAs

Agencies and VAs are usually the first people asked why a screen changed, why a workflow loads differently, or whether a new setting should be adopted. Tracking this early keeps client support, SOPs, and implementation calls cleaner.

How to use it

1. Open the affected HighLevel feature and confirm how the change behaves in a real sub-account.
2. Update any client-facing SOP, Loom, or checklist that mentions the old behavior.
3. Flag the change only for clients whose workflows, calendars, payments, sites, conversations, SaaS, or AI setup are affected.

Certified GHL Admin operator take

As a Certified GHL Admin, my read is simple: do not treat this as trivia. If the feature is part of a client fulfillment path, test it once, document the operational impact, then decide whether it deserves a client note or an internal-only SOP update. Source category: automations.