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.

When a customer who uses a WhatsApp username messages you, WhatsApp shares only their username, not their phone number. You can now add a "Share contact info" button to a WhatsApp template, or send it from a workflow, so the customer shares their phone number in one tap and a username-only lead becomes a fully contactable one.

> This is how you recover phone numbers from username adopters, so they no longer sit as contacts you cannot call, export, or run phone-based automations on.

Usernames give customers phone-number privacy, which is good for them but leaves you with contacts you cannot call, export, or run phone-based automations on. Requesting contact info closes that gap: one tap converts a username-only lead into a fully usable contact, with the number captured cleanly and no duplicates. It keeps LatAm and other high-adoption WhatsApp markets fully monetizable instead of filling up with unreachable contacts.

Chat Widget now integrates with , making it easier to keep every widget consistent with your brand. Your location’s brand colors and fonts are now available directly within the panel.

Color pickers now show from your location’s Brand Board alongside a shared palette.

Colors already used across your custom-themed Chat Widgets automatically populate the Default palette the first time you open the builder.

Any new color you use is automatically added to the Default palette and becomes available across all Chat Widgets in that location.

Fonts configured in your Brand Board now appear separately from the standard font library for easier access.

The Styles panel now uses HighLevel’s , providing a consistent color selection experience across the platform.

Colors are normalized and deduplicated automatically to prevent repeated colors from cluttering the palette.

Your existing custom colors are automatically added to the Default palette, so there’s nothing you need to recreate.

If your location doesn't have a Brand Board yet, you'll see an option to set one up directly from the builder.

Maintaining consistent branding across multiple Chat Widgets no longer requires repeatedly finding and entering the same colors and fonts.

With Brand Board integration:

Keep Chat Widgets aligned with the rest of your HighLevel brand experience.

Access approved brand colors and fonts directly while designing.

Reuse colors across every widget within a location.

Preserve existing widget colors automatically.

Spend less time manually configuring styles across multiple widgets.

Live in production for all custom-theme color pickers in Chat Widget.

Brand Colors are in Chat Widget and are managed through Brand Boards.

The can be updated and is shared at the location level.

A configured Brand Board is required for Brand Colors to appear.

Existing Chat Widgets require .

Existing website embed snippets require .

Chat Widget compliance settings are now more flexible, giving businesses greater control over how legal notices and visitor consent are handled.

The previous all-in-one HIPAA compliance setting has been upgraded to a new section.

You can now:

below the contact form without requiring any visitor action.

with custom wording for explicit opt-ins such as SMS or email marketing consent.

depending on your business needs.

when the form loads.

when required consent is missing, with a “Please tick this box to continue.” message.

, including whether consent was given, whether it was required, and the exact consent text shown to the visitor.

Navigate to:

From here, you can configure your legal notice, consent checkbox, required/optional behavior, and pre-checked state. The live preview updates as you configure the experience.

Legal disclosures and explicit marketing consent don't always serve the same purpose. Previously, they were handled through a single setting.

With this update, businesses can independently configure disclosures and consent, making it easier to create the right experience for different compliance requirements while maintaining a clear record of what each lead agreed to.

Existing widgets remain unchanged until they are opened and saved in the builder.

Existing legal text is automatically carried over to the appropriate field.

Widgets created through retain their existing compliance configuration.

New widgets default to:

Legal notice:

Consent checkbox:

Required consent:

No changes to existing website embed code are required.

You can now offer , giving bookers the flexibility to choose the meeting length that works best for them.

Instead of creating separate calendars for 15-minute, 30-minute, or 60-minute meetings, you can configure on the same calendar.

From your calendar settings, you can:

When multiple durations are configured, bookers will see them as easy-to-select options on the booking page. Selecting a different duration automatically refreshes availability to show slots that can accommodate the selected meeting length.

If only one duration is configured, the booking experience remains unchanged.

Multiple durations are supported across:

The selected duration is also supported when , allowing the meeting length to be changed along with the date or time.

Changes to your calendar's duration options .

For example, if you remove a 30-minute duration while future 30-minute appointments are already booked, those appointments remain unchanged. Their calendar events, reminders, and notifications continue to use the originally booked duration.

New appointments can only use the duration options currently configured on the calendar.

When rescheduling, bookers will see the calendar's currently available durations. If their original duration is no longer offered, they'll be asked to select a new duration before completing the reschedule.

Available for:

This update makes it easier to offer flexible meeting lengths while keeping availability, bookings, and calendar management within a .

💳

Selling through Forms and Surveys is great—but asking someone for their credit card when the order comes to nothing isn't. We've introduced a new Require Credit Card setting on the Sell Products element, so free orders can be completed without any card entry at all.

✨

A new toggle is now available on the Sell Products element in:

When turned OFF, a product order that with nothing recurring due will and complete as a free checkout.

⭐️

⚙️

📋

Free and paid offers can now live in the same Form or Survey without asking customers for card details they shouldn't need to give. 🎉

👀

👷

🌟

📝