25th of June, 2026

You can now choose to receive inbound calls only during your working hours. Turn on "Only ring during working hours" from your profile, pick the schedule that defines your availability, and any inbound call that arrives outside those hours will skip you automatically and go to the phone number's existing backup.

The setting is off by default, so nothing changes until you turn it on. During your working hours, calls ring you exactly as they do today.

: the schedule that powers this feature supports date-specific hours, which override your normal weekly hours for a single date. Add a date-specific day with no hours to take yourself off inbound calls for a holiday or a day off, without touching your regular weekly schedule.

For admins, control who can change this: this setting is tied to the "Manage calendars" permission. If you do not want a staff member changing their own call availability, remove the "Manage calendars" permission from their role under Settings > My Staff > Roles and Permissions. When that permission is off, the "Inbound call routing" card cannot be used for that user and any attempt to change the setting is blocked. This lets you keep control of after-hours call routing for your team.

🤔

Agency owners often create Email AI templates on behalf of their clients. However, if Email AI was disabled for a location, agency users couldn't access it there. This forced them to create templates in a few enabled locations and manually share them across other locations, resulting in extra effort and duplication.

✨

🏆

We have just added one more language to our Custom Code Action. Now you can change the language from the dropdown by selecting Python.

This enhances the already powerful action and opens up new avenues.

Ask AI V2 reimagines the HighLevel mobile AI assistant so you can get real answers and take real action from anywhere, not just from a laptop. Ten interactive response types, searchable history, and live streaming, all rendered natively.

You don't run your business from a desk. But until now, the mobile AI couldn't keep up. Answers were flat text, with no history to return to and no way to act on what the AI told you. So the real decisions waited until you were back at a computer.

Ask AI V2 brings the full AI experience to your phone. Ten artifact types - charts, data tables, code blocks, approval flows, question wizards, and more render natively and respond to touch. Answers stream in real time, and your entire conversation history is searchable. You decide and act on the move.

🏆

🛠️

Open Ask AI: Tap Ask AI in the HighLevel mobile app.

Ask anything: Type your question in the composer bar.

Interact: Tap charts, copy code, follow a wizard, or tap Sources to see what web search found.

🛠️

We're expanding what renders natively on mobile. The Canvas preview pipeline (9 preview types) is already built and will activate via a backend toggle, no app update needed. More artifact types and richer interactions are on the roadmap.

Roll-out & Availability

Roll-out & Availability

| Release Date | June 18, 2026 |

| Available Version | 4.18.1 (build 833) |

| Status | Public |

| HighLevel | ✅ |

| LeadConnector | ✅ |

| WL App | ✅ |

| Platforms | iOS & Android |

💬 We Want to Hear From You!

Speak with us: https://speakwith.us/nikhilsatish PM email: nikhil.siddasamudra@gohighlevel.com

🔔

We've improved the discoverability of Notifications in Forms, Surveys, and Quizzes by moving it from an icon-based entry point to a dedicated Notifications tab within the builder.

In addition, we've enhanced builder tooltips with clearer descriptions, contextual messaging, and direct Learn more links to relevant Help Center articles, making it easier for users to understand settings without leaving the builder.

These changes were driven by user feedback, particularly from new users who found it difficult to locate notification settings and understand certain builder options without assistance from support.

🚀

Previously, notification settings were accessed through an icon within the builder, making them easy to overlook, especially for new users.

With this enhancement, Notifications are now available as a clearly labeled tab, ensuring users can quickly find and manage notification preferences without additional guidance.

We've also improved several builder tooltips by providing more descriptive explanations, contextual messaging based on the selected product or field type, and direct links to Help Center documentation where applicable.

This allows users to better understand configuration options without interrupting their workflow.

By making notifications easier to find and providing more helpful in-product guidance, we're helping users get up and running faster while delivering a smoother, less frustrating onboarding experience. 🎉

WhatsApp Calling lets your team take and make real-time voice calls inside the same WhatsApp conversation, with no external dialer and no number sharing. It is built for support and sales teams who close faster on a call than over twenty messages. After a successful closed beta, it is now generally available on and the .

▶ Watch the demo: https://watchclueso.com/embed/nr66jh4pyn0my1pz

> When a customer is stuck, frustrated, or ready to buy, a two-minute call beats twenty messages. Now you can make that call without ever leaving the thread.

Before you start, each sub-account needs a phone number in state, a WABA messaging limit at the , and a phone number .

Decide who picks up when a WhatsApp call comes in. Add up to to the list, and an inbound call will ring all of them at once so the first available person can answer. No missed call because one rep stepped away.

You have two ways to route:

Use to label each configuration (for example, "Sales Team" or "Front Desk") so numbers stay easy to manage as you scale across sub-accounts.

Every WhatsApp call ends with a , so your team can capture the outcome in one tap and trigger the right next step without leaving the conversation. The moment a call ends, the summary shows the contact, the number, the call status (for example, ), and the call duration, then prompts the agent to select a .

Every sub-account starts with default dispositions like , , , , , and . Sub-account admins can edit these or add their own under , up to . Agents pick one when the call ends. Logging is optional, and one outcome is saved per call to keep your data clean.

Turn an outcome into action. In , add a trigger, set the filter to , and choose which outcomes fire which follow-ups, for example send a follow-up SMS or email, book an appointment, or add the contact to a pipeline or campaign.

Every disposition is stored and surfaced in as a Call Disposition column and filter, so you can see outcomes by user or team and spot patterns (for example, how many calls ended in "Requested Callback").

