Here is what's in the October 28th release:

Social

• Profile Variables Available in the Social Posts (Create Content) API

Relate

• Download Contacts as CSV
• Conversation Summarizer
• Revoke Text Opt-In from Relate UI
• Embedded Relate Sync Platform Includes Instagram “Like” Activity

Platform

• Notification Enhancements for Workspace Management and Identification
• Confirmation Dialog When Deleting User Invitations
• Hierarchy Manager Improvements

Compliance

• Contextual Risk Analysis Messaging Improvements
• Email Alerts on New Classification Items

Social

Profile Variables Available in the Social Posts (Create Content) API

Customers that create social posts through the Hearsay public API can now include smart fields (profile variables) in the post text. Integrations can generate a single post that automatically personalizes the post for every user with the following variables:

• {{ profile.name }}
• {{ profile.title }}
• {{ profile.main_location }}
• {{ profile.city }}
• {{ profile.page }}
• {{ profile.phone_number }}
• {{ profile.email }}

Developers can add supported profile variables to the post text in the API request. Each variable resolves per workspace from the workspace profile at publishing time, the same way as smart fields added in the Hearsay platform.

Note: The {{ profile.page }} variable inserts the user’s page URL from the workspace profile. It resolves to a single URL -  the first page with the en_US locale, or the first page if there is none. A specific locale can be targeted with, for example, {{ profile.page.fr_CA }}, which falls back to the first en_US page if not available.

---

Relate  

Download Contacts as CSV

This feature lets users export the contacts available in their current Relate Contacts view to a CSV file, making it easy to review, share, or work with contact data outside of Relate. The export includes each contact's attestation (opt-in) status alongside contact details.

This option is off by default. Admins can enable it by going to Organization Settings > Relate and switching the Enable Contacts CSV download setting to Enabled. 

Once enabled, a download option is available on the Bulk Actions menu in the Contacts view.

Conversation Summarizer

The Conversation Summarizer uses an LLM to produce concise recaps of Relate conversations, so users can catch up quickly without reading the full thread. Summaries surface explicit action items and a sentiment read, and can roll up hierarchically across a conversation's history.

A new summary is generated in the background after at least three messages have been sent since the last summary. If a generation attempt fails, the last successful summary is preserved. Users can rate a summary as positive, neutral, or negative, and negative ratings can include reasons such as a missed key point, an inaccuracy, or being too long.

This option is off by default. Admins can enable it by going to Organization Settings > Relate and switching the Enable Conversation Summarizer setting to Enabled.

Revoke Text Opt-In from Relate UI

Users can now manually revoke a contact's text message opt-in consent directly from Relate rather than requiring a support request. This makes it faster to honor a contact's request to stop receiving messages and keeps consent records up to date.

When this feature is enabled, users can revoke an opt-in in the contact’s record by clicking the three-dot menu in the upper right of a conversation, then selecting Revoke Opt-In. The revocation is recorded against the acting user with a timestamp.

This option is off by default. Admins can enable it by going to Organization Settings > Relate and switching the Enable Allow Users to Revoke Opt-Ins setting to Enabled.

Embedded Relate Sync Platform Includes Instagram “Like” Activity

Instagram Likes are now included alongside the other social activity the Sync platform already delivers, so users can see when a client or prospect engages with their Instagram content and use that as a signal for timely follow-up.

---

Platform 

Notification Enhancements for Workspace Management and Identification

Users who belong to multiple workspaces often struggle to identify which workspace a notification belongs to and can become overwhelmed by the volume of alerts. Two new notification updates allow users to immediately identify the source of a notification and provide the flexibility to silence notifications from specific workspaces that do not require their attention.

• Workspace Identification: Every workspace-specific notification now includes a distinct metadata label (e.g., "Workspace: Chicago West") so users know exactly where their attention is needed.
• Workspace-Level Toggles: A new interface in the Hearsay user settings allows users to enable or disable notifications for entire workspaces. When a workspace is disabled, notifications are filtered out of the display but remain stored in the system.

