You can now transfer calls from the mobile app to staff members who don't have a personal phone number.

On Android, the incoming call screen shows Transferred call from Michael Scott

We're introducing Working Hours for Conversation AI, giving business more control over when their AI agents respond to customers.

You can now set specific working days and hours for each agent, choose which channels should follow those hours, and configure what happens when a customer reaches out after business hours.

This helps business keep their AI aligned with their actual operating hours while still making sure after-hours customers are acknowledged and followed up with.

You can now generate an image inside a workflow. The AI Image Generation action is available under AI Actions. Give it a prompt. An AI model creates the image, stores it at a public URL, and returns that URL as text.

This is a premium action. Each execution has an additional charge.

Image generation is billed per execution. The figures below show what a typical image costs. Most generations land in this range.

Note: Treat these figures as a planning estimate, not a fixed rate.

Your actual cost per image depends on how you configure the action. The main factors are:

The generated image is stored at a public URL. Anyone with the link can open it without a login. Keep this in mind when a prompt pulls in customer data.

A workflow can now create a visual, not only move one you uploaded in advance. Use the Image URL in the actions that come after. You can attach it to an email or SMS, publish it to a social post, save it to a custom field, or pass it to a webhook. Because the prompt can come from your data, one workflow can produce a different image for every contact, or fill in an image URL for every row in a Google Sheet.

One change beyond the paste: your pricing copy revealed the quality levels, so I pulled Quality into its own bullet under What's New and named them. That mirrors the Detail level bullet in the Analyze Image doc.

You can now analyze an image inside a workflow. The AI Analyze Image action is available under AI Actions. Give it an image URL and a prompt. An AI vision model examines the image and returns the answer as text.

This is a premium action. Each execution has an additional charge.

The image URL must be public. Anyone must be able to open it without a login. Do not use a link to a page that contains the image. Use the direct link to the image file. Files in Media Storage are already public.

A workflow can now read the contents of an image, not only move the image from step to step. Use the output text in the actions that come after. You can save it to a custom field, send it in an email or SMS, pass it to a webhook, or send it to another AI action.

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.

Every chip lands in one of three states:

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.

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.

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, 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:

When a customer calls and you miss them, we’ll still try to , as long as that number can send SMS.

If it can’t, system will automatically look for the next best option:

This is especially helpful when calls come through . Instead of attempting the text from a number that can’t send, we’ll use an eligible number when one is available.

Most of the time, nothing changes. The missed caller simply receives your follow up as expected.

In some cases, the . That’s intentional. We’re choosing a number that can actually send the message rather than letting an important follow up fail.

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:

In short,

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.

🔑 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.

A dedicated Client Portal category now groups all Client Portal triggers together:

User login — moved from Courses

Client portal file uploaded — moved from Membership

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.

No action needed. Existing workflows continue to run as-is and will automatically pick up login events from the new Client Portal experience.

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.

🗓️

To keep our pricing aligned with current carrier costs and maintain optimal deliverability across global telecom networks, we are updating carrier fees for messaging traffic sent to U.S. numbers via Verizon and select providers in the 'Other' category.

:

These updates stem directly from our downstream carriers in response to changing delivery and infrastructure costs across telecom networks.

Updating our rates ensures:

• Continued high-quality service and performance

• Reliable and optimised message delivery

• Direct alignment with global carrier pricing structures

🙏

We understand how important clear and transparent communication is regarding billing updates. We are committed to keeping you informed well in advance to ensure these adjustments are as seamless as possible. No action is required on your end. The updated rates will apply automatically from the effective date.

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.

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.

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.

Available for sub-accounts on SaaS v2 system.