Maintain Service for Your Bring Your Own Channel Integration by Migrating Settings Fields
To improve the scalability of Bring Your Own Channel messaging services, we implemented changes to event-driven settings fields in the ConversationChannelDefinition and CustomMsgChannel objects. New fields are available in Winter ’26 (API version 65.0), and old fields are removed in Spring ’26 (API version 66.0). These are breaking changes.
Where: This change applies to Bring Your Own Channel for Messaging and Bring Your Own Channel for CCaaS. View required editions.
Who: These changes impact partners who create messaging provider integrations for Bring Your Own Channel for Messaging or Bring Your Own Channel for CCaaS and customers who have self-implemented Bring Your Own Channel for Messaging. These changes also impact customers using partner-provided managed packages with removed fields. Customers must update their managed package to one that contains supported fields by Spring ’26.
How: Learn more about the removed event-driven settings fields and assess whether your implementation requires updates to migrate to their replacements. Make required changes by Spring ’26, when the fields will be removed.
- For ConversationChannelDefinition, deprecated fields are
IsInboundReceiptsEnabled, IsRoutingWorkResultEnabled,
and IsTypingIndicatorDisabled.
- Use EventCapabilitiesIsInboundAcknwOptionExposed instead of IsInboundReceiptsEnabled.
- Use EventCapabilitiesIsRoutingWorkResultSupported instead of IsRoutingWorkResultEnabled.
- Use EventCapabilitiesIsTypingIndicatorOptionHidden instead of IsTypingIndicatorDisabled.
- For CustomMsgChannel, deprecated fields are HasInboundReceipts and
HasTypingIndicator.
- Use EventCapabilitiesIsInboundAcknowledgementEnabled instead of HasInboundReceipts.
- Use EventCapabilitiesIsTypingIndicatorDisabled instead of HasTypingIndicator.
If you don’t make required updates by Spring ’26 or if customers use a managed package version with removed fields starting in Spring ’26, your implementation will break.
See Also
- Object Reference for the Salesforce Platform: ConversationChannelDefinition
- Salesforce Metadata API Developer Guide: ConversationChannelDefinition
- Salesforce Tooling API Guide: ConversationChannelDefinition
- Object Reference for the Salesforce Platform: CustomMsgChannel
- Salesforce Tooling API Guide: CustomMsgChannel