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

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

Social

Create sub-settings for LinkedIn Recruiter and SalesNav message archiving

Problem Solved: LinkedIn Recruiter and Sales Navigator InMail messages can be allowed or restricted in compliance monitoring, but inbound and outbound messages cannot be distinguished in settings. 

Expected Value: Monitoring and supervision of the different LinkedIn direct messages comply with an organization’s policies and standards.

Expected Solution: Introducing a subsetting that allow/disallow all Recruiter / Sales Navigator messages or just the inbound ones 

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

Save reaction types

Problem Solved: Currently all reactions are saved as ‘like’-s in Hearsay, while natively there are multiple reaction types in LinkedIn.

Expected Value: Engagement insights can distinguish the reaction types

Expected Solution: Save the different reaction types to Hearsay archives both in case of inbound and outbound reactions:

• like
• celebrate
• support
• insightful
• love
• funny

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

Gen AI: Generate Alternate Message for Multi-Voice

Problem Solved: There are cases where the administrator needs to create multiple versions of the post so that the same post appears with different text on the users' social media channels. This can also happen if the administrator only uploads posts written by others (e.g., advertising agencies) to the Hearsay Social platform.

How can we give GenAI-based help to admins to create additional versions based on the original post?

One possible solution is to enhance the multi-voice function with GenAI support. In the Hearsay Social Publisher, this feature can be enabled to allow admins to create multiple text versions for a given post. Before publishing, users can select the version they want to publish the post with.

Expected Value: Tied to multi-voice, creating a broader variety of posts around the same topic can become much easier and without the need to access tools outside HSS.

As it is tied to an existing feature, it is a very logical place for AI help, and it does not stand out in most of the competitions' offerings.

Expected Solution: When admins want to create alternate versions to a new suggested post, they now have the option to generate it with AI by clicking on the “Generate with AI” button.

Hearsay Social Admin Publisher

There are two possible ways to use the AI generator:

1. Choose from the built-in parameters regarding the length of the text (shorter, longer, same length) and the tone of voice (e.g., casual, neutral, professional).

Create Alternate Message with AI

2. Enter a free text prompt like “Rephrase the text with a casual tone of voice and make it longer”.

Alternate Text with AI

The alternate version can be generated by clicking on the “Create Alternate Message” button. After that, the admin can decide to create additional versions or move forward with the post publishing as usual.

This feature is an addition to the current way of creating alternate versions and does not replace it. Admins can always choose whether they want to use the AI feature or enter the alternate version manually.

Who is impacted: Advisor/Agent, Compliance Admin, Marketing Admin, Program Admin
Archiving and Compliance Implications: No
Availability: Off for all organizations, but can be turned on by contacting support@hearsaycorp.com

Mobile

Relate Sending admin-created message templates for users

Problem Solved: Message templates allow users to save time when sending the same message to different clients. Administrators can already create message templates to scale consistent messages that align with their organization's best practices, and help reduce the time users spend creating the same message content. Currently, users are limited to sending message templates on the Relate web experience as they are not available in the Hearsay Mobile apps.

Expected Value: Users were limited to sending templates from the web browser and will now be able to save time sending templates anywhere from their mobile device.

Expected Solution: Users can view, select, edit the templated text, and send admin-created message templates on the go from the Hearsay Mobile app. Templates are available as an attachment in Conversations and if no templates are available to the workspace, no change will occur. 

Who is impacted: Advisor/Agent & Client
Archiving and Compliance Implications: No
Availability: On for all organizations (where admins have created Relate message templates)

Data & Analytics

Add traffic tile to Sites Overview Dashboard

Problem Solved: Sites Admins are not able to see where Sites traffic comes from. This information is already available for the users on the Sites Insights Dashboard.

Expected Value: Sites Admins can analyze the traffic sources for Sites. The traffic source categories are the ones used by Google Analytics: Direct, Referral, Organic Social, Paid, and Unassigned.

Expected Solution: On the admin Sites Overview Dashboard, the following 2 tiles are added: Visitors by Source Type and Main Source of Traffic.

New Sites Overview Dashboard Tiles

Who is impacted: Marketing Admin, Program Admin
Archiving and Compliance Implications: No
Availability: On for all organizations using HS Sites

Change Sites Overview Dashboard to filter tiles by weekly aggregates

