1.117.00 (18.02.2026)

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

Client Portal Updates:

Update: References to the old Web Plug-in page are now updated to the new design #Ops #CS

Some areas of the Portal (Website Visitors report, Intent tracking page, and inactive webchat pages/settings) were still linked to the old Website plugin configuration page.

This led to an inconsistent setup experience and potential confusion for users.

What's changed

All “Configure plugin”, “Activate plugin”, and “Get started” actions related to website tracking and webchat now correctly redirect to the new WebTrackingSetup page.

This ensures a consistent navigation path to the updated Website plugin configuration across the Portal.

Bug Fix: Incorrect info displayed in Prospect details sidebar #Ops #CS #CX

What was the issue:

In the prospect details view in the Portal, the sender information was incorrectly displayed when a prospect responded to an email.

The 'FROM' and 'TO' fields were reversed, and the responder account shown did not match the one that actually received the response, causing confusion and incorrect attribution of replies.

What has been fixed:

The prospect details view now correctly shows the 'FROM' field as the prospect’s email address and the 'TO' field as the responder account that received the response.

This behaviour is applied generically across all campaigns, ensuring accurate sender and recipient information for all affected prospects.

Bug Fix: Webchat Support Conversations not triggering notifications #Ops #CS #CX

What was the issue:

Webchat form-only submissions were not sending email notifications to active webchat users when conversations were resolved as Support.

This resulted in valid support enquiries being missed. Only Lead resolutions were triggering notifications.

What's changed:

Email notifications are now also triggered for Support and Removal resolutions.

We've also updated the subjects and the content, and it is now tailored to the type of request. This ensures all relevant webchat form submissions are surfaced to active webchat users for timely follow-up and compliance handling.

Sodastream Updates:

Update: 'Cancel termination' button has been implemented #Ops #CS #Finance

Use case:

Clients under the new contractual model who were on a 30-day Termination Notice period could not be moved back to 'Active - Multichannel service'.

The screen only offered 'Terminate' and 'Update plan' actions, preventing CS and Ops from cancelling the termination without first making the client inactive.

What's new:

A new 'Cancel Termination' button has been added for clients with Status 'Active - Multichannel service' and Sub-status 'Termination notice'.

This allows users to reactivate these clients directly during the 30-day notice period, without temporarily moving them to Inactive.

Update: SOE option included in Contract selection #Ops #CS #Finance

What's new?

We've deployed an update and introduced a new option in the Contract selection field ⇒ SOE (Service Order Extension).

This option will be visible only if the client has a 'Protected Legacy' or 'Exclusion' contractual status.

Selecting this option will allow users to bring back the client to 'Active - Multichannel service' without creating a new contract.

Update: 'Don't create campaign' tick box implemented when creating New Client #Ops #CS #Finance

Use case:

Creating a new client required selecting either an existing or a new campaign in the 'Campaign' step.

This blocked Finance and CS from creating non-billable clients when no campaign should be associated yet, preventing them from saving the new client.

What's changed:

A 'Don't create campaign' checkbox has been added to the 'Campaign' step when creating a new client.

When selected, it clears and disables the other campaign selection options, allowing users to save the client without assigning a campaign at that point.

Update: 'Don't create campaign' tick box implemented when creating New Client #Ops #CS #Finance

What was happening?

When a client was set to 'Suspended', only M1 email sends were being stopped.

Other activities, such as chasing, website tracking/widget, and client portal access, could continue, meaning suspended clients were still able to generate activity and access the Portal.

What's new?

Suspended clients now behave like Inactive clients in terms of restrictions: email outreach and chasing stop, the website widget is disabled, and associated client users cannot log into the Portal.

Once a client is unsuspended and becomes Active again, email outreach continues, and Portal access is restored

Web plug-in is however deactivated due to the suspension, and the installation would need to be verified again once the client is unsuspended.

Bug Fix: Client Termination notification not going out to Ops Owner #Ops #CS #Finance

What was the issue?

Client termination email notifications did not include the Ops Owner in CC, even though the 'Ops Owner' variable was present in the template.

As a result, Ops Owners were not reliably notified when a client was being terminated.

What has been fixed:

The client termination notification now first uses the Ops Owner specified at the client level; when that field is empty, it falls back to the Ops Owner from the client’s last active campaign.

This ensures the notification is sent to both CS and the correct Ops Owner whenever a client is terminated.

Bug Fix: Fixed term Clients moved to Inactive with overnight procedure #Ops #CS #Finance

What was the issue?

Clients with 'Active - Multichannel service' status and 'Fixed term' substatus were automatically moved to 'Inactive' status overnight.

This affected the regular sending activity, as Ops and CS were not aware of the status change, and it was affecting client reporting accuracy.

What has been fixed:

The issue has been resolved, and these types of clients will no longer be moved to 'Inactive' overnight.

The procedure was updated in the backend, and cases like this should no longer occur.

Bug Fix: IP M&E Job title checker not working as expected #Ops

What was the issue:

In SS Campaign Settings, the IPM&E Job Title checker did not validate invalid boolean operators like 'OR OR' or 'AND AND' in the job title fields.

When such errors were present, the Intent Tracker Automation could still run and pull every single job title, causing unnecessary data to be loaded into Prospects in SS.

What's been fixed:

When the Job Title fields contain 'OR OR' or 'AND AND', and the user clicks the 'Check' button, the system now displays an error message instead of allowing the configuration to pass.

Once the job title string is corrected, clicking 'Check' shows a confirmation message that the job title is valid, preventing erroneous automation runs.

Bug Fix: OOO Chasers not generated #Ops

What was the issue?

For the “Sopro UK 2025” campaign, no OOO generative chasers were being created, even though the email templates and schedules were correctly set.

This resulted in fallbacks being sent instead of the chasers being sent with a successfully generated message.

What's been fixed:

We've now implemented batching of the chasers. This will ensure that large number of messages are split and sent to AIM in separate calls.

This will ensure that the procedure does not fail, and the chasers are successfully generated.

Bug Fix: US send schedules were resetting mid-schedule after midnight #Ops

What was the issue?

For send schedules with a daily limit that started shortly before midnight, the system treated the pre‑midnight sends and the post‑midnight sends as part of the same schedule run but with a reset counter.

This caused more emails to be sent than the configured daily limit within a single continuous schedule execution (e.g. hitting the limit before midnight, then sending more right after midnight).

What has been fixed:

The daily send limit is now enforced across the full continuous schedule execution, even when it runs over midnight.

The counter no longer resets at the start of a new calendar day, ensuring that no more than the configured daily limit is sent per schedule run.