Release Notes for January 2026

We've constantly been working to improve your Sense experience; here's a summary of what has been added, improved, changed, and/or fixed in January 2026.

Feature Releases & Enhancements

Batching Across Channels

Sense Workflows (J2) now supports Batching Across Channels, enabling controlled, high-volume execution across Email, SMS, and VoiceFlow nodes directly within workflows.

Previously in Journeys (J1), batching was limited to email-only campaigns, was not supported for dynamic or rolling audiences, was unavailable for SMS and VoiceFlow, and lacked fine control over when and how much data was processed. As a result, customers running high-volume sends had no flexible way to safely distribute traffic over time, often risking provider throttling, IP reputation issues, and uneven spikes.

Batching can now be configured directly in J2 workflows and applies across Email, SMS, and VoiceFlow nodes. It is configured on the first node of a workflow path. All downstream communication nodes automatically inherit the batching configuration.

Batching also works with rolling audiences — records are continuously picked up and processed across batches until the configured end condition is met.

Users can configure batching using the following options:

• Start date — When batching should begin
• Daily time window — The hours during which records are processed (e.g., 1 PM – 6 PM)
• Throughput control — How many records are processed per hour
• Batch frequency — How often batches run (e.g., every X days/weeks)
• End condition — Stop by a specific date or after a set number of batches
• Blackout days — Skip processing on selected days

Job Match in Workflows

Job Match is now available in Sense Workflows, enabling staffing agencies and corporate companies to automatically send candidates relevant open job opportunities via Email and SMS — directly within their workflow automation.

Job Match supports the following use cases:

• Redeployment — Run campaigns targeting candidates whose placement has ended or is about to end, and send them relevant open jobs via Email or SMS.
• Reactivation — Run campaigns targeting passive candidates in your database, and send them relevant open jobs via Email or SMS.
• Silver Medalist — Run campaigns targeting applicants who were unsuccessful in their job interviews or hiring process, and send them relevant open jobs via Email or SMS.

What's included:

• Sending matching jobs via SMS and Email — Candidates receive job opportunities through their preferred communication channel.
• Default Matching Rules — Default matching rules are enabled at the time of setup and can be modified by admins self-serve directly in the UI.
• Preview — Customers can preview the matching jobs for any candidate, useful when using Job Match for the first time to verify field mapping is correct.
• Tabular View in Email — Matching jobs are displayed in a table within the email. Customers can choose which fields to display in the table.

All matching rules are customizable and admins can manage them self-serve in the UI.

Note: Job Match is an add-on capability. Contact your Customer Success Manager to learn more or you can refer to this detailed article - Understanding & setting up Job matching in workflows.

Sense Mobile App

The Sense mobile app has been updated to version 4.9.0, introducing CRM capabilities and a new app identity.

CRM Applicants & Matches

Recruiters can now manage candidates across the full hiring lifecycle, from screening to hired, directly within the mobile app.

• Ability to add candidates directly to jobs and perform all applicant-related actions seamlessly.
• Enhanced control over candidate stages for improved recruitment workflow.

App Re-Branded

The app has been rebranded from Sense Messaging to Sense Talent to better reflect its expanded capabilities.

You can refer this articles for detailed information on Sense Talent Mobile App and its capabilities - Sense Talent Mobile. 

Blank Text Template in Email Node

When opening the Email Node for the first time in a workflow, users are now prompted to choose how they want to start designing their email. Previously, Design with Layout was the only available option, which includes branding elements such as headers, footers, and logos. Users who did not require these branding elements had to manually remove them every time, resulting in extra effort and friction.

Users can now choose between two options:

• Design with Layout (Default) — Includes branding elements such as header, footer, and logo. Best suited for branded communications.
• Blank Text Template — A clean, rich-text-only editor without branding elements, ideal for simple or plain-text-style emails.

This provides flexibility to support both branded and plain-text communication use cases, and reduces time and effort by removing unnecessary cleanup steps.

ABT Rules Exports — Rule Satisfaction Timestamp

List and Workflow/Journeys exports now include the exact timestamp at which an ABT rule condition was satisfied, improving rule visibility beyond just entity attributes.

Previously, exports only included entity attribute-based rules. There was no visibility into when an ABT rule was satisfied. For event-based rules such as Email Opened, users could see that members qualified and the rule was met, but not the time the event occurred.

What's new — Rule Satisfaction Timestamp in Exports:

List and Workflow exports now include a timestamp field indicating when a rule condition was satisfied.

• For an Email Opened rule, the export will show the exact time the email open event was registered.
• The timestamp will be in agency timezone.
• The column header will be in the format: [Event Name] - [Recipient Relation] - [Time Range] (i)
• In case of multiple ABT events satisfying the rule, the earliest one will be shown.
• An (i) index number will be included to distinguish between similar rule blocks.

Scoped Rule Export:

• Only rules from the Inclusion block of Filters, Workflows, and Journeys are exported.
• Rules defined outside the Inclusion block are excluded to keep exports focused and relevant.

Disconnecting Conferencing Tools

Admins can now disconnect previously connected conferencing tools at the agency level directly from the platform.

Previously, admins could connect conferencing tools for hosts but had no way to disconnect them once they were no longer needed. Disconnection required raising a support ticket.

With this update:

• Admins can disconnect a conferencing tool for the entire agency on their own.
• No need for individual users to take action.
• No need to raise support requests.

Notable Fixes

Frequency Limit Behavior Fix in Workflows

A fix has been made to the frequency limit behavior in Sense Workflows (J2).

Previously, when a node hit a frequency limit, the record was not terminating there and was continuing to move ahead in the workflow. As a result, candidates who were supposed to receive only one call, SMS, or email were receiving multiple communications downstream.

With this fix, when a record hits a frequency limit, it will now correctly terminate at that node and not proceed further. Users will also be notified when a record terminates due to hitting a frequency limit.Survey 1.0 — NPS Tab Removal & Rename

The client and candidate NPS tabs have been removed from the Survey 1.0 analytics dashboard. Since NPS from J1 and Surveys 2.0 are now available on a unified dashboard, these tabs have been removed to avoid confusion.

The Survey and NPS section has also been renamed to Survey 1.0 for better clarity.