Problem Solved: Currently, the data on the Sites Overview Dashboard is only available on a monthly basis, after the end of each month. Sites Admins would like to filter the data more granularly and they would like to compare Sites performance against specific timely campaigns.

Expected Value: Admins will have the weekly filtering option when running the in-app Sites Overview Dashboard. This will allow a finer granularity for checking the Sites performance metrics.

Expected Solution: There will be a new date picker enabled on the admin Sites Overview Dashboard that will allow the admins to use the weekly filtering.

Date Picker

Who is impacted: Marketing Admin, Program Admin
Archiving and Compliance Implications: No
Availability: On for all organizations using HS Sites

Relate Insights for users

Problem Solved: Relate users do not have data insights available that provide key business metrics, such as the number of conversations, the number of appointments or the average response time for incoming texts.

Expected Value: Users will be provided with data and visualizations of the key business measures relevant to their Relate usage performance. They will be able to see the trends over a 30-day period, identify where their Relate 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 user dashboard will be accessible to the end-users from the Insights tab on the side menu. The Relate Insights dashboard will expose key business measures on the workspace level, as well as benchmark against other users in their hierarchy and recommend actions. 

The following measures will be available:

• Number of Conversations
• Number of Appointments
• Number of Unique Contacts Engaged
• Response Time for missed incoming calls
• Response Time for incoming texts
• Number of Incoming/Outgoing calls
• Number of Incoming/Sent messages
• Number of New Contacts
• Number of Contacts Opted-In

 Who is impacted: Advisor/Agent
Archiving and Compliance Implications: No
Availability: On for all organizations using HS Relate

The existing Display Lexicon Violations admin setting now applies to the Sites Event Publisher. The setting allows admins to enable or disable the user’s ability to see a list of lexicon violations when creating an event. Previously, the setting applied to the Post Publisher, but the Event Publisher always showed lexicon violations with no way to disable them.

When enabled, users see a list of terms that violate the organization’s lexicon within the post or event they are creating. 

Lexicon violations list

When disabled, users only see a warning that there is at least one violation within the post or event, but doesn’t explicitly tell them what the violation is. 

Lexicon violations warning only

To configure the setting in the Administrative view:

1. In the side menu, click Settings.
2. Under Organizational Settings, click the Lexicon tab.
3. Change the Display Lexicon Violations setting to Enabled or Disabled.

Setting location

A new Contacts with Opt-in filter on the Contacts page allows users to view only the contacts that have opted into receiving text messages. This new filter helps users clearly see who they have permission to contact and prevents unwanted communications. 

New filter in the Show menu

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

Social

• Create a Generative AI post description from a prompt 🔷
• Publish multi-image posts on Instagram 🔷
• X (formerly Twitter) API v2.0 roll out
• Content of original posts reposted on LinkedIn now archived by default 🔷

Sites

• Testimonials for Sites

Data & Analytics

• Generative AI post and enablement reporting
• Localization of admin dashboards
• User Maturity Model's Say Score is enhanced with clicks engagement data 
• User Maturity Model admin report now includes the Workspace Owner Email field 
• Alerts Summarized by Keyword admin report now includes a Description field 
• Auto-subscription column added to the Dynamic Relative Campaign Overview report

🔷Sandbox preview available. Contact Support at support@hearsaycorp.com for more information.

Social

Create a Generative AI post description from a prompt

After clicking New Post with AI, users can now choose whether to create description text using words and phrases (current way), or by writing a prompt. Prompts allow users to generate text based on questions or commands, similar to how most generative AI tools work. Unlike words and phrases, prompts support non-English languages and descriptions are returned in the same language as the prompt.

Example prompts that might generate useful result are:

• Why is property insurance important during the winter season? 
• Write a short social post about the need for property insurance in winter.
• Write a post about winter, snow, and property damage in four sentences or less.
• Write a Facebook post about wealth, savings, and preparing for the future.

After the user clicks Generate Post Description, the tool functions the same way it has in the past. Hearsay sends a prompt to Jasper, our secure third-party AI partner, with the specified requirements, and the engine sends back three descriptions for the user to choose from. Hearsay never sends customer data to Jasper, we only send the specifications for the post description. 

See Creating a post description with Generative AI for more information about the new workflow. 

This feature is off by default for customers who have already enabled Generative AI. Admins can enable Prompts in the Administrative view of Hearsay Desktop by doing the following:

