Here's what to look for in the March 27th release. 

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

Social

AI-Powered Content Recommendations

Problem Solved: There’s currently no way for Hearsay Social to remember content preferences of advisors/agents and their audience, which makes finding content difficult and time consuming. 

Expected Value: Better content recommendations based on individual preferences increases advisor/agent engagement with Hearsay Social and makes it more likely they will post the content to their social media pages.

Expected Solution: Using data related to audience engagement, advisors/agent interests, browsing history, and behavior, we’ll implement an AI solution that provides personalized Post Library content recommendations for each advisor/agent, similar to recommended lists in popular apps like Spotify or Netflix. The more advisors/agents use Hearsay Social, the more content recommendations are tailored to their preferences. 

There will be six sections of content in the Recommended tab, as follows:

• Highlights at : Content recommended by content creators/admins.
• Recommended for your audience: Content the advisor/agent’s audience is engaging with the most. 
• Based on your interests: Content based on the advisor/agent search and publishing history. 
• Most recent: The newest content added by content creators/admins.
• Most engaging: Content receiving a lot of audience engagement when posted by the advisor’s/agent’s peers.  
• Popular with your peers: Content being published a lot by advisors/agent’s peers. 

The regular Post Library will still exist in the new Browse tab. 

Relate 

Access LinkedIn direct messaging via Relate

Problem Solved: Advisors/agents aren’t able to access LinkedIn direct messages on Relate. LinkedIn direct messages represent a high-volume prospect/client engagement opportunity for advisors, but Relate isn’t able to leverage the potential outcomes of the channel. 

Expected Value: Integrating LinkedIn direct messages with Relate will allow advisors/agents to access LinkedIn direct messages using Relate, providing a better unified direct messaging experience on the Relate platform and reducing delays in communication. 

Expected Solution: Advisors/agents will be able to send and receive LinkedIn direct messages on Relate in Hearsay Desktop, as they would a Relate text message. Relate will frequently crawl LinkedIn direct messages between 8:00 AM Eastern Time and 9:00 PM Eastern Time to check for new messages. In order to port/view LinkedIn conversations in Relate there must first be an existing conversation in LinkedIn, i.e. the user has sent or received at least one direct message to/from another person on LinkedIn. Messages received via LinkedIn direct messaging will be marked with a blue LinkedIn icon in the Conversations tab in Relate.

This feature is only available to users who have both Hearsay Social and Hearsay Relate enabled.

Advisors/agents won’t be able to disconnect their Relate phone number

Problem Solved: Advisors/agents have the ability to disconnect their Relate phone number. Disconnecting a Relate number leads to a violation of regulatory requirements because it creates an audit trail gap that results in a lack of transparency and accountability for communication, which can lead to regulatory fines and damage to the reputation of the organization. 

Expected Value: Restricting advisors/agents’ ability to disconnect their Relate phone number provides assurance to regulators and our users that their communication is compliant, secure, and accountable. By maintaining a complete audit trail of communication, Relate ensures that all communication is fully transparent and compliant with regulatory requirements, which reduces the risk of regulatory fines and other legal consequences that may arise from non-compliance.

Expected Solution: Agents/advisors will no longer be able to disconnect or remove their Relate phone numbers.

Attestation in one workspace applies to the whole organization

Problem Solved: If an organization’s Relate attestation settings are set to Explicit Consent, Web Opt-In, or Personalized Opt-In, each advisor/agent has to send individual opt-in requests to their contacts, and the contact’s communication channel gets opened only with those advisors/agents with whom they have specifically opted-in to receive messages. This results in communication delays as well as lost opportunities for adoption and growth because only a limited number of agents/advisors in an organization are able to communicate with prospects and clients. 

Expected Value: An organizational opt-in model will replace the individual advisor/agent opt-in model so that all advisors/agents from an organization will be able to text clients who agree to receive messages from that organization. This will reduce the need for multiple opt-in approvals, increase opt-in approval rates, improve client satisfaction through faster communication, and increase the number of conversations that drive business.

Expected Solution: A contact’s attestation in one workspace will apply to the whole organization. This new attestation model will be based on 4 rules: 

