Webex Connect v6.11.0 release brings multiple new capabilities to help you continue delivering seamless customer experiences.

Summary

Here’s a list of the key updates and enhancements that are a part of this release:

• Authorization for Notify/Callback URLs
• Simplified onboarding and configuration for Branded Text through Webex Connect
• Identifiers for Branded Text in Reports, Logs, and Integrations
• Conditional Triggering for incoming RCS messages/events in Flow Start Node
• ‘Free To End User’ classification information is now available for Inbound SMS traffic in Usage Report
• Enhanced Answering machine detection in Voice APIs
• Upload original date of consent capture when importing data into Contact Policy
• Improved search experience on Group Listing page in Contact Policy
• New Error Codes for WhatsApp Message Delivery Failures
• Reseller info section in the 10DLC Brand Creation form
• Push, In-App Messaging, and Live Chat-related enhancements
• ‘Device Attributes for Mobile Apps’ Feature

📘

Release Date

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

Details

Added - Authorization for Notify/Callback URLs

We’ve enhanced our platform to enable authorization for notifications/post-backs sent to the NotifyURLs or Callback
URLs configured as part of Send Message API v1 and v2, channel specific Messaging APIs, Send nodes for various
channels, and Rules-Actions. You will need to configure the authorization credentials within 'Integrations →
Authorizations' section, and then pass the relevant Authorization ID when using this feature. If an incorrect
Authorization ID is supplied or the authorization fails, notifications will not be sent to the configured URL, however the outbound messaging request will still be processed.

Refer to the Rules chapter in v6.11.0 Platform documentation for more information.

Changed - Simplified onboarding and configuration for Branded Text through Webex Connect

Branded Text (SMS upgrade to RCS) can now be enabled for Sender IDs, Shortcodes, and Phone Numbers directly from the ‘Numbers’ section in Webex Connect.

Note:

The Branded Text feature isn’t available for use by default and needs to be enabled at a tenant level based on client
request. Please get in touch with your account manager to enable Branded Text for your tenant.
Once Branded Text feature is enabled for your tenant, you can enable it for a Number and map the corresponding RCS app to send upgraded messages.
You can also configure how long the system should wait to deliver messages via RCS before automatically switching to SMS using the new ‘Branded Text to SMS Fallback Wait Time’ option in Service Settings. The default fallback wait time is 60 seconds, and the maximum is 3600 seconds (1 hour). If you have configured the message expiry value, the upgrade to RCS will only be attempted if at least 20 seconds remain
before message expiry; otherwise, the message will be sent as SMS.

Refer to the RCS Branded Text chapter of v6.11.0 Platform Documentation for more information on this feature.

Added - Identifiers for Branded Text in Reports, Logs, and Integrations

As part of this enhancement, the following fields have been introduced for outbound and inbound Branded Text
messages:

• Attempted Upgrade to: Indicates whether an outbound SMS request was attempted to be upgraded to Branded
  Text. This field displays ‘Branded Text’ if the outbound request is sent from a number with Branded Text
  enabled. Displays ‘NA’ if Branded Text is not enabled.
• Upgrade Result: Shows the outcome of the upgrade attempt for outbound requests. If the request was
  successfully delivered as Branded Text, displays ‘Upgraded to RCS basic’. If the upgrade failed and the request
  was sent as SMS, displays ‘Fallback to SMS’. If Branded Text is not enabled, displays ‘NA’.
• Message Source: Differentiates inbound text messages received via the RCS app from those received via SMS.
  Displays ‘Branded Text’ if the message was received from an RCS app/asset mapped to a number; otherwise,
  displays ‘SMS’ if the message was received via regular SMS channels.

These new fields are now available across the Debug Console, Export Logs (downloadable from UI), Scheduled Logs, Data Streams, Outbound Webhooks, and Delivery Receipts.

Note:

In Scheduled Logs, these fields must be manually selected from the new fields dropdown and will not be added
automatically to existing reports.

Refer to the Usage Report , Debug Console, and New Export Logs chapters of v6.11.0 Platform Documentation for more information on this feature.

Added - Conditional Triggering for incoming RCS messages / events in Flow Start Node

We have added a new option, "Trigger only if there are no live sessions", to the Start Node to conditionally trigger a
flow on receiving an incoming message or event (on a given RCS asset) in case one or more live sessions are already
waiting to receive a message/event from the same MSISDN (i.e. consumer’s number). This allows you to stop triggering a new flow when an existing flow is waiting to receive a message from a consumer on a given RCS asset.

