> For the complete documentation index, see [llms.txt](https://help.sodastream.sopro.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.sodastream.sopro.io/1.135.00-28.10.2026.md).
# π 1.135.00 (28.10.2026)
A deployment of a new version of SodaStream and Client Portal inside the regular release window.
## π Update: Generative Messaging for Continuous Engagement Cycles #Ops #CS #CX
{% hint style="info" %}
**No action needed for now.** Your campaigns will keep working exactly as they do today. This update prepares the system for the upcoming **Continuous Engagement** initiative. When you decide to introduce Continuous Engagement in a campaign, you'll be able to add instructions for each cycle and tailor the messages, for example by mentioning that the prospect may have heard from the client before.
{% endhint %}
**What was happening?**
Approach Level Additional Instructions (ALAI) were one single block of instructions applied to every engagement cycle. Messages for a prospect being re-engaged were written with the same instructions as their first outreach, and there was no way to preview how a message would look for a specific cycle.
**What's changed:**
**Instructions per cycle (SodaStream)**
β In **Campaign settings βΊ Approach**, the ALAI section is now split into **Cycle Level Additional Instructions**, so you can write different instructions for each engagement cycle.
β Existing ALAIs have been moved to the new structure automatically. No instructions have been lost.
**Engagement history on every prospect**
β When prospect lists are imported or refreshed, SodaStream now records each prospect's Last Engagement Date and Last Engagement Stage, and works out their Last Engagement Cycle. Prospects with no previous engagement are imported as normal.
**Messages written for the right cycle**
β When a message is generated, only the instructions for that prospect's next cycle are used, together with the Approach Specific instructions and the prospect's engagement details.
β Each generated message is saved against the prospect with its stage and cycle number, so you can see which cycle it was written for. If generation fails, no message is saved and the error is logged.
**Preview by cycle (Client Portal)**
β The template preview in the Portal has a new **Cycle** dropdown. Select a Cycle to see its instructions in the Approach Level Additional Instructions field.
β "Generate M1" and "Generate full sequence" need a Cycle to be selected first. The message is built from that Cycle's instructions, the selected Campaign Audience and the Additional Instructions toggle.
β If you change the Cycle after generating a message, that message is marked as outdated until you generate it again.
**Impact:**
Messages are tailored to where each prospect is in their engagement journey, so repeat outreach feels relevant instead of starting from scratch. Teams can preview each cycle's message before it reaches prospects.
## π₯οΈ Client Portal Updates
### π€ Update: Include Inactive Email Profiles on the Prospects & Reporting Pages #CX
**What was happening?**
The Email profile filter on the Prospects page showed only **Active** profiles in the campaign, so it was hard to tell which senders the campaign uses now and which ones are no longer active. On top of that, filtering by the same email profile on the Prospects page and the Reporting page could show different numbers of engaged prospects.
**What's changed:**
β By default, the Email profile dropdown in **Filter events** shows only **Active** profiles, with a short note showing how many inactive profiles are hidden.
β A new **"Include inactive email profiles"** checkbox under the dropdown shows all profiles, with Active ones listed first and Inactive ones marked with a grey "Inactive" tag.
β Search in the dropdown only covers the profiles you can currently see.
β If you untick the checkbox while inactive profiles are selected, they're removed from your selection and a message tells you how many were removed.
β Saved filters remember whether the checkbox was ticked.
β The **Email group** filter on the **Reporting** page can now include inactive email profiles too.
β Filtering by the same email profile now shows the same number of engaged prospects on both the Prospects page and the Reporting page.
**Impact:**
Keeps the filters clean and focused on current senders, while still letting users look back at activity from older profiles, with numbers that match across both pages.
### π Bug Fix: Prospects Page Filtering & Export #CX
**What was happening?**
Several filters and exports on the Prospects page were returning incorrect results:
* LinkedIn Referrals didn't appear when filtering.
* The Email template filter and column always showed the initial template, even for prospects who had already received a chaser, so filtering by a later stage returned no results.
* Filtering by Prospect Country could increase the number of prospects instead of reducing it.
* Exports filtered by Email profile (including with response types or a specific link) contained incorrect results.
* Filtering by Prospect email showed prospects who had never been emailed.
* The "Today" time range showed a total that didn't match the "Showing # to # of # entries" count.
**What's changed:**
β LinkedIn Referrals now appear correctly when filtering.
β The Email template filter and column now show the template stage each prospect actually received.
β The Prospect Country filter now narrows the list correctly.
β Exports now match the filters you've applied.
β The Prospect email filter only shows prospects who have been contacted.
β Prospect counts for the "Today" time range are now consistent.
**Impact:**
Users can rely on the Prospects page filters and exports to show exactly the prospects they're looking for.
### π Bug Fix: Dashboard Improvements #CX
**What was happening?**
A few issues on the Dashboards made them harder to read and trust:
* Images were missing for the Webchat and AdSync outreach channels.
* Clicking LinkedIn Connections Accepted opened a Prospects page list that didn't match the number on the dashboard.
* Top Pages Visited could show only "/" instead of the actual page address.
* The export notification wasn't displaying correctly.
* Exports from the Leads, Intent and Engage tabs were split across two pages even when everything fitted on one, which could make the report look incomplete.
**What's changed:**
β Webchat and AdSync images now show correctly.
β LinkedIn Connections Accepted now matches the filtered Prospects page list.
β Top Pages Visited now shows the full page address.
β The export notification has been fixed.
β Leads, Intent and Engage exports no longer split onto a second page unnecessarily.
**Impact:**
Dashboards are clearer and their numbers match the detailed lists behind them.
## π¦Ύ SodaStream Updates
### π Update: Move Prospects from a Generative Email Profile #Ops
**What was happening?**
Prospects on a Generative email profile couldn't be moved to another email profile, so outreach couldn't continue from a different sender.
**What's changed:**
β Prospects with status **"New"** on a Generative email profile can now be moved with the **"Switch to email profile"** action. Prospects with other statuses can't be moved, and a message explains why.
β You can move them to any other Generative or Standard email profile you have access to.
β **Generative β Generative:** the Generative Messages regeneration window opens so messages are created using the new profile's settings. The prospects are moved when you close the window.
β **Generative β Standard:** the prospects are moved straight away, and they'll receive the profile's Fallback template instead of their earlier generated messages.
β A confirmation shows which profile the prospects were moved to.
**Impact:**
Gives Ops the flexibility to change senders mid-campaign while making sure prospects still get the right messages.
### π Update: Link Any Email Profile to an Approach #Ops
**What was happening?**
Only Generative email profiles could be linked to an Approach. Campaigns that use only legacy templates couldn't be linked, which left gaps in Audience Manager reporting and stats.
**What's changed:**
β The **Approach** option is now available for every email profile type: Generative or legacy. It works the same way for all of them.
**Impact:**
Every TAM segment and Campaign Audience can now have an Approach, so reporting and stats stay consistent across all campaigns.
### πΊοΈ Update: New Market Map Tab #Ops #CS
**What was happening?**
Building a Market Map meant going through the Campaign Audience search, which needs a Campaign and Approach to be selected first.
**What's changed:**
β A new **Market Map** tab has been added to SodaStream with two sections:
* **Search:** run a search with the usual filters, without needing to select a Campaign or Approach.
* **Market Maps:** a list of saved Market Maps that you can View, Clone or Edit, including changing the Market Map Owner.
β Results show **Prospects Found** and **Companies Found**, with tabs for **Industries & Sizes**, **Companies** and **Prospects**.
β Duplicate checks and AI Job Title Suitability don't apply to Market Maps, so they've been removed from this view. The Job Titles tab shows the list of job titles only.
**Impact:**
Makes it quicker and simpler to size up a market without setting up a campaign first.
### π¬ Update: Responder Accounts Follow the Email Address to Its New Campaign #Ops
**What was happening?**
When an existing email address was added to a new campaign, its responder account could stay connected to the old campaign, so replies could sync into the wrong campaign.
**What's changed:**
β When you create an email address and pick an **Existing** address that's already linked to another campaign, a message tells you: *"The email address will stop syncing responses in {Campaign name}"*.
β When you save, the responder account on the old campaign is disabled and replies sync to the new campaign only.
β If you cancel or pick a different address, nothing changes on the old campaign.
β Replies already synced to the old campaign stay where they are.
**Impact:**
Replies always land in the right campaign, and nothing already synced is lost.
### π Update: Domains & Email Account Improvements #Deliverability #Ops
**What was happening?**
The Domains menu showed active and inactive domains together, email accounts could be saved without key settings, and teams had to look up which campaign a disabled email address belonged to.
**What's changed:**
β The **Domains** menu now shows only **active** domains and subdomains by default. Use **"Show inactive"** to see the rest.
β **Unsub URL** and **Tracking Domain** are now required when editing an email account. If either is empty, the changes can't be saved and a "This field is required" message appears.
β "Email Address Disabled" notifications now include the **Campaign Name**, alongside the details already shown.
β A new **Outlook** page has been added under **Domains**. Only IT Admin, Deliverability and Super Admin roles can open it.
**Impact:**
A cleaner Domains view, fewer setup mistakes, and faster investigation when a sending address is disabled.
### π·οΈ Update: Sopro Band Added to Client Information #CS #Finance #Ops
**What was happening?**
There was no quick way in SodaStream to see a client's band based on their billing history.
**What's changed:**
β A new read-only **Sopro Band** field (A / B / C) appears next to Sopro Tier under **Client βΊ General Information βΊ Client Information**.
β The band is worked out from the client's invoices and updated every night. Hover over it to see months billed, total billed (Β£) and trend.
β Clients in the same client group share one band, based on all of the group's invoices.
β Non-billable clients and clients who haven't been invoiced yet have no band.
β The band is saved daily, so its history is kept for reporting.
**Impact:**
Gives teams a clear, up-to-date view of each client's value alongside their tier, to help with prioritisation and reporting.
### β±οΈ Update: Shorter Delay Between Sends for Internal Campaigns #Ops #Deliverability
**What was happening?**
The **Delay Seconds From Between Emails** setting had a minimum of 30 seconds for every campaign, including internal campaigns that don't need the same sending limits as prospecting campaigns.
**What's changed:**
β For **internal campaigns**, the minimum delay between sends is now **5 seconds**.
β For **external campaigns**, the minimum stays the same as before.
β If you enter a value below the minimum, the message tells you the correct minimum for that campaign type.
**Impact:**
Internal campaigns can send faster, while prospecting campaigns keep the same safe sending limits.
### π Bug Fix: Send Schedules Pausing Until After Midnight #Ops
**What was happening?**
In some cases, a send schedule stopped partway through the day without any error and only restarted around 12 hours later, in the middle of the night, when sends are much less effective.
**What's changed:**
β Fixed the issue so send schedules no longer pause and restart overnight.
**Impact:**
Emails go out during the scheduled window, so campaigns keep their expected reach.
### π Bug Fix: Email Address Setup in Domains #Deliverability #Ops
**What was happening?**
* Adding a Postal address through the new domain flow showed an error, and addresses created another way were missing their Tracking Domain and Unsub URL.
* Adding an app password (2FA) to an email address created a duplicate of that address in the email profile.
**What's changed:**
β Postal addresses can now be added through the new domain flow and are set up with their Tracking Domain and Unsub URL.
β Adding an app password no longer creates a duplicate email address.
**Impact:**
Email addresses are set up correctly the first time, and email profile address counts stay accurate.
### π Bug Fix: Generative Emails Sent with Unfilled Variables #Ops #CS
**What was happening?**
Some Generative messages went out with raw variables such as β\*|COMPANY|βsβ. This happened when the AI wrote a variable slightly wrong, and one broken variable could also stop the next one in the email from being filled in.
**Whatβs changed:**
* Badly written variables are now corrected as soon as an email is generated.
* Theyβre checked and corrected again just before sending, so emails generated before the fix are covered too.
* If a variable still canβt be filled in, the email isnβt sent. Itβs flagged and logged so the team can follow up.
**Impact:**
Prospects no longer receive emails with raw variables.
