Coming Soon!

Release date pending

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

Customizable Call Targets page

You can now set a maximum number of Call Targets to view at once in a paginated layout on the Call Targets page for easier navigation and faster loading:

image of the call targets page

New URLs for Scheduler API endpoints

We have updated the base URL and paths of Scheduler API endpoints as follows:

New base URL and path https://api-callback.getmindful.com/api/scheduler

  • Check widget status/widget/{widget_id}

  • Register a callback/widget/{widget_id}/request_callback

  • Cancel a callback/organization/{organization_id}/cancel_callback

  • Request callback status/organization/{organization_id}/callback_status

  • Request status of all widgets/organization/{organization_id}/widget_status

Important:

The new URLs only apply to widgets created after this release. Any previously configured widgets can continue to use the prior URLs.

If your organization uses Content Security Policies (CSP) on your website, you must update your policy to allow the new widget domains before creating new Mindful widgets.

For complete endpoint definitions and authentication guidance, see the Scheduler API documentation.

Call Detail performance improvements

The Call Detail page will no longer attempt to load more than 180 days of data, which will improve load times and performance for organizations with a large amount of historical data.

When more than 180 days (six months) of data is requested, a message will appear on the page to instruct the user to export the data to CSV.

In this scenario, the other filters will be inaccessible and no data will be loaded on the page until the date filter is adjusted to a period of less than 180 days.

example of loading too much data on the call detail page

Callback Status performance improvements

We have completed the first phase of performance improvements for the Callback Status page. Sorting columns is now quicker and more responsive, especially for organizations with large numbers of Call Targets.

We continue to work on additional performance enhancements that we will announce in the future!

Additional entries in the Audit Log

The following changes will be appear on the Audit Log page as update events with an Object Type of "Organization":

  • A Mindful super admin enables or disables the multi-factor authentication (MFA) requirement.

  • The Current Retention Period field is updated on the Data Retention page.

Resolved issues

Drill-down windows on the Callback Performance dashboard will now consider dashboard filters when presenting data.

Previously, the data shown in drill-down windows for average value metrics (such as Avg Wait Duration) did not take filters into account, resulting in incorrect data.

The Source filter on the Call Detail page will now filter for web interactions appropriately.

In the Source filter, the "Web" option unexpectedly included voice calls. With this release, each of the three options (Web, Voice, and Messaging) will filter the results as expected.

Enabling or disabling all Call Targets via the Global Settings page is now more efficient.

For organizations with a large number of Call Targets, enabling or disabling the Register Callbacks or Process Callbacks settings on the Global Settings page could take several minutes to apply to all Call Targets. We have updated the logic behind this operation so that the change takes place immediately.

An issue causing an RTP echo on the customer side has been resolved.

After sending a SIP ReINVITE with the Block Media After Reinvite setting enabled, Mindful could send an RTP packet with an unexpectedly late timestamp. This in turn could cause a client's transcoder to break, resulting in customers hearing an echo on their side of the call.

A cause of failed connections between customers and agents has been resolved.

In rare cases, a SIP Re-INVITE sent from Mindful to the contact center could collide with another message coming from the contact center to Mindful, causing the contact center to respond with a SIP 491 Request Pending message. This in turn would cause the connection between the customer and agent to fail when the customer was already reconnected.