1. In the side menu, click Settings.
2. Under Organizational Settings, click the AI tab. 
3. Change the setting Allow Writing a Prompt with AI to Enabled.  

To enable Generative AI, contact Support at support@hearsaycorp.com with the subject line “Enable Generative AI, October 2023 Release” in the subject line. In the email, please add all relevant enablement details, such as hierarchy or line of business.

Prompt page

Generated descriptions

Review and Publish page

Compliance admin note in Supervision 

Publish multi-image posts on Instagram

Hearsay now supports multi-image publishing on Instagram, allowing users to post up to 10 images at once. The images published from Hearsay will appear as a carousel post on Instagram.

X (formerly Twitter) API v2.0 roll-out

X (formerly Twitter) has announced the deprecation of the v1.1 API and now requires all API partners to transition to v2.0. As a result, certain Twitter functionalities in Hearsay have changed:

• Profile field management is no longer supported and users can only edit profile fields in X. Profile fields for X can still be added in Hearsay and compliance admins can still review and approve changes, but users must manually copy approved profile field content into their X account profile. Archiving of profile data remains unchanged.
• X Social Signals (Opportunities) have been deprecated and are no longer available. The Social Signal setting in the Admin view is set to Disabled for all customers and cannot be edited.
• Compliance monitoring now includes a daily download of social data.
• The history range for saving social engagements such as likes, comments, and reposts has been set to 7 days after publishing.
• Reposts (formerly retweets) no longer generate individual activities in the archives. Only the number of reposts is saved for each post.

In order for changes to take effect, Hearsay users with a connected X account must re-authenticate their X accounts in Hearsay. Affected users have received a notification instructing them to reconnect X on their Home page. 

Content of original posts reposted on LinkedIn is now archived by default

When a user reposts a LinkedIn post and selects Repost with your thoughts, the content of the original post that the user shared is now automatically saved to the activity archives for all organizations by default. Previously, organizations had to contact Hearsay to enable this functionality.

Note: If a user selects Repost without adding their own text to the repost, the post is not archived. 

Sites

Testimonials for Sites

Testimonials for Sites allows users to automatically publish all of their newly approved Facebook Reviews and LinkedIn Recommendations on their websites. Testimonials helps build trust and increase conversion rate by showcasing proof of positive client experiences in a way that is compliant with SEC regulations. 

Testimonials for Sites is only available to organizations that have enabled the New Marketing Rule testimonial feature and who also use a compatible website template.

This feature is off by default. To turn it on, send an email to support@hearsaycorp.com and include “Enable Testimonials for Sites from the February 2024 Release” in the subject line. In the email, please add any relevant enablement details pertinent to your organization as well as any questions that you may have.

Sample testimonials on a Hearsay Site

Data & Analytics 

Generative AI post and enablement reporting

To give admins more insight into usage metrics and the success of AI for social media engagement, the Post All Data report now has a GenAI supported column. The true/false values indicate whether the text description of the post was created using Generative AI. Admins can use the column to filter for Generative AI posts and check their performance against manually created posts.

Additionally, in order to allow admins to more easily view and manage Generative AI access at the workspace level, the Workspace Directory report now has a GenAI enabled column. The true/false values in the column indicate whether the Generative AI feature has been enabled for users in the workspace.

Localization of admin dashboards

To create a better user experience for admins who prefer a language other than English, all the text on admin dashboards and the headers on the embedded reports within dashboards are now shown in the language configured by the admin in their user settings.

User Maturity Model's Say Score is enhanced with clicks engagement data

The User Maturity Model’s Say Score and correspondingly, the User Maturity Model admin report, is enhanced with data on clicks. Previously, the Say Score only included data on likes, comments, and shares/reposts. Now, all types of engagement data that Hearsay archives and creates reports on is accounted for in the Say Score, including clicks. The following engagement data from supported social media networks is used in calculating the Say Score:

• Facebook: likes, comments, shares, and clicks
• LinkedIn: likes, comments, and clicks
• X (formerly Twitter): likes, reposts, and clicks
• Instagram: likes and comments

This update to the Say Score will also be backdated to ensure that Year-over-Year and Month-over-Month analyses are accurate.

User Maturity Model admin report now includes the Workspace Owner Email field 

The User Maturity Model admin report now includes a new Workspace Owner Email field. This new field makes it easier for admins to track down and contact individual workspace owners. 

Workspace Owner Email field in the User Maturity Model admin report

