1.104.00 (05.08.2025)
A deployment of a new version of SodaStream and Client Portal inside the regular release window.
Product/Process updates affecting clients
User Login Bug Fix for Multiple Campaigns #CX
Issue Summary: Users assigned to multiple campaigns—including at least one marked as Extinct—were unable to log in to the Portal. Specifically, if a user had one campaign labeled as Extinct and another active campaign, the system incorrectly blocked access by showing the “Inactive User” screen, preventing login entirely.
Example Scenario: A user assigned to two campaigns:
Darwinium (Inactive: Extinct)
Darwinium 2025 (Booked: New Onboarding)
When attempting to log in, the user was blocked due to the extinct campaign, despite having an active campaign.
What You Should Expect Now:
Users with multiple campaigns will be able to log in successfully as long as at least one campaign is active.
Access will be granted only to campaigns that are not extinct, unless the client’s Platform fee is active—then access to Extinct campaigns will also be permitted.
Users will no longer see the “Inactive User” screen solely because of an extinct campaign assignment.
Impact: This fix improves login reliability for users with mixed campaign statuses, ensuring uninterrupted access to the Portal for active campaigns.
Internal process updates
🤖 New Feature (Limited Release): Automated Classification for LinkedIn Responses #Ops
We’ve introduced an automated classification system for incoming LinkedIn responses synced into SodaStream, designed to reduce manual effort and improve efficiency for Ops teams.
❗❗❗Important: This feature is currently being released only to a selected list of campaigns for testing purposes. Relevant Ops Owners have been notified separately.
🧠 What’s new?
Our Data Science team has developed a model that classifies LinkedIn responses with ~99% accuracy. When a new response is synced into SodaStream:
It is automatically sent to the classification model.
The model assigns a classification label.
The label is saved in the same field used for manual classification.
The response is moved from "Unresolved LinkedIn Conversations" to "Resolved LinkedIn Conversations".
✋ Can I still edit the classification?
Yes! While the system handles classification automatically, Ops Owners can manually override the result in the "Resolved LinkedIn Conversations" section if needed.
🔧 Update: Prospect Refresh Date Filter Default Removed #Ops
To give you more visibility and flexibility when reviewing your prospect data, we've removed the default 6-month range from the Prospect Refresh Date filter in SodaStream.
What’s changed? Previously, the system automatically applied a 6-month date range to this filter. This filter will no longer be pre-filled — it will remain blank unless you manually set a value.
Why this matters: With our new Data Verification process running in the background to continuously check prospect relevancy in real time, there’s no longer a need to limit your search results by default. This update ensures you're seeing the full picture unless you choose to narrow it down.
No action is needed on your part — just enjoy the broader, more accurate data view.
Batch Request Issue for Maersk Campaign – Peter Svedberg | CBAM Generative | FR #Ops
Issue Summary: In the Maersk Campaign, specifically for the email profile "Peter Svedberg | CBAM Generative | FR," batch requests were not being automatically generated for imported prospects. This resulted in messages not being sent to these prospects.
Interestingly, when the Regenerate button was manually clicked within the Send Schedule, the system was able to generate the messages, even though no batch requests were sent to AIM. As a result, there were no corresponding logs in the database or AIM for batch requests triggered via the Regenerate action.
Additionally, the GenerativeBatchLog table for the associated email profile (ID = 21154) did not show any recorded batch requests.
Resolution: This bug has now been fixed. Batch requests will be correctly generated for automatically imported prospects, and logs will be recorded in both the GenerativeBatchLog table and AIM when batch requests are triggered—whether automatically or via the Regenerate button.
Impact: This fix ensures that:
Batch requests are properly created for all imported prospects.
Logs for batch requests are accurately recorded in the GenerativeBatchLog and AIM.
Messages are successfully sent to all intended prospects, regardless of how they were imported.
Campaign Affected:
Maersk Campaign
Email Profile: Peter Svedberg | CBAM Generative | FR
What’s Next: This fix is now live and will prevent any future issues with missing batch requests or message generation for imported prospects.
Last updated