webex contact center · stub
Transferring a digital conversation in Webex Contact Center
Verified 2026-09-15 · 12 claims · sources tier 2
Also known as Transfer conversation node, conversation transfer.
Stub. This topic has 12 verified claims and no published article. The claims below are exactly what the corpus holds today.
So far, no summary has been generated for this topic. The claims below are what the corpus currently holds.
See also
Related to
- Webex Connect digital channel flow orchestration — The transfer node lives in a Webex Connect flow
- What a transferred call leaves behind across Cisco products — Digital transfer has no consult shape and no agent target
Referenced by
- Webex Connect digital channel flow orchestration — The transfer primitive available to a digital flow
- What a transferred call leaves behind across Cisco products — The digital channel case where the voice-shaped rules do not hold
Claims
| # | Claim | Status | Confidence | Verified |
|---|---|---|---|---|
| 1 | Cisco recommends setting the node's authorization to a default authentication configured in Engage's integrations screen, because re-authenticating there updates the token for every node across every flow. Transfer conversation - WxEngage standalone · Transfer conversation node, Configuration, Node Runtime Authorization | fact | 0.90 | 2026-09-15 |
| 2 | The transfer node is addressed by a conversation identifier held in a flow variable, which is the identity a digital interaction is transferred by. Transfer conversation - WxEngage standalone · Transfer conversation node, Configuration, Conversation ID field | fact | 0.90 | 2026-09-15 |
| 3 | The digital channels are released in controlled general availability and only customers who have worked with Cisco's Solution Assurance team to plan onboarding can use them. Set up digital channels in Webex Contact Center · Set up digital channels in Webex Contact Center, About digital channels | fact | 0.90 | 2026-09-15 |
| 4 | Holding a digital conversation is a separate node from transferring one, with its own Engage API, so hold and transfer are independent operations on a conversation rather than stages of one. Hold conversation - WxEngage standalone · Hold conversation node, opening description | fact | 0.90 | 2026-09-15 |
| 5 | The transfer node is a wrapper over the Transfer conversation API from Webex Engage, so a digital transfer configured in a Webex Connect flow is executed by a different product. Transfer conversation - WxEngage standalone · Transfer conversation node, opening description | fact | 0.90 | 2026-09-15 |
| 6 | The transfer node's own configuration procedure instructs the reader to double-click the Fetch team working hours node, and it does so in both the team queue and the skill queue variants. Transfer conversation - WxEngage standalone · Transfer conversation node, Configuration, step 2 of both variants | disputed | 0.60 | 2026-09-15 |
| 7 | The Webex Contact Center article that sets up digital channels end to end does not contain the word transfer anywhere, so transferring a digital conversation is documented only in the flow platform and not in the contact centre's own setup material. Set up digital channels in Webex Contact Center · Set up digital channels in Webex Contact Center, whole article | fact | 0.90 | 2026-09-15 |
| 8 | 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. Hold conversation - WxEngage standalone · Hold conversation node and Transfer conversation node, Node outcomes tables | field-pattern | 0.90 | 2026-09-15 |
| 9 | The transfer node publishes one success outcome and six named error outcomes: transfer failed, timeout, invalid data, middleware error, invalid choice and authorization failure, with a seventh unnamed Failure category for any other runtime failure. Transfer conversation - WxEngage standalone · Transfer conversation node, Node outcomes | field-pattern | 0.90 | 2026-09-15 |
| 10 | The timeout outcome means no API response was received within the agreed time, so it does not say whether the transfer happened, and a flow taking that branch cannot know the conversation's state. Transfer conversation - WxEngage standalone · Transfer conversation node, Node outcomes, onTimeout | inference | 0.60 | 2026-09-15 |
| 11 | A digital conversation is transferred to a team queue or to a skill queue, and the transfer node offers those two targets and no option to name an agent. Transfer conversation - WxEngage standalone · Transfer conversation node, Route to a Team queue and Route to a Skill queue | field-pattern | 0.90 | 2026-09-15 |
| 12 | The node's only output variable is a request identifier generated by Webex Engage, so what the flow gets back identifies the API call and not the transferred conversation. Transfer conversation - WxEngage standalone · Transfer conversation node, Output variables | fact | 0.90 | 2026-09-15 |
Sources
tier 2 current vendor documentation
Hold conversation - WxEngage standalone
tier 2 current vendor documentation
Set up digital channels in Webex Contact Center
tier 2 current vendor documentation
Transfer conversation - WxEngage standalone
Cite this page
APA
WarmTransfer. (2026, September 15). Transferring a digital conversation in Webex Contact Center. WarmTransfer. https://warmtransfer.net/knowledge/wxcc-digital-channel-transfer
BibTeX
@misc{warmtransfer-wxcc-digital-channel-transfer,
title = {Transferring a digital conversation in Webex Contact Center},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/wxcc-digital-channel-transfer},
note = {Verified 2026-09-15}
}