Mindful for government August 2024 release notes

Released August 16, 2024

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 on planned maintenance and reported incidents (the status page for Government users can be found here).

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.

example of using an SMS short code as a messaging handle

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

If the new opt_in parameter is not present on an API callback request, no SMS notifications will be sent for that callback.

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 an opt_ins (object) parameter containing three additional string parameters:

  • use-case - Assign "callback-notifications".

  • channel - Assign "sms".

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

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.