Release highlights

Call Detail records will now display Dispatch IDs for each dial attempt.

These IDs are useful for troubleshooting, and the Support team may ask you to provide them to investigate callback issues.

We have removed the callerInput field from Call Target configuration API endpoints.

The callerInput field indicated whether or not customer speech recognition was enabled for a Call Target. Since this feature has been deprecated, the associated field has been removed from the API.

We continue to make security enhancements throughout the application.

These updates will continue to maintain compliance with modern security standards.

Resolved issues

An issue preventing certain users from viewing Insights dashboards has been resolved.

When a user with the "Callback viewer" role was assigned to a Business Unit, that user was not able to load any Insights dashboards. With this update, viewers can now access Insights for the Call Targets in their Business Unit(s).

Call Target Segments now use the appropriate Callback CID for calls to customers.

Previously, when a Segment was configured with a unique Callback CID and a callback was requested via a Diversion header or custom X-header, the underlying Call Target's Callback CID was displayed to the customer instead of the value appropriate for the Segment.

The search field on the Phone Numbers page is no longer drawn over top of the user settings dropdown menu.

Previously, the user settings menu options in the top navigation bar were drawn beneath the Search field on the Phone Numbers page, which could prevent users from clicking the Logout button.

An error message will now be displayed on Insights dashboards when an SSO email address is missing or misconfigured.

When an SSO user is configured without an email address or with a misconfigured address, they will see an error message describing the issue. Previously, Insights dashboards would not load in this scenario, with no guidance as to the cause.