1.118.00 (03.03.2026)

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

Client Portal Updates:

Update: Pending Prospects table from Company Details is removed #Ops #CS #CX

A legacy “Pending Prospects” table in the Company side modal showed non‑functional toggles and incomplete information, confusing clients and implying control that didn’t exist.

This table proved to be misleading and confusing, mainly for clients, as no action was possible on their end.

What's changed

The Pending Prospects table and its toggles have now been removed from the Company modal, simplifying the UI and aligning it with the current automated IP M&E behaviour.

Update: Response Type and Intent Type implemented for CRM Integrations (HubSpot; Pipedrive; Salesforce) #Ops #CS #CX

Taking in consideration that so far we haven't had a field that allows users to map the response types and intent types into clients' CRMs, we've been limiting their proper visibility as to what types of responses and intents are integrated in their CRMs.

What's new:

For the following CRMs:

• HubSpot

• Pipedrive

• Salesforce

You can now map a dedicated “Response Type” field to:

• HubSpot Contacts

• Salesforce Leads/Contacts

• Pipedrive Contacts

And this would mirror the same values used in Lead Status (e.g. Deferred Interest, Positive, Web Visit, SDR Log – Positive).

The field can be configured as text or dropdown/picklist and is populated and updated correctly across All Contacts and Responder-only flows, without being overwritten by unmapped events.

This gives the clients a clear, CRM‑native view of engagement intent that can be used for reporting and automation.

Bug Fix: Password Reset link updates #Ops #CS #CX

What was the issue?

Recently, more and more users were met with the “Invalid token” message when trying to reset their Portal password through the password reset links.

Upon investigation, it was noticed that this was caused by the 5‑minute token validity, and sometimes, if there was a delay in sending out the reset email, users were not able to change their password and were receiving the misleading "Invalid token" notification.

What has been fixed:

With tonight's deployment, we've implemented two fixes to the password link:

• We're extending the time limit of the reset token to 10 minutes. This would allow users more time to reset their passwords and would avoid any issues if the sending of the reset email is delayed.

• The 'Invalid token' notification has been updated to 'Reset link has expired. Please request a new password reset.' This is a more user-friendly notification that would be understandable for everyone if the reset token has expired.

Bug Fix: IP Visits still being tracked for Inactive clients #Ops #CS #CX

What was the issue?

For inactive clients, even though the plug-in was deactivated successfully and web visit logging had stopped, background IP lookups were still running, consuming IP credits and triggering “IP credits exhausted” notifications.

What's changed:

All IP lookup jobs and related services now respect client status and stop processing for inactive clients.

No IP credits will be consumed, and no IP‑related notifications will be sent once a client is marked Inactive.

Bug Fix: Blank URL fields in 'Filter Website Traffic' prevented web visits from being tracked #Ops #CS #CX

What was the issue? When no URL rules were configured for Web Tracking (Filter Website Traffic tab), the system was recording blank URL filter rows, which interfered with the system process and prevented successful tracking of all pages as expected.

What was fixed: The system no longer creates blank URL filter records when no rules are defined, and existing empty records have been cleaned up.

If no filters are set, tracking correctly defaults to “track all website pages.”

Sodastream Updates:

Update: Automated LIO - Email Profile selection #Ops

Use case:

There are various campaigns, where clients are requesting LinkedIn Outreach only for a specific group of prospects (falling under a specific Email Profile).

To name a couple of reported cases:

• Prospects being targeted with their native language (both via Email Outreach and LinkedIn Outreach)

• One specific industry is being targeted within one Email Profile

With the current process taking all prospects under one Sales Agent, Ops Users were limited in setting up campaigns for Automated LinkedIn Outreach.

What's changed:

A new field has been implemented when setting up the send schedule for LinkedIn Outreach (Email Profile).

Ops users will be able to select if they want the process to select prospects only from a specific Email Profile/s (by selecting one or multiple Email Profiles).

If no Email Profile is selected, the process will take as valid all prospects under the Sales Agent that's performing the Outreach.

This helps in further implementing the remaining campaigns on the Automated LinkedIn Outreach process.

Update: New Company Filter implemented - Company Specialities #Ops #CS

In continuous improvement of the 'Companies & Prospects search' tab (Audience creation), new filter is being implemented to improve the data filtering and getting more accurate companies when audiences are created.

What's new?

A new “Company Specialities” multi‑select, autocomplete filter was added.

Including this filter when creating the audiences will help users find companies based on key products and services listed on their Company LinkedIn Page.

A tooltip has also been added so that users are informed about the filter's functionality and what they can implement in the field.

Bug Fix: State value not populated in Database for IP Match & Engage prospects #Ops #CS

What was the issue?

US prospects imported via Source & Engage for IP Match & Engage were missing the State value in the database, even though the information existed in the Location field.

This affected reporting and CRM integrations relying on State.

What has been fixed:

The system now correctly extracts and stores the State value from the Prospect.Location field into Prospect.

State for IP Match & Engage imports aligns with the same behaviour as Audience Builder Automation imports.

Bug Fix: Sends Executed on non-working days #Ops

What was the issue?

Email sends were still being executed on US holidays (e.g. Martin Luther King Day) even when the targeted and campaign country were set to the United States, and should have been treated as non‑working days.

What has been fixed:

The send logic now correctly recognises non‑working days per targeted country (or campaign country).

This will prevent sends going out on holidays and will accurately reflect the non-working day and non‑executed schedules in the Send Schedules calendar.