# Setting up chat and email and SMS channels in Webex Contact Center Systems: Webex Contact Center For Webex Contact Center administrators configuring digital channels across Control Hub, Webex Connect, and Webex Engage. Canonical: https://warmtransfer.net/guides/wxcc-digital-channels-setup Last verified: 2026-09-30 Webex Contact Center digital channels route customer interactions through Webex Connect flows into queues that deliver them to Agent Desktop[^51][^2]. This guide walks through configuring multimedia profiles, assets, entry points, queues, and Webex Connect flow templates to enable chat, email, and SMS[^16][^45]. ## Before you start Setting up digital channels requires administrator access across Control Hub, Webex Contact Center, Webex Connect, and Webex Engage[^1]. Webex Contact Center digital channels operate under controlled general availability, requiring tenants to plan onboarding with the Cisco Solution Assurance team[^52][^53]. When a Webex Contact Center organization is provisioned, Webex Engage and Webex Connect are created automatically, and administrator user accounts synchronize between them[^54]. Newly provisioned Control Hub administrators must activate and sign in to their Webex Connect account within 7 days, or the account must be recreated[^55]. Furthermore, a cloud Webex Contact Center tenant and a Contact Center Enterprise deployment cannot share the same Webex Connect instance or Control Hub organization[^56]. ## What changes by situation - Which digital channels are you launching in this phase? Live chat only (website widget); Live chat and email; Live chat, email, and SMS. - How should voice and digital capacity combine for these agents? Blended: agents handle voice and multiple digital contacts concurrently; Blended Real-time: one mandatory real-time channel plus email; Exclusive: one contact at a time across all channels. - How should the QueueTask node pick an agent? Longest Available Agent queue without skills; Skill Based Routing queue with skills configured on the QueueTask node. ## Step 1: Authorize Webex CC integrations in Webex Connect ### Do Both the Webex CC Task and Webex CC Engage node integrations in Webex Connect must be placed in an Authorized state before setting up any channel[^57]. In Webex Connect, navigate to Assets > Integrations > Pre-built Integrations[^5]. Select Actions > Manage for each integration, click Add Authorization under Node Authorizations, and sign in with a Cisco account[^5]. The signing account must have an assigned Contact Center license with the Full Admin or Contact Center Admin role in Control Hub[^6]. ### Verify Navigate to Assets > Integrations > Pre-built Integrations and confirm that both Webex CC Task and Webex CC Engage show an Authorized status[^5]. ### Rollback Suggested rollback: Delete the integration authorization in Webex Connect. If administrator credentials change later, Webex Connect loses access and the authorization must be performed again[^4]. ## Step 2: Create the multimedia profile **Blended: agents handle voice and multiple digital contacts concurrently** ### Do Create a Blended multimedia profile in Webex Contact Center[^29]. In a Blended profile, configure voice capacity between 0 and 1, and set chat, email, and social capacities individually between 0 and 5[^24]. ### Verify Suggested check: View the profile list in the management interface and verify the profile type is Blended with the specified numeric concurrent capacities. ### Rollback Suggested rollback: Edit the multimedia profile settings or delete the profile prior to assigning it to users or sites. **Blended Real-time: one mandatory real-time channel plus email** ### Do Create a Blended Real-time multimedia profile in Webex Contact Center[^29]. Configure one mandatory real-time channel—either voice or chat—and specify the concurrent email limit[^29]. ### Verify Suggested check: View the created profile and verify that it designates a single real-time channel alongside the configured email limit. ### Rollback Suggested rollback: Edit or delete the unassigned multimedia profile. **Exclusive: one contact at a time across all channels** ### Do Create an Exclusive multimedia profile in Webex Contact Center[^29]. An Exclusive profile delivers exactly 1 contact at a time to an agent, using a hard-coded channel priority order of voice, then chat, then email, then social[^26]. ### Verify Suggested check: Check the multimedia profiles table and confirm the profile type is listed as Exclusive. ### Rollback Suggested rollback: Edit or delete the unassigned multimedia profile. ## Step 3: Assign the multimedia profile and configure RONA timeouts ### Do Assign the multimedia profile following the entity hierarchy: associate the profile to sites, associate sites to teams, and assign users to teams and profiles[^16]. Profile precedence applies such that an agent-level profile overrides a team-level profile, which overrides a site-level profile[^28]. If agents have a voice capacity allocated in their profile, they can place manual outdial calls from Agent Desktop while concurrently handling a digital contact[^27]. Next, navigate to Control Hub under Contact Center > Tenant settings > Desktop to set digital RONA timeouts[^40]. Configure the timeout for each channel within the allowable range of 1 to 6000 seconds; defaults are 30 seconds for chat, 300 seconds for email, and 30 seconds for social[^40]. ### Verify Suggested check: Review an agent user record to confirm the effective multimedia profile matches assignments. Suggested check: Confirm the saved RONA timeout values under Desktop tenant settings in Control Hub. ### Rollback Suggested rollback: Reassign the agents, teams, or sites back to their previous multimedia profiles, such as Default_Multimedia_Profile or Default_Telephony_Profile[^25], and reset RONA timers to default values[^40]. ## Step 4: Create and register the Live Chat asset ### Do In Webex Connect, open Assets > Apps > Configure New App > Mobile / Web and enable the Live Chat toggle[^21]. Select MQTT or Web Socket as the primary and secondary transfer protocols[^21]. Check Use Secured Port, which is mandatory for the Webex Contact Center integration, and ensure payload encryption is not enabled[^23]. Select Register to Webex Engage and assign the asset to a Webex Connect service[^22][^39]. Once registered, the service mapping cannot be changed[^39]. ### Verify Suggested check: Navigate to Assets > Apps, filter by Mobile / Web, and confirm the Live Chat asset shows as registered to the selected service. ### Rollback Suggested rollback: Deleting a Live Chat asset that has already been registered to Webex Engage cannot be reversed[^22]. Suggested rollback: If registration has not yet been performed, delete the app configuration from Webex Connect. ## Step 5: Configure the Email asset **Live chat only (website widget)** ### Do Follow the chat deployment path without configuring an email channel[^21]. ### Verify Suggested check: Confirm that no email asset has been registered in the environment. ### Rollback Suggested rollback: Not applicable. **Live chat and email** ### Do For the email asset, Webex Connect supports only Gmail and Microsoft 365 mailboxes, authenticating by username and password or by OAuth 2.0, with OAuth 2.0 recommended[^14]. Copy the forwarding address generated by the asset, and configure an auto-forwarding rule on the support mailbox to forward received emails to it[^12]. In Control Hub, Email is the exception among digital assets with its channel asset created directly there, and its assigned service and Email channel cannot be changed once created[^58][^59][^39]. ### Verify Confirm that inbound emails forward from the external mailbox to the generated forwarding address[^12]. In Control Hub, verify the Email asset status is registered[^58]. ### Rollback Suggested rollback: Remove or disable the auto-forwarding rule configured on the support mailbox[^12]. Do not delete a registered Email asset from the system[^13]. **Live chat, email, and SMS** ### Do For the email asset, Webex Connect supports only Gmail and Microsoft 365 mailboxes, authenticating by username and password or by OAuth 2.0, with OAuth 2.0 recommended[^14]. Copy the forwarding address generated by the asset, and configure an auto-forwarding rule on the support mailbox to forward received emails to it[^12]. In Control Hub, Email is the exception among digital assets with its channel asset created directly there, and its assigned service and Email channel cannot be changed once created[^58][^59][^39]. ### Verify Confirm that inbound emails forward from the external mailbox to the generated forwarding address[^12]. In Control Hub, verify the Email asset status is registered[^58]. ### Rollback Suggested rollback: Remove or disable the auto-forwarding rule configured on the support mailbox[^12]. Do not delete a registered Email asset from the system[^13]. ## Step 6: Procure and register the SMS asset **Live chat only (website widget)** ### Do Follow the chat deployment path without procuring an SMS number[^21]. ### Verify Suggested check: Confirm that no SMS number is provisioned or assigned. ### Rollback Suggested rollback: Not applicable. **Live chat and email** ### Do Follow the chat and email deployment path without procuring an SMS number[^21][^14]. ### Verify Suggested check: Confirm that no SMS number is provisioned or assigned. ### Rollback Suggested rollback: Not applicable. **Live chat, email, and SMS** ### Do Request an SMS number by contacting your Partner Success Manager (for Gold or partner tenants) or Customer Success Manager (for customer tenants), reachable via the Contact Support page in Webex Connect[^42]. Once provisioned, open Assets > Numbers in Webex Connect, select the number, choose Manage, and select Register to Webex Engage[^43]. Select the destination Webex Connect service; this service assignment cannot be altered once completed[^43][^39]. ### Verify Navigate to Assets > Numbers in Webex Connect and verify that both a Webex Contact Center icon and a PCI check flag are displayed next to the provisioned number[^43]. ### Rollback Suggested rollback: Do not release an active number that is in use for customer support over SMS[^41]. Suggested rollback: Coordinate decommissioning of the number with your assigned success manager. ## Step 7: Create digital entry points ### Do In the Webex Contact Center Management Portal, create an entry point for each channel being launched[^60]. Configure Channel Type as Chat for live chat, Email for email, or Social with a Social Channel Type set to SMS for text messaging[^17]. In the Asset Name field, select the corresponding asset configured in Webex Connect[^17]. Entry point names must not exceed 80 characters and may contain alphanumeric characters, underscores, and hyphens[^18]. Cisco states that the Service Level Threshold field on an entry point has no functional impact on calculations, so enter a placeholder value[^19]. ### Verify Suggested check: Review the Entry Points list in the Management Portal to verify each created entry point binds to the intended channel type and registered asset name. ### Rollback Suggested rollback: Delete or edit the created entry points in the Webex Contact Center Management Portal. ## Step 8: Create digital queues **Longest Available Agent queue without skills** ### Do In the Webex Contact Center Management Portal, create queues matching each channel type: Chat distribution for chat, Email distribution for email, or Conversation distribution for SMS[^30][^60]. Social queues cannot have a Service Level Threshold configured[^32]. Optionally, enable the Manual-assigned contacts by agents toggle so agents can manually select contacts from the Queued tab in Agent Desktop[^31]. Add the teams to the distribution groups for these queues[^30]. ### Verify Suggested check: Confirm that each queue is displayed in the Management Portal with its distribution group configured with the correct teams. ### Rollback Suggested rollback: Delete or edit the queues from the Webex Contact Center Management Portal. **Skill Based Routing queue with skills configured on the QueueTask node** ### Do In the Webex Contact Center Management Portal, create skill-based routing queues matching the channel types: Chat distribution for chat, Email distribution for email, or Conversation distribution for SMS[^30][^60]. Social queues cannot have a Service Level Threshold configured[^32]. For the routing type, select Skill-based routing and choose either Longest available or Best available as the agent selection pattern[^33]. Optionally, enable Manual-assigned contacts by agents[^31]. Skill profiles must be assigned to individual agents, as this is disputed: Cisco states that Webex Contact Center does not currently support assigning a skill profile to a team, only to an individual agent[^61]. ### Verify Suggested check: Confirm each queue displays a Skill-based routing type in the Management Portal, and verify agent records have appropriate individual skill profiles attached. ### Rollback Suggested rollback: Delete the queues and remove skill assignments from individual agent records. ## Step 9: Import flow templates and configure the QueueTask node **Longest Available Agent queue without skills** ### Do Obtain the official flow templates distributed through the Cisco DevNet GitHub repository[^62]. For each channel, create or open the Webex Connect service mapped to that asset[^45]. In the service's Flows tab, select Create Flow > Upload a flow, and upload the template file[^45]. Save each flow immediately after creation to prevent script formatting issues[^46]. Also import the 3 global flows: Task Routed, Task Modified, and Close Task[^20]. Open every Webex CC pre-built node individually in the imported flows and set its Node Runtime Authorization to the configured integration authorization[^63]. In SMS flows, configure the start-node trigger to incoming message[^44]. On the QueueTask node, set Media Type to Chat, Email, or Social to match the flow channel[^34]. Configure static Queue details by selecting the Longest Available Agent queue, or configure dynamic Queue ID (which requires Queue Task node version 1.5 or later)[^37]. Connect at least 1 node outcome to continue flow execution; available outcomes include Queued, taskFailed, onTimeout, onError, onInvalidData, onInvalidChoice, and onauthorizationfail[^64][^35]. On cloud Webex Contact Center, contact priority is configured on the QueueTask node inside the Webex Connect flow[^65]. ### Verify Save the flow and confirm it transitions into the Working Draft state without validation errors or unassigned node authorizations[^66]. ### Rollback Suggested rollback: Delete the imported Working Draft flow or discard unsaved canvas edits. **Skill Based Routing queue with skills configured on the QueueTask node** ### Do Obtain the official flow templates distributed through the Cisco DevNet GitHub repository[^62]. For each channel, create or open the Webex Connect service mapped to that asset[^45]. In the service's Flows tab, select Create Flow > Upload a flow, and upload the template file[^45]. Save each flow immediately after creation to prevent script formatting issues[^46]. Also import the 3 global flows: Task Routed, Task Modified, and Close Task[^20]. Open every Webex CC pre-built node individually in the imported flows and set its Node Runtime Authorization to the configured integration authorization[^63]. In SMS flows, configure the start-node trigger to incoming message[^44]. On the QueueTask node, set Media Type to Chat, Email, or Social to match the flow channel[^34]. Select the Skill Based Routing queue under Queue details[^37]. Configure required skills, skill conditions, and skill values directly on the QueueTask node[^37][^65]. Digital skills-based routing supports 4 skill types: proficiency (0 to 10), boolean, text, and enum[^67]. To relax skill requirements over time, configure skill relaxation rules on the QueueTask node with an interval (the default relaxation timeout is 60 seconds; node version 1.3 or higher is recommended)[^38][^68]. Connect at least 1 node outcome, such as Queued, taskFailed, or onTimeout[^64][^35]. On cloud Webex Contact Center, contact priority is configured on the QueueTask node inside the Webex Connect flow[^65]. ### Verify Save the flow and confirm it transitions into the Working Draft state with the defined skill requirements and relaxations saved on the QueueTask node[^66]. ### Rollback Suggested rollback: Delete the imported Working Draft flow or discard unsaved canvas edits. ## Step 10: Publish Webex Connect flows ### Do Open each channel flow and global flow (Task Routed, Task Modified, Close Task) and click Make Live[^66][^20]. When prompted, enter a version comment not exceeding 250 characters[^69]. Total flow size must stay under the 10 MB limit[^70]. ### Verify Confirm on the Flows list page in Webex Connect that each channel flow and global flow shows a Live state[^66]. ### Rollback Suggested rollback: Flows can be paused from the Webex Connect flow listing page[^66]. If a rollback version is published, flow runs that triggered prior to publication continue executing the older configuration that was live when they started[^71]. ## Step 11: Configure the chat widget and embed it on the website ### Do In Webex Engage, navigate to Assets > Channel assets > Livechat, edit the Live Chat asset, open the Websites tab, and click Add website[^49]. Enter the domain name without an http or https prefix (for example, `*.acme.com`), and configure the widget's initial greeting message[^49]. Manage widget visual design and customer templates within Webex Engage[^48][^15]. Switch to the Installation tab, copy the generated JavaScript snippet, and paste it immediately before the closing `` tag of your website HTML[^50]. ### Verify Load the website in a web browser and confirm the chat launcher appears in the bottom right corner of the page[^50]. ### Rollback Suggested rollback: Remove the JavaScript snippet from the website source and delete the registered website domain entry from Webex Engage. ## Step 12: Validate end-to-end routing on Agent Desktop ### Do Sign in an agent with the assigned multimedia profile and set their state to Available using the state selector[^2]. Launch an interaction from each enabled channel: initiate a live chat via the website launcher, send an email to the support mailbox (if launched), or send an SMS message to the provisioned number (if launched)[^50][^12][^43]. When the incoming task appears in the task list pane, click to accept it, or use Accept All Tasks if multiple contacts are present[^2]. Once accepted, the routed conversation adds the agent and presents the interaction pane[^72]. To eliminate manual clicks, administrators can enable the Auto accept digital interactions setting in the desktop profile (requires Standard or Premium agent licenses)[^7]. Test RONA behavior by allowing a new contact to sit unanswered past the configured timeout; the agent state automatically transitions to RONA[^3]. ### Verify Verify that incoming chat, email, or SMS interactions reach the task list pane and open successfully in the interaction pane[^2]. Transcripts and dashboards can be verified in the Webex Engage Customer Care console[^47]. Note that inbound and outbound file attachments are scanned for malware in both directions, and files failing the scan are dropped without a download option[^73]. ### Rollback Suggested rollback: Return test agents to their standard operational profiles and reset the Auto accept digital interactions toggle if enabled for testing[^7]. ## Applicability Applies to: Cisco Webex Contact Center, Cisco Webex Contact Center Agent Desktop, Cisco Webex Connect, Cisco Webex Engage, and Cisco Unified Contact Center Enterprise. Deployments: cloud, multi-tenant, contact-center-enterprise, and webex-connect. Sources checked 2026-09-30. Inbound email attachments over SMTP support file sizes up to 25 MB[^10]. The QueueTask node supports dynamic queue IDs starting in node version 1.5, and node version 1.3 or higher is recommended for skill relaxation[^37][^38]. Supported agent desktop browsers require at minimum Chrome 144+, Microsoft Edge 144+, or Firefox 140+[^74]. Agent Desktop requires at least 4 GB of RAM, with 8 GB or more recommended[^75]. ## What remains uncertain Whether carrier registration procedures such as US 10DLC are required when procuring SMS numbers through Cisco success managers is not covered by the sources below. The specific numerical limits for concurrent interactions in Blended Real-time multimedia profiles are not covered by the sources below. The default contact priority value applied by the QueueTask node when omitted is not covered by the sources below. Whether an Email asset can be created in Webex Connect rather than Control Hub is not covered by the sources below. Sources disagree on whether a skill profile can be assigned to a team[^61]. In addition, sources disagree on the exact count of representative sample flow templates, listing 7 in text and 8 in the corresponding table[^76]. ## Sources [^1]: Setting up Webex Contact Center digital channels requires administrator access to Control Hub, Webex Contact Center, Webex Connect and Webex Engage. 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), Prerequisites section. Checked 2026-09-30. [^2]: When a chat, email or social request is routed to a queue and the agent is available, it appears in the Agent Desktop task list pane and the agent must accept it to start communicating, with an Accept All Tasks option for several at once. Source: [Get started with Agent Desktop](https://help.webex.com/en-us/article/itebdl), Incoming chat, email and social requests section. Checked 2026-09-30. [^3]: If an agent does not accept a digital request within the configured timeframe, the agent's state changes to RONA. Source: [Get started with Agent Desktop](https://help.webex.com/en-us/article/itebdl), Incoming requests, RONA sentence. Checked 2026-09-30. [^4]: If the credentials used for a Webex CC node authorisation change, Webex Connect loses access and the authorisation has to be redone. Source: [Webex CC Task Integration Nodes and Node Authorizations](https://help.webexconnect.io/docs/wxcc-task-integration-nodes-and-node-authorizations), Note following the authorisation steps. Checked 2026-09-30. [^5]: Webex CC Task and Webex CC Engage node authorisation is performed in Webex Connect under Assets > Integrations > Pre-built Integrations, choosing Actions > Manage, then Add Authorization in the Node Authorizations section and signing in with a Cisco account. Source: [Webex CC Task Integration Nodes and Node Authorizations](https://help.webexconnect.io/docs/wxcc-task-integration-nodes-and-node-authorizations), Steps to authorize nodes, steps 1 to 7. Checked 2026-09-30. [^6]: The user who authorises the Webex CC nodes must have a Contact Center licence mapped to them with the Full Admin or Contact Center Admin role in Control Hub. Source: [Webex CC Task Integration Nodes and Node Authorizations](https://help.webexconnect.io/docs/wxcc-task-integration-nodes-and-node-authorizations), Node authorization prerequisites note. Checked 2026-09-30. [^7]: A desktop profile has a single Auto accept digital interactions toggle that automatically accepts new and transferred inbound digital interactions for its agents, is off by default for existing desktop profiles and requires Standard or Premium agent licences. Source: [Desktop profiles (Webex Contact Center)](https://help.webex.com/en-us/article/nvaf71f/), General settings, Auto accept digital interactions. Checked 2026-09-30. [^8]: Webex Connect's WXCC overview says the integration supports 5 channels, Facebook Messenger, SMS, Live Chat, Email and WhatsApp, which disagrees with other Cisco pages that document 6 channels including Apple Messages for Business (disputed). Source: [Overview - Cisco Webex Contact Center and Webex Connect integration](https://help.webexconnect.io/docs/wxcc-overview), Overview opening paragraph. Checked 2026-09-30. [^9]: Launching Live Chat first involves the fewest external dependencies of the three channels, because unlike SMS it needs no number provisioned through a Cisco success manager and unlike email it needs no Gmail or Microsoft 365 mailbox forwarding rule (inferred). Source: [Live Chat - WXCC](https://help.webexconnect.io/docs/livechat-asset-creation-wxcc), Whole article compared with the SMS and Email asset articles. Checked 2026-09-30. [^10]: The Webex Contact Center email channel accepts inbound attachments up to 25 MB over SMTP. Source: [Email Asset Creation - WXCC](https://help.webexconnect.io/docs/wxcc-email-asset-creation), Attachments note. Checked 2026-09-30. [^11]: The Webex Connect WXCC email article places Email asset creation in Webex Connect under Assets > Apps > Configure New App > Email followed by Register To Webex Engage, whereas Cisco's help.webex.com setup article places the Email asset in Control Hub (disputed). Source: [Email Asset Creation - WXCC](https://help.webexconnect.io/docs/wxcc-email-asset-creation), Email asset creation steps and registration steps. Checked 2026-09-30. [^12]: The email asset generates a forwarding address, and the administrator must configure an auto-forwarding rule on the support mailbox entered in the EMAIL ID field so that received emails are forwarded to it. Source: [Email Asset Creation - WXCC](https://help.webexconnect.io/docs/wxcc-email-asset-creation), Mailbox setup, forwarding address step. Checked 2026-09-30. [^13]: Cisco instructs administrators not to delete an Email asset once it has been registered with Webex Contact Center. Source: [Email Asset Creation - WXCC](https://help.webexconnect.io/docs/wxcc-email-asset-creation), Registration section, warning. Checked 2026-09-30. [^14]: Webex Connect supports only Gmail and Microsoft 365 mailboxes for the Webex Contact Center email channel, authenticating by username and password or by OAuth 2.0, with OAuth 2.0 recommended. Source: [Email Asset Creation - WXCC](https://help.webexconnect.io/docs/wxcc-email-asset-creation), Email provider and authentication fields. Checked 2026-09-30. [^15]: Templates for digital channels are created in Webex Engage and determine how each channel appears in Agent Desktop and which attachment types are permitted. Source: [Configure a chat template for Webex Contact Center](https://help.webex.com/en-us/article/nmzsthj/Configure-a-Chat-Template-for-Webex-Contact-Center), Opening section. Checked 2026-09-30. [^16]: Cisco's digital channel setup article orders the Webex Contact Center entity work as multimedia profiles, then sites tagged with those profiles, then teams, then users assigned to teams and multimedia profiles, then RONA timeouts in Control Hub. 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), Create entities in Management Portal section, ordered list. Checked 2026-09-30. [^17]: A Webex Contact Center entry point of channel type Chat, Email or Social has an Asset Name field for choosing the asset configured in Webex Connect, and a Social entry point also has a Social Channel Type of Facebook Messenger, SMS, WhatsApp or Apple Business Chat. Source: [Set up a channel in Webex Contact Center](https://help.webex.com/en-us/article/ewuay1), Asset Name and Social Channel Type field descriptions. Checked 2026-09-30. [^18]: An entry point name cannot exceed 80 characters and may contain alphanumeric characters, underscores and hyphens. Source: [Set up a channel in Webex Contact Center](https://help.webex.com/en-us/article/ewuay1), Name field description. Checked 2026-09-30. [^19]: Cisco states that the entry point Service Level Threshold field has no functional impact on the system's calculations and a placeholder value may be entered. Source: [Set up a channel in Webex Contact Center](https://help.webex.com/en-us/article/ewuay1), Service Level Threshold field description. Checked 2026-09-30. [^20]: Alongside the per-channel inbound templates, the sample set includes 3 global flows: Task Routed, Task Modified and Close Task. Source: [Flow Configuration using Sample Templates](https://help.webexconnect.io/docs/wxcc-flow-configuration-using-sample-templates), Getting the templates paragraph. Checked 2026-09-30. [^21]: A Live Chat asset for Webex Contact Center is created in Webex Connect under Assets > Apps > Configure New App > Mobile / Web, enabling the Live Chat toggle and choosing MQTT or Web Socket as primary and secondary transfer protocols. Source: [Live Chat - WXCC](https://help.webexconnect.io/docs/livechat-asset-creation-wxcc), Live Chat asset creation steps. Checked 2026-09-30. [^22]: Deleting a Live Chat asset that has been registered to Webex Engage cannot be reversed. Source: [Live Chat - WXCC](https://help.webexconnect.io/docs/livechat-asset-creation-wxcc), Register to Webex Engage, warning note. Checked 2026-09-30. [^23]: For the Webex Contact Center integration the Use Secured Port option on the Live Chat asset is mandatory and payload encryption must not be enabled. Source: [Live Chat - WXCC](https://help.webexconnect.io/docs/livechat-asset-creation-wxcc), Live Chat asset creation steps, secured port and encryption notes. Checked 2026-09-30. [^24]: In a Blended multimedia profile voice can be set from 0 to 1 and chat, email and social each from 0 to 5. Source: [Multimedia profiles (Webex Contact Center)](https://help.webex.com/en-us/article/nje7dhdb/), Blended profile field ranges. Checked 2026-09-30. [^25]: Webex Contact Center ships a Default_Telephony_Profile with voice 1 and chat, email and social 0, and a Default_Multimedia_Profile with voice 1 and chat, email and social 5 each. Source: [Multimedia profiles (Webex Contact Center)](https://help.webex.com/en-us/article/nje7dhdb/), Default multimedia profiles section. Checked 2026-09-30. [^26]: An Exclusive multimedia profile offers an agent 1 contact at a time and uses a fixed channel priority of voice, then chat, then email, then social. Source: [Multimedia profiles (Webex Contact Center)](https://help.webex.com/en-us/article/nje7dhdb/), Exclusive profile section. Checked 2026-09-30. [^27]: While handling a non-voice contact an agent can make a manual outdial call from Agent Desktop as long as the agent has a voice channel available in the multimedia profile. Source: [Multimedia profiles (Webex Contact Center)](https://help.webex.com/en-us/article/nje7dhdb/), Blended profile notes. Checked 2026-09-30. [^28]: Multimedia profiles can be assigned to a site, a team or an individual agent, and the agent-level profile takes precedence over the team profile, which takes precedence over the site profile. Source: [Multimedia profiles (Webex Contact Center)](https://help.webex.com/en-us/article/nje7dhdb/), Assign multimedia profiles section. Checked 2026-09-30. [^29]: Webex Contact Center multimedia profiles come in 3 types: Blended, where each channel's concurrent capacity is configurable; Blended Real-time, with 1 mandatory real-time channel (voice or chat) plus a configurable email limit; and Exclusive, 1 contact at a time. Source: [Multimedia profiles (Webex Contact Center)](https://help.webex.com/en-us/article/nje7dhdb/), Profile types section. Checked 2026-09-30. [^30]: When a queue's channel type is Chat, Email or Social channel, Webex Contact Center shows Chat distribution, Email distribution or Conversation distribution respectively in place of call distribution groups. Source: [Create queues and configure routing patterns](https://help.webex.com/en-us/article/ubg5qd), Channel type field description. Checked 2026-09-30. [^31]: Digital queues (Chat, Email, Social) have a Manual-assigned contacts by agents toggle that adds the queue to the Queued tab in Agent Desktop so agents can pick interactions from it. Source: [Create queues and configure routing patterns](https://help.webex.com/en-us/article/ubg5qd), Manual-assigned contacts by agents field description. Checked 2026-09-30. [^32]: A Service level threshold cannot be configured on a Social channel queue. Source: [Create queues and configure routing patterns](https://help.webex.com/en-us/article/ubg5qd), Service level threshold field description. Checked 2026-09-30. [^33]: Skills-based queues offer 2 agent selection patterns: Longest available, choosing the agent idle longest, and Best available, choosing the agent with the highest proficiency in the required skills. Source: [Create queues and configure routing patterns](https://help.webex.com/en-us/article/ubg5qd), Routing type, skills-based routing options. Checked 2026-09-30. [^34]: On the Queue Task node, Media Type is Social for SMS, Facebook Messenger, WhatsApp and Apple Messages, Email for email, and Chat for Live Chat, with Media Channel selecting the specific channel. Source: [Queue Task - WXCC](https://help.webexconnect.io/docs/wxcc-queue-task), Input fields, Media Type and Media Channel. Checked 2026-09-30. [^35]: The Queue Task node exposes outcomes including Queued on success and taskFailed, onTimeout, onError, onInvalidData, onInvalidChoice and onauthorizationfail on failure. Source: [Queue Task - WXCC](https://help.webexconnect.io/docs/wxcc-queue-task), Node outcomes section. Checked 2026-09-30. [^36]: Contact priority on the Queue Task node takes values from 1 to 9, where 1 is highest and 9 is lowest. Source: [Queue Task - WXCC](https://help.webexconnect.io/docs/wxcc-queue-task), Contact Priority field. Checked 2026-09-30. [^37]: Queue details on the Queue Task node are either static, choosing a queue of type Longest Available Agent or Skill Based Routing, or dynamic, entering a Queue ID, and dynamic queue selection requires node version 1.5 or later. Source: [Queue Task - WXCC](https://help.webexconnect.io/docs/wxcc-queue-task), Queue details and version notes. Checked 2026-09-30. [^38]: Skill relaxation on the Queue Task node is configured with a timeout, skill, skill condition and skill value, the default relaxation timeout is 60 seconds, and node version 1.3 is recommended for improved relaxation handling. Source: [Queue Task - WXCC](https://help.webexconnect.io/docs/wxcc-queue-task), Skill-based routing and skill relaxation section; version notes. Checked 2026-09-30. [^39]: Registering a Live Chat, SMS or Email asset to Webex Engage maps it to a Webex Connect service, and that service mapping cannot be changed once done. Source: [Live Chat - WXCC](https://help.webexconnect.io/docs/livechat-asset-creation-wxcc), Register to Webex Engage steps, note. Checked 2026-09-30. [^40]: RONA timeouts for digital channels are set in Control Hub under Contact Center > Tenant settings > Desktop, with defaults of 30 seconds for chat, 300 seconds for email and 30 seconds for social, each adjustable from 1 to 6000 seconds. Source: [Manage RONA timeouts (Webex Contact Center)](https://help.webex.com/en-us/article/nbkcfp1/), RONA timeouts section, channel table. Checked 2026-09-30. [^41]: Cisco warns not to release a number that is being used for customer support over SMS. Source: [SMS Asset Creation - WXCC](https://help.webexconnect.io/docs/wxcc-sms-assset-creation), Critical considerations note. Checked 2026-09-30. [^42]: SMS numbers for the Webex Contact Center integration are provisioned by request to the Partner Success Manager for Gold or partner tenants or the Customer Success Manager for customer tenants, reachable from the Contact Support page in Webex Connect. Source: [SMS Asset Creation - WXCC](https://help.webexconnect.io/docs/wxcc-sms-assset-creation), Number procurement paragraph. Checked 2026-09-30. [^43]: A provisioned SMS number is registered by going to Assets > Numbers in Webex Connect, selecting the number, choosing Manage and then Register to Webex Engage with the chosen service, after which a Webex Contact Center icon and a PCI check flag appear next to the number. Source: [SMS Asset Creation - WXCC](https://help.webexconnect.io/docs/wxcc-sms-assset-creation), Registration steps and post-registration note. Checked 2026-09-30. [^44]: For imported SMS template flows the start node must be configured with incoming message as the trigger, while the other channel templates configure their start nodes on import. Source: [Flow Configuration using Sample Templates](https://help.webexconnect.io/docs/wxcc-flow-configuration-using-sample-templates), Configuring start nodes. Checked 2026-09-30. [^45]: A sample flow template is imported by creating a Webex Connect service corresponding to the channel asset, opening its Flows tab, choosing Create Flow, selecting Upload a flow as the method and uploading the template file. Source: [Flow Configuration using Sample Templates](https://help.webexconnect.io/docs/wxcc-flow-configuration-using-sample-templates), Creating a service and importing flows, steps 1 to 6. Checked 2026-09-30. [^46]: Cisco advises saving an imported template flow immediately after creation to prevent script formatting issues. Source: [Flow Configuration using Sample Templates](https://help.webexconnect.io/docs/wxcc-flow-configuration-using-sample-templates), Post-import configuration note. Checked 2026-09-30. [^47]: Cisco's setup article points administrators to the Webex Engage Customer Care console for dashboards and conversation transcripts used to verify digital channel operation and monitor agents. 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), Testing and monitoring section. Checked 2026-09-30. [^48]: Live Chat widget design and the code for embedding the widget on a website are both managed in Webex Engage rather than Webex Connect. Source: [Live Chat - WXCC](https://help.webexconnect.io/docs/livechat-asset-creation-wxcc), Closing notes on widget configuration. Checked 2026-09-30. [^49]: In Webex Engage the Live Chat asset's Websites tab has an Add website action where the site domain is entered without an http or https prefix, for example *.acme.com, together with the widget's first message. Source: [Livechat - WxEngage standalone](https://help.webexconnect.io/docs/livechat), Assets > Channel assets > Livechat > Websites tab. Checked 2026-09-30. [^50]: The widget installation script is copied from the Installation tab of the Live Chat asset in Webex Engage and pasted before the closing body tag of the website's HTML, after which a launcher appears at the bottom right of the page. Source: [Livechat - WxEngage standalone](https://help.webexconnect.io/docs/livechat), Installation tab steps. Checked 2026-09-30. [^51]: 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. [^52]: Webex Contact Center digital channels are released in controlled general availability: only customers who have worked with the Cisco Solution Assurance team to plan their onboarding can use them. 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), About digital channels. Checked 2026-09-04. [^53]: 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. 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), Set up digital channels in Webex Contact Center, About digital channels. Checked 2026-09-15. [^54]: When a Webex Contact Center organisation is set up, Webex Contact Center automatically provisions Webex Engage and Webex Connect as digital services and the 2 products synchronise administrator user accounts. 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), Set up digital channels, Provision digital channels. Checked 2026-09-04. [^55]: A newly added Control Hub administrator must create their Webex Connect user account and sign in to Webex Connect within 7 days, or the user account has to be recreated before they can gain access. 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), Provision digital channels, Before you begin. Checked 2026-09-04. [^56]: A cloud Webex Contact Center deployment with digital channels enabled and a Contact Center Enterprise deployment integrated with Webex Connect cannot use the same Webex Connect instance or the same Control Hub customer organisation; Cisco directs partners to create a separate Control Hub organisation with a different administrator email as a temporary workaround. Source: [Cisco Unified Contact Center Enterprise Features Guide Release 15.0(1) - Digital Channels Integration Using Webex Connect](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cust_contact/contact_center/icm_enterprise/icm_enterprise_15_0_1/ucce_b_1501_features-guide/rcct_m_150_digital-channels-integration-using-webex-connect.html), Prerequisites, note box. Checked 2026-09-04. [^57]: Before any digital channel can be set up, the Webex CC Task and Webex CC Engage node integrations in Webex Connect must each be set to an Authorized state; that authorisation is what lets Webex Connect nodes communicate with Webex Contact Center and Webex Engage. 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), Before you begin, step 2. Checked 2026-09-04. [^58]: For SMS, Livechat, Facebook Messenger and WhatsApp the channel asset is created in Webex Connect and then registered against a Webex Contact Center entry point; Email is the exception, with its asset created directly in Control Hub. 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), Before you begin, step 4. Checked 2026-09-04. [^59]: Once an Email channel asset is created in Control Hub, its assigned service and Email channel cannot be changed. 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), Channel-specific prerequisites, Email. Checked 2026-09-04. [^60]: The entry point a digital contact lands on, configured with channel type Social Channel and bound to the Webex Connect asset by an Asset Name field, and the queue it is routed to are both created in the Webex Contact Center Management Portal rather than in Webex Connect. 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), Before you begin, step 5. Checked 2026-09-04. [^61]: Cisco states that Webex Contact Center does not currently support assigning a skill profile to a team, only to an individual agent (disputed). 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), Implement skills-based routing and contact priority, step 2. Checked 2026-09-04. [^62]: Predefined Webex Contact Center digital-channel flow templates are distributed through the Cisco DevNet GitHub repository rather than bundled in the Webex Connect application, and are brought in using the Create Flow then Upload a Flow method. 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), Set up digital channels, step 7; Configure flows for digital channels. Checked 2026-09-04. [^63]: Every pre-built Webex Contact Center node inside an imported template flow must be opened individually and authorised through a Node Runtime Authorization selection before the flow will function; the authorisation is per node, not tenant-wide. Source: [Flow Configuration using Sample Templates](https://help.webexconnect.io/docs/wxcc-flow-configuration-using-sample-templates), Configure Flows. Checked 2026-09-04. [^64]: Webex Connect models branching as node outcomes rather than as a separate error-path object: a node may expose 2 or more outcomes, and at least 1 must be connected to a subsequent node for the flow to continue. Source: [Flows](https://help.webexconnect.io/docs/flows-introduction), Configuring a Flow. Checked 2026-09-04. [^65]: On cloud Webex Contact Center, skill requirements and contact priority for a digital contact are configured on the QueueTask node inside the Webex Connect flow, and the resulting task is queued for agents whose skills match. 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), Implement skills-based routing and contact priority for digital channels. Checked 2026-09-04. [^66]: A Webex Connect flow has 2 states: Working Draft, saved but not serving traffic and permitted to contain errors, and Live, published and processing triggers. Save produces a Working Draft and Make Live publishes it; a live flow can afterwards be paused from the flow listing page. Source: [Flows](https://help.webexconnect.io/docs/flows-introduction), Configuring and Publishing a Flow. Checked 2026-09-04. [^67]: Webex Contact Center defines 4 skill types for digital skills-based routing: proficiency, a value from 0 to 10 representing expertise; boolean, true or false; text, matched exactly; and enum, a named set of predefined values. 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), Implement skills-based routing and contact priority, step 1. Checked 2026-09-04. [^68]: If no matching agent becomes available within the interval configured on the QueueTask node, skill requirements can be removed or reduced by specifying skill relaxations on that same node. 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), Implement skills-based routing and contact priority, step 8. Checked 2026-09-04. [^69]: A Webex Connect flow version comment must not exceed 250 characters. Source: [Flows](https://help.webexconnect.io/docs/flows-introduction), Configuring and Publishing a Flow, note box. Checked 2026-09-04. [^70]: The maximum allowed size of a Webex Connect flow is 10 MB, and Cisco recommends staying below that to avoid problems saving or publishing. Source: [Flows](https://help.webexconnect.io/docs/flows-introduction), Flows, callout box. Checked 2026-09-04. [^71]: Flow runs that were triggered before a new version was published continue to execute the configuration that was live when they started; only runs triggered after publication use the new configuration. Source: [Flows](https://help.webexconnect.io/docs/flows-introduction), Configuring and Publishing a Flow, note box. Checked 2026-09-04. [^72]: When a queued digital task is routed to an agent, Webex Connect receives a Task Routed event on a dedicated global Routed flow, an Add Participant to Conversation node adds the agent so the contact surfaces in Agent Desktop, and an optional Screen Pop node can display a URL to the agent. Source: [Flow Configuration using Sample Templates](https://help.webexconnect.io/docs/wxcc-flow-configuration-using-sample-templates), Understanding Representative Flows, Routed Flow. Checked 2026-09-04. [^73]: All inbound and outbound attachments across all digital channels are automatically scanned for malware, and an attachment that fails the scan is dropped in both directions and shown in Agent Desktop as an unknown or blocked file with no download option. 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), Supported attachment file types for digital channels. Checked 2026-09-04. [^74]: The minimum supported Agent Desktop browsers are Chrome 144+, Microsoft Edge 144+ and Firefox 140+. Cisco recommends the latest stable versions. Source: [System requirements for Webex Contact Center Desktop](https://help.webex.com/en-us/article/besrkt/System-requirements-for-Webex-Contact-Center), Supported browsers table, Minimum column. Checked 2026-09-30. [^75]: Agent Desktop needs at least 4 GB of RAM. 8 GB or more is recommended. Source: [System requirements for Webex Contact Center Desktop](https://help.webex.com/en-us/article/besrkt/System-requirements-for-Webex-Contact-Center), requirements table, Memory row. Checked 2026-09-30. [^76]: Cisco's sample-templates article states that a total of 7 representative flows are available while the table immediately below it lists 8 named flows (disputed). Source: [Flow Configuration using Sample Templates](https://help.webexconnect.io/docs/wxcc-flow-configuration-using-sample-templates), opening paragraph and flow table. Checked 2026-09-04.