Product Update - v6.13.0, November 2025

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

Summary

  • Enhanced DLT Compliance Management for SMS Messaging in India
  • RCS Subscribe and Unsubscribe Event Support

📘

Release Date

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

Details

Changed: Enhanced DLT Compliance Management for SMS Messaging in India

To streamline compliance with TRAI’s Distributed Ledger Technology (DLT) regulations for SMS traffic to India, we've
introduced a set of enhancements for managing DLT entity and sender ID mappings directly within the platform.

Centralized DLT Entity Management

A new ‘DLT Primary Entity IDs’ section is now available in Tenant Settings, allowing you to centrally add and manage
primary DLT Entity information at the tenant level.

Asset-Level DLT Registration

When configuring assets for SMS traffic to India, a new "Registered on the DLT portal" button allows you to mark assets
as ‘DLT registered’ and you can select the appropriate Entity ID for the asset.

Template Creation Enhancements

During template creation, you are now required to specify Sender IDs that have a corresponding DLT Template ID
registered.

For more information, refer to Short Code, Phone Number, Tenant Settings, Sender ID, and Templates - SMS articles in the v6.13.0 set of Platform Help Documentation.

📘

Note

Manual DLT template and sender registration is still required for SMS delivery in India at this time. These features are currently available only in the Mumbai region. For details or assistance, please contact your account manager or refer to the Help documentation.

Added – RCS Subscribe and Unsubscribe Event Support

Webex Connect now supports RCS Subscribe and Unsubscribe events, enabling your flows to capture and respond to customer opt-in and opt-out actions in real time. These events help your enterprise comply with user preferences and streamline consent management.

These events are available in the RCS Start Node (within Flow Builder and Rules) and are supported across Export Logs, Debug Console, Outbound Webhooks, and Data Streams. Please note that they are excluded from incoming message counts in Usage Reports. Currently, these events are supported in the US, UK, and Canada regions.

For more information, refer to the v6.13.0 set of the following:

📘

Note

When an Unsubscribe or Subscribe event is received from an end user, a separate “STOP” or “START” message may also be received as an additional incoming message. This is to allow you to transition to the new Unsubscribe and Subscribe webhook events. For more information, please refer to the Help documentation.

Important Additional Notes

Template URL Verification Policy Update

  • WhatsApp Template URL Verification – Policy Update
Effective Starting January 1, 2026, WhatsApp requires all businesses to ensure that any URL included in message templates is valid and verifiable. To comply with this change, the following updates should be noted:
    • Mandatory URL Verification for New Templates

      All newly created templates that require URL configuration should use the "Visit Website" CTA option to avoid template creation error or future rejection.
    • Migration of Existing Templates Using Header/Body Variables to pass URLs
      Templates that previously passed URLs through variables in the header or body are likely to be rejected and should be replaced with new templates configured with valid URL as part of "Visit Website" CTA.
    • Migration of Existing Templates using Visit Website CTA with invalid URL
      Existing templates configured with invalid URLs as part of "Visit Website" CTAs should be replaced with new templates configured with valid URL as part of "Visit Website" CTA.

Changelog

UpdateDescription
ChangedEnhanced DLT Compliance Management for SMS Messaging in India
AddedRCS Subscribe and Unsubscribe Event Support
FixedResolved the issue where the carrier and service provider fields were not displaying values in the transaction details section of the Debug Console.
FixedResolved an issue in the Event Scheduler UI where transactions were not reaching the intended flow if the
selected Event API belonged to a different service than the one chosen in the initial configuration.
[INC1200227]
FixedResolved the issue where the application displayed an 'Access denied' page instead of redirecting to the Login page upon session expiration.
FixedResolved an issue wherein onboarding a WhatsApp app using a WhatsApp-provided ‘555’ business number via the Embedded Signup flow resulted in an error while saving the asset.