New at Yext

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.

2 months ago

June 2025 Product Release

Here's what's in the June 25th release:

Platform

  • Hearsay rebranded to Yext
  • Shared authentication between Yext and Hearsay platforms

Social

  • Improved Modification Required workflow 

Relate

  • Wealthbox integration
  • New branding in Embedded Relate

Data & Analytics

  • Date range selector for Social Insights
  • See which Actions templates are for marketing purposes on Actions Template Messages All Data report
  • Voice and Messages aggregates to the Retain and Grow Value Measure Dashboard
  • See modified versus unmodified Actions templates

Platform 

Hearsay rebranded to Yext

As part of the ongoing effort to integrate Hearsay with Yext, the Hearsay logo and colors are now rebranded to Yext in the platform. The rebrand applies to all pages in the platform, mobile app, release notes, some Embedded Relate visuals, and the Help Center website. Help Center screenshots, enablement materials, slide decks, and other existing materials will be updated following the release.

This rebrand is cosmetic only and does not affect the functionality of the platform. We will announce any future updates related to platform integration in advance to help you prepare for the changes. 

Here is what does change:

  • Hearsay name and logo will change to the Yext logo.
  • Hearsay color (teal) will change to Yext color (black).

Here is what does not change:

  • Product names

    • Product names will remain the same (Relate, Social, Sites, etc). Products might be referenced without the word “Hearsay” at the beginning. 
  • Platform navigation
  • Functionalities in the platform 
  • URLs 

Before and after (gif)

Post Library before

Post Library after

Note: The Embedded Relate logo is changing from teal to black, but will still say “Hearsay Relate” in the Salesforce app until further notice. Please read the Embedded Relate release notes for more information.

For a more detailed overview of the changes, watch our rebrand video.

To get downloadable brand assets for your training materials, visit the Yext Brand Folder. 

For questions about the rebrand, please contact your Customer Success Manager. 

Shared authentication between Yext and Hearsay platforms

Logging into either Yext or Hearsay can now automatically sign you into both platforms, so you won’t need to log in again when switching between sites during the same session.

This feature is disabled by default. To enable it, contact Support at support@hearsaycorp.com with the email subject titled “Shared authentication between Yext and Hearsay, June 2025”. 

Social 

Improved Modification Required workflow

The "Modification Required" option for suggested content has been redesigned to make it easier for admins and end-users to manage post personalization while staying aligned on content and compliance. New visual indicators called chips help admins and users see where content is required and admins can customize what kind of content users should add.

Note: Modification Required posts are not currently available on Mobile. 

Admin workflow

Instead of relying on broad “Modification Required” labels or post-level editing permissions, admins can now insert a visual chip directly into the specific part of a post that requires end-user input. This chip acts as an editable placeholder that appears where changes are needed.

After a chip is added, the rest of the post becomes non-editable by default, allowing admins to protect core messaging while enabling personalized input only where appropriate. If desired, full editing access can be granted.

The chip is visible anywhere in the Suggested Post Library where the post is present, and can be updated or removed at any time.

Filtering has also been improved. Since the chip replaces the old “Modification Required” status, post statuses can be filtered based on real-time conditions like whether a post is editable by the user. Admins can also filter for campaign posts by personalization options.

End user workflow

End users can easily identify what parts of a suggested post they are allowed to personalize. Required edits are indicated with a colored chip embedded directly in the content that specifies what details their admin wants them to add.

Users can find all Modification Required posts in the Recommended tab, in the Personalized section.

Scheduled posts in the library display a Needs Attention status with a Modification Required warning. If the deadline passes, the status changes to Modification Overdue. After the user modifies the chip, it updates to a Modified state and the user can then reschedule the post. Users can find these posts in the Needs Attention tab of their Suggested Post Library to ensure timely edits. 

The chips are also displayed on the Campaign Subscription page. If a user is already subscribed to a campaign, they can go to the Calendar page and click on the chip in the post to make updates. In the Calendar, post cards change colors based on the modification status. 

Existing Modification Required posts will be updated with this new chip format. 

For user documentation see Personalizing a Library Post that Requires Modification. 

For admin documentation, see Creating Personalized Suggested Posts Using Modification Required Smart Fields.

Relate 

Wealthbox integration

The integration between Hearsay/Yext and Wealthbox now automates contact synchronization. In addition, activities, messages, and calls from Relate will now sync back into Wealthbox and appear as notes on the respective contact pages. Previously, Wealthbox users had to manually export and import contacts into Hearsay to maintain an updated book of business.

Example Wealthbox activity

To enable this feature, see Enabling Wealthbox For Your Organization.

After enabling Wealthbox for your organization, users can connect their Wealthbox account to Relate from their Workspace Settings page. See Connecting Your Wealthbox To Relate for more information.

Yext rebranding for Embedded Relate

Embedded Relate has been rebranded to Yext. The color has changed from teal to black and the Yext logo is now visible on the login page. For now, the naming of the product and widgets remain the same. We also removed the Hearsay logo from the header of pop-up modals within Embedded Relate to create a cleaner interface.

To see the branding changes, use this link to update to the latest 4.21 version of Embedded Relate.

Organizations that use the Hearsay app directly within Salesforce must manually update the app logo in the App Launcher. Since the logo can be customized it won’t be automatically updated by upgrading to the latest version. To update the logo, go to the Hearsay for Salesforce App Settings. Visit the Yext Brand Folder for downloadable logos. 

Data & Analytics 

Date range selector for Social Insights

The Social Insights dashboard now has a date range filter that allows users to view metrics from the past 7, 30, or 90 days, providing a more granular analysis of workspace social performance. Previously, they could only view metrics for 30 days. 

Note: Not every metric is time-bound, such as number of connections or interest categories. Updating the filter does not change these metrics. 

See which Actions templates are for marketing purposes on Actions Template Messages All Data report

A new Is Marketing Template (True/False) field has been added to the Actions Template Messages All Data report. This field enables admins to identify and track the performance of marketing templates only, or compare them to other types of templates.

Voice and Messages aggregates to the Retain and Grow Value Measure Dashboard

To help admin calculate aggregates for total voice and text usage, the  Retain and Grow Value Measure dashboard now has two new sections:

  • Total Voice minutes (inbound/outbound)
  • Total number of Texts (inbound/outbound)

See modified versus unmodified Actions templates

Previously, admins couldn’t track the usage of modified admin-created Actions templates or measure the performance between modified and unmodified template usage. To help admins better measure the success of modified templates, the Template ID field and a new Default field (yes/no) indicate whether an admin-created template was modified or whether the default language (unmodified) was used.