When this feature is used:

1. for tenants which have Branded Text disabled -
   1. The system checks for any in-progress RCS flows and prioritizes them before initiating a new RCS flow
2. for tenants which have Branded Text enabled -
   1. The system checks for in-progress Branded Text-enabled SMS flows as well as any in-progress RCS flows, and prioritizes their execution before initiating a new RCS flow.
   2. If an incoming text message is received via an RCS asset mapped to a Branded Text-enabled number, the
      system duplicates this message. This duplicated message is converted to an SMS incoming message and
      marked as ‘Branded Text’ in the Message Source field. The duplicated message will only execute Branded Text-enabled SMS flows that are already waiting at a Receive Node. No new SMS flows will be initiated,
      ensuring that only the intended flows are triggered.

Note:
This feature is currently in Early Access. Introduction of this feature in the platform doesn’t change the functioning of
your previously configured flows. However, if you configure some new flows and use this feature, it may impact the
functioning of existing RCS and Branded Text flows based on your configurations. Please refer to the documentation
after this release for information on best practices for using the feature.

Refer to the Start Node chapter of v6.11.0 Platform Documentation for more information on this feature.

Changed – ‘Free To End User’ classification information is now available for Inbound SMS traffic in Usage Report

The ‘SMS Inbound’ sheet in the Usage Report, exportable from the ‘Usage’ section of Webex Connect, has been
enhanced to provide information for the rate type for inbound traffic associated with a given number.
A new column 'rate_type' has been added for this purpose. It will have the following values:
Standard: The is the default value which applies in most cases.
Free To End User: This refers to the numbers that allow end users to send SMS messages free of charge. It is available only in specific cases and support varies by country and carrier.

Note:
For tenants with ‘Free To End User’ numbers, this information will start appearing in the Usage Report, post this release.

Refer to the Usage Report chapter of v6.11.0 Platform Documentation for more information on this feature.

Changed - Enhanced Answering machine detection in Voice APIs

We’ve enhanced our Answering Machine Detection (AMD) in Voice APIs with beep detection. This improves the
detection of the voicemail beep in real time, and triggers playback of pre-recorded or Text-to-Speech (TTS) messages, ensuring the entire message is delivered without being cut off.

Changed - Upload original date of consent capture when importing data into Contact Policy

In the Contact Policy app, when uploading consent records to a Consent Group, it is now mandatory to include the datetimestamp of capturing consent information from the customer. A new column has been added to capture the date for each record, formatted in UTC ISO instant format, e.g., '2011-12-03T10:15:30Z'.
Consent data files downloaded from the Upload History now also include this consent date and time for each record.

Note:
All existing records uploaded prior to this release will display the upload date as their consent date and if a user's
consent status changes after upload, the consent date will automatically update to reflect the most recent consent
action.

Refer to Manage Consent Groups and Consent Groups chapter of v6.11.0 Platform Documentation for more information on this feature.

Added – Improved search experience on Group Listing page in Contact Policy

On the Group Listing page in Contact Policy, the ‘Search’ field has been enhanced to include a dropdown option. Users can browse and select from all available groups before typing, in addition to using the existing search. The ‘Search’ field also supports Group ID based lookup to provide flexible search options.

Refer to Manage Consent Groups chapter of v6.11.0 Platform Documentation for more information on this feature.

Added - New Error Codes for WhatsApp Message Delivery Failures

We have introduced new error codes for improving the visibility into the reasons behind the WhatsApp message
delivery failures. The following error codes are being added as part of this release and will be available as part of
Outbound Webhooks, Notify URLs, Data Streams, Export logs, Debug logs, and Reports.

Refer to Channel-specific Status Codes chapter of v6.11.0 Platform Documentation for more information on this feature.

Added - Reseller info section in the 10DLC Brand Creation form

To support compliance with TCR's requirements for 10DLC campaigns, we have now added a new Reseller Info section to the 10DLC Brand Creation form. This new section now allows you to specify reseller details during the brand creation.
If you are a 10DLC reseller creating brands on behalf of customers, you can now mark your tenant as a reseller by
selecting ‘Yes’ in the 10DLC reseller section and provide the required reseller information—such as Reseller name,
Reseller email, and Reseller phone number—when creating your first brand after this change goes live. If you are not a 10DLC reseller you can mark your tenant as Not a reseller by selecting ‘No’. This information will be automatically
applied to all subsequent brands and campaigns under your tenant, streamlining campaign registration and ensuring
regulatory alignment.

