You can now in destination sub-accounts while loading a Snapshot — eliminating the need to update each sub-account individually afterward.

* — Each selected dashboard now includes a option during Snapshot Load.

* — Only one dashboard can be marked as default. Select another dashboard to switch the default, or deselect it to use the existing behavior.

* — If you don't select a default, the will continue to be used.

Previously, changing the default dashboard was a , requiring you to manually open each destination sub-account after loading a Snapshot.

For agencies loading Snapshots across hundreds or thousands of sub-accounts, this meant repeating the same configuration over and over.

Now, you can configure it .

* — Set the default dashboard once, whether you're loading to 10 sub-accounts or 1,000.

* — Ensure every destination sub-account starts with the intended dashboard.

* — No need to visit individual sub-accounts after the Snapshot is loaded.

* — If you're happy with the Snapshot's current default dashboard, simply leave the setting unchanged.

During your next , select the dashboards you want to copy and click on the dashboard you want as the destination's default.

> Make sure the selected dashboard has the appropriate view permissions for users in the destination sub-accounts.

Create or update a Contact, and HighLevel can find the right existing Company and associate the Contact automatically. If no suitable Company exists, HighLevel can create one, store its domain, and enrich it with the Company Name and Logo.

For B2B businesses, new Contacts should naturally belong to the right Company without users having to create and associate Company records manually.

With this update, Company data can organize itself in the background as Contacts enter the CRM.

This helps users:

When a Contact is created or their email is updated, HighLevel checks for a suitable existing Company before creating a new one.

Contact: sarah@acme.com

The existing Automatically create and associate companies from contact business names automation continues to work alongside the new domain-based capabilities.

For SaaS V2 accounts, when the clients update their default payment card, we now automatically update the card used for the active SaaS subscriptions too.

Your subscription renewals will use the latest card automatically, reducing the chance of a missed or failed payment because an old card was still on file.

This applies to SaaS V2 accounts with an active subscription plan. Wallet recharges continue to use your default card as before.

Businesses can now control exactly which team members can access and perform different actions across Gift Cards. Instead of providing the same level of Gift Card access to every user, admins can assign permissions based on each team member’s responsibilities - helping protect Gift Card balances, customer information, and sensitive actions such as issuing or deactivating cards.

The new Gift Card permissions provide granular control over:

Additionally:

We'll continue expanding access controls around Gift Cards as the ecosystem grows, including ensuring new Gift Card capabilities have appropriate permissions as they are introduced.

Ask AI can now call the Workflow AI agent. This means you can create and edit a full workflow without opening the builder first — just describe what you want and the agent builds it. The capability already existed inside Workflow AI; it is now available through Ask AI as well, giving you one more way to build automations. And since Ask AI runs on WhatsApp, workflows can now be created straight from WhatsApp.

Start a new chat in Ask AI, describe the workflow you want, and the agent builds it for you.

The generated workflow renders right inside Ask AI, so you can see the full structure without switching screens.

Click a trigger or action in the preview to see its full configuration.

Ask the agent to change anything and it updates the workflow in place.

A CTA takes you straight into the workflow builder to test and publish.

The same workflow creation experience is now available on WhatsApp.

Workflow creation is no longer tied to a single surface. The same agent that powers Workflow AI is now reachable from wherever you are already working — including outside the platform entirely, over WhatsApp. Ask AI handles the drafting and iteration; the builder remains the place where you verify, test & ship, so the review and publish path stays unchanged no matter where the workflow started.

Manual editing is not supported inside Ask AI. Use the redirection link in the panel to open the workflow builder and edit it there. Publishing always happens in the workflow builder after a final test.

You can now send bulk emails to associated Contacts directly from Company and Custom Object lists.

Select the Companies, Properties, Policies, Pets, or other Custom Object records you want to act on, choose the relevant associated Contacts, and send your email without rebuilding the audience from the Contacts list.

Smart Lists already let users create powerful segments using Company and Custom Object data. Until now, those segments could not be used directly for email campaigns because bulk email started from Contacts.

Now, users can segment first and communicate immediately.

📚 Learn More: Help article

We’re expanding custom fields to give you more flexibility in how you capture, structure, and manage information. With new field types and enhanced configuration options, you can collect richer data, control inputs more precisely, and tailor fields to fit your business needs.

