Product Update - v6.6.1, May 2024

Webex Connect v6.6.1 release brings multiple new capabilities to help you continue delivering seamless customer experiences. Here’s a list of the key updates:

• Addition of new numbers to existing on-behalf-of WhatsApp Business Accounts via Webex Connect
• Support for Authorization for Contact Policy Notifications
• Push, In-App Messaging, and Live Chat-related enhancements
• Delivery Failure Notifications when Sending RCS messages (Incl. SMS Fallback) via GSMA-compliant API
• Improved Handling of RCS Messages Expiry
• Multi select capability for Export logs tool

Please refer to the details below to learn about all the changes and enhancements.

📘

Release Date

The date of release will be communicated separately over an email.

Details

Changed – Addition of new numbers to existing on-behalf-of WhatsApp Business Accounts via Webex Connect

We’ve made changes to the WhatsApp asset creation interface for addition of new numbers to existing on-behalf-of WhatsApp Business Accounts. On-behalf-of (OBO) WhatsApp Business Accounts are the accounts created and managed by Webex Connect on-behalf-of client's business. With this release, users can add new numbers to such OBO WhatsApp accounts by using the ‘Manual’ sign-up method and providing the WABA ID for their existing account. This is not applicable to WhatsApp assets that were created using Embedded Sign-Up.

Added – Support for Authorization for Contact Policy Notifications

We have added an option for authorization of notifications sent to the callback URLs registered via. Contact Policy notifications subscription API. To use this feature, you will need to first add an Authorization under Assets->Integrations section. Once done, a unique Authorization ID will be generated that’s visible on the Authorization listing page. This id will need to be sent as part of the API call to add or update a notification subscription. Please refer API documentation after the release for more information.

Added – Push, In-App Messaging, and Live Chat-related enhancement

We are releasing the following versions of the SDKs as part of this release:


• iOS SDK v2.19.5
• JavaScript SDK v1.5.8

 iOS SDK upgrade includes resolution for an infrequent issue that could cause the application to crash.

 JavaScript SDK upgrade includes a new method called publishTypingIndicator to allow sending of special typing indicator messages. Apart from this, we’ve resolved an issue that causes device registration failures upon browser refresh.

Changed – Delivery Failure Notifications when Sending RCS messages (Incl. SMS Fallback) via GSMA-compliant API

Our GSMA-compliant API for RCS Messaging now returns the failure reason object, consisting of the failure code and text description, for both RCS and SMS DLRs.

Changed – Improved Handling of RCS Messages Expiry

Expanded integration with RCS operators to improve expiry support. Messages which expire at the MaaP level will now report in Webex Connect.

Added - Multi select capability for Export logs tool

We are introducing the ability to select more than one service, channel, or asset when downloading or scheduling log exports using the Export Logs tool. This feature, initially released as early access in version 6.4.1 in November, is now available to all tenants starting with version 6.6.1. The multi-select functionality is backward compatible. However, the log file naming convention has been updated to reflect multiple files in the multi-select feature, while existing schedules will retain their original naming conventions unless edited and updated with a different configuration. Please note that this option is available only for the new export logs tool, but not for the legacy one. For more details on this feature, please refer to the official documentation.

Important Additional Notes

• Google announced that starting July 15th, no new chats can be created, and entry points will be disabled from google assets (search, maps). Also starting July 31st, all messaging will be disabled. Accordingly, the support for Google Business Messages on the platform will be taken out.
• Starting July 2024 onwards, Meta will be updating the category of an approved message template if they determine that its current category is not accurate as per the template category guidelines. This will be done on the 1st of every month and will apply to marketing and utility templates. Businesses will receive advance notice on Email from Meta before a template's category has been updated, and will also be able to see the details in WhatsApp Business Manager.

Changelog