1.89.53 (17.09.2024)

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

Improvements

Generative Messaging to support different offering

Where Found: SodaStream > Campaign & Setup > Campaign Settings > Messaging

To support campaigns offering multiple products or services, the generative messaging feature has been updated to allow sender information to be pulled from different messaging sections within a single campaign.

New Drop-Down Menu in Campaign Email Profiles: The drop-down menu appears when "Generative" is selected in the Campaign & Setup > Campaign Email Profiles.

Each email profile can be connected to one messaging section, but a messaging section can be linked to multiple email profiles.

When a messaging section is selected, it sends the selection to AIM, ensuring that the generated messages correspond to the input provided in Campaign Settings.

Updated Website Field in Messaging: A new mandatory input field for the website has been added to the Messaging section. This field replaces the previous website information sourced from client management, ensuring accurate website URLs for generative messaging when multiple products/services are supported with one SS campaign.

Migration for Active Campaigns: For all active generative campaigns, the email profiles will initially be connected to "Messaging 1" to ensure consistency and prevent disruption.

Additionally, all messaging sections will have the website URL from client management mapped to the new field in Campaign Settings > Messaging

Create time stamp fields for activation date of the multichannel services

Where found: SodaStream > Campaigns & Setup > Campaign settings

To enhance reporting capabilities and enable the triggering of alerts and communications, the following activation dates are now captured in the system (SS) and ported to PH:

1. Webchat Activation Date - The date when the Webchat was published on a website.

2. LinkedIn Outreach Activation Date - The date when the first LinkedIn connection request was sent.

3. Website Plugin Activation Date - The date when the website plugin was activated.

4. Generative Messaging Activation Date - The date when a prospect was first engaged with a generative message.

5. IP Match and Engage Activation Date - The date when a prospect was first engaged via IP match and engage.

Remove libraries from Portal login to improve loading speed

Where found: Client Portal > Login page

It was identified that the libraries respond.min.js and html5shiv.min.js may not be utilized within the current system.

These libraries have been removed to clean up the codebase and enhance performance.

Bug fixes

SS Responder Inbox: Classified responses are going back to unresolved

Where found: SS > Ops & Delivery > Responders Inbox

Some responses that were manually classified as "Resolved" were incorrectly returning to the "Unresolved Responders/Reviewed by AI" tab after a few hours. The issue causing classified responses to revert to "Unresolved Responders/Reviewed by AI" has been identified and resolved. Classified responses will now remain in the "Resolved Responders" tab as expected, ensuring accurate tracking and resolution of responses.

Campaign Duplication After Deleting an Active Send Schedule

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

Deactivating and deleting a send schedule while it is currently running caused the campaign to be duplicated. This issue has been resolved to ensure that when a send schedule is deactivated and deleted while running, the system no longer triggers unintended campaign duplication. Campaigns will now maintain their integrity, preventing the creation of duplicate campaigns.

Templates are regenerated for excluded prospects

When an Ops owner manually adds a prospect to an exclusion list, new messaging is still regenerated for that prospect. This occurs both when the prospect is added to the exclusion list immediately after being uploaded and when added after Stage 1 messaging has been sent.

This issue has been resolved to ensure that when a prospect is added to an exclusion list:

• No new messaging is regenerated for that prospect.

• If the prospect is added to the exclusion list after any stage has been sent, all remaining stages are also halted, and no further messaging will be generated.

When a prospect unsubscribes, the user is still able to regenerate templates for that prospect

After a prospect clicks the 'Unsubscribe' link in a template and successfully unsubscribes, the system still allows the regeneration of templates and messaging for that prospect. This occurs even if the prospect has already received two stages of messaging and unsubscribed.

This issue has been resolved to ensure that once a prospect has unsubscribed:

• The system blocks the regeneration of new messaging for any remaining stages.

• Prospects who have opted out via the unsubscribe link are not subjected to further messaging generation.

SS Send Schedules Calendar: Marked as unsuccessful

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

Numerous send schedules were incorrectly marked in red on the calendar in SS (SodaStream) and flagged as "unsuccessful" in the database, despite executing sends successfully. This caused confusion regarding the actual status of the send schedules.

The issue has been resolved to ensure that:

• The status of send schedules on the calendar in SS and in the database accurately reflects their execution outcome.

• Only genuinely unsuccessful send schedules are marked in red and flagged as unsuccessful, while successfully executing schedules are displayed with the correct status.

Postal sends are not going out of InlineImages templates

When the "InlineImages" option is enabled, Postal was not sending messages, resulting in an "Error" status. Postal can successfully send templates containing inline images without triggering errors.

Moov Logistics don't have website sessions

Where found: Client portal > Prospects

Some prospects were marked as having visited the website as their last activity, but the details of the pages they visited were missing. The issue was linked to discarding website visits to privacy policy links that lasted less than 5 seconds, leading to an incomplete activity record.

Visits to privacy policy pages lasting under 5 seconds were discarded by the system. When these short visits were the only recorded activity, it resulted in the absence of any detailed page visit information for the prospect.

Prospects' last activity now reflects meaningful interactions, providing clearer insights into their website engagement.