Alerts Summarized by Keyword admin report now includes a Description field

The Alerts Summarized by Keyword admin report now includes a new Description field that shows the compliance terms behind Regular Expression (RegEx) definitions. The Alerts Summarized by Keyword report can have Regular Expressions (RegEx) terms in the Keyword field, making it very difficult to identify and analyze those terms. By showing the compliance terms behind the RegEx definitions in the new Description field, admins will be able to flag concerns with certain terms or determine the effectiveness of others.

Description field in the Alerts Summarized by Keyword admin report with corresponding RegEx definitions in the Keyword field

Auto-subscription column added to the Dynamic Relative Campaign Overview report

Admins can now see which campaigns have auto-subscription enabled, allowing them to see which campaigns they need to configure auto-subscriptions for or gain insight into which campaigns they can encourage users to auto-subscribe to when the functionality is enabled. The Dynamic Relative Campaign Overview report now has a Auto-subscription column with enabled/disabled values, which indicate whether auto-subscription is enabled for a campaign.

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

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

Social

Create a Generative AI post description from a prompt

Problem Solved: With the current Generative AI function, users have to provide words and phrases they want to include in the text of a post description, but cannot write a prompt, which is how most generative AI tools commonly work. 

Expected Value: The new Generative AI prompt feature will give users the option to more freely generate text based on questions or descriptive commands of what they are trying to write. 

Expected Solution: After clicking New Post with AI, users will be able to choose whether to create description text using words and phrases (current way), or by writing a prompt. Prompts can be questions or commands, and include the main subject(s) of the post and, optionally, the approximate length.

Example prompts that can generate useful result are:

• Why is property insurance important during the winter season? 
• Write a short social post about the need for property insurance in winter.
• Write a post about winter, snow, and property damage in four sentences or less.
• Write a Facebook post about wealth, savings, and preparing for the future.

After the user clicks Generate Post Description, the tool will function the same way it currently does. Hearsay sends a prompt to Jasper, our secure third-party AI partner, with the specified requirements, and the engine sends back three options for description text. The user selects a version and copies it into the Post Publisher where they can add images and links or make edits before publishing. Hearsay never sends customer data to Jasper, we only send the specifications for the post description.

Prompt page:

Generated description options:

Who is impacted: Advisor/Agent, Client, Compliance Admin, Marketing Admin
Archiving and Compliance Implications: The AI generated post is being sent to Supervision as any other post created by the user. The Compliance Admin receives a note for the Supervision item saying that the post has been generated by AI.
Availability: Off for all organizations, but can be turned on by contacting Support.

---

Sites

Testimonials for Sites

Problem Solved: Testimonials are helpful for fostering trust and credibility; however, there is not currently a way to display testimonials on Hearsay websites that is compliant with SEC regulations, and approved testimonials from social media platforms cannot be shared to Hearsay websites.

Expected Value: Displaying compliant testimonials provides proof of positive client experiences, which can attract new clients and drive the conversion rate of the website.

Expected Solution: Testimonials for Sites, available for the newest version of Sites, enables users to share their approved Facebook Reviews and LinkedIn Recommendations on their websites to build trust and increase conversion rate.

To show approved testimonials on websites, the following must be true:

• The New Marketing Rule testimonial feature must be enabled by an admin.
• The Testimonials on Sites feature must be enabled for the organization via Hearsay Support.
• The user must have a website template that supports displaying the testimonials.

This feature automatically pushes all the approved testimonials to the website.

Who is impacted: Advisor/Agent, Client, Integrator
Archiving and Compliance Implications: N/A
Availability: Off for all organizations, but can be turned on by contacting Support.

---

Data & Analytics

Generative AI post and enablement reporting

Problem Solved: Currently, the admins cannot report on which workspaces have Generative AI enabled, or compare the performance of posts created using Generative AI versus manually created posts.

Expected Value: Generative AI reporting will give admins more insight into the success of AI for social media engagement and usage metrics by Hearsay users, and allow admins to more easily view and manage Generative AI access at the workspace level.

Expected Solution: The Workspace Directory report will now have a GenAI enabled column with true/false values in the fields, indicating whether the Generative AI feature has been enabled for users in the workspace.

Additionally, the Post All Data report now has a GenAI supported column with true/false values, indicating whether the text description of the post was created using Generative AI. This allows admins to filter for Generative AI posts and check their performance against manually created posts.

