1.102.00 (08.07.2025)

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

Client Portal updates

Bug Fix: CRM Integration View on Safari Browser #CX

What was the issue? Some clients using Safari experienced display issues when integrating their CRM with our platform. Specifically, the dropdown menus showed a different background color or style compared to other browsers, making the interface look inconsistent.

This was reported by a client and confirmed during testing across different CRMs using BrowserStack.

What’s been fixed? We’ve updated the CRM integration view to ensure the dropdown menus and interface display consistently across all browsers, including Safari, matching the appearance you see in Chrome.

Impact: Clients using Safari will now have a smoother, consistent experience when setting up or managing CRM integrations.

Bug Fix: Missing "Goal Achieved" Notifications for Intent Goals #CX

What was the issue? For campaigns with intent goals enabled — such as the TalentAlly campaign — clients were not receiving "Goal Achieved" notifications, even when prospects successfully met those goals.

After investigating, we confirmed that the system did not send out these notifications, and no records appeared in the Notification Logs, even though the goals were reached.

What’s been fixed? We’ve resolved the issue so that when a prospect hits an intent goal: ✔ A "Goal Achieved" notification is now correctly sent to the client ✔ The notification is recorded in the Notification Logs for full transparency

Impact: Clients with intent goals enabled will now reliably receive notifications when those goals are met, ensuring real-time updates and better visibility of campaign progress.

Bug Fix: Data Mismatch Between Portal Reports and Exported Files #CX

What was the issue? We identified a mismatch between the figures shown in the Reporting tab on the Portal and the corresponding exported reports. This issue impacted how certain data fields were labelled and interpreted in the exported files, leading to confusion for clients trying to compare results.

For example: ✔ The Leads number on the Portal incorrectly mapped to the Intent - Inbound Webchat column in the exported report ✔ The exported Leads column reflected the number of Deferred Interest leads, not total leads ✔ The Positive Responses metric on the Portal incorrectly aligned with the Intent% value in the exported report

This discrepancy occurred across all report exports, except the Total Reports, which remained accurate.

What’s been fixed? We’ve resolved this systemic issue to ensure that: ✔ All exported report columns now match the data and terminology used in the Portal UI ✔ Figures displayed in the exported reports accurately reflect the corresponding metrics shown on the Portal ✔ The report structure is consistent and easy to interpret

Impact: Clients can now confidently compare data between Portal reports and exported files, with aligned figures, labels, and consistent terminology.

Internal process updates

Bug Fix: Master Template Reset When Editing Additional Instructions #CS #Ops

What was the issue? When configuring Generative Email Templates, users who selected a non-default Master Template (for example, "DON'T USE - Generative Email Master Prompt - All Stages - GPT-4.1 - Full Name Test") experienced an issue where making changes to the Additional Instructions field caused the Master Template to automatically revert to the default option ("Generative Email Master Prompt - All Stages").

This meant users had to manually re-select their preferred Master Template after every edit, leading to inefficiencies and the risk of generating emails with incorrect settings.

What’s been fixed? We’ve resolved the issue to ensure: ✔ When you edit the Additional Instructions field and save the template, your selected Master Template remains unchanged. ✔ No need to re-select the Master Template after each edit. ✔ More efficient and error-free configuration of Generative Email Templates.

Impact: All users working with Generative Email Templates can now confidently make edits without the system resetting the Master Template, ensuring consistency and accuracy in email generation.

Bug Fix: Incorrect Subject Line Logged for Stage 1 Emails After Switching Email Profiles #Ops

What was the issue? In some specific scenarios, the system incorrectly logged the subject line for Stage 1 (initial) emails when generating batch messaging. This happened if: ✔ A chaser (follow-up) was created before the initial email (e.g., Stage 2 added before Stage 1) ✔ A send schedule was set up ✔ A new Stage 1 email was later added to the same email profile ✔ The email profile was then switched to a different one

In this case, the system incorrectly assigned a chaser subject line to the initial email during message generation. This issue only affected the logged data and reports — the actual emails sent to prospects always had the correct subject line.

What’s been fixed? We’ve resolved the issue so the system now logs the correct subject line for all Stage 1 emails, even when switching between email profiles or creating messages out of order.

Impact: ✔ Messaging logs and reports now display accurate subject lines ✔ Downstream systems relying on logged data will reflect the correct information ✔ No impact on email sends — those have always been sent with the correct subject line

Bug Fix: Unable to Edit or Remove Subject Lines on Specific Email Templates #Ops

What was the issue? Some users experienced a problem when trying to edit or remove subject lines on specific templates within the Digital Works Group 2025 campaign. This affected the following templates:

• Andrew Salmon | AI - Generative | Stage 1 V1 | UK | URL

• Andrew Salmon | AI - Generative | Stage 1 V1 | Benelux | URL

When attempting to add a new subject line or remove an existing one, the system did not save the changes. The same issue occurred when cloning the affected templates. This only happened if Spintax was active on the campaign.

What’s been fixed? We’ve resolved the issue so that subject lines on the affected templates can now be properly managed. You can: ✔ Add new subject lines and have them saved immediately ✔ Remove existing subject lines without issues ✔ Clone templates without carrying over the problem

Impact: Campaign managers can now update, remove, and manage subject lines on Digital Works Group 2025 templates as expected, even when Spintax is active.

Bug Fix: Missing Invoice and Credits After Clicking “Go Live” #Ops

What was the issue? In some cases, when our team clicked the Go Live button for campaigns under the Arrears billing model, no invoice appeared in the Portal, and the campaign credit balance showed as 0. Oddly, credits were automatically corrected the following day by the system’s overnight processes.

Although the invoice record was created in the background, it was not visible in the Portal, leading to confusion and inaccurate credit displays immediately after launch.

What’s been fixed? We’ve introduced an additional fix to address this issue, ensuring that when the Go Live button is clicked: ✔ The invoice is immediately generated and visible in the Portal ✔ The campaign credit balance updates correctly without delay

Impact: Campaigns under the Arrears model will now have invoices and credits properly reflected in real-time after going live, removing the need to wait for overnight system processes.

Bug Fix: Chaser Emails Sent Despite Daily Limit Set to 0 #Ops

What was the issue? In campaigns using generative messaging, some users noticed that a chaser email was still being sent even when the Max number of sends for that chaser was set to 0 in the Send Schedule.

This resulted in one chaser email being sent when no emails should have gone out at all.

What’s been fixed? We’ve corrected the issue to ensure that when the Max number of sends is set to 0, the system respects that limit and does not send any emails for that chaser.

Impact: Your daily send limits for chasers will now be enforced correctly, preventing unintended emails from being sent when limits are set to 0.

Bug Fix & Improvement: Correct Credit Handling for IP Match & Engage Profiles #Ops

What was the issue? When setting up a new IP Match & Engage (IPM&E) email profile, the system incorrectly deducted credits from the client’s total balance, even though IPM&E activities should not consume credits. By default, the Credits per Prospect field was set to 1, leading to unintended credit usage.

What’s been fixed? We’ve made several improvements to ensure credit handling works as expected:

✔ When an email profile is marked as IP Match & Engage, the Credits per Prospect field is automatically set to 0, ensuring no credits are deducted for IPM&E activities.

✔ If the email profile type is later changed from IP Match & Engage to Email Outreach, the Credits per Prospect field will automatically update to the default value of 1, unless the user has already entered a custom value greater than 0.

✔ To avoid confusion, a red message now appears below the selection menu confirming: “Changes in the ‘Credits per Prospect’ section have been applied.”

Impact: IP Match & Engage activities will no longer consume credits, and the system provides clearer feedback when changes to credit settings occur.