# Managing flow versions and labels and promotion in Webex Contact Center Systems: Webex Contact Center For Contact center administrators and flow developers who publish Flow Designer voice flows in Control Hub and own the entry point bindings. Canonical: https://warmtransfer.net/guides/wxcc-flow-version-label-setup Last verified: 2026-10-01 Flow Designer has no version control feature: the flow version number counts how many times a flow has been published, and a version label such as Live, Test or Dev can be associated with each new version when it is published[^47][^34]. In this guide, test entry points use pre-production labels and production entry points use Live, because an entry point can use a labelled version instead of the default Latest version[^28]. ## Before you start Prerequisites: - You need Edit access on the flow and channel resource types, and Edit also allows creating new resources[^1]. - Flows are created and managed in Control Hub under Contact Center > Customer Experience > Flows[^48]. - Entry points are created as channels in Control Hub under Services > Contact Center > Customer experience > Channels[^49]. - On 2026-04-27 Cisco announced a modernised Flow Designer canvas with a refreshed user experience, activity groupings and better search, so screens in older material may differ from yours[^9]. - From 2026-04-24 the NewPhoneContact start activity is renamed NewContact, as part of an omnichannel start node[^31]. - These steps cover flows built in Flow Designer; digital-channel flows are built in Webex Connect rather than in Flow Designer[^50]. - In Webex Connect, flow edits go into a working draft that does not affect the live flow, and a new higher version number is created only when the flow is made live[^14]. How labels behave: - Latest is the default version label and cannot be removed from a flow version during publishing[^30]. - When version labels were introduced, flows that already existed were marked with the Live version label[^17]. - Cisco describes the Dev label for development, Test for staging validation and Live for production[^51]. - Cisco positions flow version labels as enabling a pipeline-driven promotion process from development to production, including blue-green deployments of flows[^52]. Inventory to gather:[^19][^11] - Each production flow with its owner, last edited date and version number, all of which the Flow Designer properties pane shows[^19]. - Each channel's Routing flow and Version label from its entry point settings[^10][^11]. - The user profiles of everyone who can publish flows or edit channels, since access is set per resource type as No Access, View or Edit[^1]. See also [Setting up Webex Contact Center entry points and queues](https://warmtransfer.net/knowledge/wxcc-entry-point-queue-setup). See also [Building reusable subflows in Webex Contact Center Flow Designer](https://warmtransfer.net/knowledge/wxcc-subflow-setup). ## What changes by situation - How many version labels does your team use for voice flows? Two labels: Latest for testing, Live for production; Full pipeline: Dev, then Test, then Live, with Latest always present. - Who may publish a flow with the Live label? Any flow developer who publishes flows; A named approver only. - Does the main flow call one or more subflows? No subflows; Yes, the main flow uses subflows. - Do flows also move between tenants (organizations)? No, all environments live in one tenant; Yes, flows are built in one tenant and moved to another. ## Step 1: Inventory current flows, versions and entry point bindings ### Do - Open the flows list under Contact Center > Customer Experience > Flows[^48]. - For each production flow, record the owner, last edited date and version number from the properties pane[^19]. - For each channel, record the flow chosen in the Routing flow drop-down and the value in the Version label field of its entry point settings[^10][^11]. - Expect flows that existed before version labels were introduced to carry the Live label[^17]. ### Verify Suggested check: confirm that every production entry point appears in your inventory with a flow name and a label value recorded against it. ## Step 2: Set administrator access to match the Live owner **Any flow developer who publishes flows** ### Do - Give flow developers Edit on the flow and channel resource types, which lets them view, edit and create those resources[^1]. - Use a resource collection in each developer's user profile to limit which queues the developer can reference, because a user limited to two queues can build flows only with those queues[^36]. - Record in your runbook that any flow developer may perform the final stage, which Cisco's blog describes as promoting a flow to production by assigning the Live version label[^6]. ### Verify Suggested check: sign in as a developer and confirm that the expected flows and queues are visible and no others. ### Rollback Suggested rollback: reassign the user profiles recorded in your inventory before this step. **A named approver only** ### Do - Give the named approver Edit on the flow and channel resource types[^1]. - Give developers View rather than Edit on the channel resource type[^1]. - Do not plan to hide production channels entirely, because a resource collection cannot be set to None for Queues, Teams, Sites or Channels[^12]. - Reserve the final stage, which Cisco's blog describes as promoting a flow to production by assigning the Live version label, for the approver[^6]. ### Verify Suggested check: sign in as a developer and confirm that a change to a production channel's entry point settings cannot be saved. ### Rollback Suggested rollback: reassign the user profiles recorded in your inventory before this step. ## Step 3: Create test entry points bound to pre-production labels **Two labels: Latest for testing, Live for production** ### Do - Create one test channel under Services > Contact Center > Customer experience > Channels by clicking Create[^49]. - For a voice entry point, choose the Inbound Telephony channel type[^53]. - Select the dial numbers callers will reach in the channel's Support Number section[^54]. - In the Entry Point settings section, set Routing flow to the production flow and Version label to Latest, then click Save[^25][^11]. - Cisco's lab uses the same binding, setting Version label to Latest on the channel after publishing with the Latest label[^55]. ### Verify Suggested check: place a test call to the test entry point and confirm that the flow answers it. ### Rollback - A channel in an active state cannot be deleted; it must be deactivated first[^56]. - Suggested rollback: deactivate the test channel, then delete it. **Full pipeline: Dev, then Test, then Live, with Latest always present** ### Do - Create two test channels under Services > Contact Center > Customer experience > Channels by clicking Create[^49]. - For voice entry points, choose the Inbound Telephony channel type[^53]. - Select the dial numbers callers will reach in each channel's Support Number section[^54]. - In the Entry Point settings section of the first channel, set Routing flow to the flow and Version label to Dev, then click Save[^25][^4]. - Bind the second channel the same way with Version label set to Test, then click Save[^25][^11]. - We infer that mapping a Dev or Test label to a separate test entry point before moving the production entry point is the safer route, although Cisco does not prescribe this setup[^57]. ### Verify Suggested check: place a test call to each test entry point and confirm that the flow answers both. ### Rollback - A channel in an active state cannot be deleted; it must be deactivated first[^56]. - Suggested rollback: deactivate both test channels, then delete them. ## Step 4: Bind production entry points to Live ### Do - In each production channel's Entry Point settings section, set Version label to Live and click Save[^11][^25]. - Cisco's blog says the version label chosen at the entry point applies to every contact arriving on that entry point[^5]. - Latest cannot be removed from a flow version during publishing, while an entry point bound to a label uses that labelled version instead of the default Latest[^30][^28]. ### Verify Suggested check: confirm that each production entry point now shows Live, and place one call per production entry point to confirm that behaviour is unchanged. ### Rollback Suggested rollback: set each Version label back to the value recorded in Step 1 and save. ## Step 5: Build a change and publish it to the first pre-production label **Two labels: Latest for testing, Live for production + No subflows** ### Do - Edit the flow; Flow Designer autosaves flows to avoid data loss, and autosave can be enabled or disabled[^3]. - An unpublished draft can be saved and resumed later[^40]. - Undo and redo cover the last 10 canvas actions[^58]. - Turn on the Validation toggle in the bottom right of the Flow Designer window and fix every error, because Publish stays disabled while validation is off and until all flow errors are resolved[^26][^59]. - Click Publish Flow and make sure only Latest is selected in the Add Version Label(s) list[^24]. ### Verify - The properties pane shows the flow version number, which counts how many times the flow has been published[^19][^47]. - Suggested check: confirm that the version number went up by one, that the test entry point runs the change, and that production still behaves as before. ### Rollback - Flow Designer lets a flow developer revert a flow to a previously published version[^38]. - Suggested rollback: revert to the previous version and publish it again with only the testing label, as in Step 9. **Two labels: Latest for testing, Live for production + Yes, the main flow uses subflows** ### Do - Edit the flow; Flow Designer autosaves flows to avoid data loss, and autosave can be enabled or disabled[^3]. - An unpublished draft can be saved and resumed later[^40]. - The Subflow activity passes inputs into the subflow and returns outputs to the main flow, so check every input mapping you change[^60]. - Before saving a subflow change, check its Propagate changes to all flows setting, because that setting cascades a subflow change to all parent flows that consume it[^61]. - Turn on the Validation toggle in the bottom right of the Flow Designer window and fix every error, because Publish stays disabled while validation is off and until all flow errors are resolved[^26][^59]. - Click Publish Flow and make sure only Latest is selected in the Add Version Label(s) list[^24]. ### Verify - The properties pane shows the flow version number, which counts how many times the flow has been published[^19][^47]. - Suggested check: confirm that the test entry point exercises the new subflow behaviour, and that no other main flow calling the subflow changed unexpectedly. ### Rollback - Flow Designer lets a flow developer revert a flow to a previously published version[^38]. - Suggested rollback: revert the subflow and the main flow to their previous versions and publish both again with only the testing label, as in Step 9. **Full pipeline: Dev, then Test, then Live, with Latest always present + No subflows** ### Do - Edit the flow; Flow Designer autosaves flows to avoid data loss, and autosave can be enabled or disabled[^3]. - An unpublished draft can be saved and resumed later[^40]. - Undo and redo cover the last 10 canvas actions[^58]. - Turn on the Validation toggle in the bottom right of the Flow Designer window and fix every error, because Publish stays disabled while validation is off and until all flow errors are resolved[^26][^59]. - Click Publish Flow and add Dev in the Add Version Label(s) list, alongside Latest, which cannot be removed[^24][^30]. - Cisco's blog describes publishing new work with the Dev label and attaching that Dev version to a test entry point so production calls are not affected[^4]. ### Verify - The properties pane shows the flow version number, which counts how many times the flow has been published[^19][^47]. - Suggested check: confirm that the Dev test entry point runs the change while the Test and production entry points do not. ### Rollback - Flow Designer lets a flow developer revert a flow to a previously published version[^38]. - Suggested rollback: revert to the previous version and publish it again with the development label, as in Step 9. **Full pipeline: Dev, then Test, then Live, with Latest always present + Yes, the main flow uses subflows** ### Do - Edit the flow; Flow Designer autosaves flows to avoid data loss, and autosave can be enabled or disabled[^3]. - An unpublished draft can be saved and resumed later[^40]. - The Subflow activity passes inputs into the subflow and returns outputs to the main flow, so check every input mapping you change[^60]. - Before saving a subflow change, check its Propagate changes to all flows setting, because that setting cascades a subflow change to all parent flows that consume it[^61]. - Turn on the Validation toggle in the bottom right of the Flow Designer window and fix every error, because Publish stays disabled while validation is off and until all flow errors are resolved[^26][^59]. - Click Publish Flow and add Dev in the Add Version Label(s) list, alongside Latest, which cannot be removed[^24][^30]. - Cisco's blog describes publishing new work with the Dev label and attaching that Dev version to a test entry point so production calls are not affected[^4]. ### Verify - The properties pane shows the flow version number, which counts how many times the flow has been published[^19][^47]. - Suggested check: confirm that the Dev test entry point exercises the new subflow behaviour, and that the Test and production entry points do not. ### Rollback - Flow Designer lets a flow developer revert a flow to a previously published version[^38]. - Suggested rollback: revert the subflow and the main flow to their previous versions and publish both again with the development label, as in Step 9. ## Step 6: Test and stage the change **Two labels: Latest for testing, Live for production** ### Do - Run the test plan against the test entry point bound to Latest, using the check Cisco's lab uses: sign an agent in to the Webex Contact Center Desktop, set the agent Available, call the support number, and check that the welcome prompt plays and the call is offered to the agent[^62]. ### Verify Suggested check: confirm that every case in the test plan passed and that the plan is signed off before Step 7. **Full pipeline: Dev, then Test, then Live, with Latest always present** ### Do - Publish the tested flow again with the Test version label associated, which is the stage Cisco's blog describes as promoting a tested flow to the Test (staging) environment[^8][^34]. - Run the test plan against the Test entry point, using the check Cisco's lab uses: sign an agent in to the Webex Contact Center Desktop, set the agent Available, call the support number, and check that the welcome prompt plays and the call is offered to the agent[^62]. ### Verify Suggested check: confirm that the Test entry point now runs the change, that every case in the test plan passed, and that the plan is signed off before Step 7. ### Rollback Suggested rollback: revert to the earlier version and publish it again with the staging label, as in Step 9. ## Step 7: Promote to Live **Any flow developer who publishes flows** ### Do - The developer publishes the signed-off flow and associates the Live version label with the new version[^34][^6]. - Latest stays on that version as well, because it cannot be removed during publishing[^30]. - Record the version number shown in the properties pane in the change ticket[^19]. ### Verify Suggested check: confirm that the change ticket names the flow, the new version number and the developer who published it, then continue with Step 8. ### Rollback Suggested rollback: carry out Step 9. **A named approver only** ### Do - The developer hands the approver the flow name and the version number shown in the properties pane[^19]. - The approver publishes the flow and associates the Live version label with the new version[^34][^6]. - Latest stays on that version as well, because it cannot be removed during publishing[^30]. ### Verify Suggested check: confirm that the publish was made from the approver's account and that the change ticket records the new version number, then continue with Step 8. ### Rollback Suggested rollback: the approver carries out Step 9. ## Step 8: Verify production ### Do - Cisco's blog says the version label chosen at the entry point applies to every contact arriving on that entry point[^5]. - For each production entry point, sign an agent in to the Webex Contact Center Desktop, set the agent Available, call the support number, and check that the welcome prompt plays and the call is offered to the agent[^62]. ### Verify Suggested check: confirm that the new behaviour is heard on every production entry point without any entry point having been edited. ### Rollback Suggested rollback: carry out Step 9. ## Step 9: Roll back a bad release ### Do - Cisco's blog presents flow versioning as enabling blue-green deployments with rollback to previous versions without downtime[^7]. - Open the flow and revert it to the last known-good published version[^38]. - Turn on validation and fix any errors, because a flow must be validated and its errors fixed before it can be published[^44]. - Publish it and associate the Live version label with the new version[^34]. ### Verify - The properties pane shows the version number, which counts publishes, so the rolled-back release carries a new number rather than the old one[^19][^47]. - Suggested check: place a call to each production entry point and confirm that the previous behaviour is back. ### Rollback Suggested rollback: revert to the newer version, validate it, and publish it again with the production label. ## Step 10: Move flows between tenants **No, all environments live in one tenant** ### Do - Keep development, test and production in the one tenant, where a version label mapped to an entry point lets new flow versions be developed and tested without affecting production calls[^63]. ### Verify Suggested check: confirm that every test and production entry point in your inventory belongs to the same tenant. **Yes, flows are built in one tenant and moved to another** ### Do - Use the Export a flow procedure in the source tenant and the Import a flow procedure in the target tenant, both of which the Flow Designer help article documents separately[^43]. - For larger moves, the Flow V2 APIs on the Webex Contact Center Developer Portal let teams search, validate, publish, export, lock and unlock flows, subflows and functions[^21][^18]. - API integrations use scopes such as cjp:config and cjp:config_read[^64]. - A 2024 Cisco developer blog says integration access tokens expire after 14 days and refresh tokens after 90 days, and that refreshing the access token restarts the refresh token's 90-day window[^65]. - In the target tenant, validate the imported flow and fix its errors before publishing it[^44]. - Associate the label for that tenant's stage when publishing, then set the target channels' Version label the same way as for the test and production entry points[^34][^11]. ### Verify Suggested check: confirm that the imported flow validates without errors in the target tenant and that a test call on the target entry point runs it. ### Rollback Suggested rollback: set the target entry point back to its previous label, then delete the imported flow if it did not exist before. ## Applicability Applies to: Cisco Webex Contact Center, Cisco Webex Connect, and Cisco Webex Contact Center APIs. Deployments: multi-tenant. Sources checked 2026-10-01. - The Flow V2 APIs and public Flow schema date from 2026-07-29[^21]. - The Validation toggle position, the Add Version Label(s) list and the channel Save procedure come from Cisco's 2026 lab tenant[^26][^24][^25]. - The API scope blog's example endpoint is on the US1 host api.wxcc-us1.cisco.com[^64]. - Webex Contact Center is deployed in Amazon Web Services[^66]. ## What remains uncertain - Whether a version label can sit on more than 1 version at a time, and whether publishing a new version with Live removes Live from the older version, is not covered by the sources below. - Whether an existing published version can be given an additional label without publishing again is not covered by the sources below. - Whether labels other than Latest, Live, Test and Dev can be created is not covered by the sources below. - When a changed Version label or a newly labelled version takes effect, and what happens to contacts already in a flow at that moment, is not covered by the sources below. - Whether a subflow carries its own version labels, and whether a main flow must be published again to pick up a subflow change when Propagate changes to all flows is off, is not covered by the sources below. - Whether access can be scoped so that only some administrators may publish with the Live label is not covered by the sources below. - Which referenced resources, such as queues, audio files or business hours, an imported flow keeps or loses in another tenant is not covered by the sources below. - Whether the flow APIs named in the claims include an import operation is not covered by the sources below. ## Sources [^1]: Webex Contact Center access settings give each resource type one of three levels: No Access, View, or Edit (which also allows creating new resources). Source: [Manage access in Webex Contact Center](https://help.webex.com/en-us/article/n524f2m), user profile access levels. Checked 2026-10-01. [^2]: Cisco positions the flow list, export, import and publish APIs for moving flows and subflows between organizations through deployment and migration scripts. Source: [What's new for administrators in Webex Contact Center](https://help.webex.com/en-us/article/nv7abhz/What's-new-for-administrators-in-Webex-Contact-Center), entry titled with Flow List and Flow Publish APIs (date heading not confirmed). Checked 2026-10-01. [^3]: Flow Designer automatically saves flows to avoid data loss, and autosave can be enabled or disabled. Source: [Build and manage flows with Flow Designer](https://help.webex.com/en-us/article/nhovcy4/Build-and-manage-flows-with-Flow-Designer), section 'Enable or disable autosave'. Checked 2026-10-01. [^4]: Cisco's Flow Designer blog describes publishing new work with the Dev label and attaching that Dev version to a test entry point so production calls are not affected. Source: [Rapidly Adapt Your CX Workflows With Webex Contact Center Flow Designer](https://developer.webex.com/blog/rapidly-adapt-your-cx-workflows-with-webex-contact-center-flow-designer), section 'Flow Versioning', item 'Dev (Development)'. Checked 2026-10-01. [^5]: The blog says the version label in use is chosen at the entry point and applies to every contact arriving on that entry point. Source: [Rapidly Adapt Your CX Workflows With Webex Contact Center Flow Designer](https://developer.webex.com/blog/rapidly-adapt-your-cx-workflows-with-webex-contact-center-flow-designer), section 'Flow Versioning', implementation paragraph. Checked 2026-10-01. [^6]: The blog's final stage promotes a flow to production by assigning the Live version label. Source: [Rapidly Adapt Your CX Workflows With Webex Contact Center Flow Designer](https://developer.webex.com/blog/rapidly-adapt-your-cx-workflows-with-webex-contact-center-flow-designer), section 'Flow Versioning', item 'Live (Production)'. Checked 2026-10-01. [^7]: Cisco's blog presents flow versioning as enabling blue-green deployments with rollback to previous versions without downtime. Source: [Rapidly Adapt Your CX Workflows With Webex Contact Center Flow Designer](https://developer.webex.com/blog/rapidly-adapt-your-cx-workflows-with-webex-contact-center-flow-designer), section 'Flow Versioning', rollback and blue-green paragraph. Checked 2026-10-01. [^8]: The blog's next stage promotes a tested flow to the Test (staging) environment by applying the Test version label. Source: [Rapidly Adapt Your CX Workflows With Webex Contact Center Flow Designer](https://developer.webex.com/blog/rapidly-adapt-your-cx-workflows-with-webex-contact-center-flow-designer), section 'Flow Versioning', item 'Test (Staging)'. Checked 2026-10-01. [^9]: On 2026-04-27 Cisco announced a modernised Flow Designer canvas with a refreshed user experience, activity groupings and better search. Source: [What's new for administrators in Webex Contact Center](https://help.webex.com/en-us/article/nv7abhz/What's-new-for-administrators-in-Webex-Contact-Center), entry dated April 27, 2026, 'Modern and Unified Flow Designer Experience in Webex Contact Center'. Checked 2026-10-01. [^10]: In a channel's entry point settings, the Routing flow drop-down selects the flow assigned to that entry point. Source: [Set up a channel](https://help.webex.com/en-us/article/ewuay1/Set-up-a-channel), entry point settings table, 'Routing flow' row. Checked 2026-10-01. [^11]: A separate Version label field in a channel's entry point settings selects which version of the routing flow the entry point uses. Source: [Set up a channel](https://help.webex.com/en-us/article/ewuay1/Set-up-a-channel), entry point settings table, 'Version label' row. Checked 2026-10-01. [^12]: A resource collection cannot be set to None for Queues, Teams, Sites or Channels. Source: [Manage access in Webex Contact Center](https://help.webex.com/en-us/article/n524f2m), resource collections section. Checked 2026-10-01. [^13]: In Webex Connect, an earlier version is loaded from the version history drop-down in read-only mode. Editing it creates a working draft marked as forked from that version, which must then be made live. Source: [Flow Version History - Webex Connect Platform Overview](https://help.webexconnect.io/docs/versioning), version history and restore paragraphs. Checked 2026-10-01. [^14]: In Webex Connect, flow edits go into a working draft that does not affect the live flow, and a new higher version number is created only when the flow is made live. Source: [Flow Version History - Webex Connect Platform Overview](https://help.webexconnect.io/docs/versioning), working draft and versioning paragraphs. Checked 2026-10-01. [^15]: Webex Connect digital flows use Webex Connect's own draft and make-live versioning, so Flow Designer labels do not govern them (inferred). Source: [Flow Version History - Webex Connect Platform Overview](https://help.webexconnect.io/docs/versioning), whole page, read with registry claim webex-contact-center-digital-via-connect. Checked 2026-10-01. [^16]: Because an entry point is bound to a flow plus a label rather than a version number, publishing a new version that carries the label should change what that entry point runs without editing the entry point (inferred). Source: [Set up a channel](https://help.webex.com/en-us/article/ewuay1/Set-up-a-channel), entry point settings table, 'Routing flow' and 'Version label' rows. Checked 2026-10-01. [^17]: When version labels were introduced, flows that already existed were marked with the Live version label. Source: [What's New in Webex Contact Center](https://help.webex.com/en-US/article/preview/a1gx3h/What's-New-in-Webex-Contact-Center), entry dated February 6, 2024, 'Apply version labels to a flow'. Checked 2026-10-01. [^18]: The Flow V2 APIs let teams search, validate, publish, export, lock and unlock flows, subflows and functions. Source: [What's new for administrators in Webex Contact Center](https://help.webex.com/en-us/article/nv7abhz/What's-new-for-administrators-in-Webex-Contact-Center), entry dated July 29, 2026, 'Programmatic Flow Design with public Flow Schema and new APIs'. Checked 2026-10-01. [^19]: The Flow Designer properties pane shows flow history information, including the owner, the last edited date and the flow version number. Source: [Build and manage flows with Flow Designer](https://help.webex.com/en-us/article/nhovcy4/Build-and-manage-flows-with-Flow-Designer), section 'Properties pane' (global flow properties). Checked 2026-10-01. [^20]: Flow List and Flow Publish APIs on the Developer Portal supplement the existing Import and Export APIs for flows and subflows. Source: [What's new for administrators in Webex Contact Center](https://help.webex.com/en-us/article/nv7abhz/What's-new-for-administrators-in-Webex-Contact-Center), entry titled with Flow List and Flow Publish APIs (date heading not confirmed). Checked 2026-10-01. [^21]: Since 2026-07-29, a public Flow schema and Flow V2 APIs on the Webex Contact Center Developer Portal let administrators and developers author, validate and manage flows programmatically. Source: [What's new for administrators in Webex Contact Center](https://help.webex.com/en-us/article/nv7abhz/What's-new-for-administrators-in-Webex-Contact-Center), entry dated July 29, 2026, 'Programmatic Flow Design with public Flow Schema and new APIs'. Checked 2026-10-01. [^22]: The NewContact.FlowVersionLabel variable holds the version label of the flow version that is running, so flow logic can branch on labels such as Dev, Test, Live and Latest. Source: [Build and manage flows with Flow Designer](https://help.webex.com/en-us/article/nhovcy4/Build-and-manage-flows-with-Flow-Designer), NewContact activity output variables, NewContact.FlowVersionLabel. Checked 2026-10-01. [^23]: The GoTo terminating activity chains flows by sending the contact to an entry point or to another flow. Source: [Build and manage flows with Flow Designer](https://help.webex.com/en-us/article/nhovcy4/Build-and-manage-flows-with-Flow-Designer), activity reference, 'GoTo'. Checked 2026-10-01. [^24]: In Cisco's 2026 lab, the Publish Flow pop-up has an Add Version Label(s) list, and the lab has the student make sure Latest is selected before publishing. Source: [Mission 1: Basic Call Routing (Flow Template, TTS, Language) - Tech Summit Labs](https://webexcc-sa.github.io/TS-2026/main/CoreTrack_Mission1/), flow publishing steps, 'Add Version Label(s)'. Checked 2026-10-01. [^25]: In Cisco's 2026 lab, an administrator binds a flow by finding the channel under Channels, setting Routing flow and Version label in its Entry Point settings section, and clicking Save. Source: [Mission 1: Basic Call Routing (Flow Template, TTS, Language) - Tech Summit Labs](https://webexcc-sa.github.io/TS-2026/main/CoreTrack_Mission1/), channel configuration steps, 'Entry Point settings'. Checked 2026-10-01. [^26]: In Cisco's 2026 lab, the Validation toggle is in the bottom right of the Flow Designer window, and Publish Flow sits next to it once validation reports no flow errors. Source: [Mission 1: Basic Call Routing (Flow Template, TTS, Language) - Tech Summit Labs](https://webexcc-sa.github.io/TS-2026/main/CoreTrack_Mission1/), flow publishing steps, validation. Checked 2026-10-01. [^27]: Cisco recommends version labels for taking a flow through development, test and live phases before deploying it to production. Source: [Build and manage flows with Flow Designer](https://help.webex.com/en-us/article/nhovcy4/Build-and-manage-flows-with-Flow-Designer), section 'Apply version labels to a flow'. Checked 2026-10-01. [^28]: Flow version labels can be associated with entry point mappings, so an entry point can use a labelled version instead of the default Latest version. Source: [What's New in Webex Contact Center](https://help.webex.com/en-US/article/preview/a1gx3h/What's-New-in-Webex-Contact-Center), entry dated February 6, 2024, 'Apply version labels to a flow'. Checked 2026-10-01. [^29]: Version labels let different versions of the same flow be attached to different entry points or to a GoTo activity. Source: [Build and manage flows with Flow Designer](https://help.webex.com/en-us/article/nhovcy4/Build-and-manage-flows-with-Flow-Designer), section 'Apply version labels to a flow'. Checked 2026-10-01. [^30]: Latest is the default version label and cannot be removed from a flow version during publishing. Source: [What's New in Webex Contact Center](https://help.webex.com/en-US/article/preview/a1gx3h/What's-New-in-Webex-Contact-Center), entry dated February 6, 2024, 'Apply version labels to a flow'. Checked 2026-10-01. [^31]: From 2026-04-24 the NewPhoneContact start activity is renamed NewContact, as part of an omnichannel start node. Source: [What's new for administrators in Webex Contact Center](https://help.webex.com/en-us/article/nv7abhz/What's-new-for-administrators-in-Webex-Contact-Center), entry dated April 24, 2026, 'Flow Designer Omnichannel Start Node and End Node Enhancements'. Checked 2026-10-01. [^32]: No permission scoped to version labels was found, so control over who applies Live has to come from who holds Edit on flows and channels plus team process (inferred). Source: [Manage access in Webex Contact Center](https://help.webex.com/en-us/article/n524f2m), access levels and resource collections sections (absence of a label-level permission). Checked 2026-10-01. [^33]: In Flow Designer, promotion appears to happen by publishing a version again with the next label added, not by editing a label on an existing version (inferred). Source: [Rapidly Adapt Your CX Workflows With Webex Contact Center Flow Designer](https://developer.webex.com/blog/rapidly-adapt-your-cx-workflows-with-webex-contact-center-flow-designer), section 'Flow Versioning' (Test and Live items), read with the 2024-02-06 release note that labels are applied 'when you publish'. Checked 2026-10-01. [^34]: When publishing a flow, the administrator can associate a version label such as Live, Test or Dev with the new flow version. Source: [What's New in Webex Contact Center](https://help.webex.com/en-US/article/preview/a1gx3h/What's-New-in-Webex-Contact-Center), entry dated February 6, 2024, 'Apply version labels to a flow'. Checked 2026-10-01. [^35]: While the Flow Designer validation toggle is off, the Publish button stays disabled. Source: [Build and manage flows with Flow Designer](https://help.webex.com/en-us/article/nhovcy4/Build-and-manage-flows-with-Flow-Designer), section 'Footer pane'. Checked 2026-10-01. [^36]: A resource collection assigned through a user profile limits which resources an administrator can reference. For example, a user limited to two queues can build flows only with those queues. Source: [Manage access in Webex Contact Center](https://help.webex.com/en-us/article/n524f2m), resource collections section. Checked 2026-10-01. [^37]: Reverting opens the selected earlier version in edit mode, where it can be changed and published again as a new version. Source: [Build and manage flows with Flow Designer](https://help.webex.com/en-us/article/nhovcy4/Build-and-manage-flows-with-Flow-Designer), revert procedure (flow management sections). Checked 2026-10-01. [^38]: Flow Designer lets a flow developer revert a flow to a previously published version. Source: [What's New in Webex Contact Center](https://help.webex.com/en-US/article/preview/a1gx3h/What's-New-in-Webex-Contact-Center), entry dated August 5, 2022, 'Flow Designer Enhancements'. Checked 2026-10-01. [^39]: A rollback by revert produces a new, higher version number that has to be published with Live again; version numbers never go backwards (inferred). Source: [Build and manage flows with Flow Designer](https://help.webex.com/en-us/article/nhovcy4/Build-and-manage-flows-with-Flow-Designer), revert procedure, read with 'Properties pane' (flow version counts publishes). Checked 2026-10-01. [^40]: An administrator can save an unpublished flow draft and return to continue working on it later. Source: [Build and manage flows with Flow Designer](https://help.webex.com/en-us/article/nhovcy4/Build-and-manage-flows-with-Flow-Designer), section 'Enable or disable autosave'. Checked 2026-10-01. [^41]: A subflow can be published on its own, but its changes take effect only after the main flow that uses it is republished. Source: [Build and manage flows with Flow Designer](https://help.webex.com/en-us/article/nhovcy4/Build-and-manage-flows-with-Flow-Designer), subflow sections (publishing subflows). Checked 2026-10-01. [^42]: A subflow can carry a version label such as Live, Dev or Test so the main flow can be tested end to end in each environment. Source: [Build and manage flows with Flow Designer](https://help.webex.com/en-us/article/nhovcy4/Build-and-manage-flows-with-Flow-Designer), subflow sections (subflow version labels). Checked 2026-10-01. [^43]: The Flow Designer help article has separate procedures to copy, export, import and delete a flow and to apply version labels to a flow. Source: [Build and manage flows with Flow Designer](https://help.webex.com/en-us/article/nhovcy4/Build-and-manage-flows-with-Flow-Designer), table of contents: 'Copy a flow', 'Export a flow', 'Import a flow', 'Delete a flow', 'Apply version labels to a flow'. Checked 2026-10-01. [^44]: A flow must be validated and its errors fixed before it can be published. Source: [Build and manage flows with Flow Designer](https://help.webex.com/en-us/article/nhovcy4/Build-and-manage-flows-with-Flow-Designer), section 'Footer pane' (flow validation and publishing). Checked 2026-10-01. [^45]: The Flow Designer article's statement that there is no version control predates or sits alongside the July 2026 API release note describing flow changes as versioned and reviewable. Labels and the API layer give release management but not branching or diffing in the UI (inferred). Source: [What's new for administrators in Webex Contact Center](https://help.webex.com/en-us/article/nv7abhz/What's-new-for-administrators-in-Webex-Contact-Center), entry dated July 29, 2026, compared with Flow Designer article 'Properties pane'. Checked 2026-10-01. [^46]: Flow Designer has a View version history option that shows the version details of a flow. Source: [Build and manage flows with Flow Designer](https://help.webex.com/en-us/article/nhovcy4/Build-and-manage-flows-with-Flow-Designer), 'View version history' option (flow management sections). Checked 2026-10-01. [^47]: Flow Designer has no version control feature. The flow version number counts how many times the flow has been published, and version labels can be applied. Source: [Build and manage flows with Flow Designer](https://help.webex.com/en-us/article/nhovcy4/Build-and-manage-flows-with-Flow-Designer), flow versioning section. Checked 2026-09-30. [^48]: A new flow is created in Control Hub under Contact Center > Customer Experience > Flows, then Manage Flows > Create Flows. Source: [Build and manage flows with Flow Designer](https://help.webex.com/en-us/article/nhovcy4/Build-and-manage-flows-with-Flow-Designer), Build and manage flows with Flow Designer; Create a flow. Checked 2026-09-25. [^49]: Entry points are created as channels in Control Hub under Services > Contact Center > Customer experience > Channels by clicking Create. Source: [Set up a channel](https://help.webex.com/en-us/article/ewuay1/Set-up-a-channel), Set up a channel procedure, steps 1 to 3. Checked 2026-09-30. [^50]: Digital channels for Webex Contact Center (Facebook Messenger, live chat, email, SMS, Apple Messages for Business, WhatsApp) are configured through Webex Connect, and their flows are built in Webex Connect rather than in Flow Designer. Source: [Set up digital channels in Webex Contact Center](https://help.webex.com/en-us/article/n954r0k/Set-up-digital-channels-in-Webex-Contact-Center), overview and setup steps (final step 'Create flows in Webex Connect'). Checked 2026-09-30. [^51]: Cisco describes the Dev label for development, Test for staging validation and Live for production. Source: [Rapidly Adapt Your CX Workflows With Webex Contact Center Flow Designer](https://developer.webex.com/blog/rapidly-adapt-your-cx-workflows-with-webex-contact-center-flow-designer), Flow Versioning – Streamlining Development and Deployment. Checked 2026-10-01. [^52]: Cisco positions flow version labels as enabling a pipeline-driven promotion process from development to production, including blue-green deployments of flows. Source: [Rapidly Adapt Your CX Workflows With Webex Contact Center Flow Designer](https://developer.webex.com/blog/rapidly-adapt-your-cx-workflows-with-webex-contact-center-flow-designer), Flow Versioning – Streamlining Development and Deployment. Checked 2026-10-01. [^53]: For a voice entry point the channel type choices are Inbound Telephony and Outbound Telephony; a first inbound flow uses Inbound Telephony. Source: [Set up a channel](https://help.webex.com/en-us/article/ewuay1/Set-up-a-channel), Set up a channel; Channel Type field. Checked 2026-09-25. [^54]: For an inbound telephony channel, the dial numbers callers reach are selected in the channel's Support Number section. Source: [Set up a channel](https://help.webex.com/en-us/article/ewuay1/Set-up-a-channel), Set up a channel; Support Number section. Checked 2026-09-25. [^55]: The Cisco lab publishes the flow with the Latest label, then on the channel sets Routing flow to that flow, Music on hold to defaultmusic_on_hold.wav and Version label to Latest, and saves. Source: [Mission 1: Basic Call Routing (Flow Template, TTS, Language) - Tech Summit Labs](https://webexcc-sa.github.io/TS-2026/main/CoreTrack_Mission1/), Mission 1; flow publishing and channel mapping steps. Checked 2026-09-25. [^56]: A channel in an active state cannot be deleted; it must be deactivated first. Source: [Set up a channel](https://help.webex.com/en-us/article/ewuay1/Set-up-a-channel), Set up a channel; Delete a channel. Checked 2026-09-25. [^57]: Mapping a Test or Dev version label to a separate test entry point, before moving the production entry point, is likely the safest way to test a first flow; Cisco describes labels as a way to test without affecting production calls but does not prescribe this setup (inferred). Source: [What's New in Webex Contact Center](https://help.webex.com/en-US/article/preview/a1gx3h/What's-New-in-Webex-Contact-Center), What's new; February 6, 2024 entry 'Apply version labels to a flow'. Checked 2026-09-25. [^58]: Flow Designer undo and redo covers the last 10 canvas actions. Source: [Build and manage flows with Flow Designer](https://help.webex.com/en-us/article/nhovcy4/Build-and-manage-flows-with-Flow-Designer), canvas actions, undo/redo. Checked 2026-09-30. [^59]: If the flow validation toggle is off the Publish button stays disabled, and after validation is enabled Publish stays disabled until all flow errors are resolved. Source: [Build and manage flows with Flow Designer](https://help.webex.com/en-us/article/nhovcy4/Build-and-manage-flows-with-Flow-Designer), Build and manage flows with Flow Designer; Flow validation. Checked 2026-09-25. [^60]: The Subflow activity passes inputs into the subflow and returns outputs to the main flow, so passed data can change the subflow's behaviour. Source: [Design Delightful Customer Experiences with Webex Contact Center Flow Designer](https://developer.webex.com/blog/design-delightful-customer-experiences-with-webex-contact-center-flow-designer), Subflows. Checked 2026-10-01. [^61]: A subflow setting named Propagate changes to all flows cascades a subflow change to all parent flows that consume it. Source: [Rapidly Adapt Your CX Workflows With Webex Contact Center Flow Designer](https://developer.webex.com/blog/rapidly-adapt-your-cx-workflows-with-webex-contact-center-flow-designer), Subflows – Enhancing Modularity and Reuse. Checked 2026-10-01. [^62]: The Cisco lab tests a new flow by signing an agent in to the Webex Contact Center Desktop, setting the agent Available, calling the support number and checking that the welcome prompt plays and the call is offered to the agent. Source: [Mission 1: Basic Call Routing (Flow Template, TTS, Language) - Tech Summit Labs](https://webexcc-sa.github.io/TS-2026/main/CoreTrack_Mission1/), Mission 1; testing step. Checked 2026-09-25. [^63]: A version label can be mapped to an entry point so that new flow versions can be developed and tested without affecting production calls. Source: [What's New in Webex Contact Center](https://help.webex.com/en-US/article/preview/a1gx3h/What's-New-in-Webex-Contact-Center), What's new; February 6, 2024 entry 'Apply version labels to a flow'. Checked 2026-09-25. [^64]: Webex Contact Center API integrations use scopes such as cjp:config and cjp:config_read. The blog's example endpoint is on the US1 host api.wxcc-us1.cisco.com. Source: [Navigating Webex Contact Center API Authentication with Ease](https://developer.webex.com/blog/navigating-webex-contact-center-api-authentication-with-ease), scopes section and example request. Checked 2026-09-30. [^65]: A 2024 Cisco developer blog says Webex Contact Center OAuth integration access tokens expire after 14 days and refresh tokens after 90 days, and that refreshing the access token restarts the refresh token's 90-day window. Source: [Navigating Webex Contact Center API Authentication with Ease](https://developer.webex.com/blog/navigating-webex-contact-center-api-authentication-with-ease), token lifetime paragraph. Checked 2026-09-30. [^66]: Webex Contact Center is deployed in Amazon Web Services (AWS). Source: [Webex Contact Center Architecture](https://help.webex.com/en-us/article/utqcm7/Webex-Contact-Center-Architecture), Deployment and Connectivity section. Checked 2026-09-30.