# 1.124.00 (28.05.2026)
## Client Portal Updates:
###  Update: Job Openings Tab Now Active in Company Details #Ops #CS #CX
During the initial rollout of the updated Company page, the **Job Openings** tab in the Activity widget was hidden because the required data was not yet available.
With the data source now connected, this tab has been enabled.
**What's been improved?**
✔ The **Job Openings** tab is now visible in **Company Details → Activity widget**
✔ Displays the total count and list of active job openings for the selected company
✔ If no active job openings are found, a clear empty-state message is displayed: *"We couldn't find any active job openings for this company right now"*
✔ Only the first **5 job openings** are displayed by default
✔ A **"Show more"** button allows users to expand and view the full list - consistent with the Technologies section behaviour
***Note:** Posted date and location are not yet available from the data source and are excluded from this release.*
**Impact:**
Clients can now view live job openings for any engaged company directly from the Company Details page, supporting more informed outreach conversations.
###  Bug Fix: Intent Tracker – Companies with "New" Email Stage Redirect to Error Page #Ops #CS #CX
**What was the issue?**
In the Intent Tracker **Companies** tab, clicking on the company name in the side modal for a company with **Email Stage = New** (no engaged prospects yet) redirected the user to a **500 Internal Server Error** page instead of the Company Details page.
**What's been fixed?**
✔ Clicking the company name in the Intent Tracker side modal now correctly opens the Company Details page
✔ This works for companies with **New**, **Qualified**, or any other status
✔ No 500 errors are generated when navigating from the modal
**Impact:**
Users can now access the Company Details page for any company in the Intent Tracker, regardless of engagement status.
###  Bug Fix: Engagement Overview "Select Department" Dropdown Empty #Ops #CS #CX
**What was the issue?**
When viewing a company's Engagement Overview modal (via the "See all" button), the **Select Department** dropdown filter was not displaying any options - even when department data was present in the company's Demographics tab.
**What's been fixed?**
✔ The department dropdown now correctly populates with available department values from the company's data
✔ Filtering by department works as expected within the Engagement Overview modal
**Impact:**\
Clients can now filter engagement data by department, enabling more targeted analysis of prospect activity within a company.
###  Update: Responder Exclusion Display Improved – No More Year 3025 #Ops #CS #CX
**What was happening?**
When a prospect becomes a responder, the system applies a very long exclusion period (365,000 days) to prevent re-engagement.
This was previously displayed in the Portal as **"Excluded until 3025"**, which clients found confusing and unclear.
**What's changed?**
✔ Long-duration responder exclusions now display a **user-friendly label** instead of unrealistic future dates
✔ The backend logic remains unchanged — only the UI presentation has been updated
**Impact:**
Clients no longer see confusing far-future dates.
The exclusion display now clearly communicates the intent: the prospect should not be re-engaged.
## Sodastream Updates:
###  Update: CRM Improvements & Bug Fixes (Zoho & Salesforce) #Ops #CS
Several improvements and fixes have been made across CRM integrations to improve data accuracy, expand Zoho configuration options, and add proactive monitoring for Salesforce connections.
**What's been improved?**
**Zoho – Deal Layouts Now Supported**
✔ Users can now select a **Deal Layout** from a dropdown when setting up the Zoho integration\
✔ After selecting a Deal Layout, the **Deal Stage** dropdown filters to show only values from that layout\
✔ Behaviour mirrors the existing HubSpot Deal Pipeline selection
**Zoho – Deal Closing Date Field Added**
✔ A new **Deal Closing Date** field has been added to the Zoho CRM integration setup in the Portal\
✔ Users can select a future date, which is saved and synced to Zoho for all created deals\
✔ This resolves sync errors for Zoho CRMs that require Deal Closing Date as a mandatory field
**Salesforce – Token Expiry Email Notifications**
✔ A new automated check detects expired Salesforce tokens\
✔ When detected, the system sends an email notification to [**sopropremium.dev@sopro.io**](mailto:sopropremium.dev@sopro.io) (CC: [**support@sopro.io**](mailto:support@sopro.io))\
✔ The notification includes the **campaign name**, **CRM name**, and the error type\
✔ This prevents silent integration failures that previously went undetected until clients reported missing data
**Bug Fix – Incorrect First Name / Surname Split**
✔ For prospects with multi-part names (e.g., "Ana Cristina De La Torre"), the system was incorrectly splitting the surname — duplicating parts of the first name into the surname field\
✔ The name/surname split now correctly reflects the values stored in the Prospect database\
✔ Affects all CRM integrations including HubSpot, Zoho, and Salesforce
**Impact:**
Zoho clients can now configure Deal Layouts and mandatory Closing Date fields correctly.
Salesforce token expirations are caught proactively before data is missed.
And prospect names are now accurately synced across all CRM integrations, eliminating malformed entries.
###  Update: Campaign Settings – IP Match & Engage Section Greyed Out #Ops #CS
**What was happening?**
With the recent move of IP Match & Engage configuration to the **Approach** section, the old IP M\&E section in Campaign Settings was still editable, creating potential confusion.
**What's changed?**
✔ The **IP Match & Engage** section in Campaign Settings is now **greyed out** and non-editable
✔ All changes are now made exclusively under **Approach**
**Impact:**
Prevents accidental edits in the deprecated section and ensures all IP M\&E configuration is managed in the correct location **(under Approach)**.
###  Update: Polish and Czech Language Support Added to LIO Procedure #Ops
The LinkedIn Outreach (LIO) procedure previously did not support **Czech** and **Polish** languages, which blocked LIO execution for campaigns targeting those markets.
**What's been improved?**
✔ **Polish** and **Czech** have been added as supported languages in the LIO procedure
✔ LIO can now proceed for campaigns using these languages
**Impact:**
Ops teams can now run LinkedIn Outreach campaigns in Polish and Czech without manual workarounds.
---
# Agent Instructions: Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://help.sodastream.sopro.io/1.124.00-28.05.2026.md?ask=
```
The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.