1.109.00 (14.10.2025)
A deployment of a new version of SodaStream and Client Portal inside the regular release window.
Internal process updates
New Feature: Generative Messaging - Regeneration Requests #Ops
We are moving away from requesting Regeneration of Generative Messaging templates through the Teams channel.
For this reason, we are implementing a new feature in Sodastream, where Ops users can directly request Regeneration requests and follow the status of the request.
NOTE: Ops users would only be able to send a Regeneration Request through Sodastream and follow the status of their request.
System Support / Super Admin roles would still need to process (approve/decline) the request in order for the Regeneration to be completed.
Where found:
Sending Regeneration Requests: https://sodastream.sopro.io/CampaignEmailSchedule ⇒ Generate / Regenerate button
Regeneration Requests table (following status of the request): A new menu item is implemented under 'Campaigns & Setup', named 'Regeneration Requests'.
What's new:
Changing the process of requesting regeneration of templates for Generative Messaging.
Ops would now send the Regeneration Requests through Sodastream and wait on Super Admin / System Support to process their request.
Streamlining this process helps Ops users, as they would have a clear step-by-step procedure of sending the regeneration requests, following the status of the same request, and seeing the reason if the request is potentially declined.
How it works:
1. Ops sends a Regeneration Request
The associated send schedule needs to be active
Ops selects the reason why Regeneration is needed
If Additional Instructions were changed, the system would automatically populate the text boxes for Old and New Additional Instructions
If 'Other' is selected as a reason, Ops would need to populate what the reason is.
Ops selects the time range for which the regeneration is needed.
Ops sends the request.
2. Regeneration Requests table
Ops would use this table to view the status of their request (Processed/Declined)
System support would use this table to review Regeneration requests sent by Ops, and Process or Decline them
If a Regeneration Request is declined, a comment will be left, so that Ops can view the reason why their request was declined
Benefit to you:
Faster process for sending a request for message regeneration.
No more manual work in populating tables for regeneration requests.
Prompt response to the request and a streamlined process for regenerating the messages.
No potential delays in daily delivery.
Bug Fix: Indirect Leads not being synced to the client's Zoho CRM #Ops #CS #CX
What was happening
It was reported that indirect leads were not being synced to the client's CRM, and this was related to Zoho integrations.
What's changed
A fix has been deployed that will keep syncing the indirect leads to the client's Zoho CRM.
Additionally, a historical sync has been applied to import all indirect leads to all clients with Zoho integration, from the point when the sync stopped.
Bug Fix: Test Email sequence sent to an email address, now matches the sequence shown in Sodastream #Ops
What was happening
There was a difference between the email sequence that was shown in Sodastream ⇒ Generative Preview and the email sequence that was sent to an email address as a test.
Since the same sequence was selected to be sent as a test, it was expected that the sequence shown on the Generative Preview would match the one that is sent as a test; however, this was not the case.
What's changed
This issue has now been fixed.
In Email Profiles, when Ops select the Generative Preview, and the email sequence is loaded, once the sequence is sent as a test to an email address, it will match what's showing on the Generative Preview window in Sodastram.
Benefit to you
Sending the exact same sequence would help test the deliverability of the email sequence, as Ops would have insight into whether some of the wording generated in the sequence might affect the emails' landing in the inbox.
Last updated