• When a client has opted-in (by responding YES) to texting with an advisor/agent at an organization, their number is added to the allow list and all advisors/agents at that organization will be allowed to text that client without additional opt-in requirements. 
• If a client opts-out (by responding STOP), their number will be removed from the allow list and added to the deny list. Their number will be blocked and nobody from the organization will be able to text them.
• If a client responds with UNSTOP, they will be automatically removed from the deny list and added to the allow list for the organization and advisors/agents will be able to send text messages to their number.
• Attestation in one workspace propagates to the whole organization almost in real time.

This feature is currently only available for organizations whose Relate attestation settings are set to Explicit Consent.

Mobile

Relate Mobile App includes Post Library and AI-Powered Recommendations

Problem Solved: Publishing content from the Post Library using the Hearsay Social mobile app is limited and outdated, and advisors/agents need to use two separate apps to browse the Post Library and communicate using Relate on mobile.

Expected Value: Advisors/agents can efficiently promote their brand by quickly publishing compliant content they are interested in while on the go using a single mobile app.

Expected Solution: In a continued effort to transform the Relate app into a unified mobile experience that encompasses both Relate and Social functions, advisors/agents will be able to browse, filter, and post suggested content within the Relate mobile app. The new AI-Powered Content Recommendations enhancements for Social, also in this release, will be included in the mobile Post Library and will enable advisors/agents to quickly find the most relevant posts. Advisors/agents will also be able to browse the library of all approved posts and filter by the post type, network, and tags to find the right content. 

SITES

Sites Post Library design matches the Social Post Library design

Problem Solved: Advisors/agents who use both Sites and Social can access the Post Library in two different ways: Via Sites (Sites > Posts) and Social (Social > Content). However, the look and feel of the Post Libraries are different, which can be confusing.

Expected Value: A consistent look and feel across the platform improves user experience and enables us to release Post Library improvements for Sites and Social users at the same time.

Expected Solution: The Sites Post Library will be modeled after the newer and more streamlined Social Post Library.

Current Sites Post Library (pre-release)

Social Post Library, and how the Sites Post Library will look after the release

Preview changes on Sites

Problem Solved: In the newest version of Sites, advisors/agents and compliance admins can’t preview changes to the website to see how they look.

Expected Value: When advisors/agents or compliance admins can preview Sites changes before submitting or approving them, they can more clearly see the changes and proactively address potential issues. This helps advisors/agents save time and effort going through multiple compliance revisions and helps compliance admins reduce the risk of accidentally approving something problematic.

Expected Solution: Advisors/agents will be able to preview the website before they submit to compliance, and compliance admins will be able to preview the website before they approve the changes. A Preview button will appear both when submitting and approving changes. 

Sites Profile Editor 

Supervision

PLATFORM

Desktop notifications appear in a drop-down list

Problem Solved: Clicking on the notification bell in the desktop application opens a new tab, forcing users to switch between pages to view notifications.

Expected Value: Users can view their list of current notifications without interrupting their workflow.

Expected Solution: After clicking on the notification bell in the web application, a scrollable list of read and unread notifications from the past 30 days will appear below the bell icon. Clicking on an individual notification from the list takes the user to the corresponding page they need to attend to the activity in the notification. For example,  clicking on a content suggestion takes you to a page to publish the piece of content. Notifications will be marked “read” after the user either clicks on the notification or selects Mark all as Read.  Read and unread notifications are in different colors and users can toggle Unread Only to view only notifications they haven’t read yet. A circular badge will still appear near the bell icon indicating that there are unread notifications.

Data & Analytics

Breakdown by Actions Workspaces report will show if advisors/agents are receiving daily emails and push notifications

Problem Solved: Program admins are not able to monitor which advisors/agents are receiving daily emails and push notifications and which advisors/agents have these emails and push notifications turned off. This has created a barrier to seeing every agent/advisor’s notification settings for every workspace, and better understanding each advisor/agent’s efficiency.

Expected Value: Program admins will be able to monitor if advisors/agents are receiving daily emails and push notifications for every workspace. 

Expected Solution: The Breakdown of Actions Workspaces report will be extended with two additional fields each with binary (yes/no) possible values:

• Receive daily email
• Receive push notification

New Sites Content Performance report to monitor pre-approved content usage in Sites

Problem Solved: Sites admins can’t monitor if advisors/agents are using pre-approved content, such as homepage hero images, services articles, specialists to add to “our team” pages, and default images that appear if they don’t have their own image for their custom articles. This has made it difficult to determine which content organizations should remove, replace, or add more of.

