HighLevel Updates: October 2026 Roundup

Twelve days into October the scoreboard reads one withdrawn price rise, a storefront, a backend, a schema dashboard and one better report. The headline is a reversal. On October 12, one day before it was due, HighLevel cancelled the voice pricing update it had announced on October 1, after the underlying providers confirmed the change was off. Voice rates stay as they are. The messaging and phone number rental increases from September 21 are a separate notice and still land on October 13, so the audit is narrower than it looked last week. The same day, every website and funnel gained an SEO and AEO tab where schema is managed for the whole site rather than page by page, with a coverage score, a Might be outdated flag for pages republished since their schema was written, and bulk AI generation you review before publishing. Also on October 12 the Meta Pixel moved InitiateCheckout to the moment a buyer reaches checkout instead of the moment they submit payment, so the step between starting checkout and entering card details finally shows drop-off, and InitiateCheckout counts will rise. AI Studio took two of the earlier days. On October 8 apps built there could sell products from your catalog through HighLevel's hosted checkout, with PayPal express, coupon codes, subscriptions and one-click upsells on a saved card, and every published site started reporting page views, opt-ins and every form submission without a tracking code. On October 9 each project gained Cloud, a private backend with a database, user accounts and file storage, switched on from More, then Cloud, and running about a minute later. On October 6 the Lead Source Report started showing monetary value for Open, Won, Lost and Abandoned, and any count above zero now opens the opportunities behind it. The same day A2P registration status went live on the phone numbers page, which ends the habit of sending from an unregistered number and collecting error 30034, and recurring appointment notifications were rebuilt so a series sends one confirmation and custom recurrences send anything at all. On October 10 the custom field types released in September, URL, Date and Time, Rich text, Users and image options in Radio and Checkbox fields, gained snapshot and public API support, which takes field setup out of manual sub-account onboarding and lets an integration create and update them. The rest of this page covers the releases from the final week of September that you are actually using in October: two-way voice Ask AI on the mobile app, an AI layout builder for invoices, dashboard widgets with filter conditions that persist, snapshot support for Company and Custom Object Smart Lists, Meta campaign budget control in Ad Manager and scoped unsubscribes for Community email.

This page covers October 2026 and updates as releases land. September is closed and documented in full in the September roundup.

The October 13 voice price rise was cancelled

On October 12, one day before it was due, HighLevel cancelled the voice pricing update. The October 1 notice had repriced inbound minutes in 19 countries and outbound minutes to 21 destinations, all effective October 13. The new notice says the underlying providers confirmed the cancellation, so the affected voice rates stay exactly where they are. The messaging and phone number rental changes announced on September 21 are a separate notice and still take effect on October 13.

• Voice rates are unchanged. Nothing to do and nothing to reset. Local and mobile incoming minutes keep their current list prices, as do all 21 outbound destinations. If you already raised a resale price for October 13, put it back
• Messaging and numbers still move on October 13. Outbound SMS rises for twelve destinations and monthly number rentals rise across eleven countries. Hong Kong local numbers are the outlier, going from $6.00 to $14.70 per month, which is a 145 percent increase on one line item
• What the cancelled notice would have done. Local incoming minutes were going to $0.0115 per minute across fifteen countries, mobile incoming to $0.0125 across seven, the United Arab Emirates toll free incoming rate from $0.3675 to $0.4220, and Morocco mobile outbound from $1.0748 to $1.2354 per minute. None of that applies now
• Read the first invoice after October 13 anyway. Two notices sharing one effective date, with one of them withdrawn the day before, is how a wrong line item goes unnoticed. Check voice minutes against September and check SMS and rentals against the September 21 table

Our HighLevel pricing guide covers the plan tiers these usage rates sit on top of, and Voice AI runs on the same per-minute telecom rails, so the reversal reaches it too.

Sites gained a schema dashboard and real checkout numbers