Custom Dispositions are live on the mobile app for both iOS and Android. Pick the outcome right from the call end screen. Note that on mobile, disposition options appear only when the selected sub-account matches the call's location, so use the Switch option if you take calls across multiple sub-accounts.

Why it matters:

WhatsApp protects users from unwanted calls, so the rules depend on who starts the call.

No permission is required. As long as is on, customers can call your WhatsApp number any time, from any country where WhatsApp is available.

You need the customer's permission first. Today, permission is requested through a with a call permission request. The customer taps to accept, and you can then call them within the permission window.

When the customer receives the request, they choose how to respond:

Customers can update their preference any time from the business profile, and WhatsApp shows them the date your permission is valid until. Once permission is granted:

Guardrails to keep in mind:

Inbound calls (customers calling you) work everywhere WhatsApp is available. Business-initiated calling (you calling the customer) is available in every location , where WhatsApp does not currently permit it. In those countries you can still receive inbound WhatsApp calls and display call buttons so customers can reach you with one tap.

Messaging is becoming the primary channel for customer conversations, and voice is the missing piece that closes the complex or high-intent moments. Keeping the call inside WhatsApp means your team keeps full context and a complete record, instead of pulling customers onto a separate line and losing the thread.

Chat history now shows only your own conversations.

Ask AI chat history on mobile now filters to sessions only. You see the conversations you started not chats opened by other teammates in the same sub-account.

🤔 The Challenge

When multiple users in a sub-account used Ask AI on mobile, for that location. That made it hard to find your own threads and raised privacy concerns when teammates shared the same sub-account.

✨ Our Solution

Mobile now loads your Ask AI history per user, matching how access works on web. When you open , you see only the conversations you started. The list also refreshes automatically when you switch sub-accounts or sign in as a different user.

🛠️ What's Next?

| | June 5, 2026 |

| | (build 831) |

| | Public |

| | ✅ |

| | ✅ |

| | ✅ |

| | iOS & Android |

💬 We Want to Hear From You!

Speak with us: https://speakwith.us/nikhilsatish

PM email: nikhil.siddasamudra@gohighlevel.com

Ask AI on mobile now follows the same per-user access you set on web. Grant a teammate access once, and they can use Ask AI from the HighLevel mobile app, it's no longer limited to agency admins.

🤔 The Challenge

On mobile, Ask AI was limited to , even when you'd already enabled it for sub-account users on web. Your team could use AI in the browser but hit a wall in the app, right where they do most of their on-the-go work.

✨ Solution

Mobile now respects the same per-user access you already grant on web. Teammates with access see Ask AI in the app and chat normally; everyone else won't see the entry point.

Agency users also get a when some sub-account teammates still need access, nudging you to finish setup on web. And if a usage limit or policy blocks a message, you'll see a instead of a vague "failed to send" toast.

🏆 How This Supercharges Your Business

🛠️ How to Get Started

🛠️ What's Next?

| | June 18, 2026 |

| | (build 833) |

| | Public |

| | ✅ |

| | ✅ |

| | ✅ |

| | iOS & Android |

💬 We Want to Hear From You!

Speak with us: https://speakwith.us/nikhilsatish

PM email: nikhil.siddasamudra@gohighlevel.com

Until now teams had to manually watch for conversations that were about to breach or had already missed their SLA targets. With this release, SLAs become actionable. You can now automate workflows when conversation SLAs are due soon, overdue, or manually dismissed, helping teams proactively manage response times instead of reacting after issues occur. We've also added more control over manual SLA removal, giving admins the ability to decide who can dismiss SLAs and ensuring every action is auditable.

👀

You can now build workflows that automatically run when a conversation's SLA becomes due soon, overdue, or is manually dismissed. Instead of relying on users or managers to monitor SLA timers, you can define exactly what should happen when these events occur. For example, you can: Notify a user when a conversation becomes overdue or Reassign contacts for escalation. To help prevent excessive notifications, we've also added an Avoid Repeated Triggers option. When enabled, the workflow will only run once per conversation within a 24-hour period, even if multiple messages from same contact cause additional SLA events.

We've also introduced better controls around manual SLA removal. For conversations where no response is required - such as "Thank you", "Got it", or "Not interested" messages, users can manually dismiss the SLA without replying. Admins can choose whether this action is available to all users or restricted to admins only.

As agencies manage increasingly sensitive client information, having greater control over document access is more important than ever. We're excited to introduce enhanced document privacy and access controls for files stored in the contact record's documents panel. This update gives users more flexibility in how documents are shared, helping them align with internal security policies, meet client expectations, and strengthen trust in their workflows.

* Users can now generate configurable document links with multiple access options while sharing:

* Public link – Accessible by anyone with the link

* Private link – Accessible only to authorized HighLevel users

* One-time code link – Access verified via a one-time password sent to the contact's email address

* Password-protected link – Access secured with a user-defined passcode

• Set expiration dates for shared links

• Allow or restrict document downloads

• View document details and access history for improved visibility and auditing

PS: The default behavior for the document link will be internal/private in nature (unless the user wishes to change it while sharing).

* We're working towards bringing in more privacy and data control for you to expand document security across the platform. In the next phase, these privacy and access controls will be extended to document attachments shared through notes and custom fields, creating a more consistent and secure document-sharing experience throughout HighLevel.

* Enhanced security for email attachments that go out via the marketplace apps