Expected Value: Providing data on content usage, including content types being used and the number of Sites using the content, makes it easier to assess the value of each piece of pre-approved content.

Expected Solution: A new Sites Content Performance report will be created with the following fields:

• Content category
• Content item
• Number of uses
• List of Sites using the content

This report will be filterable by date range and hierarchy.

New Sites Overview dashboard will show aggregate business measures for all Sites

Problem Solved: There is no single dashboard that provides aggregated business measures for all available Sites solutions (legacy custom Sites, Library Sites, NextGen Sites, and the newest version of Sites).

Expected Value: Program admins will have a new dashboard showing the aggregated business measures for all of their Sites, regardless of the underlying technology they are using.

Expected Solution: A new Sites Overview dashboard will be implemented that shows the aggregated business measures from all Sites types in use. The measures on the dashboard will be:

• Number of active Sites
• Number of total visitors
• Number of new visitors
• Number of returning visitors
• Number of leads (calculated based on the number of contact submission forms)
• Lead conversion rate %
• Number of Sites publishes
• Number of Events publishes

We’ve made four enhancements to our Relate desktop notifications:

• Desktop notifications no longer expire. Users must click to dismiss them. 
• Clicking on a desktop notification will open the conversation that generated the notification, if Relate is open in a browser tab. If Relate is not open in a tab, then clicking on the notification will open the Hearsay homepage.
• Browser tabs display the number of conversations with new unread messages.
• Notifications for unread messages in Relate change to read only when the user clicks on the message or anywhere in its conversation window. 

To protect customer privacy and follow data privacy guidelines, we’ve added the ability to automatically and permanently delete all advisor/agent voicemails after 30 days from Relate. Users won’t receive a notification when voicemails are deleted. This allows organizations to support customer data privacy as well as maintain compliance with communication guidelines regarding voicemail data. 

This feature is off by default. To enable it, contact your Customer Success Manager.

Here's what's in the February 13th release:

Relate

• Improved Embedded Relate integration with Salesforce 
• Sending contact cards does not require MMS to be enabled
• Twelve additional countries getting local phone number support

Mobile

• Relate Mobile App has a unified homepage experience (can preview in Testflight)
• New Relate Mobile App onboarding experience (can preview in Testflight)

Social

• Publishing content to LinkedIn requires additional permissions for some accounts
• Videos are uploaded as Reels from Hearsay Social to Instagram  

Sites

• Social video posts can also be published in Sites 🔷 

Actions

• Policy ID support in Actions 🔷 

Compliance

• Distinguish LinkedIn Recruiter InMail messages from regular DMs in supervision and archive 🔷 

Data & Analytics 

• Engagement All Data report distinguishes whether engagements come from Hearsay or from non-Hearsay accounts
• Review Invite Status report allows all admins to track their workspace invite statuses
• Evidence of Supervision report flags Sampled Items 

🔷 Sandbox preview available. Contact your Customer Success Manager for more information.

Relate 

Improved Embedded Relate integration with Salesforce

This is an enhanced set of capabilities for the Embedded Relate integration with Salesforce that offers improved admin configuration, error logging, and a rebuilt texting widget with new features. 

The Embedded Relate integration is available via the Salesforce AppExchange at an additional cost. To enable this package, contact your Customer Success Manager. 

Admin configuration

The Relate widget in Salesforce can be configured by following three steps in Salesforce’s Admin Settings:

1. In Integration Settings, enter your Hearsay Org ID, and click Save.
2. Below the Integration Settings, in Mappings, set the Enablement Status to Enabled.
3. In Mappings, click Add New Mapping, then add Relate contacts or leads and their phone numbers that can be used for Relate text messaging. 

Streamlined admin configuration

Error logging

Salesforce admins can access the Embedded Relate error log center under the Hearsay Logs tab.

Embedded Relate error log center in Salesforce

Rebuilt texting widget

The Relate texting widget can now be embedded to any Salesforce Lightning record page with a phone number field. The texting window contains the entire message history, with 25 previous messages loaded as default. Other older messages can also be loaded. Each message is labeled with its sender’s name or phone number, sending/receiving date and time, as well as its delivery status.

Ask permission to send texts

The Embedded Relate texting widget maintains compliance by providing an attestation flow that asks clients for their permission to opt in to receive text messages.

Attestation flow seeking permission