Create dedicated URL fields to capture website links, profile URLs, resource links, or other web addresses in a structured format. You can also control which URLs users can enter by . This helps ensure that the URLs being captured meet your business requirements.

Capture date and time information in the format that best fits your use case. Choose between for information such as important dates, preferred contact times, renewal dates, or scheduled events. You can also restrict the selectable dates to giving you greater control over the data entered.

Associate the right team members with a record by within a custom field. This can be useful when multiple people are responsible for managing or collaborating on the same record. Users assigned through this field will also , helping the relevant team members stay connected to the record.

Radio button fields can now . This provides additional visual context when users need to select a single option and makes choices easier to distinguish at a glance. It’s especially useful when the available options are better represented visually than through text alone.

Make checkbox fields Instead of relying only on text, users can see an image alongside each choice, making options easier to recognize and select—especially for fields involving products, designs, categories, or other visual choices.

Capture detailed information without being limited to plain text. Rich text fields support formatting options such as , helping users organize longer notes or structured information so that important details are easier to read and understand.

This is the biggest WhatsApp pricing change we have ever made. Starting , HighLevel is removing the 5% processing fee on every WhatsApp message you send. Marketing, utility, service, all of it. From that day you pay Meta's published rate to the cent

> 💥 Open Meta's rate card. Open ours. The numbers will match exactly. That is the whole announcement.

Per marketing message, what you pay today and what you pay from October 1:

This is Meta's published rate card and it is exactly what you will be billed. Service is priced the same as utility in every market.

Rebilling is applied as a multiplier on cost, so your client-facing price moves with the rate. Review your multiplier under and set it where you want it ahead of October 1.

Two categories of messages that are currently free become billable from 1 October 2026. Both changes apply on a per-message basis, consistent with how template messages are already charged.

> 💚 Conversations that start from a Click to WhatsApp ad or a Facebook Page call-to-action button remain free for a full 72 hours, for every message type. Marketing, utility and service messages are all at no charge inside that window. This is the single biggest lever you have to keep your WhatsApp costs down after October 1.

the customer service window is independent of the FEP window. If the 24-hour customer service window closes, you can only send template messages, even though the FEP window is still open and those templates are still free.

route more first-touch traffic through Click to WhatsApp ads and Page CTA buttons. Every conversation that starts there gives you three days of completely free messaging, which the new service-message charge does not touch.

Per-message rates change in the following markets from 1 October 2026. Markets marked * are also moving out of their regional "Rest Of" pricing bucket, see Change 4.

*Market is being moved out of its respective "Rest Of" pricing region to be standalone on the rate card.

The nine markets with utility rate updates were given four months' notice rather than the usual one month.

In the markets marked as an increase above, Meta's increase is larger than the 5% we are removing, so your rate is higher than what you pay today. Everywhere else your rate goes down. The full card is above.

Six markets moved out of their respective "Rest Of" pricing region on 1 July 2026: Hong Kong, Singapore, Hungary, Poland, Romania and Qatar. From 1 October 2026 a further nine markets become standalone on the rate card.

Bangladesh, Iraq, Kazakhstan, Kuwait, Morocco, Nepal, Oman, Sri Lanka and Ukraine.

Until 30 September 2026 a message to one of these countries is priced at its regional "Rest Of" rate. From 1 October 2026 the country has its own line on the rate card, with its own per-message rate.

Many WhatsApp platforms add anywhere from 6% to 25% on top of Meta's rate and never tell you.

Publishing a workflow just got a lot safer. If your workflow has unresolved configuration issues, we now stop the publish, show you exactly what is broken, and help you fix it on the spot. Broken workflows no longer slip silently into production.

This sits on top of a full year of validation coverage built across triggers and actions. Users no longer guess what is misconfigured. The canvas tells them, the sidebar fixes it, and the publish gate makes sure only working workflows go live.

You can now manually retry failed subscription payments directly from the Subscription Details page for NMI, Authorize.Net, Square, and Mercado Pago.

This gives businesses another way to recover subscription revenue after automatic payment retries have been exhausted or unavailable, along with an option to update the card for the subscription and collect payment from a new payment method.

Go to and open any subscription with an '' or '' payment status.

Once automatic retries are exhausted, you can:

- https://help.leadconnectorhq.com/support/solutions/articles/155000008665-how-to-manually-retry-a-failed-subscription-payment

We will continue improving subscription payment recovery across payment providers and making failed payment management more seamless.