Page cover

1.89.59 (29.10.2024)

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

Improvements

Responder AI improvements

  1. Different email pattern, same domain: Responders are splitting the email address and prospecting email addresses into email pattern and email domain. The system will now cross check if the email domain corresponds/is identical to a prospecting email with a different email pattern from the list of prospects engaged.

  2. New filters have been added for the undelivered messages so that the number of undelivered responses that are classified is increased.

  3. This rule is applied only to Undelivered responses. When there are multiple suggestions in the "Check Email" section for a responder under a matching domain, the system automatically selects the suggestion that shares the same date and has the closest time proximity between the “Last Sent” and “Response Received” timestamps.

  4. Responses that have "Marked for manual review" flag are now marked in SS as well. This will provide better visibility as to why a response wasn't resolved by AI.

  5. All responses associated with sopro.io will be automatically moved to Invalids.

  6. Warm up email address was matched as a response, we have identified the issue and it's resolved.

Include additional points for generative messages

To improve the effectiveness and personalization of generative chasers, we have introduced new data points that will enrich generated messages with contextual insights, where available.

Details

The system now includes the following data points in message generation:

  1. Recently Contacted Prospects in Recipient Company: If recent engagement has occurred, messages will display relevant contacts within the recipient's company, including name, position, and contact recency (e.g., "David Jones / CEO / 5 days ago").

  2. Alternative Qualified Prospects Not Yet Contacted: When applicable, messages will list additional qualified prospects within the recipient's company who have not yet been emailed, identified by name and position (e.g., "David Jones / CEO").

  3. Recent Buyer Intent from Recipient’s Company IP Address: A buyer intent indicator based on web visits will inform whether the recipient company has shown interest recently:

  • Last 30 Days: [Yes/No]

  • Last 90 Days: [Yes/No]

  1. Direct Buyer Intent from Recipient: Similarly, buyer intent data for the individual recipient will be indicated based on recent web activity:

  • Last 30 Days: [Yes/No]

  • Last 90 Days: [Yes/No]

These data points enable more tailored and contextually relevant chasers, resulting in enhanced engagement through improved message personalization.

Send the Previous Emails (for Chasers) in a specific form

When sending previous emails to AIM for template generation, the current format did not adhere to the required structure, causing AIM to misinterpret the content and impacting message generation accuracy.

Emails are now sent to AIM in the correct format for improved contextual understanding. The new format lists emails in reverse order, with each message clearly labeled and enclosed in quotes as follows:

  • Email 3: "message 3 content"

  • Email 2: "message 2 content"

  • Email 1: "message 1 content"

Push Sender Info button limitations

Currently, clicking the Push Sender Info button multiple times under SodaStream > Campaign & Setup > Campaign Settings > Messaging creates duplicate Test Sender entries in AIM. This can lead to multiple test senders for the same campaign, causing confusion and clutter. The functionality has been updated so that each time the Push Sender Info button is clicked, it will now overwrite the existing Test Sender on AIM rather than creating a new entry.

Sender Info Lookup button renaming and new text boxes

To improve the ease of populating Sender Info, the Sender Info Lookup button in SodaStream > Campaign & Setup > Campaign Settings > Messaging has been renamed and enhanced with a new UI and functionality to better support the CS team.

  1. Button Renaming and New Function:

    • The Sender Info Lookup button is now renamed to Auto-suggested Messaging.

    • Clicking this button sends a request to AIM to generate suggested content for text boxes, including Company Description through USPs.

  2. New Auto-Suggested Text Boxes:

    • Upon clicking Auto-suggested Messaging, a set of new text boxes will appear on the right side of the Messaging section.

    • These text boxes are automatically populated with AIM-suggested content specific to each field.

  3. One-click Copy Feature:

    • A new Copy All button allows CS users to transfer all content from the auto-suggested text boxes on the right to the corresponding fields on the left with a single click.

  4. Temporary Data Display:

    • The content in the auto-suggested text boxes is temporary and will not be saved; it will reset upon refreshing the page.

These updates streamline the process for CS teams to populate Sender Info, allowing for quick and efficient use of AIM-generated suggestions without unnecessary data retention. The improved UI and functionality reduce setup time and enhance the usability of the Messaging section.

Retrieve Sender Info/Messaging from AIM to SS

