Here's what to look for in the November 13th release. 

The guidance in this document is offered for early planning purposes and is subject to change up to the time of release. 

Data & Analytics

Sites Insights for advisors

Problem Solved: Advisors/agents using Sites do not have data insights available that provide their Site’s key business measures, such as the number of visitors or the referrers (like Google search, social media, etc.) sending visitors to the Site.

Expected Value: Advisors/agents will be provided with data and visualizations of the key business measures relevant to their Sites' performance. They will be able to see the trends over a 3-month period, identify where their Site's performance is better or worse than the performance of their peers, and they will receive recommended actions that are useful to help them improve their performance figures.

Expected Solution: A new advisor/agent dashboard will be accessible to the end-users from the Insights tab in the side menu. The Insights dashboard will expose key business measures at the individual Site level, as well as benchmarking against other advisors/agents in their hierarchy and recommended actions. The following measures will be available:

• Number of visitors with a breakdown of new and returning visitors 
• Average time spent on the Site 
• Number of visitors by source type (e.g. Google Paid, Organic, HS Social) 
• Number of leads (based on the number of visitors who have submitted contact forms) 
• Lead types (based on whether the contact form was submitted as an event RSVP or whether the lead was sourced from the standard contact form).

Who is impacted: Advisor/Agent
Archiving and Compliance Implications: No impact
Availability: On for Sites customers in organizations that allow Hearsay’s Google Analytics.

Localization of admin reports

Problem Solved: Currently, the in-app admin reports have English headers, regardless of the user’s language setting. With the new localized versions, the admin report headers will be translated as per the language set by the admin.

Expected Value: User experience will be improved by providing translated versions of the in-app Admin reports.

Expected Solution: The headers for the in-app Admin reports will be translated into the preferred language set by the Admin.

Who is impacted: Compliance Admin, Marketing Admin, Program Admin
Archiving and Compliance Implications: No impact
Availability: On for all organizations.

Breakdown by Relate Workspace report will include the workspace owner’s email address 

Problem Solved: The workspace owner’s email address is currently not included in the Breakdown by Relate Workspace report, which makes it difficult for admins to track workspace-specific Relate performance.

Expected Value: The workspace owner’s email address can be used as an identifier when tracking workspace-specific Relate performance, and to facilitate contacting the workspace owner.

Expected Solution: The Breakdown by Relate Workspace in-app Admin report will be extended with a new Email address field which will contain the email address of the workspace owner.

Who is impacted: Marketing Admin, Program Admin
Archiving and Compliance Implications: No impact
Availability: On for all organizations using Relate.

Relate

Send a personalized opt-in message from Embedded Relate for Salesforce

Problem Solved: Embedded Relate users must use a standard opt-in message when initiating a conversation. There is no option to personalize or edit the standard opt-in message in Embedded Relate, even if the settings are differently configured for desktop or mobile Relate.

Expected Value: Embedded Relate users will be able to personalize their opt-in messages used in Embedded Relate and adopt a more client-centric approach in their communications.

Expected Solution: Embedded Relate users will be able to send personalized opt-in messages if enabled by the organization.

Who is impacted: Admin, Advisor/Agent 
Archiving and Compliance Implications: No impact
Availability: Can be installed from a package by Salesforce admins.

Embedded Relate for Salesforce supports opting-in by implied consent 

Problem Solved: Embedded Relate only permits advisors/agents to start sending messages when the contact replies YES to the initial opt-in message. This hinders communicating with contacts who already have an existing business relationship and/or who have a reasonable expectation of receiving specific messages. 

Expected Value: Advisors/agents will not have to wait to send messages until the contact has replied YES to their opt-in message. They will be able to immediately send messages to contacts after an implied consent opt-in message has been sent.

Expected Solution: Organizations that have enabled implied consent attestation will be able to start sending messages using Embedded Relate without waiting for the contact to reply with an attestation confirmation. With implied consent enabled, Embedded Relate will permit texting a contact immediately after sending an implied consent attestation message.

