This provides support for any FAQs and gives users direct access to beneficial material and collateral from our Sopro Knowledge Centre.
Update: New Notification has been implemented to indicate Generative Message setup issue #Ops #CS
What was happening?
There were multiple cases where users would create an Email Profile and link it to a Campaign Messaging Setup that was initially created blank.
The 'Sender info to be taken from' appears as successfully populated and linked in the frontend, but since the Messaging Setup was created afterwards, this remains blank in the database.
Additionally, a misleading notification was being displayed in the Portal, asking users to shuffle a new prospect.
What has changed?
We've implemented a new notification that will alert users that the setup is not done right.
If the Email Profile is not successfully linked to a Campaign Messaging in the background, when users try to generate a message, the Portal will display the following notification:
"Check the Generative Messaging Setup - 'Sender info to be taken from' in the Email Profile is empty"
This will indicate that the users will need to recheck and save the Email Profile with the accurate Campaign Messaging, in order for the Portal to successfully generate the messaging.
Bug Fix: Timestamp for daily/weekly prospect/company visits now displays the exact value #CX #Ops #CS
What was the issue?
When users were being notified of prospect or company goals on a daily or weekly basis, the timestamp was always displaying 00:00:00 in the summary table sent in the notification email.
What has changed?
This issue is now resolved. Post deployment, the daily or weekly summary notifications for both prospect or company intent goals should display the exact timestamp of when the visit/intent goal happened.
Bug Fix: SDR and Indirect Lead links not loading filtered results #Ops #CS
What was the issue?
An issue was reported in Portal ⇒ Reporting tab affecting SDR and Indirect Lead links, not displaying the correct results in the Prospects tab.
When clicking the SDR Leads or Indirect Leads number in the Success Report section of the Reporting tab, the Portal was redirecting to a blank Prospects page, and not filtering the respective leads.
What has been fixed:
The issue has been identified and fixed.
Indirect and SDR lead links now redirect to a Prospect page, which displays and shows the leads that fall under the respective category.
This gives users a clear display of all prospects or companies which we are categorising as Indirect or SDR leads, and these can be accessed again by just clicking the hyperlinked number.
Bug Fix: Password change in 'Account settings' has now been fixed #CX #Ops #CS
What was the issue?
A bug appeared that prevented users from changing their Portal password from 'Account Settings' in Portal (https://portal.sopro.io/manage)
What has been fixed:
We've successfully resolved the issue, and this option now works as expected.
When needed, users can access this option and change their old Portal password to a new one.
Sodastream updates
Update: UX/UI improvements in Companies & Prospects Search #Ops
A request came in from Ops users to improve the UX/UI in the Companies & Prospects Search tab.
What was happening?
When using Negative Keywords in order to exclude specific Job Titles, Sodastream displayed these in blue, the same as the values that are to be included in the search.
What has changed?
We've made an update to change the colour of the excluded values in the Job Title filter.
Once users implement certain Negative Keywords in the filter, these will now be marked in red, in order to provide better visibility, and avoid misunderstanding in what's excluded from the search.
Update: Credits per prospect is now removed from Email Profile modals #Ops
As we've moved to the new commercial model, and credits are no longer being used, we're adjusting all credit references that are present in Sodastream.
With the latest deployment, we are removing the 'Credits per prospect' field in the Email Profiles, as this is now obsolete and is not needed when creating Email Profiles.
Bug Fix: Company name text box in Campaign Audience not expanding when multiple values are entered #Ops
We've deployed a UI/UX fix for a text box in Campaign Audience.
When users were trying to create an Audience with filters in the 'Company name' search bar, the text box was not expanding.
This was preventing users from having visibility into what was implemented in the search, and caused inconvenience when this search option was used.
A fix has been deployed to improve the UI/UX of this search option.
The text box should now expand when multiple values are included in the 'Contains' option in 'Company name', giving accurate visibility to Ops users.
Bug Fix: Excluding companies from Campaign Audience is not working properly #Ops
What was the issue?
When users were creating Campaign Audiences and wanted to exclude specific companies from the audience, Sodastream was not excluding them, and the companies kept showing up in the search results.
This prevented users from having accurate data and excluded unwanted companies from email engagement.
What's changed:
The issue has now been resolved, and the feature works as expected.
When Ops users create an audience search with specific filters, upon review of the companies that are displayed, they will be able to exclude the unwanted companies.
When selecting the companies, Sodastream successfully excludes the selected companies, and when the 'Search' button is clicked, the search does not display the excluded companies.
Bug Fix: Pipedrive integration syncing full URLs instead of company domains #Ops #CX
There was an issue related to Pipedrive integrations, which resulted in syncing full URLs (i.e. https://sopro.io) instead of the exact company domain (sopro.io) to the client's CRM.
This resulted in data being pushed with inaccurate values to the Pipedrive CRM of the client.
What's been fixed:
We've deployed a fix, and Pipedrive integrations should now sync the exact company domain of the prospect that was engaged.
A switch has been made in the backend logic on where this information will be pulled from.
Post-deployment the domain field will be populated with the required format, instead of syncing the full URL.