A Retrieve Sender Info button has been added to the Messaging section, enabling users to easily refresh sender information from AIM for a given campaign.

  1. Retrieve Sender Info Button:

    • A new Retrieve Sender Info button has been introduced in SodaStream > Campaign & Setup > Campaign Settings > Messaging.

    • Clicking this button will pull updated sender information from AIM, overwriting existing data for the associated campaign based on the AIM Test Sender ID.

    • The layout of buttons under Messaging has been reorganized to improve accessibility and workflow.

This update allows users to quickly refresh sender information for campaigns, ensuring accuracy and alignment with AIM data, while the updated layout enhances usability in the Messaging section.

Creating Test Senders on AIM naming conventions

With the recent addition of multiple Messaging sections for Generative Messaging, the Push Sender button functionality has been updated to ensure clear identification of each Test Sender on AIM.

Details

  1. Automatic Naming for Test Senders:

    • When the Push Sender button is clicked in any Messaging section, a corresponding Test Sender will be created on AIM with a unique name reflecting the section, such as:

      • Sopro - Messaging 1

      • Sopro - Messaging 2

      • Sopro - Messaging 3

  2. Consistent Naming for Clarity:

    • This structured naming convention ensures each Test Sender aligns with its specific Messaging section, improving clarity and management of multiple Test Senders for campaigns.

    This update allows users to easily distinguish between multiple Messaging sections on AIM, supporting more organized and effective Generative Messaging setup and tracking.

Show "SDR Direct Sign up" SDR Lead type in New Reports

Where found: https://portal.sopro.io/report

The “Direct Sign-Up” SDR Lead type is now available in the reporting suite for clients enabled with this specific lead type. This update provides visibility into Direct Sign-Up leads, incorporates them into lead calculations, and ensures accurate lead counts.

  • Client Portal → Reports → Lead Column (Expanded View): “Direct Sign-Up” leads will appear in the expanded Lead column. If the count is greater than zero, it will display by default; otherwise, clients can toggle it on in the Lead type selection filter.

  • Client Portal → Reports → Filter Lead Type: The “Direct Sign-Up” type has been added to the Lead Type filter for easier segmentation and analysis.

  • Client Portal → Reports → Lead Count: Lead counts will now include “Direct Sign-Up” leads, reflecting this type in totals and summaries.

  • Client Portal → Dashboard → Leads Card: The overall lead count on the Leads card now factors in “Direct Sign-Up” leads.

This update ensures more comprehensive reporting for clients using the “Direct Sign-Up” SDR Lead type, delivering improved visibility and accurate lead tracking across Reports and Dashboard views.

WCH - User changes

Where found: https://portal.sopro.io/webchat-settings

New user management enhancements have been implemented for webchat roles in the Portal to streamline permissions, increase flexibility for clients, and maintain internal visibility for CS and OPS owners.

All client sales agents will now be created as webchat users by default, with the Team Member role. Sopro account managers can upgrade selected sales agents to Admin to allow role flexibility on the client’s end.

Client Admins, and Sopro account managers can now add additional webchat users and assign roles using the Add User button in the Portal.

Client Admins can only see client-specific users in the dropdown and will not have visibility of internal Sopro users.

Assigned OPS and CS owners will automatically be set as webchat Admins with availability set to "unavailable" and notifications turned off, preventing them from being considered in chat assignments.

These users can invite additional CS and OPS users with the Admin role via the Portal if needed.

The list of CS and OPS owners will be visible only to internal Sopro users, ensuring clients do not have access to this internal information.

These updates provide greater control and clarity in webchat user management, with improved role assignment for clients and secure internal visibility for CS and OPS roles.

WCH - storing contact information

Where found: https://portal.sopro.io/webchat

Information submitted by visitors through contact forms is now captured, classified, and made available across various channels for streamlined follow-up and tracking.

  1. Data Capture: All contact form submissions are now stored for further use.

  2. Automated Classification: Submitted information is sent to AI for automatic classification, enhancing response relevance and follow-up accuracy.

  3. Agent Notifications: Contact form data is included in missed chat emails sent to agents, ensuring no lead information is overlooked.

  4. Prospect Preview in Portal: Form details are displayed in the Portal’s prospect webchat preview for quick reference.

  5. SodaStream Webchat Inbox Visibility: Contact form information is accessible in the SodaStream Webchat Inbox for efficient lead handling and tracking.

These enhancements enable agents to respond to leads more effectively by providing centralized visibility of contact form submissions across key interfaces.

Enable/disable tracking _obid on email template level