On October 12 schema markup moved out of the page builder. Every website and funnel now has an SEO and AEO tab holding a schema dashboard for the whole site. Keeping schema current used to mean opening each page in the builder one at a time, which is why most sites drifted out of date.

• A coverage score for the site. The Schema coverage card rates the site Needs work, Getting there, Good or Excellent, with counts for Up to date, Might be outdated and No schema
• Every page on one screen. Each page lists its schema types, its status of Up to date, Might be outdated, No schema, Unpublished or Unsaved, and when its schema was last updated. Search by page name or path and filter by status
• Bulk generation with review. Select pages, click Generate schema, watch progress live, then read the output before it goes anywhere. Generated or edited schema stays Unsaved until you click Save and publish, and Discard throws it away
• Manual control is still there. Add schema on a page that has none, or click any schema tag to open the editor. Editing inside the page builder works exactly as before and both views stay in sync
• Stale schema gets flagged. A page edited and republished two or more times since its schema was created is marked Might be outdated, which is the check nobody was running by hand
• One trap. Running Generate schema on a page that already has schema replaces it entirely, so review before you save, especially where the markup was written deliberately

Nothing to switch on and no data loss. Existing schema appears in the tab automatically and pages without any are flagged so they can be fixed in bulk. Accurate markup is what makes a page eligible for Google rich results and what helps AI answer engines read and cite a business, so this is the first schema tool in the platform aimed at a site rather than a page. Run the Might be outdated filter first, then generate for the No schema list.

The same day, Meta Pixel tracking stopped counting checkout twice. InitiateCheckout now fires when a buyer reaches the checkout page rather than when they submit payment, and AddPaymentInfo carries full order and customer detail. It applies to funnels, websites and stores that have the Meta Pixel set up with the InitiateCheckout event enabled.

• When it fires now. On page load for store checkout pages and for any page where InitiateCheckout is set at page level, and on the buyer's first click, tap or keystroke in an order form everywhere else. One-step, two-step, popup and the new order form are all covered
• No double counting. It fires at most once per page visit even where a page holds several order forms or more than one trigger, and browser autofill, password managers and fields focused automatically on load do not set it off
• Abandoned carts and express wallets. A buyer returning through an abandoned cart link triggers the event once the saved cart has loaded, so the cart value and products are included. A buyer who goes straight to Apple Pay without touching the form triggers it when payment starts
• Richer AddPaymentInfo. Order value, currency, product IDs and hashed email, phone, name and external ID where available, which is what Meta uses to raise Event Match Quality and improve attribution
• Expect the counts to rise. InitiateCheckout now includes buyers who reach checkout and leave, so the gap between it and AddPaymentInfo is real drop-off for the first time. Any report or automated rule built on cost per InitiateCheckout needs a new baseline
• Timing note. Page-level settings can take up to 24 hours to apply on pages that are already published. Editing and saving the page applies them at once

Consent handling and the Conversions API are unchanged. Nothing is sent when a visitor has not accepted advertising cookies, and browser and server events are still sent together and deduplicated in Events Manager. Free orders still skip AddPaymentInfo, with one change: an order fully covered by a gift card now sends it with a value of 0. If InitiateCheckout is not enabled on your pixel, nothing about this release reaches you.

AI Studio became a real app platform

In two days AI Studio stopped being a page builder. Three releases landed. Apps built in AI Studio can take payments through HighLevel's own checkout, and every published AI Studio site now reports its own traffic and opt-ins with no tracking code to install. Since October 9 each project can also run a private backend of its own.