Permission question asked to client

Send and receive attachments

The texting widget also supports sending and receiving attachments in .png, .jpg, and.gif formats. These attachments can be selected from the Salesforce attachment directory or uploaded from the local drive.

Sending and receiving attachments

Send scheduled messages

Messages can be scheduled to be sent at a later time, based on the time zone setting in your local Salesforce instance. Scheduled messages can be reopened, edited, or deleted. 

Schedule messages to be sent at a later time

Edit or delete scheduled messages

Delegate someone to text on your behalf

Advisor users can access all Relate conversations within the workspaces to which they are assigned as owners or as delegates. The workspace can be switched in the widget header, located in the dropdown menu under the profile image. This allows conversations with clients to continue with a delegate, if the primary advisor/agent is out of the office or unavailable.

Selecting another workspace

Workspace owners' messages are displayed with a light blue background, while delegates' text messages are shown with a gray background. When the user is a delegate in a workspace, the message is sent out on behalf of the workspace owner and the delegate’s name is appended in parenthesis in the beginning of the message text. 

Replying on behalf of another agent/advisor

The Embedded Relate integration is available via the Salesforce AppExchange at an additional cost. To enable this package, contact your Customer Success Manager. 

Sending contact cards does not require MMS to be enabled

Agents/advisors can send contact cards, including any logos or thumbnail images, without enabling MMS. This update allows those organizations who have disabled MMS to send new contact cards through Relate.

Twelve additional countries getting local phone number support

As the second part of our continued effort to expand Relate access globally, we are adding local phone number provisioning support for the following countries that were previously not supported:

• China
• India
• Ireland
• Japan
• Luxembourg
• Philippines
• Singapore
• South Korea
• Sweden
• Taiwan
• United Arab Emirates
• Vietnam

This release provides local country support only. For example, an advisor/agent in Sweden will be able to text their contact who also has a Swedish number. Only text messaging is supported for these countries. Voice calling is not supported.

This feature is off by default. To enable this feature, contact your Customer Success Manager.

MobilE 

Relate Mobile App has a unified homepage experience

The Relate Mobile app will start hosting more Social features in an effort to create a unified mobile experience. A part of the experience includes the new unified homepage, which helps advisors/agents prioritize important tasks, streamline their communications, and engage on social media. The new homepage now contains the following activities and notifications: 

• LinkedIn Direct Message to Call & Text: : When a contact shares a phone number in a LinkedIn direct message, Hearsay automatically detects the number and prompts the advisor/agent to either tap Call to call the number, tap Message to continue an existing conversation or start a new conversation thread, or tap X to dismiss the notification.
• Unread Text Older than 24 Hours: Reminds the advisor/agent to look at unread texts older than 24 hours and prompts them to respond by tapping Reply, Call, or X (dismiss).
• Missed Call older than 24 hours: Reminds the advisor/agent to look at missed calls older than 24 hours and prompts them to respond by tapping Call Back, Message, or X (dismiss).
• Publish a Suggested Post: Suggests engaging content from the content library for a user to publish. The advisor/agent can tap the content, then tap Review & Publish to the selected social media channel. Tapping Delete dismisses the content and removes it from the Post Library for the workspace, then generates a new piece of suggested content if one is available.
• Subscribe to a Campaign: Suggests an available campaign to subscribe to, which was previously limited to Hearsay Desktop. The advisor/agent can tap the campaign to view the details, and tap Subscribe to Campaign to subscribe. Tapping Remove dismisses the campaign and removes it from the workspace, then generates a new campaign suggestion if one is available.
• Onboarding Tasks: As part of the enhanced onboarding experience also included in this release, the homepage includes relevant onboarding tasks, like enabling notifications and connecting social media accounts.

Activities on the homepage are customized to each advisor/agent based on the types of interactions they’ve recently had with clients, and the products they have permission to use. For example, an advisor/agent without Social cannot see the sections for posts and campaigns on their homepage.

Homepage - Unread text, missed call, suggested content

Homepage - LinkedIn DM to call & text, subscribe to campaign

If you would like to view and test changes prior to the releases, you can access them on an Apple device via Testflight. Contact your customer success manager if you would like to preview these changes on Testflight.

New Relate Mobile App onboarding experience

In order for Social only and Social + Relate users to onboard effectively in the Relate Mobile App, the onboarding experience has been simplified and tailored to how each advisor/agent uses the app. 

