The test phone number field in the Send SMS action now uses the standard phone input with a country flag picker, the same one you see elsewhere in the app. Type your number the way you dial it and the test sends. The old "please add country codes" hint is gone, and the error text is now just "Invalid phone number".

The picker sits in front of the field and defaults to your sub-account's country. Whatever flag is selected, the number is saved in full international format before the test goes out, so the country is always known. Click the flag to open the list and search by country name or dialing code to switch it.

Most people type their own number the way they dial it, without a country code. That failed every time and gave an error that read like the number itself was wrong, so a quick test turned into a guessing game about formatting.

An agency on an India sub-account types 9089786755 to test a reminder SMS. The picker already shows the India flag, so the test sends to +919089786755.

The same agency wants to check the copy on a US client's number. They switch the flag to US, type 4088613552, and the test sends to +14088613552.

Creating a certificate can now start with a simple prompt. Certificate AI Beta turns your requirements into a complete, editable certificate design in minutes.

Certificate AI is currently in Beta, and we’ll continue improving the experience based on your feedback. 🚀

The setting now has a smarter counting mode across Calendars, Services, and Rentals. A new Count available days only toggle lets businesses ensure their booking window reflects real working days — not calendar days that include weekends or days they're closed.

Protected snapshot assets are now more flexible to work with. You can reuse protected assets freely within your own agency while the original creator's protection remains intact when content is shared outside the agency.

— Use imported protected assets across your own sub-accounts and build new snapshots with them without restrictions.

— Protected assets still cannot be shared or resold to another agency.

— When a snapshot contains both protected and non-protected assets, eligible assets can still be shared while protected ones are excluded.

— Easily identify which assets in a snapshot are protected before attempting to share it.

— Whether an asset is imported, reused in another snapshot, or loaded into another sub-account, its protection status is preserved.

Previously, protected assets remained restricted even within the agency that imported them. This meant that once a protected asset became part of a snapshot, that snapshot could hit a dead end — even when it was only being reused internally.

Now, protection is enforced where it matters: at the agency boundary. You can freely build and reuse protected assets within your agency, while sharing them outside your agency remains restricted.

— Reuse imported assets across your agency without unnecessary restrictions.

— Continue building snapshots even when they contain protected assets.

— Protected assets still can't be redistributed to other agencies.

— Know exactly which assets are protected before sharing a snapshot.

Forms, Surveys, and Quizzes are often used for time-sensitive campaigns like event registrations, flash sales, webinars, contests, and limited-time offers—but until now, they remained available indefinitely unless manually removed or restricted.

With , you can now control exactly when a Form, Survey, or Quiz starts and stops accepting submissions. You can also decide what visitors see before it opens or after it expires, giving you full control over the experience without having to manually manage availability.

🚀

A new Schedule visibility setting is now available in:

Once enabled, you can configure:

✨

⚙️

🎯

💡

Previously, once a Form, Survey, or Quiz was published, it could remain available for submissions indefinitely. For agencies running time-sensitive campaigns, this could result in registrations, leads, quiz entries, or orders continuing to arrive after a campaign had already ended.

Scheduling removes that manual work by automatically controlling availability while still giving agencies complete control over what visitors experience before and after the active window.

As customers have highlighted:

Forms, Surveys, and Quizzes can now follow the lifecycle of your campaigns—open when you're ready, close when the deadline arrives, and guide visitors to the right experience at every stage.

We've updated how WhatsApp messaging limits appear in your sub-account to match Meta's new model. Meta moved messaging limits from a per-phone-number basis to a business portfolio (WABA) basis, so all numbers under a portfolio now share one daily limit. HighLevel now shows that single shared limit accurately, instead of implying each number has its own quota.

> 🚨 Under Meta's model, one high-volume number can consume your entire portfolio's daily capacity. You now see the one number that actually governs what your business can send today.

Meta's messaging limit is the maximum number of unique WhatsApp user phone numbers you can deliver to, outside the 24-hour customer service window, in a rolling 24-hour period. As of Oct 7, 2025, that limit is calculated and set at the and shared across every phone number in the portfolio.

Before this change, the limit shown under each number suggested every number had its own daily quota. It did not, and under Meta's portfolio model that gap matters more: a single high-volume number can burn the whole portfolio's capacity, which is exactly the situation that leads to unexpected send failures once the shared limit is hit. HighLevel now shows one accurate view of what your business can actually send today, so you can plan volume against the real ceiling instead of a per-number illusion.

You can now trigger workflows for multiple , directly from the list view.

* Select multiple Company or Custom Object records and trigger an automation in bulk

* Choose the workflow you want to run without updating records individually

* Track progress and review record-level results from

Sometimes you need an automation to run for records that already exist, without waiting for a new workflow trigger.

With this update, you can quickly process a selected group of records for use cases such as:

* Running onboarding or follow-up workflows for Companies

* Triggering renewal automation for Policies or Subscriptions

* Processing imported Custom Object records

* Running one-time operational workflows on selected records

You can monitor the results from .

📚 Learn More

We’ve enhanced Marketplace App Access controls to give agencies more flexibility over which apps their sub-accounts can access, while also addressing gaps in the existing approval system.

Agencies can now choose to show only approved apps to sub-accounts and manage approvals for all Marketplace apps from a single view.

As part of this update, we’ve replaced the previous auto-approve new apps setting with a simpler control: agencies can either allow all Marketplace apps or restrict their sub-accounts to approved apps only.

A new “Show only approved apps to sub-accounts” toggle is available under Manage App Access.

The page has also been revamped using Highrise components for a more consistent Marketplace experience.

Previously, app access management relied on auto-approval behavior that could result in new apps being approved automatically and created confusion around which apps were accessible to sub-accounts.

We recommend reviewing and cleaning up your approved apps list, especially if you plan to enable the new setting, as existing approval-related issues have now been fixed.

We’ve enhanced guest management for , giving businesses more flexibility over the information they collect from guests while improving guest contact data.

---

Previously, guest details were limited to . Businesses can now choose which information they want to collect for each guest:

When guest details are collected, a contact is automatically created or matched for each guest using their email and/or phone number.

Calendars already collecting guest details will continue with , so there is no change to the existing booking experience.

Guest details will default to , helping businesses capture richer guest information from the start.

---

Guest contacts created during a booking will now inherit the instead of automatically using the business timezone.

If the guest already exists as a contact in the CRM, their existing timezone will remain unchanged.

---

These enhancements allow businesses to:

---

The Create WhatsApp Template builder now validates your variable placeholders inline as you type, so you catch mistakes at authoring time instead of finding out after WhatsApp rejects the submission.

> No more saving a template, waiting, and getting a WhatsApp rejection you have to decode. Bad variables are flagged immediately, right in the builder.

Nothing to enable. Validation is built into the builder (). Just build your template, and any invalid variables are flagged inline before you can save.

Create Template is one of the most-used WhatsApp surfaces, and a template rejected by WhatsApp after you save is pure wasted effort: you have to guess what WhatsApp did not like and retry. Catching variable mistakes inline turns a delayed, opaque rejection into a clear, immediate fix, so templates go live faster and generate less support confusion on a core messaging surface.