Changelog
Follow up on the latest improvements and updates.
RSS
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.
What's New
AI Studio adds the chat for you
- Ask AI Studio for a chat and it shows a card to create the widget: Live Chat, orEmail Chatfor visitors who leave a message and get a reply by email.
- The widget is created in your account, named after your project, and wired into your app.
- For a new chat, AI Studio asks a few quick design questions (greeting, placement, tone), then builds it.
Designed to match your site
- The chat is built into your app's own code, so it uses your site's colors, fonts and layout.
- Change its look the way you change anything else: ask AI Studio, or edit it in code.
- A project can have more than one widget — for example, live chat on every page plus a separate after-hours chat.
The real HighLevel chat underneath
- Built-in security:Visitor sessions use secure tokens that never touch your app's code, and a captcha appears automatically when the chat suspects a bot.
- Spam & abuse protection:Rate limits and your widget's spam settings apply to every message.
- Attachments:Visitors can share files in live chat, within the widget's supported file types and size limits.
- Conversation history:Returning visitors pick up where they left off, and older messages load as they scroll.
- Delivery status:Messages show as sending, sent or failed, and failed messages can be retried.
- Business rules:Business hours, out-of-hours messages, inactivity timeouts, chat ratings and chat-ended messages follow your widget settings.
- Conversations:Every message lands in HighLevel Conversations, just like the standard widget.
- Your wording:AI Studio can set the welcome message and feedback lines when you ask — e.g. "greet visitors with: Hello, how can we help?"
Chat widget analytics
Go to
More → Analytics → Chat Widgets
to see the leads your project's chat widgets bring in.- At a glance:Chat loads, opens, open rate, and visitor feedback and satisfaction from chat ratings.
- Every lead in one table:Contact, email, phone, chat type, the page the chat started on, and which widget it came from.
- Flexible views:Filter by widget and date range, choose which columns to show, and select leads to download.
Chat widget settings, inside AI Studio
Go to
More → Chat Widgets
to see your project's widgets. Open one to manage it without leaving AI Studio:- Widget name:Rename it right there.
- Messaging:The welcome and acknowledgement lines visitors see in the conversation.
- Contact form:The details visitors give before their first message.
- Compliance notice & consent:Legal notices and opt-in consent for privacy, marketing, SMS and HIPAA needs.
- Spam protection:Suspicious leads are kept for review and tagged, with optional DND on SMS, email or both.
- Business hours (Live Chat):When live chat is open. Outside those hours, visitors see your offline message instead.
- No widget yet?TheAdd a chat widgetbutton asks AI Studio to create one for you.
Availability
- Live Chat and Email Chat are supported in both TanStack Start and React projects.
- Voice chat, WhatsApp, Facebook Messenger and Instagram chat widgets aren't supported in AI Studio yet.
What’s New
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.
How to use it:
- Select sub-accounts on the Sub-Accounts listing page.
- Click Update features.
- Choose the features you want to change, then click Next.
- For each feature, choose Enable or Disable.
- Click Apply changes.
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.
Why It Matters
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.
Notes
- Changes take effect in about 2–5 minutes after you apply them.
- You can follow the status of every request in Bulk Actions History.
new
Automations
Conversations
Conversations: Add Internal Comments Using Workflows
Overview
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.
What’s New?
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.
How to Use
- Go to Automation → Workflows.
- Create a new workflow or open an existing one.
- Add the Internal Comment action.
- Enter your comment and @mention team members as needed.
- Save and publish the workflow.
Why It Matters
This helps teams automate internal communication, keep everyone informed, and ensure important customer context reaches the right people at the right time.
new
Funnels and Websites
SEO
Schema management at Website/Funnel level
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:
- See overall schema health. The Schema coverage card rates your site as Needs work, Getting there, Good, or Excellent, with counts for Up to date, Might be outdated, and No schema.
- Check every page at a glance. Each page shows its schema types, its status (Up to date / Might be outdated / No schema / Unpublished / Unsaved), and when it was last updated.
- Generate schema with AI, one page or many. Select pages and click Generate schema. Progress shows live, and results appear for your review before anything goes live.
- Add or edit schema manually. Click + Add schema for pages with none, or click any schema tag to open the editor.
- Review, then publish. Generated or edited schema stays Unsaved until you click Save and publish. You can also Discard it.
- Find what needs fixing. Search by page name or path, and filter by schema status.
- Spot stale schema. Pages edited and republished 2 or more times since their schema was created are flagged Might be outdated.
Why this matters?
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.
Impact on existing users
- No data loss and no action required.
- Every website and funnel now has an SEO & AEO tab. Any existing schema appears there automatically.
- Pages without schema are flagged No schema, so user can fix them in bulk.
- Schema editing in the page builder still works exactly as before. Both places stay in sync.
- Running Generate schema on a page that already has schema replaces it entirely. Review before Save and publish click.
How to use
- Go to Sites → Websites/Funnels → select one → SEO & AEO.
- Check the Schema coverage card, and filter by No schema or Might be outdated.
- Select pages and click Generate schema, or use + Add schema / click a tag to edit manually.
- Review the results, then click Save and publish.
Sample screens
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
improved
Funnels and Websites
Meta Pixel: Improved InitiateCheckout Accuracy & Enhanced AddPaymentInfo Data
InitiateCheckout now fires when a buyer
reaches checkout page
, 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.
🆕
What's New
- Smarter InitiateCheckout timing: The event now fires at the moment the buyer starts checking out:
- When the page loads on store checkout pages.
- When the page loads on any page where you added InitiateCheckout at the page level.
- On the buyer's first click, tap or keystroke in an order form everywhere else. This covers one-step, two-step and popup order forms, plus the new order form.
- Page-level control:Adding InitiateCheckout at the page level makes it fire as soon as that page loads. Adding it at the funnel, website or webinar level makes it fire on the buyer's first interaction with the order form.
- Protection against duplicates and false triggers: InitiateCheckout fires at most once per page visit, even when a page has several order forms or more than one trigger is configured. Browser autofill, password managers and fields that are focused automatically on load don't trigger it.
- Abandoned-cart recovery support:When a buyer comes back through an abandoned-cart link, the event waits for their saved cart to load, so it includes the cart value and products.
- Express wallet coverage:Buyers who go straight to Apple Pay etc without touching the form are still counted. For them, InitiateCheckout fires when payment starts.
- Richer AddPaymentInfo data: AddPaymentInfo now includes order value, currency, product IDs, and hashed customer details (email, phone, name, external ID) when they're available.
💡
Why It Matters
- See real checkout drop-off:InitiateCheckout and AddPaymentInfo used to count the same buyers, so the step between "started checkout" and "entered payment" showed nothing. You can now see how many buyers reach checkout but leave before paying.
- Better ad optimisation: Meta can now optimise and build audiences around buyers who show checkout intent, including those who don't complete the purchase.
- Higher Event Match Quality: Full order and customer details on AddPaymentInfo help Meta match more events to real people, which improves attribution and targeting.
- Consistent, trustworthy data:Every event now reports the same currency for an order, and invalid or blank values are never sent to Meta.
✨
What Stays the Same
- Setup:Your Meta Pixel settings work exactly as before. No reconfiguration is needed.
- Other events: PageView, ViewContent and Purchase fire at the same moments as before.
- Consent:Events still respect your cookie-consent settings. If a visitor hasn't accepted advertising cookies, nothing is sent.
- Conversions API:When the Conversions API is enabled, browser and server events are still sent together and deduplicated in Meta Events Manager.
- Free orders:If an order requires no payment details at all, AddPaymentInfo is not sent, same as before. New: orders fully covered by a gift card now send it (with a value of 0).
- Pixels without InitiateCheckout:If InitiateCheckout isn't enabled on your pixel, nothing changes.
✨
What to Expect
- InitiateCheckout counts will go up.This is expected: the event now includes buyers who reach checkout and leave without paying. The gap between InitiateCheckout and AddPaymentInfo/Purchase now shows real checkout drop-off. Keep this in mind when you compare reports, automated rules or cost-per-InitiateCheckout before and after this release.
- Page-level settings may take up to 24 hours to take effect on already-published pages. To apply them immediately, edit and save the page.
- No change to consent or Conversions API behavior.Events still respect your cookie-consent settings. When the Conversions API is enabled, browser and server events are still sent together and deduplicated in Events Manager.
- No action required. The update applies automatically.
new
Phone System
📢 Voice Pricing Updates - Effective October 13, 2026
Overview
The previously announced Voice pricing updates scheduled to take effect on October 13, 2026 will no longer be implemented.
Underlying providers have confirmed the cancellation of these changes. As a result, the affected Voice rates will remain unchanged.
You can view the original announcement here: Voice Pricing Updates - Effective October 13, 2026
No action is required for now.
We’re sharing this update to ensure you have the latest pricing information and avoid any confusion ahead of the previously communicated effective date.
We are thrilled to announce our new web templates, designed to elevate your marketing efforts. Whether building a website, creating a sales funnel, or sending email campaigns, our versatile and user-friendly templates have you covered. Fully customizable and professional, they streamline your workflow, saving you time and letting you focus on engaging your audience and driving results.
List of New Templates
------------------------------------------------------
🚀
21New Website Templates Published
🚀------------------------------------------------------
Legal - 1
------------------------------------------------------
🚀
1 New Funnel Templates Published
🚀------------------------------------------------------
Automotive - 1
------------------------------------------------------
🚀
1 New Email Templates Published
🚀------------------------------------------------------
Restaurant & Bar - 1
-----------------------------------------------------
🚀
1 New Survey Templates Published
🚀-----------------------------------------------------
Business, Coaching & Consulting - 1
-----------------------------------------------------
🚀
8 New Social Templates Published
🚀-----------------------------------------------------
Marketing Agency - 2
Creative - 2
Business Coaching and Consulting - 2
Financial. -2
-----------------------------------------------------
🚀
2 New Facebook Ad Templates Published
🚀-----------------------------------------------------
Creative - Interior Designer
Real Estate - Realtor
-----------------------------------------------------
🚀
5 New Google Ad Templates Published
🚀-----------------------------------------------------
Other - Medical Research
Medical - Dental Clinic
Marketing Agency - Digital Marketing Services
Legal - Mediation Services
Insurance - Life Insurance
-----------------------------------------------------
🚀
6 New LinkedIn Ad Templates Published
🚀-----------------------------------------------------
Real Estate - Real Estate Appraiser
Real Estate - Escrow Officer
Marketing Agency - AI Marketing Implementation Specialist
Marketing Agency - Conversion Rate Optimization
Business Coaching & Consulting - Diversity, Equality & Inclusion Consultant
Creative - Interior Architecture Firm
------------------------------------------------------
📣
1 New Snapshot
📣------------------------------------------------------
Finance - Bookkeeper
Overview
We're excited to announce that
snapshot and public API support
is now available for all our recently launched custom field types (URL, Date & Time, Rich text, Users field, Image support in Radio and Checkbox fields - https://highlevel.canny.io/changelog/introducing-new-custom-fields)With these enhancements, you can now seamlessly replicate custom field configurations across sub-accounts using snapshots and manage custom field data programmatically through public APIs.
Whether you're setting up multiple sub-accounts, building integrations, or automating processes, these additions make it easier to manage, reuse, and scale your custom fields across HighLevel.
What's new?
1. Snapshot support for new custom field types
- You can now include the newly introduced custom field types in your snapshots, eliminating the need to manually recreate field configurations across sub-accounts.
Why it matters:
Save time, maintain consistency, and simplify sub-account setup by reusing custom field configurations through snapshots.2. Public API support for new custom field types
- We've also extended our public APIs to support all the newly introduced custom field types, allowing developers to work with these fields programmatically.
Why it matters:
Build more flexible integrations, synchronize custom field data with external applications, and automate processes without relying solely on manual updates.Availability
: Both snapshot and public API support are now live in production and available to all accounts. If you've already enabled the new custom field types through Labs,
you can start taking advantage of these enhancements without any additional activation.With snapshot and public API support now available, we're making custom fields more powerful, reusable, and easier to integrate into your everyday business processes.
☁️ Your AI Studio apps can now have a real backend
You've built a great app in AI Studio, and now it needs to remember things. It needs to know who's signed in and store the photos people upload. Until now, that meant wiring up a backend yourself.
Not anymore.
Open
More → Cloud
and turn it on from Overview
. In about a minute, HighLevel creates a private backend just for that project, with a database
, user accounts
, and file storage
. There's nothing extra to connect.- You can keep building while it sets up.
- If setup stops, your app is untouched, and Try againpicks up where it left off.
- AI Studio checks with you before it builds anything against Cloud.
🌟
Once Cloud is running, here's what you get:
🗃️ Database: your app's memory
- See every table, roughly how many rows it holds, and whether row-level security is on.
- Open a table to add rows, double-click a cell to edit it, or select rows to delete them.
- Need a new table or policy? Just ask AI Studio in chat and it handles the schema.
- Slow or costly database? Optimizesends a health check to chat. It uses credits, like any message.
- Daily Backupssnapshot your schema and rows (not storage files or app code).
- Restorereplaces the live database with a snapshot. The app pauses its database access for a few minutes while that happens. If the schema no longer matches your code, ask chat to patch it.
👥 Users: the people using your app
- Watch signups on a chart and search people by email.
- Create new useradds someone already confirmed, with no email sent.Send invitationemails them a link to set a password.
- Open a person to see how they sign in, or Delete user. Deleting can't be undone.
- Signup, invite, and reset emails go out through your account's email, and the links open your app.
Auth settings
lets you shape sign-in:
- Email confirmation is required by default. Auto-confirm emailis for testing only.
- Close registration any time with Allow new sign-ups. Existing users stay signed in.
- Reject passwords found in public breaches, and set your own password rules.
- Set your Site URLandRedirect URLs. A mismatch here is the usual reason a login fails. Preview URLs are handled for you, and you can add your own, including mobile links likemyapp://callback.
⚠️
Heads up for v1:
sign-in supports email and password only. We'll expand to more sign-in methods in future releases.📁 Storage: where files live
- Bucketshold uploads. Public buckets open for anyone with the link. Private ones are for signed-in users.
- Names use lowercase letters, numbers, and hyphens (3 to 63 characters) and can't be changed later.
- Upload, organize into folders, download, delete, rename, and Copy URL. Renaming a file changes its URL.
- Set an Upload size limitand review who can read and write through RLS policies.
📈 Advanced settings: grow at your pace
- Database sizestarts atTiny (free). Move up to Mini, Small, Medium, Large, or X-Large, or back down, once an hour. Each size shows its hourly price. A change takes a few minutes and briefly restarts the app.
- Database storagecan grow, never shrink, up to 4 times a day. You pay hourly for the space you set aside, even when paused.
- File storagegrows and shrinks with your files, and you pay for what's actually stored.
- Pausestops access to your data while keeping it safe.Resumewakes it.
- If your wallet can't cover Cloud, it pauses itself. Nothing is deleted, and Wake upreturns once billing is fixed. You can still move down to Tiny.
- Remove Cloudpermanently deletes that project's database, users, and files. Export tables as CSV and download files first. Other projects aren't affected.
🛡️ A friendly watchdog
If the security advisor spots a problem, a card appears on
Overview
. View issues
lists them, and Try to fix
asks AI Studio to repair them.- Fix criticalissues before you publish.
- Warningsare worth a look but aren't urgent.
✅ Good to know
- Cloud works with apps built on TanStack Start. For an existing React project, go toProject Settings → Migrate to SSRfirst. That creates an upgraded copy and leaves your original live. Migrating doesn't turn Cloud on.
- Your published site stays as is until you publish again.
- Sharing or remixing doesn't copy your Cloud data. The copy can still send requests to the original project's Cloud, following its access rules.
new
Studió AI
AI Studio: Sell Products and Accept Payments
You can now take payments in apps built with AI Studio. Connect the products in your catalog, ask the agent to “add payments”, and your app gets a secure, hosted checkout.
Payments in AI Studio uses HighLevel’s native payments. Your products, orders, payment providers and subscriptions are the ones already set up in your HighLevel account. There’s nothing extra to set up.
What’s new
Payments in a few clicks
- More → Paymentsis a new settings tab. Turn Payments on, switch between test and live mode, and choose which catalog products your app can sell.
- Choose how each product is priced: one fixed price, a selected set of variations (sizes, tiers, plans), or the product’s full catalog.
- Only the products and prices you allow can be shown or charged. Your settings decide what buyers can buy.
The agent adds the checkout for you
- Ask the agent to add payments. It shows a card asking you to approve the connection, then builds a storefront and checkout into your app.
- The payment code is managed by the platform, so neither you nor the agent can break it by accident. Edits to it are restored on the next turn.
A hosted checkout
- Card details are entered and processed in the platform’s hosted checkout, never in your app’s code.
- PayPal express checkout is supported.
- Coupon codes can be entered at checkout, and a fully discounted order goes through without asking for a card.
- Subscriptions work in checkout and upsells, including carts with more than one subscription product.
- Your colours: the checkout picks up your site’s colour scheme instead of a fixed default.
- Bot protection runs on every purchase.
One-click post-purchase upsells
- After a successful purchase you can show buyers an offer page. They can accept it with one click, without entering card details again.
- One-click works with saved cards from Stripe (3D Secure supported), Square, Authorize.net, NMI, Adyen and Mercado Pago. Other payment methods use the regular payment form.
- An upsell can only be charged after the original order is paid, and only once per order, even with several tabs open.
Product pages
- Generated storefronts show product listings and detail pages from your catalog, with thumbnails and formatted descriptions.
Availability
- Payments currently works only with apps built on TanStack Start. Other project types won’t see the option yet.
- To use Payments in an existing React project, migrate it. Go to Project Settings → Migrate to SSR. This makes an upgraded copy of your project and leaves the original unchanged and live. You can also test the new copy before you publish it.
Load More
→