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

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

1. A number you’ve successfully messaged this contact from before
1. Your default outbound number
1. 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.

🗓️ Effective Date

• October 1, 2026 → Verizon and 'Other' Category Carrier Fee Updates

Overview

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.

Verizon Carrier Fee Updates

Key changes for outbound messaging via the Verizon network:

• Outbound SMS (Long Code, Short Code, Toll-Free, Authy & Verify): $0.0045 → $0.0050 per message
• Outbound RCS Rich: $0.0045 → $0.0050 per message

Other Carrier Fee Updates

Key changes for outbound messaging via 'Other' Category Carrier network:

• Outbound SMS (Long Code, Short Code Group B, Toll-Free, Authy & Verify): $0.0040 → $0.0042 per message
• Short Code Group A SMS: $0.0025 per message (No change)

🔍 Why It’s Happening

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

🙏 Thank You

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.

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.

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.