Gift Card communications now support backend translations, ensuring customers receive localized communications based on the selected locale.

A new marketing template type that puts a live countdown clock inside the message itself, drawn by WhatsApp and ticking down in your customer's chat. The discount code sits right beneath it, ready to copy with a single tap. You set the expiry fresh on every send, so one approved template runs campaign after campaign.

> ⏳ Your customer watches the deadline shrink in real time instead of reading the words "offer ends soon." The countdown is rendered by WhatsApp, not baked into an image you have to redo every campaign.

if you send with an expiry that has already passed, Meta still accepts the message and the chat shows the offer as already expired. Double-check the deadline before a bulk send.

Deadline-driven offers have always been awkward on messaging. You either wrote "ends soon" and hoped it landed, or you baked a date into an image and rebuilt the creative for every campaign. Neither approach shows the customer a deadline they can actually watch, and both put a Meta approval cycle between you and your next promotion.

Creating and editing WhatsApp templates now happens in a completely rebuilt builder with a live phone preview, so what you see while you author is what your contact actually receives. And media headers no longer need a hard-coded URL: point them at a dynamic value and the right image, video, or document resolves per contact at send time.

> 📎 Send every customer their own invoice, ticket, or personalized image from a single template. No more cloning a template for every asset and waiting on Meta to approve each copy.

the resolved value must be a publicly reachable URL that Meta can download. Private Drive links, URLs behind a login, and empty fields will fail.

Personalized media used to carry a hidden tax. Every variation meant another template, and every template means another round of Meta approval before you can send anything. That made per-customer invoices, tickets, certificates, and personalized campaign images impractical for most agencies, so they either skipped them or built fragile workarounds.

AI Studio checkouts just got more flexible. Pick exactly which fields buyers fill in, capture leads before they pay with a two-step checkout, and show a full order summary once payment goes through.

Show, hide or require the phone number and each billing address field (street, city, state, ZIP, country). Name and email are always required.

Capture the lead first and take the payment second, just like the Two Step Order form in Funnels.

new leads fire the trigger, not Order Form Submission. Check that your workflows listen for the right one.

The confirmation screen now shows the order ID, items, taxes and total paid, plus the next charge for subscriptions. Prefer your own page? Send buyers to a custom thank-you page that displays their real order.

Projects already using Payments get all of this on their next prompt. No need to reconnect.

Connect a GitHub account to any AI Studio project and keep your code in sync both ways. AI Studio creates a private repository for the project, pushes every version you save, and pulls back every commit made outside it. Work in any editor or coding agent (Claude Code, Codex, Cursor, Copilot, Gemini CLI) and your changes land back in the project with a fresh preview.

A new AI Studio permission controls Git access and code downloads. It's , so nobody loses access. Agency admins can turn it off per user in . Users without it won't see the Git tab or Download options, but can still build, edit and preview as usual.

You can now add native chat widgets to your AI Studio apps — built and styled by AI Studio to match your site, instead of a generic chat bubble. Just ask AI Studio to "add a live chat", and it builds a real HighLevel chat widget into your app.

Chat widgets in AI Studio run on HighLevel's chat widget, so the conversations, contacts and widget settings are the ones you already use in your HighLevel account. There's nothing extra to set up.

Go to to see the leads your project's chat widgets bring in.

Go to to see your project's widgets. Open one to manage it without leaving AI Studio:

You can now update feature access for many sub-accounts in one go. Select the sub-accounts you want on the Sub-Accounts page and click Update features. Choose the features you want to change, then pick whether each one should be enabled or disabled. When you apply the changes, they’re queued and processed for you.

You can search for features, select whole groups at once, and use Enable all or Disable all to speed things up. You can also remove a feature from the list before applying.

You no longer need to open each sub-account to change its features. Rolling out a new feature, restricting access, or standardizing setups across many sub-accounts now takes a few clicks, so you spend less time on repetitive admin.

You can now automatically add Internal Comments to conversations using Workflows. Until now, teams had to manually add internal comments to share context, provide instructions, or keep other team members informed. With this workflow action, you can automate internal comments based on specific events, ensuring important information is captured directly in the conversation without manual effort.

We've introduced a new Add Internal Comment workflow action that lets you automatically post internal comments to conversations when a workflow runs. You can use this to share important context, provide follow-up instructions, or notify specific team members by @mentioning users directly in the comment.

For example, when a high-priority lead enters a workflow, you can automatically add an internal comment mentioning the assigned team member with instructions for the next steps. These comments appear directly in the conversation history, keeping internal communication and customer context in one place without sending anything to the customer.

This helps teams automate internal communication, keep everyone informed, and ensure important customer context reaches the right people at the right time.

We’re launching a Schema markup dashboard at the website and funnel level, under the new SEO & AEO tab. User no longer need to open each page in the builder to check or fix its schema. From one screen, user can:

Accurate, current schema makes your pages eligible for Google rich results and helps AI answer engines understand and cite your business. Until now, keeping schema current meant going through the builder one page at a time, so most sites fell out of date. This dashboard turns that into a quick check you can act on in bulk.

Screen 1: SEO & AEO - Schema home screen 1

Screen 2: SEO & AEO - Schema home screen 2

Screen 3: SEO & AEO - Select page For Schema generation

Screen 4: SEO & AEO - Schema generation progress

Screen 5: SEO & AEO - Schema generated using AI

Screen 6: SEO & AEO - Schema edit

InitiateCheckout now fires when a buyer , not when they submit payment. AddPaymentInfo now also sends full order and customer details to Meta. Together, these changes give you an accurate picture of checkout drop-off and give Meta better signals to optimise your campaigns.

This applies to funnels, websites and stores that have the Meta Pixel set up with the InitiateCheckout event enabled.

🆕

💡

✨

✨