• Payments live in a settings tab. More, then Payments. Switch payments on, pick test or live mode, and choose which catalog products the app is allowed to sell. Each product is priced as one fixed price, a chosen set of variations, or its full catalog range, and only what you allow can be shown or charged
• The agent builds the checkout for you. Ask the agent to add payments, approve the connection on the card it shows, and it builds a storefront and checkout into the app. The payment code is managed by the platform, so edits to it are restored on the next turn rather than quietly breaking the cart
• A hosted checkout, not your code. Card details are entered and processed in the platform's hosted checkout. PayPal express is supported, coupon codes work, a fully discounted order goes through without asking for a card, subscriptions work including carts holding more than one subscription product, and the checkout picks up your site's color scheme instead of a fixed default
• One-click post-purchase upsells. An offer page after a successful purchase charges a saved card with one click, on Stripe with 3D Secure, Square, Authorize.net, NMI, Adyen and Mercado Pago. Other payment methods fall back to the regular form. An upsell charges only after the original order is paid, and only once per order even with several tabs open
• Analytics with nothing to install. More, then Analytics. Page views, unique visitors, opt-ins and opt-in rate with trends and the change on the previous period, plus top pages, time on page, traffic sources, devices, browsers and geography. Form Submissions lists every lead with a link to the contact, filterable by form and date, and a workflow can be built from there
• Visit history lands on the contact. Contacts created from an AI Studio site keep the pages they viewed, where they came from and the form they submitted, under Contacts, Contact details, Activity. Sites, then Analytics, then AI Studio puts every project next to your funnels and websites

Two caveats decide whether this reaches you this week. Payments works only on apps built on TanStack Start, so an existing React project needs Project Settings, then Migrate to SSR, which makes an upgraded copy and leaves the original live while you test. Forms connected before October 8 keep counting opt-ins, but linking a submission to the pages that visitor saw first needs a reconnect and a republish. AI Studio left Labs on September 22, so this is a general release rather than a beta, and the ecommerce guide covers the catalog, orders and payment providers these checkouts run on.

On October 9 AI Studio added the part that was missing: a backend. More, then Cloud, then switch it on from Overview. About a minute later the project has a private database, user accounts and file storage with nothing to connect. Setup runs in the background so you can keep building, a failed setup leaves the app untouched and Try again resumes it, and AI Studio asks before it builds anything against Cloud.

• A database you can actually open. Every table with its approximate row count and whether row-level security is on. Add rows, double-click a cell to edit it, select rows to delete them. Ask chat for a new table or policy and it writes the schema. Optimize sends a health check into chat and costs credits like any message. Daily Backups snapshot schema and rows, not storage files or app code, and Restore swaps the live database for a snapshot while database access pauses for a few minutes
• User accounts without an auth provider. A signup chart, search by email, Create new user for someone already confirmed, Send invitation for an email link to set a password. Signup, invite and reset emails go out through your account's email and the links open your app. Email confirmation is required by default, Allow new sign-ups closes registration without signing existing users out, passwords found in public breaches can be rejected, and Site URL and Redirect URLs decide whether a login works at all. Version one is email and password only
• File storage in buckets. Public buckets open to anyone with the link, private ones only to signed-in users. Bucket names are lowercase letters, numbers and hyphens, 3 to 63 characters, and permanent. Upload, folders, download, rename, delete and Copy URL, with an upload size limit and RLS policies controlling read and write. Renaming a file changes its URL
• Hourly pricing you set yourself. Database size starts at Tiny, which is free, and moves up to Mini, Small, Medium, Large or X-Large, or back down, once an hour, with each size showing its hourly price. Database storage grows but never shrinks, up to four times a day, and bills for the space reserved even while paused. File storage bills for what is actually stored. Pause stops access and keeps the data, and a wallet that cannot cover Cloud pauses it rather than deleting anything
• A security advisor on the Overview. When the advisor finds a problem a card appears, View issues lists them and Try to fix hands them back to AI Studio. Critical issues are worth fixing before you publish, warnings are worth a look

Three things to know before switching it on. Cloud needs an app built on TanStack Start, the same requirement as payments, so a React project goes through Project Settings, then Migrate to SSR first, and migrating does not turn Cloud on by itself. The published site stays as it is until you publish again. Sharing or remixing a project does not copy its Cloud data, and the copy can still send requests to the original project's Cloud under that project's access rules. Remove Cloud permanently deletes the project's database, users and files, so export tables as CSV and download the files first.

The Lead Source Report stopped being a counter

