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

Users can now navigate to site-specific data for each website listed on their My Websites page. When a user clicks the new Go to Sights Insights link next to a specific website on the My Websites page, the Insights page opens and automatically filters for data for the specified website instead of showing aggregated data for all websites in the workspace. This enhancement allows users to get data for a single site more easily with one click rather than filter for it.

My Websites page with new Insights links 

Here's what to look for in the December 11th release. 

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

Relate 

Group Texting

Problem Solved: Advisors/agents cannot communicate with a group of people at the same time. For example, an advisor/agent cannot simultaneously hold conversations with multiple individuals in a household, or with multiple team members in a client organization. The absence of Group Texting hinders collective discussion, collaboration, coordination, as well as sharing information efficiently.

Expected Value: Group Texting will provide the following value: 

• Provide enhanced ability to reach out to multiple contacts with one message to optimize efforts,  as well as build and strengthen relationships. 
• Improve the advisor/agent’s productivity by decreasing the repetitive work of maintaining separate conversations about the same subject with multiple different members of a group. 
• Encourage a collaborative and participatory approach to sharing information, which enhances transparency.
• Drive a better user experience and make cross functional collaboration easier and more productive.
• Support data monitoring capabilities for sales, training, customer success, and finding new opportunities.
• Archive data and meet compliance guidelines.

Expected Solution: Relate Group Texting will allow advisors/agents to compose and send messages as well as share files (in JPEG, GIF, and PNG formats) with groups of up to 10 contacts simultaneously while meeting compliance guidelines. All group members will need to opt-in to receiving messages to be included in the group. Once a group has been created, the advisor/agent and group members will be able to send and receive messages from the group. Advisors/agents will be able to create a group name or edit the name of an existing group. Advisors/agents will also be able to filter the messages in their conversation window to only view Group Texts.

Group Texting will follow your organization’s existing archiving and compliance policies. 

Advisors/agents will not be able to add additional members to an existing group or remove members from an existing group. If people need to be added or removed from a group, then a new group will need to be created. 

If any group member changes their attestation status and opts out of receiving text messages, then the advisor/agent will not be able to send messages to the group. However, the group will still receive messages from other members and the advisor/agent will be able to view these messages in the conversation window.

Group Texting will initially only be available on Relate Desktop and the Hearsay Mobile iOS app, while advisors/agents on Android and Salesforce Embedded Relate will see a message saying that Group Texting is not currently available, but is coming soon. 

Group Texting will initially not support sending scheduled messages or voice calling.     

Who is impacted: Advisor/Agent, Client, Compliance Admin
Archiving and Compliance Implications: None
Availability: On for all organizations. Group Texting will initially be available on Relate Desktop and the Hearsay Mobile iOS app, while users on Android and Embedded Relate for Salesforce will be shown a message saying that Group Texting will be enabled in a future release.

To take advantage of the following enhancements, update to the latest version of the Hearsay Mobile app. Apple/iOS updates are currently available in the App Store for Hearsay Mobile, Hearsay for Intune, and Hearsay for Blackberry. Android updates will be available in the Play Store for Hearsay Mobile and Hearsay for Intune by the end of next week. 

Relate onboarding language change in Hearsay Mobile

The Relate onboarding process no longer mentions “texting prospects” in order to comply with TCPA regulations.  

New language 

Hearsay Mobile text composer enhancements

A modernized message composer makes composing messages and starting conversations easier. It includes the following changes:

• The character limit for web and personalized opt-in messages has increased from 160 to 500. 
• The composer window can be expanded to fit larger messages by touching the horizontal bar at the top of the window and dragging it up or down.
• Users can send photos, saved links, and share contact information with fewer taps and a larger, more detailed preview window.
• Minor changes to shading and button colors creates a more modern look and feel.

 Increased opt-in character limit

Expanding text composer

New attachment preview window 

Due to changes in X/Twitter’s v2.0 API, Hearsay is no longer able to support users liking their own posts or replying to comments on their post in the Hearsay platform. To prevent inactive tools from confusing users and cluttering the interface, the Like button has been removed from X/Twitter accounts on the Respond page in the Published Posts tab. The Reply button is now called Replies, and allows users to view past replies to their post, but not create new replies in Hearsay. Users can still publish an X/Twitter post via Hearsay, and Hearsay can still crawl X/Twitter and create alerts for likes and replies.

X/Twitter Like button removed and Reply button replaced with Replies