Product Update - v6.10.0, May 2025
Webex Connect v6.10.0 release brings multiple new capabilities to help you continue delivering seamless customer experiences. Here’s a list of the key updates and enhancements that are a part of this release:
Summary
Here’s a list of the key updates and enhancements that are a part of this release:
- Inclusion of SMS Carrier details in Downloaded Usage Report
- Link shortening feature in Messaging APIs
- Link Shortener Node
- Usage Report Enhancements
- Push, In-App Messaging, and Live Chat-related enhancements
- Email Notifications for Deletion of a Service
Release Date
The date of release will be communicated separately over an email.
Details
Changed - Inclusion of SMS Carrier details in Downloaded Usage Report
The SMS Inbound and SMS Outbound sheets in the dowloaded Usage Report, which can be exported from the Usage section of Webex Connect, have been enhanced to provide insights into the carrier that delivered the SMS traffic.
Two new columns have been added:
- carrier_id: A short carrier identifier.
- carrier_name: Full name of the carrier that delivered the SMS traffic.
Note: While these fields are being added for all tenants, Carrier details will be available only for Webex Connect tenants that are hosted in the US. Please make relevant changes in your applications if you consume data from Usage Report ‘.XLSX’ file programmatically.
Changed - Link shortening feature in Messaging APIs
We are enriching the link shortening capabilities offered by Webex Connect as part of this release. Here’s a list of enhancements that we are making:
- Link Shortening capability that is available only for SMS channel currently, will now be supported for MMS, RCS, Email, Live Chat, In-App Messaging, Facebook Messenger, and WhatsApp. The link shortening will be supported for URLs that are sent as part of the message content and may not be available for other fields within the overall message body.
- Notifications for click events for these shortened links will be sent over the Notify URLs mentioned in the Send Message API v1 and Send Message API v2.
- Further, you will be able to add up to two reporting tags along with your link shortening requests. This will allow you to view the counts of links generated and clicked at individual reporting tag level. These will be accessible under the 'Reports' section.
For full details, refer to the documentation after this feature is released.
You must complete certain prerequisite configuration steps before you can use this feature. These enhancements are being released in an Early Access mode.
Added - Link Shortener Node
In addition to the link shortening enhancements in Messaging APIs as mentioned above, we are introducing a new Link Shortener Node. This node allows you to pass a long URL and convert it into a short URL which can then be embedded in the message content when sending messages to customers on channels supported by Webex Connect Flow Builder.
- The domain you want to use for creating shortened links needs to be mapped with your Webex Connect tenant by following certain configurations which will be added to our documentation alongside this release. These configurations can be done by any Tenant Owner or Full Access Users with requisite permissions.
- In addition to creation of short links, you will be able to add up to two reporting tags along with your link shortening requests. This will allow you to view the counts of links created and clicked at individual reporting tag level. These will be accessible under the 'Reports' section.
- Further, you will have the ability to configure details such as Callback Data, Correlation ID, and Notify URLs to get notified anytime this link is clicked by a recipient.
Note:
- The existing Shortened URL capability available in SMS Send Node will continue to exist.
- This node is currently in Early Access mode, and will not be available by default. Please raise a support ticket if you want to get this node enabled for your tenant.
For full details, refer to the documentation after this feature is released.
Changed: Usage Report Enhancements
We have made a few enhancements to the Usage Reports that can be exported from the ‘Usage’ section of the platform UI. Here are the details:
Two new fields ‘basic_sent' and ‘single_sent’ have been added to the ‘RCS’ sheet of the report.
- basic_sent: Count of RCS Basic messages sent via Webex Connect. This doesn’t include the Branded Text message counts as those are reported as part of the SMS usage sheets.
- single_sent: Count of RCS Single messages sent via Webex Connect.
The date of activation for these new fields may not be same as the date of release for a few regions. We will be communicating the specific dates over email in such cases.
This apart, some of the existing fields i.e., ‘text_sent’, ‘media_sent’, ‘carousel_sent’, ‘richcard_sent’, ‘messages_read’ will be discontinued and will no longer be reported in ‘Usage’ section. These fields will continue to be displayed in the ‘Reports’ section of the platform UI.
Please make relevant changes in your applications if you consume data from Usage Report ‘.XLSX’ file programmatically.
Added – Push, In-App Messaging, and Live Chat-related enhancements
We are releasing the following SDK versions as part of this release:
- Modular Android SDK v3.0.3
- Legacy Android SDK v2.20.7 (check important additional notes)
Here’s a summary of the changes:
- We are releasing the latest versions of our Android SDKs, namely the Modular Android SDK and Legacy Android SDK, which will be compatible with Android 16.
Added - Email Notifications for Deletion of a Service
We will be sending email notifications to all active tenant owners, as well as to the individual who created the Service and the one who deleted it, whenever a Service is deleted from the platform.
Important Additional Notes
- We've decided to deprecate Instagram as a native channel on Webex Connect. The decision has been taken keeping in view various factors including client feedback on preferred channels for supporting business customer interactions. This change allows us to accelerate our roadmap for other channels and platform capabilities.
- This apart, we highly recommended you to upgrade to the latest modular SDK, since this is the last planned version upgrade for the legacy Android SDK.
- We have deprecated the ‘Record a Clip’ option in the Voice Media section. This feature previously
allowed users to call a number displayed in the Voice Media section to record a voice message.
Changelog
Update | Description |
---|---|
Changed | Inclusion of SMS Carrier details in Downloaded Usage Report |
Changed | Link shortening feature in Messaging APIs |
Added | Link Shortener Node |
Changed | Usage Report Enhancements |
Added | Push, In-App Messaging, and Live Chat-related enhancements |
Added | Email Notifications for Deletion of a Service |
Fixed | Apple Messages for Business app asset creation failure for users who are logged in via Webex SSO (Single Sign-on). |
Fixed | An issue with automated generation of Apple Messages for Business rich link for a small set of links. |
Fixed | Fixed issue while creating voice prompt using Text to Speech in Voice Media page of the Sandbox environment. |
Fixed | When an SMS router is allocated at a Group-level, any new Service created within the Group should default to using the Group-level router. However, the Service-level router was being selected instead. |
Fixed | Resolved an issue where drop-down options in the ‘Authorization' section of the 'Custom Node' for the 'SOAP API’ type were not displaying. The fix ensures that all options are now correctly visible and accessible. |
Fixed | In the 10DLC ‘Register New Campaign’ page, users were unable to insert values other than URLs in the ‘Terms and Conditions Link’ and ‘Privacy Policy Link’ fields. |
Fixed | Users were incorrectly prompted to raise a support ticket when attempting to enable 10DLC for a number in a tenant without a Brand, instead of being directed to the appropriate self-serve page for Brand creation. This has been fixed. |
Fixed | The 10DLC campaign creation page for 'Mixed Use Cases' category now correctly requires two sample messages by default, with the option to add up to five messages. For ‘Other Use Cases’ category, a fix has been applied to address an issue where the UI was incorrectly requiring two sample messages by default. It now requires only one sample message by default, while still allowing users to add up to a total of five messages if needed. |
Fixed | When the output variables of an HTTP node contain a variable that matches with the variables defined in flow session, they were being replaced with empty values instead of the actual value for that variable. |
Fixed | ‘Contact Policy' option is not being shown in the 'Applet' drop-down while inviting a user in the 'Restricted Access' role from 'Teammates’ section. |