Client Portal Updates:
Update: New logic for notifying Sales Agents for Qualified but not Engaged Company intent
#Ops #CS
For 'Company Intent Notifications' triggers, if 'All Qualified Companies' was selected, the system was not able to identify a Prospect Owner/Sales Agent as there are cases where companies were not yet engaged by any Sales Agent.
What's new:
A new logic has been implemented for 'Company Intent Notifications'.
There are two different cases, for 'Engaged Companies Only' and for 'All Qualified Companies' trigger notifications.
What's changed:
If 'Engaged Companies Only' is selected as a trigger, the Portal will send notifications for the Company Intent of engaged companies only.
If there are multiple prospects engaged from the company that's triggering the intent goal, the Sales Agent from the most recent prospect engaged will receive the notification
If 'All Qualified Companies' is selected as a trigger, the Portal will send notifications for companies that hit a specific intent, and fall under the IP Match and Engage targeting in Sodastream ⇒ Campaign Settings
The system will notify the Sales Agent who is related to the Email Profile linked with the IP Match and Engage targeting in Sodastream.
Update: 'State' field implemented for Exclaimer Salesforce Integration
#Ops #CS
Exclaimer is a client with an active Salesforce integration. With their outreach being mostly in the US, their requirement was a custom field to be implemented on our Portal, so that we can transfer the State value from the prospect engaged.
What's new?
With the deployment, an update has been made, and a custom 'State' field has been introduced for Exclaimer.
Once a new integration has been made, the 'State' field can be matched with the respective field in their Salesforce, and we will push the State values for the prospects that are engaged through the outreach.
Update: Source field not populated for Simple Grants CRM Integration
#Ops #CS
The client Simple Grants has an active CRM integration with the old triggers.
This has affected the Source field from being properly populated for some prospects that were integrated into their CRM.
What's changed
A fix has been applied. Post deployment, the source field will be populated as expected and the 'Sopro' value will be integrated into the client's CRM.
Bug Fix: RTE Requests were not processed in Portal
#Ops #CS #CX
What was the issue:
Users have reported that the Portal was not processing and removing data for RTE requests in the Compliance tab.
This was affecting the business's compliance, as Ops and CS users were not able to act on the SAR/RTE requests coming from prospects.
What has been fixed:
We've identified the issue, and a fix has been deployed that will resolve this issue.
Users will be able to process the SAR/RTE requests as expected, and the Portal will remove the data that we store for the prospects that request the SAR removal.
Bug Fix: Users can't re-enter their LinkedIn Credentials
#Ops #CS #CX
What was the issue:
Once a user enters their LinkedIn Credentials and deletes them, they are not able to re-enter the credentials.
The Portal was displaying a notification that the 'Account already exists' even though it was deleted.
Our system was not making a proper check in the background to see if the user with the same email had been deleted or not.
What's changed:
A fix was deployed that will resolve this.
If a user enters and deletes their LinkedIn credentials in the Portal, the system will make a proper check and allow users to re-enter their credentials.
Sodastream Updates:
Bug Fix: Sodastream was stuck when opening Resolved tab in the Responders tab
What was the issue:
There was an issue when users were trying to review a resolved responder in Sodastream ⇒ Responders tab.
If a specific campaign was selected and the Resolved tab was opened, Sodastream was stuck at 'Processing', and no results were shown.
What has been fixed:
An update has been made, and with the new improvement, the Resolved tab is expected to open properly and load faster than previously.
Bug Fix: Filtering by Email Profile in Companies and Prospects search not working
#Ops
What was the issue:
For campaigns with multiple Audiences created, Ops usually used the 'Email Profile' filter to find a specific Audience linked to that Email Profile.
This was not working as expected, which prevented users from fast browsing through the audiences.
What's been fixed:
The issue has been identified, and a fix was deployed.
Filtering by Email Profile in the 'Companies and Prospects search' tab is now working as expected. Users will be able to browse the audiences related to a specific Email Profile faster.
Bug Fix: Filtering by Email Stage in Email Templates was broken
#Ops
What was the issue:
Ops Users were not able to browse and filter by Stage in Email Templates in Sodastream.
This caused issues in campaigns with a larger volume of email templates, as users were having trouble finding an email template from a specific stage.
What's been fixed:
A fix has been implemented that resolved this issue.
Filtering and browsing by Stage in Sodastream ⇒ Email Templates now work as expected. Filtering by a specific stage now returns email templates that only fall under the selected email stage.
