Mindful platform January 2026 hotfix release notes

Released January 29, 2026

Read about the latest system updates, feature enhancements, and new features on the Mindful platform.

Note: Looking for more?
  • Visit our Known Issues page to keep up to date on current issues.
  • Subscribe to our status page for up-to-the-minute notifications.

Release highlights

New option to hide internal IP addresses in SIP INVITEs

A new setting is available to Mindful super admins which will replace internal IP addresses with the Mindful domain in the FROM header of INVITE messages. This will be enabled by default for organizations created after January 2026.

New status page

The Mindful status page has moved to mindfulcallback.status.medallia.com and includes helpful new features.

image of the new status page

Resolved issues

The two Number of Days Out to Allow Scheduling settings now behave differently.

The Number of Days Out to Allow Scheduling (Widget/API) setting was operating according to the same rules as the related Voice option, which was not intended. We have updated the behavior of the Widget/API setting so that non-business days are skipped in the calculation. Moving forward, the two settings will have different behavior:

  • Number of Days Out to Allow Scheduling (Widget/API) — Excludes non-business days when determining the number of days out to allow scheduling.

  • Number of Days Out to Allow Scheduling (Voice) — Includes all calendar days when determining the number of days out to allow scheduling.

An issue causing audio to drop on the customer side of callbacks has been resolved.

In a rare case, a failure to send keepalive packets for long-lived TCP connections could cause subsequent SIP messages to fail, resulting in dead air on the customer side. We have updated our SIP router to issue keepalive packets for TCP connections to address the issue.

An issue causing the Call Detail page to fail to display call counts has been resolved.

In a rare case affected by a fast disconnection, calls in the database could be missing vital attributes. This in turn could cause the Call Detail page to throw an error when attempting to load call counts, if the affected calls were in the filtered date range. We have adjusted the logic for loading call counts to prevent this potential error.