On October 6 the Lead Source Report widget learned what each channel is worth. Until now it counted leads by source and put a single value on the total. It now prices every status and lets you click through to the records, which is the difference between knowing a channel is busy and knowing it pays.

• Value for every status. Open, Won, Lost and Abandoned each carry their own monetary value on the source row. Compare won value against lost value per channel and the spend question answers itself
• Drill down from any number. Click any count greater than zero under Total leads, Open, Won, Lost or Abandoned and the exact opportunities behind it open. No separate search, no rebuilding the filter by hand
• Attribution gaps are visible. Opportunities with no source appear as an N/A row instead of being left out of the report, and the Source filter accepts Is empty and Is not empty. A report that quietly dropped unsourced records was flattering every channel in it
• Lead value permissions still hold. The figures show only to users who can view lead value, so the drill-down does not hand revenue numbers to staff you scoped out of them

Row heights and column widths were tidied in the same release, so the table survives a laptop screen. HighLevel lists support for a custom field as the revenue source as what comes next. Run the Is empty filter first. If a meaningful share of your opportunities land in the N/A row, every channel comparison you have made this year was built on a partial table, and the CRM guide covers where sources get set in the first place.

A2P registration stopped being a black box

On October 6 two smaller releases landed next to the Lead Source Report, and both remove a guessing game.

• Live A2P registration status. Every number attached to an A2P campaign now shows Pending, Registered or Failed, and a number fully registered with carriers carries an A2P Verified tag on the phone numbers page. Existing numbers were updated automatically
• Error 30034 becomes avoidable. A number previously showed only that it had been submitted. Carrier registration takes anywhere from minutes to several days, and anything sent inside that gap failed with error 30034 and usually a support ticket. You can now see the moment a number is ready to text, and spot a rejected registration without asking anyone
• Rejection guidance that matches how you registered. On October 8 the View required fixes modal was rewritten. Common rejection reasons now carry separate instructions for Chat Widget quick setup and for manual setup, because the fix sits in a different place for each. Where carriers require exact wording, the steps give it. Where the cause is something the platform generates, such as the chat widget's consent text, it says so and points you to support instead of spending a resubmission, and where a resubmission cannot help, such as a business type mismatch, it says what has to change first
• One confirmation per recurring booking. Default recurring appointments sent a confirmation for every occurrence. They now send one that covers the whole series, while reminders and follow-ups still fire per occurrence
• Custom recurrences get notifications at all. Custom recurring appointments created in-app previously sent nothing. They now send confirmations, reminders, follow-ups, reschedules and cancellations, following the This appointment, All appointments or This and following option you pick when you make the change
• The pattern shows in the message. Custom recurrence notifications can print the recurrence next to the date, for example October 14, 2026 12:00 PM (reoccurs every Thursday), so a recipient can tell whether a change hit one session or the series. Your template needs the appointment date and time custom value for that to appear, and this covers calendar notifications only, not workflows

Registration usually completes within 24 hours but the timing belongs to the carrier, so a Pending status inside that window is expected rather than broken. Check the pill before the first send from any number you bought this month. The appointment changes need no setup and apply to newly booked appointments and to any appointment you edit.

Ask AI gained a voice and invoices gained a designer

On September 25 Ask AI in the mobile app learned to hold a spoken conversation. Tap the mic and speak. Your words transcribe live, the reply streams back as audio with the text highlighting in time with the voice, and you can cut in mid-sentence to redirect it. The mic pauses on its own when the assistant asks a question or shows an approval card, then resumes once you answer. A dropped connection reconnects into the same conversation. Voice and typed messages share one thread and one history. The web version already did this. Mobile reaching parity is the part that counts, because the phone is where you are between appointments.

On September 28 invoices gained an AI layout builder. Describe the invoice you want and it builds the layout. Upload one you already send and it recreates it. From there you adjust individual elements in a visual builder, step back to an earlier version from the chat, then publish the layout to the invoices your customers see. Layouts sit in their own list with preview, clone, rename and delete, and each one keeps a record of who changed it. Invoice design in HighLevel is no longer a choice between fixed templates.