By default, all workspaces are visible and notifications display the workspace name as it existed at the time the notification was created.

To enable these features, contact support at help@yext.com. After it is enabled, workspace labels automatically appear on new notifications. Users can manage workspace notifications in My User Settings > Notification Settings.

Confirmation Dialog When Deleting User Invitations

When an admin attempts to delete an invitation, the system now displays a confirmation dialog. The admin must confirm the intent before the invitation is deleted, providing a safeguard against accidental clicks and data loss.

Hierarchy Manager Improvements

The new hierarchy management interface significantly improves legibility and navigation for large-scale account structures. Additionally, the update streamlines the workflow by allowing users to navigate directly from hierarchy management to specific workspace locations.

The improved interface introduces a tabbed experience that separates Hierarchy Management and Workspace Management. Key updates include:

• Tabbed Navigation: Tabs for hierarchy and workspace managers provide a focused experience.
• Improved Layout: A redesigned top section uses less vertical space.
• Enhanced Search: Added searching by hierarchy name or reference id in the Hierarchy tab
• Legacy Support: A dedicated tab/link can access the legacy workspace manager if needed.
• Feature Parity: Rebuilt CSV export functionality within the new frontend, maintaining support for current download routes and root district behavior.
• Real-time Updates: Improved data synchronization so that changes made when assigning or unassigning workspaces are immediately reflected in the hierarchy manager.

Compliance 

Contextual Risk Analysis Messaging Improvements

Contextual Risk Analysis (CRA) and PII checks now incorporate additional context from the message when evaluating risk, greatly increasing their accuracy and resulting in fewer false positives. This new behavior happens automatically within the existing checks and there is no change to how admins configure or run them.

Email Alerts on New Classification Items

Compliance admins can now get an email notification if Supervision item contains a certain classification. For example, every item with the “Threat” or “Promissory Statement” classification generates an email to the relevant queue it is assigned to. This can help teams keep better track of the most high-priority items without having to manually search through the queue. 

To enable the email notification, do the following:

1.  Go to Organizational Settings > Lexicon > Classification Alert Notifications. 
2. Set the Enable Classification Alert Notifications to Enabled. 
3. Under Alert Classifications, select which classifications should generate email notifications.

Here is what's in the September 16th release:

Social

• Publish Stories on Instagram and Facebook
• Edit Published Posts
• Opportunities Tab Moved

Compliance

• Contextual Risk Analysis Improvements

Social 

Publish Stories on Instagram and Facebook

Users can now publish Instagram and Facebook Stories directly from the Hearsay platform. Stories are the highest-engagement format on Meta platforms, offering a full-screen, immersive experience to share time-sensitive content with followers.

To publish a story, click the Story tab on the New Post modal. This option is only visible for users with a connected Facebook or Instagram account.

The remaining publishing workflow is the same as the Feed Post publisher, allowing users to select their accounts (Facebook and Instagram only) or choose to schedule the post for later before requesting approval. Scheduled or published stories appear in the Post Calendar and Post Library with a visual badge distinguishing them from feed posts.

Stories are not currently available for admin-created content or on the mobile app.

Stories appear as regular feed posts on the Supervision page and continue to be tracked after their 24- hour expiration period on the platform. 

Edit Published Posts

Users can now correct mistakes in published social posts in Hearsay without deleting the original post and starting over or switching to the platform to modify it.

To edit a post, on the Respond tab, click Edit on the post. The user can then modify the text and submit the changes. After the post is approved and republished, it retains its original engagement metrics (likes, comments, shares) on the network.

The edited post generates an Edit Event item in Supervision, where Compliance admins can see the modified content as well as the original post.  

Currently, editing is only available for Facebook and LinkedIn posts. 

Admins can enable editing by doing the following on the Administration page:

1. In the sidebar, click Settings.
2. Under Organization Settings, click the  Content & Email tab.
3. Change the setting Allow users to edit already published posts to Enabled. 

Once enabled, the Edit button appears automatically on eligible posts in the Respond tab.

Opportunities Tab Moved

