Product Update - v6.6.0, April 2024

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

• Send Node for MMS Channel
• Brand and Campaign Registration for US 10-Digit Long Codes is now available within Assets
• Conditional variable ‘requestIdentifier’ for quick reply response in Apple Messages for Business Start node and Rules
• Export Logs for Contact Policy module
• Watchtower Monitoring Capability
• Manage Integrations page and node UI updates for pre-built integrations built on Integrations Studio
• Ability to pass List-Unsubscribe Headers for Emails sent via AWS SES route using Webex Connect Messaging API v2
• Push, In-App Messaging, and Live Chat-related enhancements
• Call User node-related enhancements

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

Details

Added – Send Node for MMS Channel

The MMS Send node can be used to configure MMS messages with various sender IDs, and send multimedia files comprising video, pictures, audio files, and text messages over the MMS channel.

The MMS Send node allows you to send up to 9 attachments simultaneously of various file types like PDFs, video, audio, and pictures, with the only restriction being the total file size supported by in-country network operators. In the United States and Canada, the total file size supported is normally 750 kilobytes, including headers. The maximum file size permitted by various network operators in some countries can be as low as 250 kilobytes.

The MMS channel is fully supported in the United States and Canada, but the support in other countries is limited due to the operator coverage. Numeric senders are fully supported to all countries, but Alpha Sender ID support is restricted by limited or local in-country operator support.

Please reach out to your account manager if you would like to enable this for your tenant, or for any questions about network coverage. For more information, refer to the MMS Node documentation of Platform Help.

Changed – Brand and Campaign Registration for US 10-Digit Long Codes is now available within Assets

For easier access, the ‘Brand and Campaigns (10DLC)’ module has been moved from the Settings section to a more prominent spot under the Assets section in the main menu i.e., below the Numbers section. The module is renamed to 10DLC. You can continue to manage brands and campaigns from within the 10DLC module, while procurement and management of the 10DLC Numbers continue to remain available under the Numbers section. The way you create brands and campaigns hasn’t changed, but the 10DLC module now opens as an AppTray application, but with the same window. You can directly logout from Webex Connect platform using the Profile options available on the 10DLC landing page. However, clicking the Return to Services Dashboard button will help you access the Webex Connect main menu and the Services dashboard.

For updated views of the UI, refer to the Brands & Campaigns (10DLC) chapter of Platform Help.

Added – Conditional variable ‘requestIdentifier’ for quick reply response in Apple Messages for Business Start node and Rules

We’ve added the ‘abc.requestIdentifier’ variable to the list of variables available under the Conditions section for Apple Messages for Business Quick Reply response within the Start Node, and within Rules. This will allow you to selectively trigger flows and/or Rules, depending on the value of this variable.

For more information, refer to the Apple Messages for Business chapter of Platform Help.

Added – Export Logs for Contact Policy module

The Export Logs feature has been enhanced to provide users with the ability to export logs related to consent changes within Contact Policy app. This capability is only provided under the Schedule Export option of the Export Logs. Here, the users can select the concerned Consent Group(s), configure the desired schedule for exporting these logs, and send the Group-wise consent change details to the configured destination in the CSV format. Please refer to the docs after this release for more information.

This feature is available on request only for tenants that have Contact Policy app enabled. Please reach out to your account manager if you would like to enable this for your tenant. This feature isn’t available on Webex Connect Azure site at the moment.

For more information, refer to the Advanced Export Logs chapter of Platform Help.

Added – Watchtower Monitoring Capability

We are introducing a new monitoring capability named ‘Watchtower’ with this release. Watchtower enables application monitoring teams and other platform users to monitor health, usage, and/or performance metrics of various communications handled using Webex Connect.

In this current release, we are adding throughput utilization dashboards that allow you to monitor Transactions perSecond (TPS) utilization for both the Messaging API, and Event API including Inbound Webhooks. This dashboard will also provide valuable insights into counts of transactions rejected due to TPS or message volume limits. This feature is in Controlled Beta mode currently. Please reach out to your account manager to have it enabled on your tenant.

For more information, refer to the Throughput Utilization chapter in Platform Help.

Changed – Manage Integrations page and node UI updates for pre-built integrations built on Integrations Studio

We have launched a new Integrations Studio i.e., a portal for our partners to build & publish pre-built integrations for the Webex Connect platform. In Manage Integrations page, integrations built using the Studio will have details such as name of the partner who provides the integration, integration version, changelog, user guide, privacy policy & data security, and support contact details for your perusal. User guide, privacy policy, data security documentation, and integration-specific support team contact information will also be available in the node UI of the Flow Builder.

For more information, refer to the Introduction chapter in the Prebuilt Integration section of Platform Help.

Added – Ability to pass List-Unsubscribe Headers for Emails sent via AWS SES route using Webex Connect Messaging API v2

We are adding the ability to optionally pass list-unsubscribe headers when sending emails using Webex Connect Messaging API v2. This will allow you to pass the links to your own unsubscribe management portal as part of the list-unsubscribe headers instead of using Webex Connect unsubscribe management capability. The following headers can be passed:  

• listUnsubscribeUrl 
• unsubscribeEmailAddress 
• unsubscribeEmailSubject 

When the list-unsubscribe URL and/or unsubscribe mail to address are added, the Webex Connect platform will overwrite the asset setting with the values provided in the Messaging API, even for the assets for which the platform manages unsubscriptions. In such cases, the Webex Connect platform will no longer have control over the Outbound Webhook notifications for the unsubscribe events originated from the list-unsubscribe header. Therefore, businesses are expected to use these options only when they have a mechanism to handle unsubscriptions (including one-click unsubscription) on their own. 

Since it’s an email compliance requirement, the one-click unsubscribe header will be added to the outbound email, every time the list-unsubscribe URL is added in the Messaging API. Businesses are expected to handle one-click unsubscriptions, i.e., receive post back from the email clients, perform action (add user email address to unsubscribe list), and respond with appropriate success status. The feature is not yet available on the Send node.

The feature is not yet available on the Email Send node in the visual flow builder. For more information, refer to the Email section in the Send Message v2 chapter of API Reference documentation.

Changed – Push, In-App Messaging, and Live Chat-related enhancements

We are releasing an updated version of iOS SDK i.e., iOS SDK v2.19.4 with this release. It contains various technical enhancements such as updating user’s Firebase Console Messaging (FCM) token in the backend after each re-register following a previous un-registration.

For more information on the updates, refer to the JavaScript SDK and iOS SDK release note in API Reference Documentation.

Changed – Call User node-related enhancements

We've reorganized the SIP error codes, mapping them to both error edge and rejected edge for better management, ensuring that specific error codes will not trigger call retries. These response codes signify why a call either terminated or failed to complete, sorted into various scenarios like incomplete numbers, network problems, call rejection, caller disconnection, and server errors. As a result of this update, errors like incomplete or invalid customer numbers will now be directed away from the Error Edge of the call user node, ensuring they are handled appropriately without retry attempts.

Important Additional Notes

• The enforcement date for WhatsApp authentication templates that do not meet the updated guidelines introduced in May 2023, is extended from April 1, 2024, to May 31, 2024. If you are using WhatsApp Authentication Templates, please replace the old templates with the preset authentication message templates as per WhatsApp’s guidelines to avoid disruption.
• WhatsApp has started limiting the number of marketing template messages a customer can receive from all businesses in a given period of time, starting with conversations that are less likely to be read. Marketing template message that failed to deliver due to the above limitation, can be identified using “additional_info” field within delivery receipt payload sent to the configured Outbound webhook and/or Notify URL. Refer to the error/status codes for WhatsApp in our documentation here.

Changelog