Implied consent attestation will work for organizations that have enabled or disabled personalized opt-in messages.

Who is impacted: Admin, Advisor/Agent 
Archiving and Compliance Implications: No impact
Availability: Can be installed from a package by Salesforce admins.

Social

Alternative descriptions for suggested posts enabled by default

Problem Solved: Social media network algorithms favor content with variables, and this feature that allows variable post descriptions isn’t enabled by default. Enabling this already existing optional feature for all organizations helps increase the reach of the posts. 

Expected Value: Alternative descriptions allow admins to create one post they can customize for different types of users and audiences, increasing efficiency and improving social media strategy. 

Expected Solution: When creating a suggested post, admins can click Add Alternate Description and create a different description to go with the post. When a user publishes the post, they can choose which description to use by clicking the < > arrows. Admins can add an unlimited number of descriptions per post.

Alternate description when suggested creating a post

Arrows to choose which description to publish

Who is impacted: Advisor/Agent, Marketing Admin
Archiving and Compliance Implications: The alternative post descriptions are treated like any other post description in supervision and archiving.
Availability: On for all organizations.

Ignore or archive responses to LinkedIn Recruiter & Sales Navigator InMail messages

Problem Solved: In the previous Hearsay release, a new setting was introduced to configure whether LinkedIn Recruiter and Sales Navigator InMail messages are ignored or archived. However, when set to Ignore, only Recruiter and/or Sales Navigator messages received by users were ignored and user responses to those messages were still archived as regular private messages. 

Expected Value: The archiving settings for Recruiter and SalesNavigator InMail messages will fully align with customer compliance policies, providing comprehensive control over conversations.

Expected Solution: With this enhancement, responses to Recruiter and SalesNavigator messages will also be archived or ignored based on the admin setting.

Who is impacted: Compliance Admin
Archiving and Compliance Implications: Responses to Recruiter and InMail messages can be ignored.
Availability: On for all organizations.

Archive LinkedIn Recruiter and/or Sales Navigator InMail messages independently of regular private messages

Problem Solved: Private message compliance policies differ customer-by-customer. The current LinkedIn Review & Archive settings allow admins to archive Recruiter and/or Sales Navigator InMail messages only if the regular private messages are also archived.

Expected Value: The archiving settings for Recruiter and Sales Navigator InMail messages will fully align with customer compliance policies, providing comprehensive control over conversations.

Expected Solution: Any combination of regular private messages, Recruiter InMail, and Sales Navigator InMail messages can be archived or ignored in accordance with individual customer compliance policies. 

Recruiter and Sales Navigator settings will no longer a subset of Private Messages in Hearsay Desktop

Who is impacted: Compliance Admin
Archiving and Compliance Implications: LinkedIn Recruiter and Sales Navigator messages can be archived without all private messages set to be archived.
Availability: On for all organizations.

Platform

Increased API security after creating a token

Problem Solved: API tokens/keys are always visible in the admin view, under Settings > Integrations, which makes them easy to copy and misuse.

Expected Value: Better token security improves the safety of customer data.

Expected Solution: The API Token value will only be shown immediately after it is created. After that, it will be hidden in the list of tokens on the Integrations page. If access is needed for a new application, a new token will need to be created.

Message about token visibility

Who is impacted: Integrator and Program Admin
Archiving and Compliance Implications: No impacts
Availability:On for all organizations.

Reactivate deleted contacts when imported or added via the API

Problem Solved: For compliance purposes, deleted contacts are only hidden and cannot be permanently deleted from the system. But if a user tries to import a contact that was previously imported and then “deleted”, the contact is still hidden and unavailable until it is restored manually on the Contacts page.

Expected Value: Contacts that are imported or added via the API are available for use, even if they were previously hidden from view. 

Expected Solution: When a contact record is imported or added via the public API, any matching record that was deleted will be restored and unhidden. 

Who is impacted: Advisor/Agent, Program Admin, Integrator
Archiving and Compliance Implications: No impact
Availability: On for all organizations