Overview: We've introduced a new Mixed Use Case option in the Chat Widget A2P registration flow, allowing businesses to collect separate marketing and informational consent through a single widget.

What's new:

• A new Mixed message type is now available alongside Marketing/Promotional and Transactional/Non-Marketing in the Chat Widget flow. When selected, the campaign use case is automatically set based on account type (e.g., Low Volume Mixed for standard accounts, Sole Proprietor for sole prop accounts).
• The generated Chat Widget automatically includes two independent consent checkboxes, each with its own locked disclosure block. End users can opt into marketing only, informational only, or both. Neither checkbox is pre-checked.
• All consent language, STOP/HELP disclosures, and compliance fields are system-controlled and non-editable — just like the single use case widget flow.

Previously: Businesses that needed to send both marketing and informational messages had no path through the Pre-Built Chat Widget flow and were forced to use the Self-Serve flow, which carries higher compliance risk and rejection rates.

Why it matters: Mixed use case campaigns can now be registered through the same quick, streamlined Chat Widget flow — with built-in consent separation, locked disclosures, and reduced rejection risk.

What’s new?

We’ve upgraded the field picker in both the Custom Value Picker and If/Else action. Search now returns fields from inside nested folders, navigation across folders and subfolders is easier, and the field list is better organized for a cleaner, more consistent selection experience.

Improvements

• Nested field search – Find fields inside folders and subfolders without opening each one first.
• Easier navigation – Move through nested folders more smoothly.
• Cleaner organization – Fields are grouped more clearly, making them easier to scan.
• Better readability – Long field names now show tooltips, making it easier to read full values without cluttering the picker.
• Consistent experience – The picker now feels the same across If/Else and Custom Value Picker options across the platform

How it works

When you search for a field, matching results can now appear even if that field lives inside a folder or subfolder. The picker also uses a more consistent dropdown pattern across workflows, so finding and selecting fields feels the same in Custom Values and If/Else.

How to use it

• Open the field picker in Custom Values or an If/Else branch filter.
• Type the field name in search.
• Select the matching field directly from the results, including fields stored inside nested folders.

Why we built it

Previously, finding the right fields in automations took more effort than it should have. Users had to manually open folders and return to the search box to find nested fields, which slowed setup and made some available fields easy to overlook.

Additional Notes

• Search now shows matching field names from inside folders and subfolders.
• Only enabled folders appear in search results. Once you clear the required dependencies, the available fields would show up.
• The updated picker experience is aligned across If/Else and Custom Value Picker.
• Users will only see fields and folders that are available and enabled in that context.

Preview

What’s new?

We’ve upgraded the field picker in both the Custom Value Picker and If/Else action. Search now returns fields from inside nested folders, navigation across folders and subfolders is easier, and the field list is better organized for a cleaner, more consistent selection experience.

Improvements

• Nested field search – Find fields inside folders and subfolders without opening each one first.
• Easier navigation – Move through nested folders more smoothly.
• Cleaner organization – Fields are grouped more clearly, making them easier to scan.
• Better readability – Long field names now show tooltips, making it easier to read full values without cluttering the picker.
• Consistent experience – The picker now feels the same across If/Else and Custom Value Picker options across the platform

How it works

When you search for a field, matching results can now appear even if that field lives inside a folder or subfolder. The picker also uses a more consistent dropdown pattern across workflows, so finding and selecting fields feels the same in Custom Values and If/Else.

How to use it

• Open the field picker in Custom Values or an If/Else branch filter.
• Type the field name in search.
• Select the matching field directly from the results, including fields stored inside nested folders.

Why we built it

Previously, finding the right fields in automations took more effort than it should have. Users had to manually open folders and return to the search box to find nested fields, which slowed setup and made some available fields easy to overlook.

Additional Notes

• Search now shows matching field names from inside folders and subfolders.
• Only enabled folders appear in search results. Once you clear the required dependencies, the available fields would show up.
• The updated picker experience is aligned across If/Else and Custom Value Picker.
• Users will only see fields and folders that are available and enabled in that context.

Preview

What’s new?

We’ve upgraded the field picker in both the Custom Value Picker and If/Else action. Search now returns fields from inside nested folders, navigation across folders and subfolders is easier, and the field list is better organized for a cleaner, more consistent selection experience.

Improvements

• Nested field search – Find fields inside folders and subfolders without opening each one first.
• Easier navigation – Move through nested folders more smoothly.
• Cleaner organization – Fields are grouped more clearly, making them easier to scan.
• Better readability – Long field names now show tooltips, making it easier to read full values without cluttering the picker.
• Consistent experience – The picker now feels the same across If/Else and Custom Value Picker options across the platform

How it works

When you search for a field, matching results can now appear even if that field lives inside a folder or subfolder. The picker also uses a more consistent dropdown pattern across workflows, so finding and selecting fields feels the same in Custom Values and If/Else.

How to use it

• Open the field picker in Custom Values or an If/Else branch filter.
• Type the field name in search.
• Select the matching field directly from the results, including fields stored inside nested folders.

Why we built it

Previously, finding the right fields in automations took more effort than it should have. Users had to manually open folders and return to the search box to find nested fields, which slowed setup and made some available fields easy to overlook.

Additional Notes

• Search now shows matching field names from inside folders and subfolders.
• Only enabled folders appear in search results. Once you clear the required dependencies, the available fields would show up.
• The updated picker experience is aligned across If/Else and Custom Value Picker.
• Users will only see fields and folders that are available and enabled in that context.

Preview

What’s new?

We’ve upgraded the field picker in both the Custom Value Picker and If/Else action. Search now returns fields from inside nested folders, navigation across folders and subfolders is easier, and the field list is better organized for a cleaner, more consistent selection experience.

Improvements

• Nested field search – Find fields inside folders and subfolders without opening each one first.
• Easier navigation – Move through nested folders more smoothly.
• Cleaner organization – Fields are grouped more clearly, making them easier to scan.
• Better readability – Long field names now show tooltips, making it easier to read full values without cluttering the picker.
• Consistent experience – The picker now feels the same across If/Else and Custom Value Picker options across the platform

How it works

When you search for a field, matching results can now appear even if that field lives inside a folder or subfolder. The picker also uses a more consistent dropdown pattern across workflows, so finding and selecting fields feels the same in Custom Values and If/Else.

How to use it

• Open the field picker in Custom Values or an If/Else branch filter.
• Type the field name in search.
• Select the matching field directly from the results, including fields stored inside nested folders.

Why we built it

Previously, finding the right fields in automations took more effort than it should have. Users had to manually open folders and return to the search box to find nested fields, which slowed setup and made some available fields easy to overlook.

Additional Notes

• Search now shows matching field names from inside folders and subfolders.
• Only enabled folders appear in search results. Once you clear the required dependencies, the available fields would show up.
• The updated picker experience is aligned across If/Else and Custom Value Picker.
• Users will only see fields and folders that are available and enabled in that context.

Preview