Who is impacted: Program Admin, Marketing Admin
Archiving and Compliance Implications: N/A
Availability: On for all organizations.

Localization of admin dashboards

Problem Solved: Currently, the in-app admin dashboards have English text displayed, regardless of the user’s language setting. 

Expected Value: Admins who prefer a language other than English will have a better user experience when using dashboards.

Expected Solution: All texts on the dashboard and the headers in the tables will be available in the preferred language configured by the admin in their user settings.

Who is impacted: Program Admin, Marketing Admin, Compliance Admin
Archiving and Compliance Implications: N/A
Availability: On for all organizations.

User Maturity Model is enhanced with share/repost and click types of engagement data

Problem Solved: The Say Score in the User Maturity Model includes engagement data, such as likes and comments, but does not include other types of engagement data, such as shares/reposts and clicks. This gap makes the Say Score a partial measurement because important types of engagement data are not taken into account.

Expected Value: Improving the types of data considered by the User Maturity Model will increase the value of the report as well as help businesses measure social media usage with more accuracy.

Expected Solution: The User Maturity Model and correspondingly, the data in the User Maturity Model admin report will be enhanced with data on shares/reposts and clicks. All types of engagement data that Hearsay archives and creates reports on will be included in the User Maturity Model’s model Say Score. The following engagement data from supported social media networks will be used in calculating the Say Score:

• Facebook: likes, comments, shares, and clicks
• LinkedIn: likes, comments, and clicks
• X (formerly Twitter): likes, reposts, and clicks
• Instagram: likes and comments

Who is impacted: Program Admin, Marketing Admin
Archiving and Compliance Implications: N/A
Availability: On for all organizations

User Maturity Model admin report now also includes the Workspace Owner Email field

Problem Solved: The User Maturity Model admin report does not include the workspace owner’s email address, which makes it time-consuming for admins to track down and contact workspace owners.

Expected Value: Admins will not have to manually map the workspace owners' IDs with email addresses, and they will be able to easily get workspace owners’ contact information.

Expected Solution: The User Maturity Model admin report will be extended with a new Workspace Owner Email field.

Who is impacted: Program Admin, Marketing Admin
Archiving and Compliance Implications: N/A
Availability: On for all organizations

Alerts Summarized by Keyword admin report now includes a Description field

Problem Solved: The Alerts Summarized by Keyword report can have Regular Expressions (RegEx) terms in the Keyword field, making it very difficult to identify and analyze those terms. RegEx terms don’t give any clear indication of what they are alerting on and as a result, there is no efficient way to flag concerns with certain terms or determine the effectiveness of others.

Expected Value: By extending the Alerts Summarized by Keyword admin report with a Description field, admins will be able to see the compliance terms behind the RegEx definitions.

Expected Solution: The Alerts Summarized by Keyword admin report will be extended with a new Description field that shows the compliance terms behind the RegEx definitions.

Who is impacted: Compliance Admin
Archiving and Compliance Implications: N/A
Availability: On for all organizations

Auto-subscription column added to the Dynamic Relative Campaign Overview report

Problem Solved: Currently, the admins cannot easily tell whether auto-subscription is enabled for users when they subscribe to a campaign.

Expected Value: Visibility into auto-subscription enablement allows admins to see if they need to configure auto-subscriptions for campaigns, and gives admins insight into which campaigns they can encourage users to auto-subscribe to when the functionality is enabled.

Expected Solution: The Dynamic Relative Campaign Overview report will have a new Auto-subscription column with enabled/disabled fields, which indicate whether users can auto-subscribe to the campaign.

Who is impacted: Program Admin, Marketing Admin
Archiving and Compliance Implications: N/A
Availability: On for all organizations.

The Text Messages All Data report now includes metrics on Group Texting usage. A new Message Type field is added to the report which indicates whether a message is a Group Text or a 1:1 message. 

For outbound Group Texts, the Number From field in the Text Messages All Data report contains the phone number of the advisor/agent sending the message, and the Number To field contains the phone numbers of all the other group members. 

For inbound Group Texts, the Number From field in the Text Messages All Data report contains the phone numbers of all the group members except the advisor/agent, and the Number To field contains the phone number of the advisor/agent. 

Text Messages All Data Report with metrics on Group Texting usage

Here's what's in the December 11th release:

Relate

