Managing service bookings just got a whole lot easier! You can now fully edit without needing to cancel and recreate the booking. Whether your customer wants to add another service, change the assigned staff member, update add-ons, or apply a coupon after booking, you can make those changes seamlessly while keeping the booking, order, and payment information in sync.

This has been one of our most requested Services enhancements, and we're excited to finally bring it to you!

We've successfully migrated the Submission Page for Forms, Surveys, and Quizzes to HighRise! 🎉 This enhancement modernizes the underlying architecture, improving maintainability and preparing the platform for future innovations—all while preserving the familiar user experience.

✨

🔑

⚙️

The submission experience remains unchanged from an end-user perspective. Behind the scenes, the submission page is now powered by the HighRise framework, providing a more robust, scalable, and maintainable implementation.

📝

The action now supports as a goal event. Workflows can now jump contacts directly to a goal when a team member replies to a conversation, making it easy to stop or redirect automations once human engagement has started.

Configure a action and select as the goal event. When a user sends a reply through a supported conversation channel, the contact immediately skips ahead to the Goal step, bypassing any intermediate workflow actions. This allows your workflow to react instantly to team activity instead of continuing scheduled automation.

Automated workflows should adapt when your team steps in. By supporting as a Goal event, you can prevent contacts from receiving unnecessary automated messages, reduce duplicate communication, and seamlessly transition from automation to human-led conversations.

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. Combined with the timeout option, you can now build powerful SLA workflows that automatically escalate if no user reply is sent within your target response time.

When configuring a Wait action, select User Replied as the wait condition and optionally define a timeout. The workflow pauses until a user replies or the timeout is reached - whichever happens first. If a reply is detected, the workflow continues immediately. If the timeout expires first, you can route the contact through escalation steps such as notifications, reassignments, or reminders.

Response-time SLAs are critical for sales and support teams. This enhancement lets you automate first-response tracking, reduce manual monitoring, and ensure conversations are escalated when response targets are missed - all without building complex workflow logic.

You can now start workflows when a replies to a conversation. This trigger fires whenever a user (team member) sends a reply to a contact, making it easier to automate internal processes after an agent responds instead of waiting for a customer reply.

Add the trigger to any workflow and choose the conditions that should start it. Once a user replies to a contact through a supported conversation channel, the workflow runs automatically and can continue with actions such as notifications, tagging, assignments, or follow-up automations.

Many automations need to react to your team's actions- not just customer activity. The User Replied trigger helps you build workflows that track agent engagement, trigger internal notifications, update records, or kick off the next step immediately after a team member responds.

We're introducing , a new way to track every snapshot that has ever been loaded into a sub-account. You can now view a complete, organized history of snapshot activity directly from the menu on the page.

* Added a new option alongside the existing action in the menu.

* View a complete list of all snapshots that have been loaded into a sub-account.

* Open any snapshot to see its detailed load history, including every time that specific snapshot was applied.

* Drill down further to view the exact assets—such as workflows, calendars, and more—that were included in each snapshot load.

* Each history entry displays:

* Who loaded the snapshot

* When it was loaded

* The snapshot version

* The snapshot type (Template, Created, Imported, or Marketplace)

Previously, there was no simple way to determine when a snapshot was loaded into a sub-account, who loaded it, or which version was used. This made troubleshooting, auditing account changes, and understanding account setup history difficult and time-consuming.

With , all of this information is now available in one place, making it easier to investigate changes and maintain visibility into your account setup.

* Quickly identify what was loaded and when without relying on support tickets or team members.

* See exactly who initiated every snapshot load.

* Access the complete snapshot history of any sub-account in just a few clicks.

* Drill down from the overall history to individual snapshot loads and the exact assets included in each load.

We're continuing to enhance the Snapshot History experience with improvements such as search and filtering capabilities, making it even easier to navigate and audit snapshot activity as your accounts grow.

We're introducing a set of enhancements to the Services payment experience that make checkout more flexible for customers while improving the accuracy of deposit calculations.

Once enabled, customers booking services with deposits will be able to choose whether to pay the deposit or the full amount during checkout.

You can now visually see and times directly in the and calendar views. Buffers are displayed as informational blocks, making it easier to understand appointment spacing without affecting scheduling flexibility.

HighLevel now lets sub-accounts control whether the "Sign in with Google" option appears on the Client Portal sign-up and login pages. Admins can enable or disable Google Sign-In directly from the Client Portal app permissions — giving businesses the flexibility to align their sign-up experience with their own compliance and data-handling requirements (for example, GDPR and other European regulatory considerations).

🛠️

💡

Available on the Client Portal Web platform.

More triggers to help admins respond faster and engage smarter! We've added 4 new Communities triggers to HighLevel Workflows, giving admins even more ways to act on important member activity — automating follow-ups, alerts, moderation flows, and event-based engagement directly from what members do inside groups.

⚡

Trigger a workflow when a member's request to join a group is rejected.

Filters: Group (required)

Trigger a workflow when a new post is created in a group.

Filters: Group (required), Channel, Post Title, Post Content

Trigger a workflow when a new comment is added to a group post.

Filters: Group (required), Channel, Post Title, Post Content, Comment Content

Trigger a workflow when a member registers for a group event.

Filters: Group (required), Event Title

💡

More automation possibilities — Turn everyday community activity into instant workflow actions.

Smarter targeting — Use filters like channel, post content, comment content, and event title to trigger workflows only when it matters.

Faster moderation and visibility — Alert the right people, flag key activity, or route updates automatically.

Less manual effort as groups grow — Automate repetitive engagement and follow-up moments at scale.

Stronger Communities + Workflows connection — Posts, comments, event registrations, and membership decisions can now power even more automated journeys.

🛠️

Go to Automation > Workflows in your sub-account.

Create a new workflow or open an existing one.

Click Add New Trigger and search "Community" to find the new triggers.

Select your trigger, choose the Group (required), and apply any optional filters like Channel, Post Title, Post Content, Comment Content, or Event Title.

Build out your workflow actions and hit Save trigger, then Publish — your automation is live!