Claim record · Transferring a digital conversation in Webex Contact Center
The transfer node's success outcome is named onConversationTransferred and the hold node's success outcome is named Success, so two nodes of the same family documented on the same site use different conventions for the same position.
field-pattern · verified 2026-09-15
Success Success Conversation put on hold successfully
- Vendor
- Cisco
- Product
- Webex Connect
- Subsystem
- Conversation transfer
- Deployment
- multi-tenant
- Region
- not restricted
- Release range
- current as of 2026-09-15
- Status
- field-pattern
- Confidence
- 0.90
- Verified
- 2026-09-15
Sources
- Hold conversation - WxEngage standalone — Cisco Systems, Inc. (Webex Connect documentation) · tier 2 current vendor documentation · Hold conversation node and Transfer conversation node, Node outcomes tables
Cite this claim
APA
WarmTransfer. (2026, September 15). Transferring a digital conversation in Webex Contact Center: claim wxdxfer-sibling-nodes-disagree-on-outcome-labels. WarmTransfer. https://warmtransfer.net/knowledge/claims/wxdxfer-sibling-nodes-disagree-on-outcome-labels
BibTeX
@misc{warmtransfer-claim-wxdxfer-sibling-nodes-disagree-on-outcome-labels,
title = {Transferring a digital conversation in Webex Contact Center: claim wxdxfer-sibling-nodes-disagree-on-outcome-labels},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/wxdxfer-sibling-nodes-disagree-on-outcome-labels},
note = {Claim wxdxfer-sibling-nodes-disagree-on-outcome-labels, verified 2026-09-15}
}