Where found: https://sodastream.sopro.io/EmailTemplate/List

To improve flexibility in deliverability testing, a new selection menu for OBID tracking has been added in SS > Email Templates.

Users can now select from the following options for OBID tracking:

  • Use OBID - OBID will be tracked for the specific email template

  • Don’t use OBID - OBID won't be tracked for the specific email template

  • Use client preference (default option) - OBID will be tracked as per the settings in Client management

The “Use client preference” option will be checked by default.

This update enhances the customization of email templates for deliverability testing, ensuring users can easily manage OBID tracking preferences based on their needs.

Hide audience insights

Where found: https://portal.sopro.io/audience-insights

This feature was affected with the introduction of the new data sourcing functionalities. Given all new channels and features that we've introduced and in-line with the business model we're removing this page from the Portal.

Bug fixes

CP Generative Templates: Incorrect sample data

Where found: https://portal.sopro.io/email-templates

The Ops team identified that two specific campaigns were displaying randomly generated data in the CP Email Templates, rather than pulling information from the designated campaign audience. The issue has been addressed to ensure that the CP Email Templates now correctly pull prospects from the designated campaign audience. This adjustment will guarantee that only relevant audience data is displayed in the templates.

SS Load Prospects: Pending prospects

Where found: https://sodastream.sopro.io/Prospect

When exporting prospect data from Sopro Data as a result of a Prospect Search in SodaStream (SS), the industries listed in the exported file did not exactly match our standardized industry names. For instance, where SS expects "Health, Wellness and Fitness," Sopro Data might return "Health, Wellness And Fitness." Because this field is case-sensitive, SS would send the prospects to "Pending" status upon upload and mark them as having an invalid industry in the database (Prospects table).

SS now automatically standardizes incoming industry names from Sopro Data to match our exact industry names during upload. For example, "Health, Wellness And Fitness" will be converted to "Health, Wellness and Fitness," ensuring seamless uploads without affecting reporting.

CRM Integrations: Skip update / create on manual response classification

Where found: https://portal.sopro.io/crm-integrations

Previously, when a response was received in the SS Responder Inbox, the Responder AI would automatically classify the response type and immediately send the prospect to the client’s CRM. Following this, the Operations (Ops) team would manually verify and classify each response type. If the Ops manual classification matched the AI’s prediction, a second, redundant update/insert would occur in the client’s CRM, potentially causing data conflicts if clients had made changes to that prospect’s CRM record in the interim.

The process has been optimized to prevent unnecessary CRM updates. Now, if the Ops team’s manual classification matches the Responder AI’s initial prediction, no additional update or insert will occur in the CRM. However, if the manual classification differs from the AI’s prediction, the prospect’s data will be updated or re-added to the CRM as needed.

This update reduces redundant CRM entries, minimizes data conflicts, and enhances data accuracy by aligning CRM updates only when necessary. Clients can expect smoother CRM integrations with fewer disruptions from multiple updates.

New reports -> Filter by Email Address shows same email addresses multiple times

Where found: https://portal.sopro.io/report

Previously, when filtering by email address in the New Reports, duplicate email addresses would appear if they were associated with multiple email profiles, leading to redundant entries in the filter view.

The Email Address filter in New Reports has been optimized to display only unique email addresses, grouping them across different email profiles. This ensures a clean, streamlined list of unique email addresses in the filter.

Incorrect validation message for the 'Preferred tone for messaging' field in Email Templates

Where found: https://sodastream.sopro.io/Campaign/CampaignsList?status=true

In the ‘Preferred Tone for Messaging’ field under SS > Campaign Settings > Messaging, users are guided by a tooltip to “Add a minimum of 3 words” and can save settings with exactly three words. However, in Portal > Email Templates, a toast notification incorrectly prompts users to "add at least three words" when attempting to generate a template with exactly three words, preventing successful template generation.

The validation has been updated to ensure that the template generation process in Portal > Email Templates accepts exactly three words in the 'Preferred Tone for Messaging' field, in alignment with the tooltip guidance.

Edit on second page in Planhat doesn't work

Where found: https://sodastream.sopro.io/CampaignPlanHat

When navigating to the second page of the PlanHat Licenses section in SS and attempting to edit a license, the edit modal fails to open, preventing any changes from being made.

The issue has been resolved, and the edit modal now opens correctly when selecting "Edit" on any page of the PlanHat Licenses section.

Last updated