1.110.00 (28.10.2025)

A deployment of a new version of SodaStream and Client Portal inside the regular release window.

Client Portal updates

Portal Update: Chasers generated in Portal Preview now use random chaser types #CX

When we moved the Generative Messaging preview and editing in Portal, the chasers that were being generated for a preview only pulled one chaser type across all stages.

What's changed:

With the latest fix, we are implementing a change in logic, where each chaser will be generated for a preview with a different chaser type from the ones ticked in Sodastream.

Benefit to you:

This change will provide diversification in the chasers that are being generated, as they will be using different chaser types.

With this update, the chasers that will be displayed in the preview will not be similar to each other, and will avoid using the same chaser type.

Bug fix: Time Range selection visible again for Old Reports #CX

🔍 What was the issue?

It was reported that the Time Range picker was not visible for the Old Reporting page.

This affected users not being able to apply a specific date range in the Old Reporting.

✅ What’s been fixed?

The Time Range picker is now fixed and visible for the users who need to view the Old Reports.

Bug fix: Excel/CSV Export By Month is now fixed #CX

🔍 What was the issue?

When trying to export the Performance by Month stats in Excel/CSV on the Reporting tab, the Portal did not start any download, and users were not able to export/download the stats.

✅ What’s been fixed?

The issue has now been resolved, and the Portal users will now be able to export the stats in the Performance by Month tab.

Internal process updates

New: Job Title Suitability AI Checker #Ops

A new feature has been implemented in the 'Companies & Prospects search' when creating audiences.

To support Ops and ease the process of creating accurate audiences, we've implemented an AI Checker for suitable/unsuitable job titles.

What's new?

A new functionality that helps Ops remove unsuitable job titles from searches in campaign audiences.

Once a search is created in 'Companies & Prospect search', and the 'Check for Duplicates' button is clicked, a new button - 'AI Job Title Suitability' will appear in the 'Job Titles' tab that would automatically check and exclude unsuitable/irrelevant job titles.

Ops would have the opportunity to save the unsuitable job titles as Cache to the related Messaging.

Your benefit:

• More accurate data, as the AI checker would remove irrelevant job titles

• Faster process in creating audiences

• Cached unsuitable job titles would automatically be removed in any new search

• Option to manually change 'Unsuitable' to 'Suitable' by clicking a toggle button, if needed.

Increased limits on processing and saving Campaign Audiences #Ops

To support the Ops workflow in creating audiences, we have increased the limits in processing and saving Campaign Audiences in the 'Companies & Prospects search'.

What’s new?

When creating Campaign Audiences, there was a limit of 8,000 prospects to process the Deduplication process.

We've increased this number to 10,000 new prospects. If the created audience consists of up to 10,000 new prospects, you will now be able to click the 'Check for Duplicates' button.

Additionally, once the Deduplication process is completed, the limit for saving a Campaign Audience has been increased. Until now, the limit was set to 2,000 new prospects. This is now increased to 4,000 new prospects.

What this means for you:

• You can now process and save larger campaign audiences.

• With the larger number of prospects to be engaged on a monthly level, larger audiences would support seamless delivery.

Check Boxes for Generative messaging automatically checked in Email Profile #Ops

There were some cases noticed where Ops have missed ticking the 'Generate M1 Messages Only' and 'Is Batch generating' boxes, when an Email Profile is marked with the 'Generative' label.

What's changed?

We've introduced a solution that would save time on the Ops side and would avoid additional manual steps.

Once an Email Profile is marked with the Generative label, the two boxes will automatically be checked.

Given that if the Email Profile is generative, both boxes would need to be ticked by default, they will remain visible, but Ops users would not be able to untick any of the boxes.

This would only be doable through a Super Admin role.

Benefit to you:

• No need to manually check the boxes.

• One step less when creating/cloning/editing an Email Profile.

• Safeproofing in order to make sure that the messages are generated for M1 only, and are included in the Batch Processing model.

Option to request Chaser Regeneration now available for Super Admin roles #Ops

✅ What’s new?

With the new feature to request message regeneration through Sodastream, users were not able to request regeneration for chasers.

Considering there are some cases where chaser regeneration would still be needed, we've decided to make requesting Chaser Regeneration available only for Super Admin roles.

SS Bug: Full Email Sequence now generated in Email Profile generative preview if prospect exists in multiple campaigns #Ops

🔍 What was the issue?

Users noticed that the Generative Preview in Email Profile only displays the initial template for a prospect that exists in multiple campaigns.

This affected users' ability to review the generative messaging for a specific campaign if the prospect is present in another campaign.

✅ What’s been fixed?

The issue has been resolved. If a specific prospect exists in multiple campaigns in the same time, Sodastream will now generate the full email sequence for preview, for every campaign.

SS Bug: Reclassifying Resolved Responses moves the response to Invalids #Ops

🔍 What was the issue?

When Ops users were reclassifying a 'Resolved Response', the response was being moved to Invalids.

✅ What’s been fixed?

We've fixed this issue, and Ops users would now be able to seamlessly reclassify a Resolved response when needed.

Once the response is reclassified, it will not be moved to Invalids.

SS Bug: Spintax Subject lines can't be edited if a special character is entered #Ops

🔍 What was the issue?

When users entered a special character (i.e. *, /, or similar) in a spintax subject line, they were not able to delete or edit the spintax subject line in Sodastream.

This affected delivery as Ops would need to reach out to System Support and wait while this was resolved in the background.

✅ What’s been fixed?

The issue has now been resolved. Users will be able to edit and delete special characters if they've entered them by mistake in the spintax subject line.