1.89.50 (20.08.2024)

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

Improvements

Send number 0 to be disabled in Email templates

Where found: SodaStream > Email templates

We have implemented several enhancements to the email template management system, focusing on improving usability and visibility controls. The option to set the send number to '0' has been removed. All email templates must now have a send number greater than or equal to 1.

When creating a new email template, the send number will now be set to '1' by default. This change ensures that each new template is immediately ready for use in campaigns.

The "In use" field has been renamed to “Visible in SodaStream.” This update clarifies the purpose of the field, indicating whether the template is actively available within the SodaStream platform.

A new checkbox labeled “Visible on the Portal” has been added to the email template settings. This checkbox will be ticked by default for new templates, making them automatically visible on the Portal (Email templates page). When the "Visible on the Portal" checkbox is ticked, the corresponding email template will become visible on the Portal, making it accessible for users as intended.

HubSpot - v2 Owners API Sunset

HubSpot will discontinue the v2 API and migrate to the new v3 Owners API before August 30, 2024. This update is part of our ongoing effort to improve functionality, reliability, and the overall user experience.

The current v2 Owners API will be deprecated and no longer supported after August 30, 2024. This means that any applications still using the v2 API will no longer be able to sync owner-related data, potentially causing errors and disrupting service for our clients.

The new v3 Owners API has been designed to enhance performance, provide more robust functionality, and offer a more streamlined experience. This update includes improvements in data syncing, error handling, and API reliability.

Duplicate prospects engaged

Where found: SodaStream > Campaign & Setup > Campaign send schedules

We have implemented an important update to the prospect status workflow to improve tracking and management of prospects in the campaign process. This update introduces new statuses and ensures more accurate handling of prospects at different stages of the campaign.

When a prospect is scheduled for sends, their status field will now be updated to 'queueing.' Each 'queueing' prospect will be assigned a unique ID to ensure accurate tracking.

Once the system retrieves prospects marked as 'queueing,' their status will be automatically updated to 'queued.' This status indicates that the prospect is in line and ready for the next action in the campaign sequence.

After the scheduled action is completed (e.g., an email is sent), the prospect’s status will be updated to 'sent.' This confirms that the action has been successfully executed.

If a prospect is skipped due to specific campaign rules—such as reaching the maximum number of contacts allowed per day for a company—their status will be reset to 'new.' This ensures that skipped prospects are properly identified and can be re-evaluated in future campaign cycles.

The update ensures a more controlled and organized engagement process, reducing the likelihood of duplicate engagements.

SS WU 2.0: Date restrictions to be removed

Where found: SodaStream > Warm up

We have streamlined our warm-up processes by deprecating Warm-up 1.0 and removing the restrictions from Warm-up 2.0. This update allows for the use of Warm-up 2.0 with all email addresses, ensuring a more unified and flexible warm-up process.

With the shutdown of Warm-up 1.0, we have removed the following restrictions previously applied to Warm-up 2.0:

• Email Address Creation Date: No longer restricted by an email address creation date from the SS Database being after 01.06.2023.

• Domain Created Date: No longer restricted by a domain creation date from the SS Database being after 01.06.2023.

• Email Profile Creation Date: No longer restricted by an email profile creation date being after 01.06.2023.

• Active Warm-up 1.0 Schedule: No longer restricted by whether the email address is part of an active Warm-up 1.0 schedule.

These changes mean that Warm-up 2.0 can now be used for all email addresses, providing a more flexible and comprehensive warm-up solution.

Campaign inbox to skip Responder AI check for uncategorised

Where found: Client Portal > Campaign inbox

We have updated the behavior of the Portal system to improve the handling of uncategorized messages. The Portal will no longer recheck these pending messages, preventing unnecessary processing and improving the loading speed of the whole page.

Bug fixes

Send Schedule: OOO templates are sending emails for non-OOO prospects

Where found: SodaStream > Campaign & Setup > Campaign send schedules

We have identified an issue in our campaign system where more Out-of-Office (OOO) responses are being sent than expected. This is affecting the flow of campaign emails, particularly when recontacting prospects multiple times.

During our investigation, we discovered that when a prospect replies with an OOO response, all subsequent re-engagements in that campaign are being sent from the OOO template chain, regardless of the current status of the prospect.

The system should only send an OOO chaser if a new OOO reply is received in response to the last sent email. If no OOO reply is received, the regular template chain should continue as expected.

We are pleased to announce that the issue causing the system to send more Out-of-Office (OOO) responses than expected in campaigns has been resolved.

Campaigns should now proceed as intended, with the correct email templates being sent based on the prospect’s most recent reply status.

SS Campaign Settings: Credits Adjustment log cannot be removed

Where found: SodaStream > Campaign settings

We have identified and addressed an issue where the system was incorrectly reverting the credit adjustment log related to expired credits in campaigns, despite the "Allow Expired Credits" setting being enabled.

Despite this setting being turned on, the system continued to revert the credit adjustment log daily, specifically the log labeled “System Created - Credits should expire,” which was intended to be removed.

The system will no longer revert the credit adjustment log related to expired credits. The log “System Created - Credits should expire” will remain removed as expected, aligning with the "Allow Expired Credits" setting.

SS WU2.0: Edits are not updating in both DBs (Sopro live + WU2.0 DB)

Where found: SodaStream > Warm up

We have resolved an issue where updates to an existing warmup schedule were not being correctly reflected in the Warmup 2.0 database (DB). This fix ensures that changes made to the warmup schedule are accurately synchronized across all relevant databases. When editing an existing warmup schedule, specifically changing the email address and the warmup send type, the updates were correctly saved in the Sopro live database but were not being reflected in the Warmup 2.0 database. The issue has been resolved, and updates to the warmup schedule—including changes to the email address and warmup send type—are now correctly reflected in both the Sopro live DB and the Warmup 2.0 DB.

SS WU2.0: Editing a schedule is auto-changing the email profile address

Where found: SodaStream > Warm up

We have fixed an issue where the system was incorrectly switching to the first email profile address record when editing a warmup schedule, even when a different record was selected. This update ensures that the selected email profile is correctly retained and saved during the editing process.

SS Responder Inbox: Blank email content

Where found: SodaStream > Ops & Delivery > Campaign inbox

We have resolved an issue reported by the Ops team where replies in the Responder Inbox appeared blank within SodaStream, despite being fully visible when accessed directly in Gmail. This fix ensures that all replies are correctly displayed in the Responder Inbox.

CP Dashboard: Not opening companies

Where found: Client Portal > Dashboard

We have resolved a navigation issue within the Client Portal where URL changes were causing users to be unable to open company details from the Dashboard. This fix ensures that all links and redirects function correctly, allowing seamless access to company information.

OBIDs attributed to random people

We have identified and resolved an issue where OBID parameters on specific pages in the Portal were inadvertently cached by internal users, leading to inaccurate tracking of web visits and web goals. These parameters have now been removed to ensure more accurate tracking.

Certain pages in the Portal contained OBID parameters. When internal users clicked these links, the OBID parameters were stored in their cache, causing the system to incorrectly associate their internal visits with prospect visits. The OBID parameters have been removed from the Portal, eliminating the risk of internal visits being misattributed to prospects.