Note:
If your tenant is already mapped to a reseller, these details will appear pre-filled in your 10DLC Brand creation form.
The existing 10DLC Brands and Campaigns under your tenant will continue to work and don't require any action from
your side but this may change at a future date. The reseller information cannot be changed after a reseller ID is assigned to your tenant. Please contact customer support for assistance with updates to reseller information section.

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

We are releasing JavaScript SDK v1.7.0 with the following enhancements:

• We have introduced a new message type, threadAlert, for Live Chat and In-App Messaging channels. This message can be used to notify customers reaching out over Live Chat / In-App Messaging channels about key chat events such as chat getting transferred to new agent.
• JavaScript SDK now supports multiple tabs within the same browser for Live Chat Messaging. This enhancement resolves the earlier limitation that led to repeated disconnections and reconnections when users interacted with the Live Chat Messaging across different tabs.
• We have introduced rate limits in the JavaScript SDKs to regulate typing indicator events (start or stop), ensuring that only one event is sent every 5 seconds. If any typing event is triggered within this interval, it will be suppressed by the SDK. This update reduces unnecessary event traffic and potential misuse.
• We have made several technical enhancements. For details on the SDK updates, please refer to the SDK release notes in our documentation.

Note:
The Live Chat related features will be released on WxCC in a later release.
This apart we have made the following platform-side enhancements to the Live Chat/In-App Messaging channel :

Support for Typing Indicators:

We have added 'Typing Indicator' as a new event in Start Node, Rules, Outbound Webhook, and Data Streams for Live Chat/In-App Messaging channel.
Additionally, we’ve included the ‘inappmessaging.type’ variable in the conditions section for Live Chat/In-App Messaging within the Start Node and Rules.
We have added support for sending typing indicators in the Webex Connect Messaging API for Live Chat and In-App Messaging.

Note:
Debug logs for typing indicators are not available, and message count for this message type won't be included in Usage Reports. Typing indicators are not present in the Send Node or Receive Node.

Support for Thread Alerts:

We’ve added ‘Thread Alerts’ as a new message type in Messaging API v1. This is also available as an event in Outbound Webhooks, and Data Streams.
In the Usage Report, Thread Alert Messages will be counted as part of messages_sent.

Refer to In-App Messaging chapter of v6.11.0 Platform Documentation for more information on this feature.

Deprecated - ‘Device Attributes for Mobile Apps’ Feature

As previously outlined in our documentation, the Legacy SDKs (v2.x.x) for Android and iOS were deprecated on 20th August, 2025. With the support for legacy SDKs coming to an end, the ‘Device Attributes for Mobile Apps’ feature will no longer be supported for the Push, Live Chat, and In-App Messaging channels on Webex Connect. No further action is needed at your end if you have not been using these features.
Refer to the SDK Documentation for more information on this feature.

Important Additional Notes

• As of 20th August 2025, the Legacy SDKs (v2.x.x) for Android and iOS are officially deprecated and will no longer receive support or updates. We recommend upgrading to the latest Modular SDKs (Android and iOS) immediately to ensure uninterrupted access to enhancements, compatibility, and ongoing support.
• Starting November 1, 2025, all new apps and updates submitted to Google Play that target Android 15+ devices must support 16 KB page sizes on 64-bit devices. Our Legacy SDK uses SQL Cipher 4.5.4, which does not support 16 KB page sizes. We recommend upgrading to the Modular Android SDK, since it uses SQL Cipher 4.6.1, which supports 16 KB page sizes. For more information, refer to these links: Support 16 KB page sizes, Android SqlChiper 4.6.1 for 16kb devices support.​
• Starting Oct 1, 2025, WhatsApp will migrate WhatsApp Business Accounts (WABAs) onboarded through manual
  onboarding to the Shared Access model. This change transfers WABA ownership to your business, allowing
  direct communication from Meta and access to WhatsApp Manager for insights and analytics. Migration
  requests will be sent to your Meta Business Suite and will auto-approve after 30 days if no action is taken. No
  downtime or service impact is expected during this process.

Changelog