Here are release notes for the latest features and enhancements from Yext (formerly Hearsay Systems). Click Subscribe to Updates to have future updates delivered to your inbox.
When importing a CSV file into the Contact page, rows that are skipped and the reason they were skipped are now included in the results email. The attachment in the email includes the skipped rows and an extra column to indicate the reason, which is most often missing data. This enhancement allows users to more easily identify and resolve issues with their CSV import files.
Here's what to look for in the November 13th release.
The guidance in this document is offered for early planning purposes and is subject to change up to the time of release.
Problem Solved: Advisors/agents using Sites do not have data insights available that provide their Site’s key business measures, such as the number of visitors or the referrers (like Google search, social media, etc.) sending visitors to the Site.
Expected Value: Advisors/agents will be provided with data and visualizations of the key business measures relevant to their Sites' performance. They will be able to see the trends over a 3-month period, identify where their Site's performance is better or worse than the performance of their peers, and they will receive recommended actions that are useful to help them improve their performance figures.
Expected Solution: A new advisor/agent dashboard will be accessible to the end-users from the Insights tab in the side menu. The Insights dashboard will expose key business measures at the individual Site level, as well as benchmarking against other advisors/agents in their hierarchy and recommended actions. The following measures will be available:
Who is impacted: Advisor/Agent
Archiving and Compliance Implications: No impact
Availability: On for Sites customers in organizations that allow Hearsay’s Google Analytics.
Problem Solved: Currently, the in-app admin reports have English headers, regardless of the user’s language setting. With the new localized versions, the admin report headers will be translated as per the language set by the admin.
Expected Value: User experience will be improved by providing translated versions of the in-app Admin reports.
Expected Solution: The headers for the in-app Admin reports will be translated into the preferred language set by the Admin.
Who is impacted: Compliance Admin, Marketing Admin, Program Admin
Archiving and Compliance Implications: No impact
Availability: On for all organizations.
Problem Solved: The workspace owner’s email address is currently not included in the Breakdown by Relate Workspace report, which makes it difficult for admins to track workspace-specific Relate performance.
Expected Value: The workspace owner’s email address can be used as an identifier when tracking workspace-specific Relate performance, and to facilitate contacting the workspace owner.
Expected Solution: The Breakdown by Relate Workspace in-app Admin report will be extended with a new Email address field which will contain the email address of the workspace owner.
Who is impacted: Marketing Admin, Program Admin
Archiving and Compliance Implications: No impact
Availability: On for all organizations using Relate.
Problem Solved: Embedded Relate users must use a standard opt-in message when initiating a conversation. There is no option to personalize or edit the standard opt-in message in Embedded Relate, even if the settings are differently configured for desktop or mobile Relate.
Expected Value: Embedded Relate users will be able to personalize their opt-in messages used in Embedded Relate and adopt a more client-centric approach in their communications.
Expected Solution: Embedded Relate users will be able to send personalized opt-in messages if enabled by the organization.
Who is impacted: Admin, Advisor/Agent
Archiving and Compliance Implications: No impact
Availability: Can be installed from a package by Salesforce admins.
Problem Solved: Embedded Relate only permits advisors/agents to start sending messages when the contact replies YES to the initial opt-in message. This hinders communicating with contacts who already have an existing business relationship and/or who have a reasonable expectation of receiving specific messages.
Expected Value: Advisors/agents will not have to wait to send messages until the contact has replied YES to their opt-in message. They will be able to immediately send messages to contacts after an implied consent opt-in message has been sent.
Expected Solution: Organizations that have enabled implied consent attestation will be able to start sending messages using Embedded Relate without waiting for the contact to reply with an attestation confirmation. With implied consent enabled, Embedded Relate will permit texting a contact immediately after sending an implied consent attestation message.
Implied consent attestation will work for organizations that have enabled or disabled personalized opt-in messages.
Who is impacted: Admin, Advisor/Agent
Archiving and Compliance Implications: No impact
Availability: Can be installed from a package by Salesforce admins.
Problem Solved: Social media network algorithms favor content with variables, and this feature that allows variable post descriptions isn’t enabled by default. Enabling this already existing optional feature for all organizations helps increase the reach of the posts.
Expected Value: Alternative descriptions allow admins to create one post they can customize for different types of users and audiences, increasing efficiency and improving social media strategy.
Expected Solution: When creating a suggested post, admins can click Add Alternate Description and create a different description to go with the post. When a user publishes the post, they can choose which description to use by clicking the < > arrows. Admins can add an unlimited number of descriptions per post.
Alternate description when suggested creating a post
Arrows to choose which description to publish
Who is impacted: Advisor/Agent, Marketing Admin
Archiving and Compliance Implications: The alternative post descriptions are treated like any other post description in supervision and archiving.
Availability: On for all organizations.
Problem Solved: In the previous Hearsay release, a new setting was introduced to configure whether LinkedIn Recruiter and Sales Navigator InMail messages are ignored or archived. However, when set to Ignore, only Recruiter and/or Sales Navigator messages received by users were ignored and user responses to those messages were still archived as regular private messages.
Expected Value: The archiving settings for Recruiter and SalesNavigator InMail messages will fully align with customer compliance policies, providing comprehensive control over conversations.
Expected Solution: With this enhancement, responses to Recruiter and SalesNavigator messages will also be archived or ignored based on the admin setting.
Who is impacted: Compliance Admin
Archiving and Compliance Implications: Responses to Recruiter and InMail messages can be ignored.
Availability: On for all organizations.
Problem Solved: Private message compliance policies differ customer-by-customer. The current LinkedIn Review & Archive settings allow admins to archive Recruiter and/or Sales Navigator InMail messages only if the regular private messages are also archived.
Expected Value: The archiving settings for Recruiter and Sales Navigator InMail messages will fully align with customer compliance policies, providing comprehensive control over conversations.
Expected Solution: Any combination of regular private messages, Recruiter InMail, and Sales Navigator InMail messages can be archived or ignored in accordance with individual customer compliance policies.
Recruiter and Sales Navigator settings will no longer a subset of Private Messages in Hearsay Desktop
Who is impacted: Compliance Admin
Archiving and Compliance Implications: LinkedIn Recruiter and Sales Navigator messages can be archived without all private messages set to be archived.
Availability: On for all organizations.
Problem Solved: API tokens/keys are always visible in the admin view, under Settings > Integrations, which makes them easy to copy and misuse.
Expected Value: Better token security improves the safety of customer data.
Expected Solution: The API Token value will only be shown immediately after it is created. After that, it will be hidden in the list of tokens on the Integrations page. If access is needed for a new application, a new token will need to be created.
Message about token visibility
Who is impacted: Integrator and Program Admin
Archiving and Compliance Implications: No impacts
Availability:On for all organizations.
Problem Solved: For compliance purposes, deleted contacts are only hidden and cannot be permanently deleted from the system. But if a user tries to import a contact that was previously imported and then “deleted”, the contact is still hidden and unavailable until it is restored manually on the Contacts page.
Expected Value: Contacts that are imported or added via the API are available for use, even if they were previously hidden from view.
Expected Solution: When a contact record is imported or added via the public API, any matching record that was deleted will be restored and unhidden.
Who is impacted: Advisor/Agent, Program Admin, Integrator
Archiving and Compliance Implications: No impact
Availability: On for all organizations
Due to an API change announced by X (Twitter) in late September 2023, Post Library users mentioning an account in an X (Twitter) post must now enter the exact name of the account they want to @@mention. Previously, users could search for partial matches to the account name and select which one they wanted to @@mention from a list.
Mentioning an X account
The following updates only apply to organizations subscribing to Embedded Relate for Salesforce.
Embedded Relate for Salesforce provides the option for organizations to display a consent confirmation note for advisors/agents in the message composer. This consent confirmation note appears just below the text drafting box, and it can be worded to remind advisors/agents to make sure that they have received permission to text the number to which they are drafting their message. Adding this consent confirmation note also changes the language of the message composer’s Send button to Agree and Send, which provides advisors/agents and their organizations with a way to confirm that they have obtained consent to send texts. Organizations can provide their own consent confirmation note to add here.
This feature is only available to organizations that have updated to the Embedded Relate for Salesforce 3.1.1 package. To enable it, contact your Customer Success Manager.
Consent message in the Embedded Relate message composer
Logging into Embedded Relate for Salesforce no longer requires advisors/agents to find an activation code in Relate Desktop, which would previously require them to open a new tab, log into Relate, and search for their activation key in the settings menu. Instead, when logging in, advisors/agents can click a link that directly takes them to the specific page in Relate’s settings where they can access their activation code. This improvement reduces several steps in the login process and provides a more seamless experience, while preserving the security provided by the activation code.
Additionally, advisors/agents will no longer have to select an organization when logging in. The Embedded Relate login flow will automatically detect the correct organization to log the user into based on the email address provided.
This feature is only available to organizations that have updated to the Embedded Relate for Salesforce 3.1.1 package.
Access activation code directly from the login flow
The new Conversations widget for Embedded Relate allows advisors/agents to view and access all of their text message conversations in one place, making it easier for them to reach out to their contacts and manage their ongoing conversations. The Conversations widget can be accessed via its dedicated tab on Salesforce’s top menu. The Conversations widget provides the ability to:
This feature is only available to organizations that have updated to the Embedded Relate for Salesforce 3.1.1 package.
Embedded Relate Conversations widget
Advisors/agents can quickly communicate with several people by sending a Broadcast Message to selected contacts. Broadcast Messaging allows advisors/agents to send a single text message and share it with multiple recipients. The recipients receive the text message individually and privately, allowing them to respond to the conversation one-on-one with advisors/agents. This saves time and creates efficiency in communication because advisors/agents no longer have to send individual messages. Broadcast Messages can be especially useful for communicating urgent, time-sensitive announcements like changes in business hours, changes in availability and scheduling, etc.
Broadcast Messaging is not group messaging. A traditional group text message allows everyone to write and view the responses of each participant. Instead, Broadcast Messaging enables sharing the same information with customers one-on-one, privately, without needing to send the same text message over and over again.
Broadcast Messages can be accessed from the Conversations widget. When creating a Broadcast Message, advisors/agents will be required to acknowledge a disclaimer that informs them not to use Broadcast Messages for advertising purposes. The Broadcast Message also blocks sending messages to contacts who haven’t consented to receive text messages.
This feature is only available to organizations that have updated to the Embedded Relate for Salesforce 3.1.1 package.
As part of Hearsay’s continued effort to transform the Hearsay Relate app into a unified mobile experience that encompasses both Relate and Social functions, the Hearsay Relate app has been rebranded to Hearsay Mobile. Removing Relate from the mobile app name makes the app welcoming to all of Hearsay’s users, regardless of their product access. The Mobile Device Management (MDM) versions of the Hearsay Relate apps have also been updated to Hearsay for Intune and Hearsay for Blackberry (iOS only).
Relate functionalities within the Hearsay Mobile app remain unchanged and all Social publishing capabilities available in the Hearsay Social app are now available in the Hearsay Mobile app. In addition to new features that help get more done on the go, unifying the mobile experience in the Hearsay Mobile app brings the security controls of Microsoft Intune and other Mobile Device or Mobile Application Management (MDM/MAM) providers to Hearsay Social.
New Hearsay Mobile icon
Hearsay for Intune icon
Hearsay for Blackberry icon
The screen that shows when the Hearsay Mobile app launches has also been updated.
Hearsay will host a webinar on Wednesday, October 4th at 12PM Eastern Time for users to learn more about logging into and using the Hearsay Mobile app. To register for the webinar, use the link https://register.gotowebinar.com/register/6694275824628610646.
The Hearsay Social app will include a link to open or download the new Hearsay Mobile app beginning on October 5th. No additional changes to any functionality within the Hearsay Social app are included with this release, and the app will continue to be supported until March 2024 with no additional enhancements or feature updates.
No changes to any functionality within the Hearsay Mobile app are included with this release.
Admins can now include a Sites link in Social campaign posts, growing the number of leads originating from social media activity and increasing lead conversion by gathering contact information. When the user subscribes to a campaign, a link to their Site is automatically added to the end of the posts in the campaign. If a visitor looks at the campaign post and wants more information, they can click on the link to the website and provide a phone number and email address by filling out the contact form.
Campaigns with links enabled have a Contains Website Links label. Any time a user with multiple websites subscribes, a popup asks them to confirm which link they want to include.
To learn more about how to add links to campaign posts, see Adding Sites Links to Campaign Posts.
Label
Popup
Here's what's in the October 2nd release:
Social
Relate
Platform
Actions
Data & Analytics
🔷Sandbox preview available. Contact your Customer Success Manager for more information.
Original content performs significantly better than suggested library content, and helping advisors/agents create more original content with less effort saves time and helps increase engagement.
A new Generative AI solution helps advisors/agents create more original content by generating descriptions for posts on any of their social media accounts. The tool works as follows:
Note: Generative AI is currently only available in English.
To see how to generate a post description, see Creating a post description with Generative AI.
To learn more about how the AI works, see How does Generative AI work?
Create a New Post with AI workflow
Post description example
Review and Publish page
This feature is off by default. To turn it on, or to enable the sandbox preview, contact your Customer Success Manager.
After Hearsay turns the feature on for your organization, you can enable it in the new AI tab. For complete instructions, see Enabling Generative AI.
Generative AI setting
The Post Library contains several tabs: Recommended, Browse, Prereleased, Campaign, Scheduled, Published, Promoted, Denied, and Pending. However, the large number of tabs creates confusion, and improving the organization and layout of the tabs improves usability and creates a smoother and faster journey from post selection to publication.
To improve the user experience, all the tabs currently in the Post Library have been merged into four tabs:
Explore: A renamed tab that displays released and pre-released organization posts.
My Posts: A new tab that contains scheduled, published, pending, and denied posts.
Explore tab
My Posts tab
To simplify the user experience, The Public Comments page, along with its related functionalities, is being removed from the Hearsay Social product. Users can now view and respond to comments on the Published Posts tab.
Instead of showing the vague error “Posting content to Twitter has failed” for any publishing error that occurs on Twitter’s (X’s) side, Hearsay now displays a more helpful error message specific to the problem.
Sample error
Hearsay users can disable Hearsay’s ability to crawl for and capture Instagram DMs by changing a setting in the Instagram app, and Hearsay cannot override the setting, even when Instagram DMs are configured to be captured at the org level. To prevent compliance gaps and ensure Hearsay can save Instagram DMs, Hearsay now generates a Recommended Actions item on the user’s Homepage that notifies them that this setting is against their organization’s compliance policy and gives them a link to an article that explains how to fix it.
Setting in Instagram
Recommended Action item
To allow organizations more control over whether LinkedIn Recruiter and Sales Navigator InMail messages are saved to the archive or not, Hearsay has added the option to archive or ignore either type of message.
To change the settings:
If the Private Messages setting is changed from Ignore to Archive, the Sales Navigator and Recruiter InMail settings automatically change back to the last configuration before the Private Messages setting was set to Ignore. The setting only applies to incoming DMs. If a Hearsay user replies to a Sales Navigator or Recruiter InMail message, their reply will still be sent to archives regardless of whether the setting was set to Ignore or not.
Settings page
Message templates allow users to save time when sending the same message to different clients. Administrators can now create message templates, allowing them to draft consistent messages that align with their organization's best practices, and helping them reduce the time advisors/agents spend creating the same message content. Advisors/agents can access available templates in the Relate message composer.
A new menu item is available in the admin view’s side navigation panel called Templates, where admins can view, create, and delete message templates. The Templates tab contains a message template library that shows message template cards containing individual template's title, textual content, and creation date and time.
Advisors/agents can view, select, edit, send, or schedule to send admin-created message templates from their Relate message composer.
Message templates will only be available in the Relate web platform initially. Administrators can create a maximum of 20 templates. Templates have 1600 character limit. Templates apply to the entire org and they cannot be restricted/enabled by hierarchy.
To learn more about creating message templates, see Creating and Managing Text Message Templates.
To learn more about using templates to send text messages, see Using Text Message Templates.
Message Template library in the admin-view
Message Template composer
Message Template drawer in the Relate message composer
A new login page has been introduced, providing a cleaner and more seamless experience to access Hearsay via SSO. The login via Facebook and LinkedIn buttons have been removed from the login page, and instead users are first prompted to enter their registered email address and a link to the authentication page is sent to that email address. The authentication page contains options to use SSO, Facebook, or LinkedIn to login, however the user is only presented with those options that they have available, based on their organization’s configuration. For example, if the user’s organization only has SSO available, then the authentication page will only show them the SSO option. After selecting their method of authentication, all further login steps remain the same.
This update does not change any of our supported authentication methods, it only changes how we present these authentication methods to our users. Organizations that use a URL redirect to an SSO will continue to be able to do so.
To preview the new login experience before it goes live on October 2nd:
New login pages
Actions
A new Actions API is replacing the current API, which doesn’t provide mandatory validation and prompt feedback when the sent record contains invalid fields. The new Actions API provides fast and accurate feedback to external systems about the success or failure of the record insertion, creating faster time to value and making it easier to make data corrections.
The new API has backward-compatible insertion payload and format, and accepts the same API token as the existing Actions API. However, the new API has a different URL.
There will be a six-month grace period from the day of release (October 2nd) where existing Actions customers can switch to the new API, and after the grace period, the old Actions API will be disabled.
To learn more about the transition process and set a date to begin the migration, or to enable the sandbox preview, contact your Customer Success Manager.
To enable admins to have more control over Actions workspaces and more efficiently resolve advisor/agent change requests, a new Workspace Management tool allows admins to activate and deactivate Actions workspaces and provision selected workspace-specific parameters via the Administration view in Hearsay Desktop. Here is a complete list of capabilities admins have with the new Actions Workspace Management tool:
This feature is off by default. To turn it on, or to enable the sandbox preview, contact your Customer Success Manager.
Filtering and searching
Managing Actions-specific workspace data
The Post All Data report now includes posts published as Instagram Stories, as well as their associated impressions and engagements. The Publish Type field of the Post All Data report displays the value Story for all Instagram Stories. The impression metric of the Instagram Story appears in the Num.Impressions field and the reply metric appears in the Num.Comments field.
Previously advisor/agents’ and their audience’s top interests were only available on the Social Insights for advisors dashboard. These will now also be visible to administrators in the Breakdown by Workspace report. The Breakdown by Workspace report is extended with 2 new fields: “Advisor’s Top Interest” and “Audience’s Top Interest”. These fields display the top interest categories for advisor/agents (based on their historically published posts), and the top interest categories for the advisors/agent's audience (based on their engagements with posts). This information will be available at the individual workspace level.
Breakdown by Workspace report with top interest categories
Administrators can track the number of posts originating from Content+ at the individual post level, allowing them to see if a specific post came from Content+. This information about post origins is available in the Post All Data Report, which has a new Origin field with 2 possible values:
Post All Data report showing origins of posts
Hearsay Sites administrators can now see if leads are originating from Sites Events RSVPs or if leads are originating from contact forms on Sites pages. This information about lead sources is available in the Contact Form Submission All Data report, which has a new Event RSVP field with 2 possible values:
Contact Form Submission All Data report with Sites lead source information
Marketing Admins can now view a list of who has subscribed to a campaign in the Administrator view instead of having to create a report. To see a list of subscribers:
A searchable list of subscribers appears, and clicking on a subscriber's name navigates to their respective Workspaces & Accounts page.
Campaigns tab
Subscribers list
Here's what to look for in the October 2nd release.
The guidance in this document is offered for early planning purposes and is subject to change up to the time of release.
Problem Solved: The current advisor/agent Post Library contains multiple tabs for viewing different kinds of posts, such as Recommended tab (for AI-powered content recommendations), the Browse tab (for viewing all posts available in the workspace), the Prereleased tab (for pre-approved content), the Campaign tab (for viewing posts in specific Campaigns), as well as several other tabs for viewing published posts, scheduled posts, posts pending approval, etc. Our UX testing has revealed that this large number of tabs in the Post Library creates confusion for advisors/agents and impedes them from using all the available functionalities provided by Hearsay.
Expected Value: Improving the organization and layout of the large number of tabs in the Post Library will lead to a smoother and faster journey from post selection to publication, and improve the usability of the platform overall.
Expected Solution: The large number of tabs currently in the Post Library will be merged into the following 4 tabs:
Explore
My Posts
Who is impacted: Advisor/Agent
Archiving and Compliance Implications: N/A
Availability: On for all organizations
Problem Solved: According to our studies, original content performs significantly better than library posts, but it can be time-consuming and difficult to create new posts from scratch.
Expected Value: Generative AI can help advisors/agents create more high-value original content with less time and effort.
Expected Solution: We have created a generative AI solution that creates descriptions for advisors/agents to add to posts on any of their social media accounts. The tool works as follows:
Who is impacted: Advisor/Agent, Client, Compliance Admin, Marketing Admin
Archiving and Compliance Implications: Posts created using Generative AI will be treated as regular posts in Supervision.
Availability: Off for all organizations, but can be turned on by contacting your Customer Success Manager.
Problem Solved: The Public Comments page is almost identical to the Published Posts in the Respond tab, which causes confusion.
Expected Value: Simplified functionalities without redundant processes create an easier navigation experience for advisors/agents.
Expected Solution:The Public Comments page along with its related functionalities is being removed from the Hearsay Social product. Advisors/agents can use the Published Posts tab to view and respond to comments on their posts instead.
Who is impacted: Advisor/Agent
Archiving and Compliance Implications: N/A
Availability: On for all organizations
Problem Solved: Message template functionality is not available, requiring users to manually input the same content many times over. This leads to an inefficient use of time when drafting commonly used messages like meeting reminders and anniversary greetings.
Expected Value: Message templates will allow users to save time when sending the same content to different clients and promote best practices in those communications. Administrators will be able to create and customize message templates, allowing them to create consistent messages that align with their organization's best practices, and helping reduce the time advisors/agents spend creating the same message content.
Expected Solution: A new menu item will be created within the Admin view’s side navigation panel called Templates, where admins will be able to view, create, and delete message templates. The Templates tab will contain a message template library that will show message template cards containing individual templates' title, textual content, and creation date and time.
Advisors/agents will be able to view, select, edit, and send admin-created message templates from their Relate message composer.
Message templates will only be available in the Relate web platform initially.
Who is impacted: Advisor/Agent, Compliance Admin, Marketing Admin, Program Admin
Archiving and Compliance Implications: Messages created using Message Templates will be treated as regular 1:1 messages, and they will follow existing archiving and compliance functionalities.
Availability: Off for all organizations, but can be turned on by contacting your Customer Success Manager.
Problem Solved: Currently, the most prominent buttons on Hearsay’s login page directs users to login via their Facebook or LinkedIn accounts. However, less than 5% of our users login by using Facebook or LinkedIn. The vast majority of our users login via SSO, but the option to send the SSO link to their registered email is hidden behind a small Not sure how to login? button. This organization of login methods impedes a smooth and quick way to access Hearsay for most of our users, who have to go through an additional step when logging in.
Expected Value: By prioritizing SSO login, we are able to better serve the vast majority of our users with their preferred login method and provide a more seamless experience.
Expected Solution: The Facebook and LinkedIn buttons will be removed from the login page, and instead, users will be prompted to enter their registered email address. Once the correct email address is entered, a link to the authentication page will be sent to that email address. The authentication page contains options to use SSO, Facebook, or LinkedIn to login, however, the user will only be presented with those options that they have available, based on their organization’s configuration. For example, if the user’s organization only has SSO available, then the authentication page will only show them the SSO option. After selecting their method of authentication, all further login steps will remain the same.
This update will not change any of our supported authentication methods, it will only change how we present these authentication methods to our users. Organizations that use a URL redirect to an SSO will continue to be able to do so.
Who is impacted: Advisor/Agent, Compliance Admin, Marketing Admin, Program Admin, Integrator
Archiving and Compliance Implications: N/A
Availability: On for all organizations
Problem Solved: API tokens/keys are always visible in the admin view, under Settings > Integrations, which makes them easy to copy and misuse.
Expected Value: Better token security improves the safety of customer data.
Expected Solution: The API Token value will only be shown immediately after it is created. After that, it will be hidden in the list of tokens on the Integrations page. If access is needed for a new application, a new token will need to be created.
Who is impacted: Integrator and Program Admin
Archiving and Compliance Implications: N/A
Availability: On for all organizations
Problem Solved: Currently, Actions receives triggers from external systems via a multi-use Hearsay synchronization API. This limits the possibility of enhancing the Actions API with mandatory validation and prompt feedback information. Actions reports come one day after the status change due to the standard Hearsay Reporting architecture.
Expected Value: Faster and more accurate feedback from the Actions API creates faster time to value and helps organizations make corrections immediately if the sent request record contains invalid fields.
Expected Solution: A new Actions API will provide more immediate feedback to external systems about the success or failure of the record insertion. The new API has the same insertion payload and format, and accepts the same API token, as the existing Actions API. The new API will have a different URL. There will be a six-month grace period from the day of release where existing Actions customers will be able to switch to the new API, and after the grace period, the old Actions API will be disabled.
To learn more about the transition process and set a date to begin the migration, contact your Customer Success Manager.
Who is impacted: Program Admin, Integrator
Archiving and Compliance Implications: N/A
Availability: On for all organizations with Actions enabled
Problem Solved: Currently, only Hearsay Services can activate Actions workspaces and upload Actions-specific workspace parameters such as Nickname and external ID(s). This slows down the workspace activation and configuration process, where admins don’t have access to steps required to ease bottlenecks in manual processes.
Expected Value: Enabling admins to have more control over Actions workspaces helps organizations more efficiently manage Actions and speed up the resolution of Advisor change requests.
Expected Solution: Organization admins will be able to activate and deactivate Actions workspaces and provision selected workspace-specific parameters via the Administration interface in Hearsay Desktop. Here is a complete list of capabilities admins will have with the new Actions workspace management tool:
Who is impacted: Program Admin, Advisors/Agents
Archiving and Compliance Implications: N/A
Availability: On for all organizations
Problem Solved: There is no data reporting available for Instagram Stories, which prevents administrators from better understanding their activity and engagement on this social media network.
Expected Value: Administrators will be given data on posts published as Instagram Stories, as well as their associated impressions and engagements.
Expected Solution: The Post All Data report will include the number of posts published as Instagram Stories, as well as their associated impressions and engagements. The “Publish type” field of the Post All Data report will display the value “Story” for all Instagram Stories. The impression metric of the Instagram Story will appear in the “Num.Impressions” field and the reply metric in the “Num.Comments” field.
Who is impacted: Marketing Admin, Program Admin
Archiving and Compliance Implications: N/A
Availability: On for all organizations
Problem Solved: Advisor/agents’ and their audience’s top interests are key measures that are currently reported only on the Advisor dashboards. Administrators would also like to have a view on these measures for all workspaces.
Expected Value: Administrators will be able to identify the top interest categories that the advisor/agents are posting about as well as the top interest categories that their audience found engaging.
Expected Solution: The Breakdown by Workspace report will be extended with 2 new fields: “advisor’s top interest” and “audience’s top interest”. These fields will display the top interest categories for the advisor/agents (based on their historically published posts), and the top interest categories for the advisors/agent's audience (based on their engagements with posts). This information will be available at the individual workspace level.
Who is impacted: Marketing Admin, Program Admin
Archiving and Compliance Implications: N/A
Availability: On for all organizations
Problem Solved: The number of social media posts originating from Content+ are currently only reported in the Suggested Content Performance report, which provides insight into Content+ usage at the content library level, but not at the individual post level.
Expected Value: Admins will be able to track the number of posts originating from Content+ at the individual post level, allowing them to see if a specific post came from Content+.
Expected Solution: The Post All Data Report will be extended with a new “Origin” field, with 2 possible values:
Who is impacted: Marketing Admin, Program Admin
Archiving and Compliance Implications: N/A
Availability: On for all organizations
As part of Hearsay’s continued effort to transform the Hearsay Relate app into a unified mobile experience that encompasses both Relate and Social functions, the Hearsay Social app icon has been updated to a hashtag in iOS, as follows:
This change allows the old Hearsay Social icon to be used as the new unified Hearsay app icon. No changes to any functionality within the Hearsay Social app are included with this release, and the app will continue to be supported until March 2024 but with no additional enhancements or feature updates.
The app icon will be updated for Android on or around Thursday, September 7th.
For more information about the transition to the Hearsay app, see Hearsay’s Unified Mobile App Release Information.