The Opportunities tab on the Respond page has been moved to the right side of the tab menu. This change allows for users to more quickly navigate to their more highly utilized tabs with less friction. This is a minor navigation change only and does not affect the functionality of the tab.

Compliance 

Contextual Risk Analysis Improvements

Contextual Risk Analysis uses an improved two-step analysis flow to provide more accurate risk detection for Compliance teams. The updated system first identifies candidate risk categories, then performs a more focused category-specific analysis before creating a compliance signal.

This reduces false positives from broad or ambiguous language while surfacing more meaningful signals for thematic risks such as promissory statements, securities instruments, and politically leaning statements.

Relate iOS users can now send text messages through a guided Siri conversation in the mobile app.

The user must enable Siri for the app by doing one of the following:

• Follow instructions on the Manage Siri Messages action card on their Home screen 
• Go to Settings > Siri > Manage Siri Messaging

After Siri is enabled, the user can direct Siri to create a message by saying something like “Hey Siri, use Hearsay to send a text.”

Hearsay then searches the user’s contacts, verifies that the recipient has a usable primary phone number and is attested, then uses an existing conversation or creates one when needed. If a recipient cannot be found, Siri asks again up to two times. No message is sent if the contact cannot be found or can’t receive text messages. Siri reads back the recipient and text message content to confirm before sending.

To get Siri for Hearsay Relate, upgrade the app to version 9.6.1 for iOS. 

Siri messaging is not available for Intune, group and broadcast conversations, attachments, media, templates, scheduled messages, and messages with other rich-text features. 

Upgrade to the latest version of Embedded Relate to get the following enhancements:

Group Messaging for Embedded Relate

Embedded Relate users can now send group messages directly within the Embedded Relate interface, bringing it to parity with the core Relate product. All group messages follow existing compliance workflows (review, approval, and supervision) where applicable.

Embedded Relate Latency Improvements

After resolving latency issues that were affecting system performance, the Embedded Relate experience has been improved with faster load times and better responsiveness.

Users with group texting enabled can now mark group conversations as spam in the Hearsay mobile app. Previously, users could only hide unwanted group conversations, which could reappear when a new message arrived.

Once marked as spam, the group conversation is removed from the active conversation list and remains in the Spam filter unless the user restores it. This action does not mark the individual participants or their one-to-one conversations as spam. Broadcast conversations cannot be marked as spam.

To mark a group conversation as spam, do the following:

• iOS: Swipe left on a group conversation and select Spam
• Android: Open the conversation’s action menu and select Mark as Spam

To get this feature, update to the latest version of the mobile app. 

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

• Image and Attachment PII Scanning and Removal

Compliance  

Image and Attachment PII Scanning and Removal

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.

Create Multi-Image Posts via API

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:

• Supports up to 10 image URLs per post.
• Value must be an array of strings containing valid image URLs.
• Duplicate URLs are automatically deduplicated before the content is created; the first occurrence is preserved.
• Instagram content requires at least one image in picture_urls.
• If more than 10 unique image URLs are provided, the API returns a 400 error with error_code: "too_many_photos".

To publish multi-image posts, do the following:

1. Review the updated API documentation: docs.hearsaysocial.com/reference/create-content
2. Update your API request payload to include picture_urls as an array of up to 10 valid image URLs.
3. Ensure your error handling accounts for the "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.

More Granular Control Over Respond Tab Capabilities 

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:

1. In the sidebar, click Settings. 
2. On the Organizational Settings page, click the Content & Email tab. 

3. Configure the Allow users to like and comment on published posts setting. 

   1. Enabled (default): Users can like, comment, and delete posts on the Respond page. 
   2. Disabled: Users can only delete posts on the Respond page. 

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:

Automatic Source Channel Labeling

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.

Workspace-Specific Working Hours

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:

1. In the sidebar, click Settings. 
2. Under Organizational Settings, on the Content & Email tab, set the Allow workspaces to upload PDFs setting to Enable or Disabled. 

PDF uploads for end users are enabled by default. This setting does not affect admin-level PDF uploads in suggested content.