Advisors/agents can now access the app directly after logging on and complete onboarding for each activity as they do them instead of completing all onboarding steps at once as a prerequisite to accessing the app. For example, if the user doesn't have Relate set up but navigates to the Conversations tab, they are presented with instructions for setting up their Relate account. 

Example onboarding steps

• Allow Notifications: Tap Allow Notifications to open device settings and allow notifications, or tap X to dismiss.
• We’re Working on Connecting Your Landline: Appears while a landline account is still being enabled for texting. Tap X to dismiss.
• Connect/Reconnect Social Media Accounts: Appears when a workspace has access to Social but does not have any networks connected, and links to a Hearsay Help Center article about connecting accounts using a web browser.

Example onboarding activities on the homepage

If you would like to view and test changes prior to the releases, you can access them on an Apple device via Testflight. Contact your customer success manager if you would like to preview these changes on Testflight.

Social

Publishing content to LinkedIn requires additional permissions for some accounts

LinkedIn recently announced that its Share and UGC APIs are being deprecated after February 28th, 2023, and the content uploading functionalities those APIs provided will now be supported by the Post API. 

Because the Post API requires different permissions than the old APIs, LinkedIn profiles and company pages that were linked to the Hearsay platform before Oct. 19th, 2022 must be reconnected to Hearsay. 

*On February 16th, 2023 (previously February 15th), between 4:00 AM and 6:00 AM Eastern Time, Hearsay will automatically disconnect all the profiles and business pages that lack appropriate permissions. ** Impacted profile and business page owners will receive a notification from Hearsay when they log onto Hearsay Desktop, instructing them to reconnect their account(s) to restore Hearsay Social functionality.

* Automatic disconnects were originally planned for February 15h,  but due to unforeseen technical issues, was replanned for February 16th. 

** Previously, we stated that impacted users will receive an email the week of February 6th. This was an error. Impacted users will only receive notifications in Hearsay Desktop about this issue the week of February 6th.

Videos are uploaded as Reels from Hearsay Social to Instagram 

Instagram has discontinued the native support of videos in their application and introduced Reels. Videos published from Hearsay Social to Instagram are now converted to Reels automatically with no impact on the Hearsay user experience.

Reels have different characteristics than traditional videos. For example, they are looped, are on a dedicated Reels feed, and have different format specifications, found here:

Sites

Social video posts can also be published in Sites

Posts containing video content in Social can also be simultaneously published on Sites. Advisors/agents can check the Sites icon when creating video posts in Social, which also publishes these video posts on their Site. This allows advisors/agents to seamlessly publish video content across their websites and social media accounts.

This is only available on the newest version of Sites and is off by default. To enable it, contact your Customer Success Manager.

Posting videos on Sites via Social

Actions

Policy ID support in Actions

Advisors/agents can now simultaneously manage a separate workflow for each individual policy belonging to the same contact. For example, if a contact has multiple policies expiring during the same week, an advisor/agent can have a renewal request workflow active for each policy. 

In the API, Contact IDs are now paired with Policy IDs to trigger Action workflows. Each new ContactID/PolicyID pair triggers a separate event and starts a new Actions workflow, but if an existing ContactID/PolicyID pair receives multiple triggers for an active workflow, Actions doesn't start a new workflow, unless the existing workflow has been already completed. If only a Contact ID is included in the event, the Actions workflow works as it has in the past.

Separate outcome survey forms are available for each workflow, and each form includes a reference to the corresponding Policy ID. For example, How did the conversation go with ?

To add Policy IDs to the API requests that trigger the start of Action workflows, contact your Customer Success Manager. There is no need to change any other configurations to enable multiple workflows for the same contact.

Compliance

Distinguish LinkedIn Recruiter InMail messages from regular DMs in supervision and archive

LinkedIn offers the premium InMail feature, which allows recruiters to send direct messages to LinkedIn members without being connected with them. Compliance admins can now see whether a DM was an InMail message in the supervision queue and the archives, making it easier to follow messaging threads. To tell the difference between the types of messages, InMail messages are labeled as Recruiter InMail, and outbound messages are labeled Private Message. 

This feature is off by default. To enable it, or to enable the sandbox preview, contact your Customer Success Manager. 

