Release highlights

Handles for messaging notifications can now be configured with SMS short codes.

The Handle field determines the number displayed to customers when they receive SMS notifications from Mindful. If your organization uses short codes for SMS messages, you can now use those short codes in your Mindful notifications.

When requesting a callback via API, you can now specify that a customer has opted in to receive SMS notifications.

In order to track that a customer has opted in to receive callback notifications, it is now possible to include an opt_ins property with API requests to Mindful Callback Scheduler widget API endpoints.

See the example cURL request below:

curl --request POST \ 
--url 'https://<ORG_ID>.gov-scheduler-rt.getmindful.com/api/widget/<WIDGET_ID>/request_callback?time_zone=240' \ 
--header 'content-type: application/json' \ 
--data '{ "contact_number":"<PHONE_NUMBER>", "appointment_time":"<APPT_TIME>", "opt_ins": [ { "use_case": "callback-notifications", "channel": "sms", "timestamp": 1718372902847 } ] }'

To indicate that a customer has opted in to receive notifications, add the opt_ins property and specify an array of opt_in objects, each with the following properties:

• use_case — Assign "callback-notifications".

• channel — Assign "sms".

• timestamp — Provide a Unix-formatted time stamp to record the time the customer opted in.

When receiving a request to a Mindful Callback Scheduler widget API endpoint that includes the opt_ins property, Mindful Callback Callback will assess whether the opt_in object for the relevant use case and channel includes a timestamp property.

Initially, the only use_case and channel supported are “callback-notifications” and “sms” respectively. For callback requests submitted via the widget API endpoint, callback notifications will only be sent by SMS for requests where either:

• The opt_in object includes a timestamp; or

• The opt_ins property is not present (for backwards compatibility)

Fixed issues

(MENG-941) An issue causing the API Endpoints modal window to show an incorrect Organization ID in a specific scenario has been resolved.

After switching Organizations in the top menu bar, the Client ID in the API Endpoints window could still reference the prior Organization. An update in this release ensures that the Client ID is associated with the correct Organization.

(MENG-951) An issue causing the Callback Status page to become unresponsive has been resolved.

When switching between Call Targets or Reporting Categories on the Callback Status page, the data could intermittently fail to display for the selected Call Target or category.

We continue to make security enhancements throughout the Government instance to ensure compliance and proactively mitigate new issues.