July 9, 2026. GoHighLevel shipped a run of changelog updates on July 7 and 8 that close a long-standing gap in its automation engine: workflows can now react to what your team does, not just what the customer does. For agencies running client accounts, that unlocks enforceable response-time SLAs inside the CRM itself.
Key developments
- User Replied workflow trigger (July 8). Workflows can now start the moment a team member replies to a contact: update the opportunity stage to Contacted, tag the record, notify a manager, or queue a 48-hour follow-up task automatically.
- Wait step with User Replied and a timeout (July 8). This is the SLA builder. A workflow can wait up to, say, 15 minutes for a rep to answer a new lead; if no reply lands, it escalates with an urgent task and a manager alert. GoHighLevel's own examples cover a 30-minute support SLA with supervisor reassignment.
- Goal action with User Replied (July 8). Contacts jump out of a nurture sequence the moment a human takes over the conversation, ending the classic embarrassment of automated day-3 emails after a rep already closed the thread.
- RCS messaging lands in Workflows (July 7, private beta). New Send RCS and RCS Interactive Message actions support rich cards and buttons, with branching based on which button the customer taps. The beta also covers 1:1 and bulk RCS plus template management, with general availability planned for the end of Q3 2026.
- Also this week: sub-account Snapshot Load History (who loaded which snapshot, when, and which version, a real audit trail for agencies) and Services checkout upgrades that let customers choose deposit or full payment, with smarter deposit math and buy now, pay later support on the full amount.
What it means for operators
Speed to lead is the most controllable variable in lead generation, and until now enforcing it in GoHighLevel meant dashboards and nagging. The User Replied trio turns the response-time SLA into a workflow: notify the rep, wait 15 minutes for User Replied, escalate on timeout, and stop every nurture the moment a human engages. Build that watchdog on your two highest-value pipelines this week. Agencies should also switch snapshot governance on for client accounts, and ask their Customer Success Manager about the RCS beta now so branded interactive messaging is ready the day it goes GA. It extends the platform's steady automation push we covered in the July 1-2 update roundup and the MCP server launch. If you want these SLA workflows, escalation paths and RCS-ready journeys configured properly, our GoHighLevel services team does exactly this, wired into a full lead generation system.
Frequently Asked Questions
Released July 8, 2026, it starts a workflow when a team member replies to a contact, rather than when the customer does. Paired with the matching Wait condition and Goal event, it lets automations react to human engagement: updating stages, stopping nurtures and tracking first response times.
On a new-lead trigger, notify the assigned rep, then add a Wait action set to User Replied with a timeout matching your SLA, for example 15 minutes. If the rep replies in time the workflow continues normally; if the timeout fires first, escalate with an urgent task and a manager notification.
RCS is the richer successor to SMS, with branded senders, cards and interactive buttons. As of July 7, 2026 it works inside Workflows via Send RCS and RCS Interactive Message actions for private beta users, with general availability planned for the end of Q3 2026. Access currently goes through your Customer Success Manager.
Sub-account Snapshot Load History for auditing who loaded which snapshot and when, calendar buffer-time visibility, new Communities workflow triggers, a Google sign-in toggle for client portals, and Services checkout upgrades including a customer choice between deposit and full payment with buy now, pay later support.