Ensure you have LinkedIn Private Message archiving turned on prior to enabling this feature. This is configurable in the admin interface by going to Organization Settings > Review & Archive > LinkedIn > Private Messages > Archive.

Data & Analytics

Engagement All Data report distinguishes whether engagements come from Hearsay or from non-Hearsay accounts

This release adds a new field to the Engagement All Data report that differentiates between engagements coming from their own company or competitors using Hearsay and all other engagements from social media users without Hearsay accounts. It is important to be able to make this difference because non-Hearsay engagements include those from prospective and current clients.

New field added to the Engagement All Data report that differentiates between Hearsay and non-Hearsay users

Review Invite Status report allows all admins to track their workspace invite statuses

The Review Invite Status report has been enhanced to allow all admins to track the workspace invites sent out at their hierarchy level and lower. This is an improvement from the previous version, when only root admins with full access to all hierarchies could see workspace invites. This updated solution improves reporting for Hearsay program management.

Evidence of Supervision report flags Sampled Items

The Evidence of Supervision report has been enhanced to include a new field named Sampled, which provides a way to distinguish between records collected from supervision alerts and records collected through random sampling. This additional information improves the compliance team’s efficiency by helping them evaluate if they are over-sampling and allowing them to correspondingly change their activity.

Evidence of Supervision report with new Sampled field that shows records collected from supervision alerts and records collected through random sampling

We've made some enhancements to the testimonials process for both advisors/agents and for compliance admins. 

Social

View all testimonials on the Testimonials page

Advisors/agents can now see testimonials they’ve received through Hearsay on the Testimonials page. Testimonials with the following statuses are available:

• Testimonials to which the advisor/agent still needs to attest are displayed, along with the due date. The advisor/agent can click the testimonial to complete the attestation steps. 
• Testimonials that have already been attested to are displayed with a No Action Needed label. This status means the testimonial is either being reviewed by compliance or is live on the advisor/agent’s social media page. 
• Testimonials that are overdue are displayed with an Overdue label. This means the advisor/agent didn’t attest to the testimonial in time, and it has either been removed (LinkedIn), or we’ve automatically disavowed it in a comment (Facebook). 

Help Center documentation is available at https://success.hearsaysocial.com/hc/en-us/articles/12126893027607 

Example testimonials on the Testimonials page

Compliance

See answers to attestation questions in Supervision

Compliance admins can now view and archive the answers advisors/agents give when answering attestation questions about a testimonial. The answers appear as a comment in the Internal to Team section of either the alert the testimonial generates, or in the prohibited review alert created if a testimonial is automatically rejected. 

Additionally, the Evidence of Supervision report now displays the attestation answers in the Internal Comment column. 

Help Center documentation has been updated at https://success.hearsaysocial.com/hc/en-us/articles/9991899785367.

Example alert with answers in the Internal to Team section

Time zones are now visible next to the event time when creating events in the Events Publisher and viewing them on the Events page. This time zone is based on your preferences in the User Settings. 

This feature is on for all Sites customers.

Event creation with time zone information

Existing Event with time zone information

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

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

RELATE

Access LinkedIn direct messages via Relate

Problem Solved: Agents/advisors aren’t able to access LinkedIn direct messages on Relate. 

Expected Value: Integrating LinkedIn direct messages with Relate will allow agents/advisors to access direct messages using Relate, providing a better unified direct messaging experience on the Relate platform.

Expected Solution: Agents/advisors will be able to send and receive LinkedIn direct messages on Relate. In order to port/view LinkedIn conversations in Relate there must first be an existing conversation in LinkedIn, i.e. the user has sent or received at least one private message to/from another person on LinkedIn.

To enable this feature, please contact your Customer Success Manager. 

Who is impacted: Advisor/Agent, Client, Program Admin 

Archiving and Compliance Implications: N/A

Availability: Will be off for all organizations, but can be turned on by contacting your Customer Success Manager. This feature is only available for users with both Hearsay Social and Hearsay Relate enabled.

Sending contact cards does not require MMS to be enabled 

Problem Solved: Some organizations have disabled multimedia messaging service (MMS), which blocks users from sending new contact cards through Relate. 

Expected Value: Relate users will be able to send contact cards without enabling MMS, allowing all organizations to send contact cards seamlessly.

Expected Solution: Agents/advisors will be able to send contact cards, including any logos or thumbnail images, without enabling MMS.

