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 a post contains restricted lexicon terms and the organization requires compliance review before publishing, the social publisher now shows a newly-labeled Needs Approval badge. The old Non-Compliant badge could be misleading, making users believe their post was rejected entirely and that they would not get a chance to submit it for review.
New Needs Approval badge
Here is what's in the August 5th release:
Compliance
Relate now applies PII rules to images and document attachments, not just message text. Using optical character recognition (OCR), the system reads text inside images, screenshots, and PDFs and runs it through the same lexicon and rules already applied to written messages. When sensitive personally identifiable information (PII) is detected, such as a driver's license or Social Security card, the attachment is automatically removed from the conversation and replaced with a notice, while the original content is retained in the compliance archive.
Integrators can now publish posts containing multiple images in a single API call to the Create Content endpoint (POST /content). Previously, the public API only supported single-image posts, requiring workarounds for multi-image content. This update enables richer, more visually engaging posts, particularly for programs that automate content distribution via the Hearsay API.
Key behavior:
picture_urls.error_code: "too_many_photos".To publish multi-image posts, do the following:
picture_urls as an array of up to 10 valid image URLs."too_many_photos" error code (HTTP 400) if the image count could exceed 10.Example request body:
{
"author_id": 24542,
"messages": ["Text post with multiple images"],
"social_networks": ["facebook", "linkedin"],
"modification_rule": "optional",
"picture_urls": [
"https://example.com/images/product-1.png",
"https://example.com/images/product-2.png",
"https://example.com/images/product-3.png"
]
}The same constraints (supported file formats, max file size, resolution limits) apply to images uploaded via the API as to those uploaded in-app.
No configuration changes are required. Integrators already using the Create Content endpoint can immediately begin passing picture_urls with multiple URLs.
Organizations can now allow users to delete their own published posts on the Respond tab without allowing them to engage via likes or comments. This provides more precise control over what actions users can take on the Respond tab, enabling organizations to match the product experience to their compliance and governance policies.
This feature is configurable via an admin setting. To configure it in the Administration view:
Configure the Allow users to like and comment on published posts setting.
Respond tab with setting Enabled (Like and Comment visible)
Respond tab — Published Posts view with setting Disabled (Like and Comment hidden, Delete still available)
We have made the following enhancements to Hearsay Actions:
Contacts and leads are now automatically labeled with their source channel at creation. Labels include sources such as Actions flow or a website chat. Labels are sortable and filterable, giving admins visibility into where activity is coming from.
This feature is OFF by default. To enable it, go to Actions > Organization Settings and turn on the Automatic Labeling setting.
Actions can now use workspace-specific working hours configured in Relate rather than a single organization-level schedule. This ensures the correct message template (inside vs. outside business hours) is used for each workspace and that follow-up notifications reach users at the right time. This is especially useful for organizations with users across multiple time zones.
This feature is OFF by default. To enable it, go to Actions > Organization Settings and turn on the Workspace-Specific Working Hours setting. Existing Do Not Disturb settings are unaffected.
Admins can now control whether end users are allowed to upload PDFs when creating social posts.
To configure the PDF setting for users:
PDF uploads for end users are enabled by default. This setting does not affect admin-level PDF uploads in suggested content.
Here's what's in the June 24th release:
Admins can now create reusable workspace groups to efficiently target posts to specific sets of workspaces. Here are key behaviors when working with workspace groups:
Admins can view, edit, or create workspace groups on the Organization page. To create a new workspace group:
To suggest a post to a workspace group:
Limitations
Hearsay is rolling out a standardized AI signposting system across the platform. This gives you clear, consistent visibility into when AI is at work. It's designed to keep Hearsay aligned with global regulations, including the EU AI Act, without adding complexity to your workflow.
AI signposting is being added across the platform on a rolling basis. These will appear as "Powered by AI" labels and AI icons to help you quickly understand where AI is infused in the product.
Yext and Hearsay platform users now benefit from a unified cross-platform experience. Yext Accounts are linked to Hearsay Organizations, and users are matched across both systems, enabling shared login sessions and instant platform switching from the navigation bar.
Overall, the new behavior is more reliable than logging in and out consistently adds or removes access across both platforms, and an active session in either platform allows seamless navigation to the other without re-authenticating.
To enable this feature, reach out to Yext Support.
Contextual Risk Analysis uses LLM-powered detection to identify thematic compliance risks in communications, moving beyond traditional keyword-based rules. This approach reduces false positives and provides more meaningful alerts for compliance users, especially in environments with large volumes of unreviewed alerts.
Contextual Risk Analysis works by using predefined prompts to identify and create an alert for the following risk category signals:
This feature is off by default. To enable it, contact Support at support@hearsaycorp.com.
Admins can now decide which Salesforce object mappings participate in phone-based record matching. This helps customers route conversation-list and scheduled-message navigation to the right business object, such as Case instead of Contact, without changing record-page widget lookup or conversation creation behavior.
A new setting, Include in phone-based matching, has been added to the Hearsay Admin mapping modal. This setting controls whether a given Salesforce object mapping is considered during phone-based record matching.
To configure the new phone-based matching, upgrade to Embedded Relate v4.44.0, then do the following:
No changes are needed for existing organizations — legacy mappings are included by default.
A new Conversation ID field has been added to the Text Message All Data report, making it easier to filter for specific conversations and analyze messages as a single conversation thread.
Users now receive a desktop system notification when an inbound call arrives, helping them quickly identify the caller and decide whether to answer. This prevents missed or delayed responses and improves response time and call-handling efficiency.
When a desktop call arrives, a notification containing the caller’s name and phone number appears even if the browser page containing the Hearsay web app is minimized. Clicking the notification returns the user to Hearsay to accept or manage the call.
To enable desktop notifications for calls, users must grant browser permissions to Hearsay when prompted or manually enable notifications for the browser in their computer settings. Users must also ensure Do Not Disturb or Focus modes are turned off for their browser.
This feature is ON by default for all organizations. To disable it, contact Support at support@hearsaycorp.com.
Here is what's in the May 13th release:
Social
Relate
We have improved Hearsay Social’s AI-assisted writing to help users create high-quality, social-ready posts faster with less manual editing.
With this update, you can expect:
This feature will allow advisors to move from idea to publish-ready copy more quickly while also allowing marketing and compliance teams to spend less time reworking content to meet quality standards.
Advisors and agents can now add, edit, or remove website URLs in their workspace profile without needing Support. This reduces onboarding friction and helps users publish smart fields posts immediately with accurate website information.
To update websites, navigate to Workspace Settings and select the Websites tab. Once you click Modify, a pop-up opens where users can add new URLs or edit/delete existing URLs. Each website entry supports:
A Language selected from a dropdown
Hearsay now supports Threads monitoring, which enables compliance officers to supervise and archive activity. This is a monitoring-only integration, meaning all content must be published directly within the Threads.
To access this feature, you will need to connect your Threads account to Hearsay
This update includes:
Please note: With the release of v4.43.0, Embedded Relate v4.41.0 and earlier will no longer be supported. Customers on v4.41.0 or earlier should upgrade to stay up to date with the latest functionality.
Embedded Relate now supports inline attachment preview, making it easier and faster to review documents without leaving the context of a conversation. When you select an attachment in the widget, it can now be previewed directly inline rather than opening in a separate browser window. We've also improved the reliability of attachment loading, so you won’t encounter error states when opening supported file types.
No additional setup is required. The attachment preview is available as part of the standard Embedded Relate package beginning with v4.43.0.
Embedded Relate now supports configurable widget height, giving you greater control over how the widget fits within your CRM layout. This allows you to better use available screen real estate, especially on larger monitors or more complex page layouts, and tailor the experience to match how your team works.
To configure, set your desired height in the Embedded Relate component properties or layout configuration where the widget is placed. Once saved, the new height applies automatically. The configured height applies uniformly to that Embedded Relate instance for all users and records. If no custom height is configured, the widget behaves exactly as it did before.
This new functionality is available with the updated Embedded Relate package v4.43.0.
In the mobile app, you can now record a video on your device and add it directly to a social post. This eliminates the need to record and save a video to your device's gallery before adding it to a post.
This feature is available for the following app versions:
• iOS version: Hearsay 9.2
• Android version: Hearsay 6.1.2
Here is what's in the April 1st release:
Social
Relate
Platform
Compliance
End users can now personalize the image used in corporate-authored suggested posts while keeping the approved message unchanged. This feature allows all image options to be managed within a single suggested post, reducing the need to create duplicate posts while keeping reporting and supervision streamlined.
Provide Multiple Admin-Approved Image Options
When creating a suggested post, begin the add images flow and select the Alternative Image Upload option. Admins will then be able to upload up to 9 images and set one as the default image that appears pre-selected for end users. Admins can also allow end users to upload their own images by selecting the checkbox below the uploaded images section.
When publishing or previewing a suggested post, end users can select from the Admin-approved images attached to the post or upload their own image if that option is enabled. The final published post always includes one image and the approved corporate text.
Selecting from Admin-approved images does not trigger additional compliance review beyond the existing workflow. If user-uploaded images are permitted, those images follow the organization’s existing compliance review processes.
Require End Users to Upload Their Own Image
In addition to providing multiple Admin-approved image options, Admins can choose to require end users to upload their own image when personalizing a suggested post. By enabling the required user upload option and not attaching any images to the post, Admins ensure that end users must add a custom image before publishing.
When this option is selected, end users will not be able to publish or schedule the post until an image is uploaded. The final published post always includes one image alongside the approved corporate text.
User-uploaded images continue to follow the organization’s existing compliance review processes.
Users can now specify Meta Special Ad Categories (such as Credit) when creating boosted posts in Hearsay Social. This helps reduce rejected boosts and supports compliance with Meta advertising policies.
When boosting a post, users can select a Meta Special Ad Category if required. The selected category is passed to Meta through the Ads API as part of the boost creation. Organic posts are not affected.
The Meta Special Ad Category option will appear in the boosted post workflow when applicable.
GenAI features in Hearsay Social are now generally available, helping advisors and marketing teams draft social content faster while maintaining existing compliance and supervision workflows.
When enabled, users can access GenAI assistance in the compose experience to draft or refine posts. Generated content can be edited and is archived and supervised like any other post.
To enable GenAI features, navigate to the admin settings page and activate the features under the AI tab. Before activation, admins must accept the GenAI terms in the AI Terms acceptance modal.
Customers can now track links included in Picture Posts, not just Link Posts. This ensures UTM parameters are applied even when advisors choose a Picture Post format with a link in the text, helping teams more accurately measure social campaign performance.
When a Picture Post contains a link, Hearsay Social automatically detects the URL and applies UTM parameters and URL translation based on your existing URL Translation configuration.
You can reach out to support to check if your URL Translation rules are set up as desired.
Advisors using Embedded Relate can now personalize templates with contact-specific placeholder variables. This enhancement reduces redundant typing and strengthens communication consistency by automatically pulling details like names or email addresses directly from the contact record.
To create a template with variables:
This feature is available to all organizations that have upgraded to the latest version of Embedded Relate. If your organization is not already leveraging variables in Relate, please contact Hearsay Support or your Customer Success Manager to enable them.
To ensure feature parity across the Relate suite, Starred Conversations are now available in Embedded Relate. Advisors can now prioritize critical client threads in Salesforce just as they do on Web and Mobile, with all "starred" statuses syncing automatically across platforms for a consistent experience.
Once a conversation is starred, users can use the conversation filter to view only their high-priority threads. Additionally, if sound notifications are enabled, starred conversations use a distinct audio cue, allowing advisors to immediately recognize priority messages as they arrive.
To enable Starred Conversations for your organization, upgrade to the latest Embedded Relate Salesforce package, and then contact your Hearsay representative or Support to request activation.
Relate’s template supervision workflow has been extended to Salesforce, ensuring a consistent compliance experience across all platforms. Program and compliance teams can now apply the same review and approval workflows to templates created within Embedded Relate as they do for those created in the main Hearsay application.
When a user creates a workspace template in Salesforce, it will now automatically route through your organization’s standard compliance flow. Once approved, these templates—including those with system-generated variables—can be used to send messages that bypass manual supervision alerts, reducing queue noise while maintaining full archival records.
To enable supervised templates for Embedded Relate, upgrade to the latest Embedded Relate Salesforce package. If your organization already uses supervised templates on other Relate platforms, they will be automatically available here as well. To enable supervised templates for the first time, please contact Support or your Customer Success Manager.
Admins can now restrict the visibility of organization-level Relate templates based on specific organizational hierarchies. Previously, all org-level templates were visible to every user, which could lead to a cluttered template picker; now, advisors only see the messaging relevant to their specific region, division, or channel.
To configure this, admins can select a Template Region from a dropdown when creating a new Relate template. By choosing a specific hierarchy (and any applicable sub-levels), the template will only be available to users within that segment. Templates intended for universal use should keep the default All Regions setting.
This feature is available by default as part of the April 2026 Release. Please note that once a template is published, its hierarchy settings cannot be changed.
The Workspace and Accounts pages have been combined into a single unified screen to simplify navigation and management for users and admins. The legacy Workspace and Accounts pages have been removed and replaced with this updated experience.
Hearsay now supports OAuth-style API authentication with expiring tokens, providing a more secure way to access APIs. Any compromised tokens are time-limited in their ability to access data.
To learn more about enabling this OAuth-style authentication, reach out to your Yext representative.
The Yextpert AI web widget has replaced the previous ‘Help’ widget on the Hearsay desktop platform. All users can now ask product-specific questions and receive real-time answers directly within Hearsay.
The Hearsay page previously labeled as "Review" will now be labeled as "Supervision" throughout the platform. This is a UI label change only and does not impact underlying functionality.