Dashboard widgets and CRM segments became reusable

On September 24 general widgets on sub-account dashboards became editable, and on September 29 segments became portable. Taken together these are the operational changes agencies will feel first.

• Permanent filter conditions. A Conditions tab filters any general widget by assigned user, tags, source, lead value, custom fields and attribution, and the filter holds every time the dashboard is opened rather than resetting
• Date range overrides. Lock a single widget to its own period, independent of the dashboard date filter, and compare it against last period or last year. Each widget face now shows which date property and range it calculates on
• Smart Lists travel in snapshots. Company Smart Lists and Custom Object Smart Lists became snapshot assets on September 29. Configure segmentation once and deploy it to every destination sub-account. Refreshing an existing snapshot picks up lists created since it was saved. Include the objects and fields the list filters on in the same snapshot, otherwise it arrives with nothing to filter on
• Field options can finally be deleted. Dropdown, multi-select, radio and checkbox options on Custom Objects and Companies can be removed, matching what Contact and Opportunity fields already allowed. Records holding a deleted option keep the value, the option simply leaves future selection, and the interface shows how many records use it before you commit
• New custom field types travel too. On October 10 snapshot and public API support went live for the custom field types released in September: URL, Date and Time, Rich text, Users and image options in Radio and Checkbox fields. Those field configurations now replicate across sub-accounts inside a snapshot instead of being rebuilt by hand, and the create custom field endpoint accepts every new type, so an integration can create and update them programmatically. Both are live in production for all accounts, and field types already switched on through Labs need no further activation

Snapshot level segmentation is the piece to test first. White label agency setups rebuild the same Smart Lists in every client account, and this removes that step from onboarding. With the new field types in snapshots as well, a destination sub-account can arrive with its objects, its fields and its segments already built. The CRM guide covers how companies, custom objects and smart lists fit together.

Ad Manager, Communities and a Mexico number warning

On September 29 Ad Manager gained Meta campaign budget control. Choose whether the budget sits at campaign level, where Meta distributes it across ad sets automatically, or at ad set level where you set each one yourself. Budget sharing across ad sets can be switched on, and supported budget and bid strategy settings are managed inside the campaign builder instead of in Meta.

On October 8 Community posting opened up to the API. The Social Planner public API can now list eligible community members, check that a member is still active and permitted, and schedule or publish a community post as a specific member. Social Planner rechecks eligibility at publish time, so a post never goes out under the wrong identity, it fails with a readable error instead. Connect the group first under Marketing, Social Planner, Settings, Social Accounts. Draft posts need no member selection. This matters if you run announcements for client communities from outside the platform, which until now meant posting by hand.

On September 30 Community email unsubscribes stopped being a platform wide switch. Clicking unsubscribe in a Communities email could previously opt a member out of all platform email. The preference now applies only to the community that sent the email and the specific notification type, such as a comment mention or an at-everyone post. If you run a community alongside marketing email to the same people, this closes a quiet list attrition path you probably could not see.

Mexico local numbers no longer send SMS. An upstream carrier migration ended SMS support on Mexico local phone numbers, and on September 29 HighLevel added an SMS unavailable pill in the Phone Numbers table under Manage Numbers so admins can spot affected numbers at a glance. It applies to existing and newly purchased numbers. Audit your Mexico inventory now. The voice minute increase announced for October 13 was cancelled on October 12, but the September 21 notice covering international SMS rates and monthly number rentals still takes effect that day.

Twelve days in, October has produced a withdrawn price rise, a storefront, a backend, a site-wide schema dashboard, one better report and three fixes that remove support tickets. The September releases described above are documented in full in the September 2026 roundup, and this page fills out as October does. October 13 is still the date to watch, but only for international SMS rates and phone number rentals now that the voice increase has been withdrawn. The weekly roundup tracks releases as they land.

Frequently Asked Questions