• Group Texting 🔷

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

Relate 

Group Texting

Group Texting on Relate allows users to send and receive messages as well as share files (in JPEG, GIF, and PNG formats) with groups of up to 9 contacts simultaneously, while also meeting compliance guidelines. Group Texting makes several use cases possible, such as allowing a wealth advisor to simultaneously hold conversations with multiple individuals in a household, or empowering an insurance agent to communicate with many different team members in a client organization at the same time.

After a group has been created, all group members can send and receive messages from the group. Each group has a group name, which can be edited. It is not possible to add or remove members from an existing group. If people need to be added or removed from a group, then a new group must be created. After a message is sent to the group, anyone in the group can respond. A check mark appears on sent messages indicating the message has been received by the carrier. 

Note: Toll-free numbers are not supported in group texts.

Opting In and Attestation Functionality

All group members must have previously opted in to receiving messages to be included in the group. If a contact has not opted in to receiving messages, they must complete the organization’s opt-in process before that can be added to a group. If any group member opts out of receiving text messages, the group creator can no longer send messages to the group. However, the group will still receive messages from other members and these messages will be viewable in the conversation window.

Archiving and Compliance

Group Texting follows the organization’s existing archiving and compliance policies. Currently, only the violation appears in Supervision, but the entire thread will be viewable in early 2024. 

Support for Additional Features in Relate

Group Texting supports: 

• Using Message Templates
• Sending attachments in JPEG, GIF, and PNG formats
• Filtering all messages to only view Group Texts  

 Group Texting does not support: 

• Sending scheduled messages 
• Sending contact cards
• Voice calling
• Reminders     

Preview

To preview Group Texting in a sandbox environment for Hearsay Desktop, or to preview the Group Texting availability note on Android, contact your Customer Success Manager.

To preview Group Texting in the Hearsay Mobile iOS app, use this TestFlight link: https://testflight.apple.com/join/PPhPE362

To preview Group Texting in the Hearsay for Intune iOS app, use this TestFlight link: https://testflight.apple.com/join/XdyF7Qs5   

To learn more about how to use TestFlight to test mobile features, click here.

Availability

This feature is DISABLED for all organizations by default and can be enabled per organization at the hierarchy level by contacting your Customer Success Manager. 

Group Texting is initially only available on Hearsay Desktop and on the Hearsay Mobile iOS app. Users on Android and Embedded Relate for Salesforce will see a message saying that Group Texting is currently not supported and they can view their group texts by logging in to their account on Hearsay Desktop. 

Group Texting is expected to be released for Android early next year, followed by Embedded Relate for Salesforce later in 2024. 

Learn More

To learn more about how to use Group Texting, see these articles in Hearsay's Help Center:

• Creating a Group Text on Hearsay Desktop
• Creating a Group Text on the Hearsay Mobile iOS app
• Editing a Group Name on Hearsay Desktop
• Editing a Group Name on the Hearsay Mobile iOS app
• Filtering Conversations to only view Group Texts on Hearsay Desktop
• Filtering Conversations to only view Group Texts on the Hearsay Mobile iOS app

Group Texting on the Hearsay Mobile iOS app

Temporary message about Group Texting shown to Android users

Group Texting on Hearsay Desktop

Create a new group on Hearsay Desktop

Filter for Group Texts on Hearsay Desktop

A new Expires filter helps admins see which posts are expiring soon in the Suggested Posts Library, which allows for prompt replacement of expiring content.

The new filter finds posts that are expiring during the next 7, 30, or 60 days.

Top of Filters view with new Expires option

The Hearsay functionality that automatically creates contacts from social media interactions, like post replies and likes, often doesn’t provide enough contact information to be valuable to advisors/agents. To avoid creating contacts that may not be useful, admins can now disable creating contacts from social media interactions, which helps advisors/agents focus on more actionable clients, prospects, and leads.

To disable contact creation from social media interactions, reach out to your Customer Success Manager.  

To make it easier for admins to oversee all AI-related settings at one place, the organizational setting that allows users to view and select posts from the Recommended tab in the Post Library has been moved. Previously, the setting was in Organizational Settings, under the Workspace & Emails tab. Now, it is in the AI tab. 

In addition, the setting has been renamed from Recommended in Post Library to Allow Recommended tab with AI in Post Library. The new name better clarifies the function of the setting.

Allow Recommended tab with AI in Post Library setting