To enable this feature, contact your Customer Success Manager.

Who is impacted: Advisor/Agent, Client

Archiving and Compliance Implications: N/A

Availability: Will be off for all organizations, but can be turned on by contacting your Customer Success Manager.

Twelve additional countries getting local phone number support 

Problem Solved: Relate has limited support in the international market, leaving users in many countries without access to a local phone number for compliant texting and calling. 

Expected Value: Productivity in international teams will increase because agents and advisors in additional countries will be able to communicate with prospects and clients in their local market in a compliant, timely, and effective manner.

Expected Solution: As the second part of our continued effort to expand Relate access globally, we will add local phone number provisioning support for the following countries that were previously not supported:

• China
• India
• Ireland
• Japan
• Luxembourg
• Philippines
• Singapore
• South Korea
• Sweden
• Taiwan
• United Arab Emirates
• Vietnam

To enable this feature, contact your Customer Success Manager.

Who is impacted: Advisor/Agent, Client, Compliance Admin, Program Admin

Archiving and Compliance Implications: N/A

Availability: Will be off for all organizations, but can be turned on by contacting your Customer Success Manager.

Actions

Policy ID support in Actions 

Problem Solved: Currently, a single Actions workflow can be active at a time for each contact, and only when the current workflow is closed can a new one be opened. In some use cases, like for a policy renewal, a contact might have multiple policies expiring on the same day or week, but there isn’t a way for an agent/advisor to have a renewal request workflow active for each policy simultaneously.

Expected Value: Agents/advisors will be able to run parallel Lead and Client Action workflows at the same time for a single contact.

Expected Solution: Contact IDs will be paired with Policy IDs to trigger Actions from the Actions API. Each new ContactID/PolicyID pair will trigger a separate event and start a new Actions workflow. If an existing ContactID/PolicyID pair receives multiple triggers for an active workflow, Actions doesn't start a new operation. 

If only a Contact ID is included in the event, the Actions workflow will continue to work as it has in the past.

Who is impacted: Advisor/Agent, Client, Program Admin, Integrator

Archiving and Compliance Implications: N/A

Availability: Will be on for all organizations.

Mobile

Unified Mobile Homepage 

Problem Solved: There isn’t a central place in the mobile app to see and prioritize tasks in order to maintain strong client relationships and social engagement. There’s also not a streamlined way to effectively use Social and Relate together.

Expected Value: Introducing a set of suggested activities on the homepage will prompt users to reply back to texts and calls more often, post more engaging content to their social networks, onboard onto the mobile app more easily, and capture client phone numbers shared via LinkedIn DMs and respond by text or call.

Expected Solution: The Unified Mobile Homepage is moving from the beta stage into production, and is part of an effort to repurpose the current Hearsay Relate app into a unified Hearsay Mobile app. The Relate app homepage will include the new onboarding experience as well as missed calls, missed texts, engaging content, campaign content, and LinkedIn messages with phone numbers detected in them. A user will only see the actions for the products they have permissions to use. For example, if the user does not have Social enabled they will not see the section for posting engaging content.

Who is impacted: Advisor/Agent, Client, Marketing Admin, Program Admin.

Archiving and Compliance Implications: N/A

Availability: Will be on for all organizations.
 

Unified Mobile Onboarding and Authentication 

Problem Solved: Authentication and onboarding in the current Relate app is currently for Relate users only. As part of an effort to create a unified app from the current Relate app, the onboarding experience has to be updated to allow Social only and Social + Relate users to onboard and authenticate in the app. The current Relate onboarding experience on mobile also requires the user to take many sequential onboarding steps before gaining access to the app, which makes it more likely the user won’t complete the onboarding process.

Expected Value: A simplified onboarding and authentication experience for mobile users regardless of the product they’re using will make the onboarding experience more user friendly and allow users to get only the onboarding experience that pertains to them.

Expected Solution: The onboarding experience will no longer be a sequence of steps. Instead, users will access the app directly after authentication and complete onboarding for each activity as they do them. For example, if a Relate user wants to send a text for the first time and navigates to the Conversations tab, they will be presented with instructions for how to send and receive text messages. 

The new Unified Mobile Homepage experience, also included in this release, will display onboarding information and to-dos, in addition to other recommended actions.

Who is impacted: Advisor/Agent, Client, Compliance Admin, Marketing Admin, Program Admin

