# What happens to a flow when a contact is transferred to an entry point Canonical: https://warmtransfer.net/knowledge/wxcc-routing-strategy-reruns Last verified: 2026-09-15 When a contact transfers to an entry point, the source flow terminates while the receiving entry point evaluates its own configuration[^3][^9]. Routing logic at the target destination executes based on the strategy active at the moment the transfer arrives[^9][^6]. ## Entry point arrival and routing execution Cisco states that when a contact arrives at an entry point, the routing engine checks which entry point routing strategy is active at the given time and follows that configuration[^9]. In the GoTo activity, the entry point option instructs the reader to select it if flow logic should change based on the active routing strategy at the time of transfer[^6]. WarmTransfer's reading of the sources is that a transfer to an entry point runs that entry point's routing strategy afresh rather than continuing the transferring flow[^11]. Within flow navigation, the Start Flow activity is the only documented way into a flow, and no activity enters another flow part way through[^10]. ## Transfer activities and source flow termination The Blind Transfer activity is terminal, meaning the flow ends once the transfer executes and nothing of the transferring flow runs after it[^3]. On a blind transfer to an entry point or dial number, the target is presented to the receiving entry point flow as a dialled number identification service value, which is available in a flow variable that the receiving flow can evaluate[^8]. The Bridged Transfer activity is the single case where Cisco states that the call flow continues, and the destination it names is a third-party interactive voice response or automatic call distribution system rather than an entry point[^4]. ## Variable handling Variable behavior depends on whether the destination is another flow or an entry point[^5]. Going to another flow allows variables to be mapped by hand, whereas going to an entry point carries global variables only when both the name and data type match[^5]. ## See also - See also [The entry point](https://warmtransfer.net/knowledge/wxcc-entry-point-artefacts). - See also [Webex Contact Center Flow Designer architecture](https://warmtransfer.net/knowledge/webex-cc-flow-designer). - See also [Webex Contact Center queues teams and routing strategies](https://warmtransfer.net/knowledge/webex-cc-routing). ## Applicability Applies to: Cisco Webex Contact Center. Sources checked 2026-09-05. ## What remains uncertain No source states in words whether a transfer to an entry point re-runs its routing strategy, with the terms "re-evaluate", "restart", and "mid-flow" occurring 0 times across the 4 documents that describe entry points and flows[^7]. Whether an explicit Cisco sentence exists stating whether a transfer re-runs the routing strategy is not covered by the sources below. In addition, whether an entry point transfer spends the 25-transition routing budget is not covered by the sources below. Finally, whether an event flow enters a flow other than at Start Flow is not covered by the sources below. ## Sources [^1]: The one documented way a campaign call reaches a live agent from an IVR campaign is a Goto Entry Point activity into a separate flow associated with an inbound entry point. Source: [Configure Voice Outbound Campaign Modes in Webex Contact Center](https://help.webex.com/en-us/article/nqu2kub/Configure-Voice-Outbound-Campaign-Modes-in-Webex-Contact-Center), Configure Voice Outbound Campaign Modes, escalating an IVR campaign call. Checked 2026-09-15. [^2]: An event flow is an asynchronous extension of the same flow on its own canvas, with a unique start and end and no activities shared with the main flow. Source: [Build and manage flows with Flow Designer](https://help.webex.com/en-us/article/nhovcy4/Build-and-manage-flows-with-Flow-Designer), Flow Designer, event flows. Checked 2026-09-05. [^3]: The blind transfer activity is terminal and the flow ends once the transfer executes, so nothing of the transferring flow runs after it. Source: [Build and manage flows with Flow Designer](https://help.webex.com/en-us/article/nhovcy4/Build-and-manage-flows-with-Flow-Designer), Flow Designer, Blind Transfer activity. Checked 2026-09-05. [^4]: The bridged transfer activity is the one case where Cisco says the call flow continues, and the destination it names is a third-party interactive voice response or automatic call distribution system rather than an entry point. Source: [Build and manage flows with Flow Designer](https://help.webex.com/en-us/article/nhovcy4/Build-and-manage-flows-with-Flow-Designer), Flow Designer, Bridged Transfer activity. Checked 2026-09-05. [^5]: Going to another flow allows variables to be mapped by hand, where going to an entry point carries global variables only when name and data type both match. Source: [Build and manage flows with Flow Designer](https://help.webex.com/en-us/article/nhovcy4/Build-and-manage-flows-with-Flow-Designer), Flow Designer, GoTo activity, Go to Flow against Go to Entry Point. Checked 2026-09-05. [^6]: The GoTo activity's entry point option tells the reader to choose it if the flow logic should change based on the active routing strategy at the time of transfer. Source: [Build and manage flows with Flow Designer](https://help.webex.com/en-us/article/nhovcy4/Build-and-manage-flows-with-Flow-Designer), Flow Designer, GoTo activity, Flow Destination Settings, Go to Entry Point. Checked 2026-09-05. [^7]: No source states in words whether a transfer to an entry point re-runs its routing strategy; re-evaluate, restart and mid-flow occur 0 times across the 4 documents that describe entry points and flows. Source: [Set up routing strategies](https://help.webex.com/en-us/article/nfrs2adb/Set-up-routing-strategies), Set up routing strategies, Flow Designer, the architecture article and Set up a channel, counted against the rendered article. Checked 2026-09-05. [^8]: On a blind transfer to an entry point or dial number, the target is presented to the receiving entry point flow as a dialled number identification service value, available in a flow variable the receiving flow can evaluate. Source: [Build and manage flows with Flow Designer](https://help.webex.com/en-us/article/nhovcy4/Build-and-manage-flows-with-Flow-Designer), Flow Designer, blind transfer to an entry point or dial number. Checked 2026-09-05. [^9]: Cisco states that when a contact arrives at an entry point the routing engine checks which entry point routing strategy is active at the given time and follows that configuration. Source: [Build and manage flows with Flow Designer](https://help.webex.com/en-us/article/nhovcy4/Build-and-manage-flows-with-Flow-Designer), Flow Designer, Entry point routing strategies. Checked 2026-09-05. [^10]: The Start Flow activity is the only documented way into a flow, and no activity enters another flow part way through. Source: [Build and manage flows with Flow Designer](https://help.webex.com/en-us/article/nhovcy4/Build-and-manage-flows-with-Flow-Designer), Flow Designer, activity catalogue and Start Flow. Checked 2026-09-05. [^11]: A transfer to an entry point runs that entry point's routing strategy afresh rather than continuing the transferring flow (inferred). Source: [Build and manage flows with Flow Designer](https://help.webex.com/en-us/article/nhovcy4/Build-and-manage-flows-with-Flow-Designer), Flow Designer, Entry point routing strategies and the GoTo activity and the blind transfer DNIS passage. Checked 2026-09-05.