HighLevel Release Notes
258 release notes curated from 1 source by the Releasebot Team. Last updated: Sep 5, 2026
- Sep 4, 2026
- Date parsed from source:Sep 4, 2026
- First seen by Releasebot:Sep 5, 2026
Improved: Dynamic Value Chips with Improved error segmentation
HighLevel adds three-state dynamic value chips in the workflow builder, making it easier to tell valid, missing-source, and invalid values apart. It also now matches handlebars spacing, reducing false red errors while keeping execution behavior unchanged.
What's new?
Dynamic value chips have three states now instead of two. A dynamic value chip used to be valid or invalid, so anything the builder couldn't resolve came back red with "value not recognized". The new middle state is a yellow chip, and it covers values that are real on the platform but have no source in the workflow you have open. Giving a clear distinction between values that could render blank and values that won't render at all.
How it works
Every chip lands in one of three states:
- Blue, value available in this workflow. The workflow can fill it, whether that comes from the contact record, a system value like the current date, or an earlier step.
- Yellow, value not available in this workflow. The value is real on the platform, but nothing in this workflow supplies it, for example {{sheet.10.rowNumber}} in a workflow with no Google Sheets step. It renders blank unless another workflow passes it in through Add to Workflow with pass input trigger parameters.
- Red, value doesn't exist on the platform. Nothing on the platform matches it, for example {{applesheet.10.rowNumber}}, so no workflow will render it.
Spacing inside the handlebars stopped mattering too. The platform stores Attribution Url as {{ attribution.first.url }} with the spaces, so typing {{attribution.first.url}} used to come back red. Both forms match now.
Why we built it
Earlier all fields which wouldn't render would show an error state with a red chip. However you might drop {{invoice.url}} into an Add Notes action on a workflow that no invoice trigger starts, or hand a value from one workflow to another through Add to Workflow.
The red chip earlier called those values unrecognized and pointed you at the picker, so a configuration you built on purpose read like a mistake you had made. Splitting the states puts red back on the cases worth acting on. Red now means the value is wrong. Yellow means check whether something else supplies it.
Additional Notes
Yellow is a warning, not a block. Save and publish the workflow as usual.
Red still catches typos, for example {{contact.frist_name}}.
This changes the UI only. Values resolve at execution time the way they did before, so anything that ran before still runs.
Preview
Original source - Sep 4, 2026
- Date parsed from source:Sep 4, 2026
- First seen by Releasebot:Sep 5, 2026
📞 More Reliable Missed Call Text Back with Smarter Number Selection
HighLevel improves Missed Call Text Back with smarter sender selection, automatically using an eligible messaging number when the called number cannot send SMS. This helps more missed callers receive follow up texts while staying aligned with messaging requirements.
📥 Overview
A missed call can be a missed opportunity, and your follow up text should not fail simply because the number your customer called cannot send SMS.
Previously, Missed Call Text Back always tried to send the follow up SMS from the same number your customer called. But some numbers are designed primarily to receive calls or may not currently be eligible to send SMS. In those cases, your text back could fail even when another messaging ready number was available in your account.
We’ve improved this experience. HighLevel will now automatically choose an eligible sending number, helping more of your missed call follow ups reach your customers while staying aligned with messaging requirements.
The result is simple: more missed callers receive your follow up message, while your texts stay aligned with messaging requirements.
📊 What’s New?
✅ Your Missed Call Text Back Has a Better Chance of Reaching the Customer
When a customer calls and you miss them, we’ll still try to text them back from the number they called first, as long as that number can send SMS.
If it can’t, system will automatically look for the next best option:
- A number you’ve successfully messaged this contact from before
- Your default outbound number
- Another eligible messaging number available in the location
This is especially helpful when calls come through number pools, call tracking numbers, unverified toll free numbers, or other numbers that aren’t eligible to send SMS. Instead of attempting the text from a number that can’t send, we’ll use an eligible number when one is available.
💬 What Will Your Customers Notice?
Most of the time, nothing changes. The missed caller simply receives your follow up as expected.
In some cases, the SMS may come from a different number than the one they originally called. That’s intentional. We’re choosing a number that can actually send the message rather than letting an important follow up fail.
🔍 Why It Matters
When someone calls your business and you cannot answer, that first follow up can be important for keeping the conversation going.
With smarter number selection, you can:
- 📩 Reach more missed callers instead of losing the follow up because one number cannot send SMS
- ⚡ Keep follow ups automatic without manually managing which number should be used
- 🛡️ Stay aligned with messaging requirements such as A2P and toll free verification
- 🤝 Respond to potential leads sooner and keep conversations moving even when you miss the initial call
In short, if you have an eligible number available, we’ll automatically use it to give your missed call text a better chance of reaching the customer.
💡 Good to Know
Answered calls will continue to work as before and will not trigger a text back.
If Missed Call Text Back is disabled in your Phone System settings, no message will be sent.
Your contacts’ communication preferences and DND settings will continue to be respected.
If there is no eligible number available, you’ll see the failed attempt in the conversation along with the reason, giving you clear visibility into what happened.
Original source All of your release notes in one feed
Join Releasebot and get updates from HighLevel and hundreds of other software products.
- Sep 3, 2026
- Date parsed from source:Sep 3, 2026
- First seen by Releasebot:Sep 4, 2026
🔐 Client Portal: "User login" Workflow Trigger Now Supports the New Client Portal Experience
HighLevel adds Client Portal login automation support, so the User login workflow trigger now fires for the new Client Portal experience too. It also introduces a dedicated Client Portal trigger category for clearer, easier workflow setup.
Overview
The User login workflow trigger now fires for logins from the new Client Portal experience — not just legacy membership logins. We've also added a dedicated Client Portal category in the workflow trigger picker, so all Client Portal triggers live in one place.
What's New
New Client Portal logins now fire the "User login" trigger
Successful logins from the new Client Portal experience now emit the same workflow trigger event as legacy membership logins. Any workflow already using the User login trigger will start running on these logins automatically — no reconfiguration required.
New "Client Portal" category in the trigger picker
A dedicated Client Portal category now groups all Client Portal triggers together:
- User login — moved from Courses
- Client portal file uploaded — moved from Membership
Clearer helper text
The User login trigger now spells out that it covers both legacy membership logins and logins from the new Client Portal experience — removing the confusion caused by its old placement under Courses.
How to Use
Automate on Client Portal member login
Open the Workflow Builder.
Click Add trigger and search for User login.
Select it under the new Client Portal category (previously found under Courses).
Save your workflow — it will now fire on both legacy membership logins and logins from the new Client Portal experience.
Already using this trigger? No action needed. Existing workflows continue to run as-is and will automatically pick up login events from the new Client Portal experience.
Why This Matters
Agencies on the new Client Portal experience previously had no way to automate off a member login, because the trigger only covered legacy memberships. Trigger placement was inconsistent too — login sat under Courses while file upload sat under Membership — making it unclear what each trigger actually covered. This update closes the gap and puts both triggers where you'd expect to find them.
Original source - Sep 2, 2026
- Date parsed from source:Sep 2, 2026
- First seen by Releasebot:Sep 3, 2026
Privacy Policy + T&C URLs on Toll-Free Verification
HighLevel adds required Privacy Policy and Terms & Conditions URLs to toll-free verification, helping new submissions pass carrier checks and avoid rejection. The update adds two live fields in Step 3 while leaving existing verified numbers unchanged.
Overview
Toll-free verification now asks for your Privacy Policy URL and your Terms & Conditions URL. Carriers will begin rejecting any new toll-free verification without both links on September 15, 2026, so both fields are live now and required before you submit.
What's new
Two new fields on Step 3 (Messaging use case), directly below your opt-in workflow images. Both are required before you can send the submission.
Steps 1 and 2 are unchanged. Existing verified numbers are out of scope and need no update or re-verification.
Previously
The form didn't ask for policy links, so a missing o policy page only surfaced when Carriers rejected the submission.
Why it matters
From September 15, 2026, a toll-free submission without both links is rejected outright. Providing them now keeps your new numbers moving.
Original source - Sep 1, 2026
- Date parsed from source:Sep 1, 2026
- First seen by Releasebot:Sep 2, 2026
Delete Saved Payment Methods on SaaS v2 Sub-Accounts
HighLevel adds saved payment method deletion for sub-accounts on SaaS v2, making billing easier to manage.
What's New
You can now delete a saved payment method from your sub-account. If a card is outdated, expired, or just no longer needed, you can remove it directly instead of leaving it on file indefinitely.
Why It Matters
This gives you full control over the cards saved to your account and keeps your billing dashboard clean and easy to manage — no more sorting through payment methods you no longer use.
Notes
Available for sub-accounts on SaaS v2 system.
Original source Similar to HighLevel with recent updates:
- Smokeball release notes144 release notes · Latest Sep 4, 2026
- Cosmolex release notes20 release notes · Latest Jul 30, 2025
- PracticePanther release notes36 release notes · Latest Aug 11, 2026
- Salesforce release notes71 release notes · Latest Sep 1, 2026
- Microsoft release notes820 release notes · Latest Sep 4, 2026
- Zoom release notes210 release notes · Latest Aug 31, 2026
- Aug 29, 2026
- Date parsed from source:Aug 29, 2026
- First seen by Releasebot:Jun 1, 2026
- Modified by Releasebot:Aug 29, 2026
Introducing New Templates
HighLevel adds new web templates across websites, funnels, email, social, and ad channels, plus a workflow template and a revamped existing template. The update focuses on customizable, professional designs that streamline marketing and improve user experience.
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
🚀 1 New Website Templates Published 🚀
Business Coaching & Consulting - 1
🚀 1 New Funnel Templates Published 🚀
Marketing Agency - 1
🚀 1 New Email Templates Published 🚀
Business Coaching & Consulting - 1
🚀 4 New Social Templates Published 🚀
Other - 2
Home Services - 2🚀 2 New Facebook Ad Templates Published 🚀
Automotive - Car Detailing
Business Coaching & Consulting - Education Tutor🚀 5 New Google Ad Templates Published 🚀
Other - Cell Phone Repair
Medical - Hair Regrowth
Marketing Agency - Digital Content Creator
Legal - Personal Injury Law Firm
Insurance - Commercial Insurance Services🚀 7 New LinkedIn Ad Templates Published 🚀
Finance - Financial Investor
Insurance - P&C Insurance Advisor
Marketing Agency - Digital Networking Services
Creative - Engraving Shop
Business Coaching & Consulting - Learning Specialist
Real Estate - Home Loan Specialist
Finance - Financial Record Keeper🚀 1 New Workflow Templates Published 🚀
Industry-Specific - Insurance Policy Renewal Reminder
💥 1 Revamped Existing Template 💥
Updated templates featuring new copy, refreshed images, and improved navigation and heading tags. These enhancements aim to deliver a more engaging user experience and provide relevant, useful content, ultimately improving the functionality and visual appeal of our templates.
Business Coaching & Consulting - Career Coach
Original source - Aug 28, 2026
- Date parsed from source:Aug 28, 2026
- First seen by Releasebot:Aug 28, 2026
Target Announcement Banners by Sub-account and User
HighLevel adds targeted Announcement banners with sub-account and user audience controls, multi-condition AND/OR rules, and CTA links that can open in a new tab for safer external promotions and landing pages.
👀 What's New?
You can now target Announcement banners to specific sub-accounts and users, instead of only broadcasting to your entire agency
Build multi-condition rules — combine conditions like sub-account, country, timezone, or user role, with AND/OR logic
CTA buttons can now open links in a new tab, so you can safely link out to external promotions or landing pages
👷 How It Works:
Open your Announcement, go to the Audience tab
Set Agency-level and Sub-account-level visibility
Under Advanced filters, choose a field (e.g. Sub-account, Country, User Role), an operator, and a value
Add more conditions to refine further — conditions in the same group must all match (AND); add a new group for alternate match paths (OR)
🌟 Why It Matters:
Reach the right audience — stop showing every banner to every user; target only the sub-accounts or users a message is relevant to
Run smarter campaigns — combine multiple conditions to support promotions, onboarding nudges, or role-specific alerts
Link out safely — CTAs can now open in a new tab, so customers keep their place in your app while checking out a linked offer
⏭️ What's Next?
NA
📝 Notes:
Available to all agencies
Sub-account and user targeting is available now;
Setting target
URL in new tab
Original source - Aug 28, 2026
- Date parsed from source:Aug 28, 2026
- First seen by Releasebot:Aug 28, 2026
Workflow Builder: Pick an Email Sender Domain for Each Workflow!
HighLevel adds a Sender domain dropdown in Workflow Settings, letting users send workflow emails from any verified dedicated domain on a sub-account. It brings per-workflow domain control, fallback options, and clearer sender overrides for better deliverability management.
What's new?
Workflow Settings now has a Sender domain dropdown under Sender details. Pick any verified dedicated domain on the sub-account and every email action in that workflow sends from it, the same way domain selection already works in Email Campaigns. If the sub-account has no dedicated domains configured, the dropdown doesn't appear.
How it works
The Sender domain dropdown shows all verified dedicated domains on the sub-account, plus All domains.
All domains: Enter the sender name and email prefix, such as 'marketing'. Emails continue to send across configured domains using weighted distribution configured in the sub account
Specific domain: Select a domain and enter the email prefix. For example, marketing with example.com sends as .
If you enter a full sender email on a different domain. In that case, the sender email overrides the selected domain and a Sender domain mismatch warning appears because mismatched domains may affect deliverability. Sender details set inside an individual email action take final preference over the workflow-level settings.
How to use it
Add and verify your domain under Email Services, Dedicated Domains.
Open the workflow, go to Settings, and pick the domain under Sender domain.
Set a From name and From email, then save. Every email action in the workflow inherits it.
Why we built it
Until now every workflow in a sub-account went out on the same domain. You could change the From address on a workflow, but that only changes the name people see, not the domain the email is actually sent on, so a promo blast and a booking confirmation always rose and fell together. One bad campaign and risks that other email confirmations landing in spam as well.
Now you pick the domain workflow by workflow. Reminders and receipts sit on one domain, promos and cold outreach on another, and a campaign that lands badly costs you that domain alone. You can also try a new domain on a single workflow and watch how it does before moving anything else across.
Simple example
A sub-account sends appointment reminders and payment receipts on mail.acmeclinic.com, and runs its monthly promo nurture on news.acmeclinic.com. The promo volume builds reputation on its own domain, so a bad month there leaves the reminders untouched.
Additional Notes
Only verified domains from Email Services show up in the dropdown.
Sender details on an email action override what the workflow settings have, including the domain.
Email headers configured in your dedicated email settings take priority over the ones in workflow settings.
Original source - Aug 27, 2026
- Date parsed from source:Aug 27, 2026
- First seen by Releasebot:Aug 27, 2026
SMS Action: Test SMS Now with a Country Picker and enhanced UI
HighLevel improves the Send SMS test phone number field with a standard phone input and country flag picker, making test messages easier to send in local format while saving numbers in full international format and simplifying validation errors.
What's new?
The test phone number field in the Send SMS action now uses the standard phone input with a country flag picker, the same one you see elsewhere in the app. Type your number the way you dial it and the test sends. The old "please add country codes" hint is gone, and the error text is now just "Invalid phone number".
How it works
The picker sits in front of the field and defaults to your sub-account's country. Whatever flag is selected, the number is saved in full international format before the test goes out, so the country is always known. Click the flag to open the list and search by country name or dialing code to switch it.
How to use it
Open the Send SMS action in your workflow and scroll to Test Phone Number.
Leave the flag on your sub-account's country, or click it and pick another.
Type the number in local format and click Send test SMS.
Why we built it
Most people type their own number the way they dial it, without a country code. That failed every time and gave an error that read like the number itself was wrong, so a quick test turned into a guessing game about formatting.
Simple examples
An agency on an India sub-account types 9089786755 to test a reminder SMS. The picker already shows the India flag, so the test sends to +919089786755.
The same agency wants to check the copy on a US client's number. They switch the flag to US, type 4088613552, and the test sends to +14088613552.
Preview
Original source - Aug 27, 2026
- Date parsed from source:Aug 27, 2026
- First seen by Releasebot:Aug 27, 2026
Certificate AI Beta is now live
HighLevel adds Certificate AI Beta, letting users create editable certificate designs from simple prompts in minutes. It guides setup with relevant questions, supports full Certificate Builder elements, and lets users customize the result in Memberships → Credentials.
Creating a certificate can now start with a simple prompt. Certificate AI Beta turns your requirements into a complete, editable certificate design in minutes.
What’s new?
- Generate with AI: Describe the certificate you want and let AI create the design for you.
- Guided creation: AI asks relevant questions, such as certificate orientation, to understand your requirements.
- Complete designs: AI can use text, frames, signatures, QR codes, and other Certificate Builder elements to bring your certificate together.
- Fully editable: Continue customizing your AI-generated certificate directly in the Certificate Builder.
- Quick prompts: Start quickly with ideas for course completions, milestones, event participation, training, and more.
How to access
Go to → Memberships →Credentials and describe the certificate you want to create.
Certificate AI is currently in Beta, and we’ll continue improving the experience based on your feedback. 🚀
Original source - Aug 27, 2026
- Date parsed from source:Aug 27, 2026
- First seen by Releasebot:Aug 27, 2026
📅 Date Range Setting Can Now Count Only the Days You Actually Work
HighLevel adds smarter date range counting for Calendars, Services, and Rentals with a new Count available days only toggle. The update helps booking windows skip closed days, work with minimum scheduling notice, and better reflect real availability across different schedules.
Overview
The Date Range setting now has a smarter counting mode across Calendars, Services, and Rentals. A new Count available days only toggle lets businesses ensure their booking window reflects real working days — not calendar days that include weekends or days they're closed.
What's New?
Count Available Days Only Toggle
A new toggle — Count available days only — now appears directly below the Date Range setting. When enabled, the system skips days outside your availability schedule when counting the date range. A business closed on weekends with a 2-day range no longer shows a blank calendar on Fridays — the window extends to Monday and Tuesday instead.
Smarter Interaction with Minimum Scheduling Notice
When the toggle is on, the date range starts counting from the first available day after the minimum scheduling notice period ends. Bookers always see the full number of days configured — even when notice rules push the window forward.
Works Across All Calendar Types
The toggle is available on Meeting Calendars, Services, and Rentals.
Round robin and collective calendars are supported — a day counts as available if at least one assigned team member has availability on that day.
Date-specific hour overrides are also respected: days added via date-specific hours count toward the window, and days blocked via date-specific hours are skipped.
How to Use It
Go to Calendars → Calendar Settings and click edit on the calendar you want to update.
For Services, navigate to Services → Global Settings → Service Settings.
For Rentals, edit a listing and go to Booking Settings.
Find the Date range setting.
Toggle on Count available days only directly below the Date Range input.
Save changes.
Why This Matters
Businesses closed on weekends or operating on custom schedules (Mon/Wed/Fri, Tue/Thu, etc.) no longer see their booking window silently consumed by days they don't work.
Bookers visiting on a Friday no longer see a blank calendar — they see the next actual working days available.
The fix works for any schedule configuration, not just standard Mon–Fri businesses — making it genuinely useful for salons, clinics, field service teams, and any business with a non-standard week.
Minimum scheduling notice and date range now work together predictably — notice clears the required lead time, and the date range fills in the correct number of working days after that.
Reduces customer confusion and support tickets caused by booking widgets appearing empty when availability genuinely exists in the following week.
Original source - Aug 27, 2026
- Date parsed from source:Aug 27, 2026
- First seen by Releasebot:Aug 27, 2026
🔐 Reuse Protected Snapshot Assets Within Your Agency
HighLevel improves protected snapshot assets with more flexible reuse inside an agency while keeping creator protection intact outside the agency. The update also makes it easier to build mixed snapshots and identify protected assets before sharing.
Protected snapshot assets are now more flexible to work with. You can reuse protected assets freely within your own agency while the original creator's protection remains intact when content is shared outside the agency.
What’s New?
- Reuse protected assets within your agency — Use imported protected assets across your own sub-accounts and build new snapshots with them without restrictions.
- Protection applies outside your agency — Protected assets still cannot be shared or resold to another agency.
- Share snapshots containing mixed assets — When a snapshot contains both protected and non-protected assets, eligible assets can still be shared while protected ones are excluded.
- Know what’s protected before sharing — Easily identify which assets in a snapshot are protected before attempting to share it.
- Protection stays with the asset — Whether an asset is imported, reused in another snapshot, or loaded into another sub-account, its protection status is preserved.
Why It Matters
Previously, protected assets remained restricted even within the agency that imported them. This meant that once a protected asset became part of a snapshot, that snapshot could hit a dead end — even when it was only being reused internally.
Now, protection is enforced where it matters: at the agency boundary. You can freely build and reuse protected assets within your agency, while sharing them outside your agency remains restricted.
What You’ll Benefit From
- More flexibility — Reuse imported assets across your agency without unnecessary restrictions.
- No more snapshot dead ends — Continue building snapshots even when they contain protected assets.
- Creator protection remains intact — Protected assets still can't be redistributed to other agencies.
- Greater transparency — Know exactly which assets are protected before sharing a snapshot.
- Aug 27, 2026
- Date parsed from source:Aug 27, 2026
- First seen by Releasebot:Aug 27, 2026
Schedule Availability with Custom Open & Expiry Experiences - Form, Survey & Quiz
HighLevel adds scheduled visibility for Forms, Surveys, and Quizzes, letting teams set when they open and close, choose time zones, and control what visitors see before launch or after expiry, including custom pages or redirects for time-sensitive campaigns.
Forms, Surveys, and Quizzes are often used for time-sensitive campaigns like event registrations, flash sales, webinars, contests, and limited-time offers—but until now, they remained available indefinitely unless manually removed or restricted.
With Scheduling, you can now control exactly when a Form, Survey, or Quiz starts and stops accepting submissions. You can also decide what visitors see before it opens or after it expires, giving you full control over the experience without having to manually manage availability.
What's New
A new Schedule visibility setting is now available in:
- Forms
- Surveys
- Quizzes
Once enabled, you can configure:
- When it should open
- When it should close
- The time zone used for the schedule
- What visitors see before it opens
- What visitors see after it closes
- Whether visitors should see a custom page or be redirected to another URL
Key Highlights
- Schedule when Forms, Surveys, and Quizzes go live - publish them in advance and choose exactly when they should start accepting responses.
- Automatically expire them - stop new submissions once your campaign, promotion, quiz, or registration window ends.
- Flexible scheduling - choose Right away or a specific date for opening, and Never or a specific date for closing.
- Time zone support - configure the time zone used for both opening and closing schedules.
- Custom pre-launch experience - show a tailored message before the scheduled opening time.
- Custom expired experience - decide what visitors see once submissions are closed.
- Redirect visitors - send visitors to another URL instead of showing a custom page.
- Rich content customization - design the message shown outside the active submission window.
- Preview the experience - see how the configured unavailable page will appear to visitors.
- No more manual disabling - scheduled closing automatically prevents submissions after the deadline.
- Existing Forms, Surveys, and Quizzes continue to work exactly as before when scheduling is not enabled.
How It Works
Open your Form, Survey, or Quiz and navigate to its settings.
Enable Schedule visibility.
Configure when it should open: Right away, or Pick a date
Configure when it should close: Never, or Pick a date
Select the appropriate time zone.
Configure what visitors should see outside the active window.
Choose either:
- Show a page to display a customized message, or
- Open a link to redirect visitors to another URL.
At the configured opening time, it automatically starts accepting responses.
At the closing time, new submissions are automatically blocked and visitors see the experience you configured.
Use Cases
- Event Registrations : Automatically close registration once the event or webinar deadline has passed.
- Flash Sales & Limited-Time Offers : Keep a Form or Survey available only during a promotion window and automatically close it afterward.
- Webinars & Campaign Launches : Publish ahead of time while showing a custom “Registration opens soon” experience until launch.
- Quizzes & Contests : Set a fixed participation window so entries stop automatically once the campaign ends.
- Post-Campaign Traffic : Redirect visitors to another offer, waitlist, landing page, or upcoming event after the original experience expires.
- Coupon & Promotional Campaigns : Prevent submissions after a promotion deadline without relying on someone to manually disable the experience.
Why This Matters
Previously, once a Form, Survey, or Quiz was published, it could remain available for submissions indefinitely. For agencies running time-sensitive campaigns, this could result in registrations, leads, quiz entries, or orders continuing to arrive after a campaign had already ended.
Scheduling removes that manual work by automatically controlling availability while still giving agencies complete control over what visitors experience before and after the active window.
As customers have highlighted:
"Clients distributing coupons with automatic expiration preventing post-deadline usage." — Dave Mears
"Critical for agencies and evergreen webinar funnels. Needs: expiring funnel pages based on registration time." — Linn KlosterForms, Surveys, and Quizzes can now follow the lifecycle of your campaigns—open when you're ready, close when the deadline arrives, and guide visitors to the right experience at every stage.
Original source - Aug 27, 2026
- Date parsed from source:Aug 27, 2026
- First seen by Releasebot:Aug 27, 2026
WhatsApp messaging limits: now shown at the portfolio level
HighLevel updates WhatsApp messaging limits to match Meta’s portfolio-based model, showing one shared daily cap across all numbers in a sub-account. The new Messaging Limits panel replaces misleading per-number quotas with clearer, localized guidance in WhatsApp Settings.
We've updated how WhatsApp messaging limits appear in your sub-account to match Meta's new model. Meta moved messaging limits from a per-phone-number basis to a business portfolio (WABA) basis, so all numbers under a portfolio now share one daily limit. HighLevel now shows that single shared limit accurately, instead of implying each number has its own quota.
🚨 Under Meta's model, one high-volume number can consume your entire portfolio's daily capacity. You now see the one number that actually governs what your business can send today.
📊 What changed on Meta's side (effective Oct 7, 2025)
Meta's messaging limit is the maximum number of unique WhatsApp user phone numbers you can deliver to, outside the 24-hour customer service window, in a rolling 24-hour period. As of Oct 7, 2025, that limit is calculated and set at the portfolio level and shared across every phone number in the portfolio.
🪜 The tier ladder changed
New entry point above the starting limit: 2,000 replaces 1,000 as the first step up from the 250 starting limit, and it is the on-ramp to automatic scaling.
How you reach 2,000: Complete a scaling path, either verify your business, have your partner verify it, or send 2,000 delivered messages to unique recipients over a rolling 30-day period using high-quality templates.
Above 2,000 is automatic: Increases to 10,000, then 100,000, then Unlimited happen on their own if you keep quality high across all your numbers and templates, and use at least 50% of your current limit over 7 days.
Faster re-evaluation: Meta reassesses roughly every 6 hours, down from 24.
No more quality-based downgrade: The "Flagged" number-quality state is gone. Low quality now gates scaling up, rather than knocking your limit down.
No warm-up for new numbers: A new phone number instantly inherits the portfolio's current limit. On cutover, existing portfolios kept the highest limit among their numbers.
🛠️ What we changed in HighLevel
📇 A portfolio-level messaging limits panel
See the real shared limit: A new messaging limits panel under WhatsApp Settings shows the true portfolio-level limit that governs all your numbers.
🧹 Removed the misleading per-number column
No more false impression of separate quotas: We removed the messaging limit column from the individual Phone Numbers view, because under the new model each number does not have its own limit.
💬 Clearer context
Tooltip: A tooltip explains that the limit is shared across the portfolio and that a single number can consume the full quota.
🌍 Localized
13 languages: The new panel is fully localized.
📍 Where to find it
Go to your sub-account.
Open WhatsApp Settings.
Select Messaging Limits.
Why this matters
Before this change, the limit shown under each number suggested every number had its own daily quota. It did not, and under Meta's portfolio model that gap matters more: a single high-volume number can burn the whole portfolio's capacity, which is exactly the situation that leads to unexpected send failures once the shared limit is hit. HighLevel now shows one accurate view of what your business can actually send today, so you can plan volume against the real ceiling instead of a per-number illusion.
Resources
WhatsApp messaging limits (HighLevel support)
Meta: WhatsApp messaging limits
Original source - Aug 26, 2026
- Date parsed from source:Aug 26, 2026
- First seen by Releasebot:Aug 26, 2026
Trigger Automation in Bulk for Companies & Custom Objects
HighLevel adds bulk workflow triggering for Company and Custom Object records from list view, letting users run automations on multiple selected records at once and track progress and record-level results from Bulk Actions.
You can now trigger workflows for multiple Company or Custom Object records at once, directly from the list view.
What's New?
- 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 Bulk Actions
Why This Matters
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
How to Use
Open Companies or a Custom Object
Select the records you want to process
Click Trigger Automation
Select the workflow
Confirm the action
You can monitor the results from Bulk Actions.
📚 Learn More
Original source
Curated by the Releasebot team
Releasebot is an aggregator of official release notes from hundreds of software vendors and thousands of sources.
Our editorial process involves the manual review and audit of release notes procured with the help of automated systems.