Archiving and Compliance Implications: N/A

Availability: Will be on for all organizations.

Platform

Desktop notifications appear in a drop-down list 

Problem Solved: Clicking on the notification bell in the desktop application opens a new tab, forcing users to switch between pages to view notifications.

Expected Value: Will enable users to view a list of current notifications without interrupting their workflow.

Expected Solution: After clicking on the notification bell in the desktop application, a scrollable drop down list of read and unread notifications from the past 30 days will appear below the bell icon. Clicking on an individual notification from the list will take the user to the corresponding page they need in order to attend to the activity in the notification. For example, clicking on a content suggestion notification will navigate to a page to publish the piece of content. Notifications will be marked “read” after the user either clicks on the notification or selects Mark all as Read. Read and unread notifications will be in different colors and users can toggle Unread Only to view only the notifications they haven’t read yet. A circular badge will still appear near the bell icon indicating that there are unread notifications.

 Who is impacted: Advisor/Agent, Compliance Admin, Marketing Admin, Program Admin

Archiving and Compliance Implications: N/A

Availability: Will be on for all organizations.

Data & Analytics

Engagement All Data report distinguishes whether engagements come from Hearsay or from non-Hearsay accounts

Problem Solved: There is no way to distinguish between engagements received from internal employees or competitors using Hearsay and all other engagements received from social media users without Hearsay accounts.

Expected Value: Administrators will be able to differentiate between engagements coming from their own company or competitors using Hearsay and all other engagements from social media users without Hearsay accounts. It is important to be able to make this difference because non-Hearsay engagements include those from prospective and current clients.

Expected Solution: This field will be added to the Engagement All Data report: 

• HS connected social account (yes/no).

 Who is impacted: Marketing Admin

Archiving and Compliance Implications: N/A

Availability: Will be on for all organizations.

Review Invite Status report allows all admins to track their workspace invite statuses

Problem Solved: The Review Invite Status report only showed workspace invites to root admins with full access to all hierarchies, which barred other lower-level admins from seeing the invites that they sent out.

Expected Value: The updated solution improves reporting for Hearsay program management. All admins will be able to track their own workspace invite statuses.

Expected Solution: The Review Invite Status report is now filtered at the workspace hierarchy level, allowing admins to view invites sent to workspaces in their hierarchy level and lower.

 Who is impacted: Program Admin

Archiving and Compliance Implications: N/A

Availability: Will be on for all organizations.

Sampled items marked (or flagged) in the Evidence of Supervision report

Problem Solved: The Evidence of Supervision report did not provide a way to distinguish between records collected from supervision alerts and records collected through random sampling.

Expected Value: Improve the compliance team’s efficiency by disclosing whether records were collected through supervision alerts or through random sampling. This allows compliance teams to evaluate if they are over-sampling and correspondingly change their activity.

Expected Solution: A new field will be added to the Evidence of Supervision report: 

• Sampled (yes/no)

Who is impacted: Compliance Admin

Archiving and Compliance Implications: N/A

Availability: Will be on for all organizations.

Advisors/agents can now easily view the preferred name of their contact in the web app on their desktop. On the Contacts screen, click on the contact’s row, and the Preferred Name field is displayed at the top of the side panel under Engagement Information. Click the edit icon to change the name.

A new setting allows admins to hide the Creator in the advisor/agent Post Library. When the setting is enabled, it hides the Creator filter and removes the Creator from all post cards. 

This setting is disabled by default.

To enable the setting, in the admin interface, click Settings > Organization Settings > Workspace & Emails. 

Then, under Workspace Settings, change the Hide content creator’s name setting to Enabled. 

For more intuitive navigation, the name of the System Emails tab has also been updated to Workspace & Emails.

A new Campaign Summary report helps admins understand and compare campaign performances and identify the best and worst performing campaigns in their organization.

The report is in the admin interface under Analyze > Reporting and contains the following fields:

• Campaign ID
• Campaign Title
• Campaign Create date
• Campaign Type (dynamic or relative)
• Current State (draft, published, expired)
• Number of Content Items
• Number of Workspaces Subscribed
• Number of Publishes
• Number of Engagements
• Engagement Rate (num. of engagements divided by num. of publishes)
• Number of Views
• Number of Clicks
• Clicks per Publishes

The report has filtering options for hierarchy and date range.