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.

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

Social

• Reusable Content Distribution Groups

Platform

• AI Signposting
• Navigation Bridge Enhancements

Compliance

• Contextual Risk Analysis

Relate

• Embedded Relate Phone-Based Matching Mapping Control

Data & Analytics

• Add Conversation ID Field to Text Message All Data Report

Social

Reusable Content Distribution Groups

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:

• No hierarchies within groups - Groups have no hierarchy between them and a workspace can belong to multiple groups. 
• No retroactive effects on posts - Editing or deleting a group does not affect previously scheduled or published posts.
• Multiple post targeting methods - Admins can target a mix of workspace groups and individual workspaces for a single post.

Admins can view, edit, or create workspace groups on the Organization page. To create a new workspace group: 

1. In the side menu, click Organization, then click the Workspace Groups tab.
2. Click Create a New Workspace Group and add the required information. 
3. Click Save.

To suggest a post to a workspace group:

1. In the Post modal, click the Suggest To dropdown. 
2. Select Workspaces and Groups. 
3. Enter the name of the workspaces and workspace groups you want to target the post to. 
4. Continue publishing the post.

Limitations

• A workspace group can contain a maximum of 200 workspaces. 
• Admins can suggest a post to a total of 200 workspaces, including those that are part of groups.
• Workspace groups are not yet available for campaigns.

Platform

AI Signposting

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.

Navigation Bridge Enhancements

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.

Compliance

Contextual Risk Analysis

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:

• Promissory Statements: Language that guarantees a specific outcome, promises a future return, or uses definitive "will/shall" language regarding value or performance.
• Securities Instruments: References to stocks, bonds, mutual funds, ETFs, options, futures, derivatives, brokerage accounts, crypto-assets, IRAs, 401ks, or tokens. Does not flag insurance, annuities, bank products, loans, or mortgages.
• Politically-Charged Statements: Political or policy-related language that could be interpreted as partisan, advisory, or influential.
• Threats: Threats of violence or harm to the company, employees, or leadership. Does not flag criticism, insults, or legal threats.

This feature is off by default. To enable it, contact Support at support@hearsaycorp.com. 

Relate

Embedded Relate Phone-Based Matching Mapping Control

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.

• Enabled mappings are considered when matching conversations or scheduled-message notifications back to Salesforce records by phone number.
• Excluded mappings are ignored in those navigation flows.
• If all mappings are excluded, conversation-list search returns no recipients and notification search returns the existing NO_MAPPING_FOUND behavior.
• Record-page widget lookup and conversation creation remain outside this change.

To configure the new phone-based matching, upgrade to Embedded Relate v4.44.0, then do the following:

1. Navigate to the mapping modal for the desired Salesforce object mapping.
2. Toggle the Include in phone-based matching setting on or off.
3. Save the mapping configuration.

No changes are needed for existing organizations — legacy mappings are included by default.

Data & Analytics

Add Conversation ID Field to Text Message All Data Report

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.