Create idle codes and add them to the desktop profile.

Create an address book and add it to the desktop profile.

Create wrap-up codes and add them to the desktop profile.

The requested desktop experience maps to three desktop-profile objects. First, to stop receiving inbound engagements without hurting KPIs, agents need an idle code configured in the desktop profile. Idle codes allow agents to move out of available status for recognized reasons rather than appearing as missed or mishandled contacts. Second, to transfer calls to frequent destinations, the administrator creates an address book and assigns it to the desktop profile so those destinations are available in Agent Desktop consult and transfer workflows. Third, to categorize the call intent, wrap-up codes must be created and added to the desktop profile so agents can classify the interaction after handling. A multimedia profile set to Exclusive would restrict simultaneous contacts, but it does not address transfer destinations, KPI-safe unavailable states, or call intent classification. Screen pop settings are related to CRM display behavior, not this stated goal. Reference: Cisco Help, Manage desktop profiles; Webex Contact Center Setup and Administration Guide.

The failure occurs after the standard Live Chat workflow template is deployed and the widget can be started, so the website widget itself is not the main issue. The Resolve node response in the exhibit points to a missing or invalid Live Chat domain value used by the workflow. Cisco's Webex Connect live chat and create conversation documentation identifies Livechat Website Domain as a value stored under custom variables and used when resolving or creating live chat conversations. The standard template depends on that workflow custom variable being populated with the valid domain where the Live Chat widget is embedded. Changing media type and media channel on the Resolve node would not fix a missing domain variable in the deployed template. The option using chat Domain is close but not the named workflow custom variable indicated by the template. Setting the Workflow Custom Variable LiveChat Domain to a valid value resolves the failure. Reference: Webex Connect Help, Livechat; Create conversation - WxEngage standalone; Resolve Conversation - WXCC.

Outdial calling in Webex Contact Center needs both a tenant or system caller-ID source and a desktop permission path that lets the agent place outbound calls. Cisco's Control Hub voice settings document the Default Outdial ANI field, which determines the default caller ID used for outdial behavior when a dial number is not otherwise mapped. Cisco's desktop profile documentation then controls whether an agent can actually use outdial from Agent Desktop. When Outdial is enabled on the desktop profile, the administrator selects the outdial entry point and, where applicable, the Outdial ANI list. Adding an agent to an outbound team is campaign-related and not a prerequisite for ordinary outdial. ANI in Flow Designer can influence call presentation in flows, but it is not the required administrative setup for agent outdial. A wrap-up reason for an outdial queue is useful for classification after a contact, not the base telephony enablement. Reference: Cisco Help, Set up voice settings for Webex Contact Center; Manage desktop profiles.

WebRTC voice in Webex Contact Center is exposed to agents through the Desktop telephony option. Cisco's desktop profile documentation lists voice channel options, including Agent DN, Extension, and Desktop. The Desktop option allows the agent to sign in through the browser and use the Agent Desktop as the voice device rather than entering an external directory number or extension. Cisco's voice channel setup documentation also describes WebRTC-capable agents selecting Desktop under their telephony option so calls are routed to the Agent Desktop device. Browser is not a desktop profile voice option; it describes the client environment. Extension and Agent DN are traditional station credentials and would make the agent use a phone or configured number instead of browser-based WebRTC. Therefore, to enable agents to make and receive calls using WebRTC, the administrator must configure the Desktop option in the desktop profile. Reference: Cisco Help, Manage desktop profiles; Set up voice channels for Webex Contact Center.

A REST PUT request that modifies a contact-service queue is an administrative write operation. Cisco's Webex Contact Center API model uses scopes to separate read-only access from configuration changes. The endpoint /organization/{orgid}/v2/contact-service-queue/{id} updates an existing queue object, so the integration must hold the organization-level administrative write scope. The read scopes, such as cjp:config_read or cjds:admin_org_read, are appropriate when an application only retrieves configuration data. They do not authorize mutation of queue configuration. The cjp:user scope is also not sufficient because queue configuration is a tenant or organization-level administrative resource, not a simple user-context operation. The scope cjds:admin_org_write is therefore the correct scope for a PUT operation on contact-service-queue. This matches the principle used throughout Cisco's API documentation: write methods require write-capable scopes, especially for configuration entities. Reference: Webex Contact Center Developer API Reference, Contact Service Queues; Webex Developer, Contact Center Service Apps.

The requirement is to detect customer dissatisfaction before it escalates. Cisco's AI Assistant reporting and quality features include automatic CSAT scoring, which estimates customer satisfaction from interaction signals and gives the contact center a proactive way to identify poor experiences without waiting for a manual survey response. Topic analytics identifies common contact drivers and trending issues, which is valuable for operational improvement but does not directly score whether a specific customer is dissatisfied. AI-generated summaries reduce after-call work and improve handoff context, but they do not by themselves predict dissatisfaction. Real-time transcripts provide the text foundation for analysis and assistance, but the feature that turns interaction data into a customer-satisfaction signal is automatic CSAT scoring. For a customer-experience program focused on early dissatisfaction detection and proactive resolution, automatic CSAT provides the required risk signal. Reference: Cisco Help, AI Assistant reports in Analyzer; Cisco AI Assistant for Webex Contact Center documentation.

For OAuth 2.0 custom connector authentication in Webex Contact Center, Cisco documents client credentials using either a client secret or a private key/certificate method. The custom connector configuration supports Client credentials - client secret, where the administrator enters a client ID and client secret, and Client credentials - private key, where the private key corresponds to the certificate material used by the application. Those two choices are valid grant/authentication methods for service-to-service integration because a backend connector needs machine-to-machine authorization rather than a user authorization code flow. Client credentials - token is not a grant type; the token is the output of a successful OAuth exchange. Client credentials - certificate is too imprecise in the option set because Cisco's configuration wording identifies private key/certificate material. Server credentials - certificate is not a documented OAuth grant type for the Webex Contact Center custom connector. Reference: Cisco Help, Configure custom connector for Webex Contact Center; Webex Developer, Integrations and Authorization.

Agent break behavior is an agent-state activity, so the correct Analyzer repository is Agent Activity Record. Cisco's Analyzer documentation explains that Analyzer repositories separate session-level and activity-level data for customers and agents. A break is not a customer contact segment and not a call session metric; it is a state transition or activity performed by the agent. Agent Activity Record is the repository that captures detailed agent activity state events, idle codes, availability changes, and similar state-driven information. Customer Session Record summarizes the end-to-end customer session. Customer Activity Record captures customer/contact activities such as call segments and handling details. Agent Session Record summarizes an agent's signed-in session, but it does not provide the granular count of times an agent entered a break state. For counting how many times an agent went on a break, the report needs the activity-level state records, not the session summary. Reference: Cisco Help, Cisco Webex Contact Center Analyzer User Guide; Webex Contact Center Analyzer Stock Reports.

The least privileged role that satisfies both capabilities is Supervisor. The user must participate in telephone campaigns and must also speak to an agent without the customer hearing, which is supervisor whisper coaching. Standard and Premium Agent roles can handle assigned interactions based on license capabilities, but they do not provide supervisory monitoring, whisper coaching, barge-in, or team oversight controls. An Administrator role would provide much broader configuration authority than needed, violating the least-privilege requirement. Cisco's Contact Center licensing and role model separates agent capabilities from supervisor capabilities; Premium Agent adds additional digital and reporting capabilities, while Supervisor adds monitoring and assistance functions. Whisper coaching is specifically a supervisor call-monitoring function, not a standard agent function. Because the scenario does not require tenant configuration, user provisioning, routing setup, or recording policy administration, Administrator is excessive. Supervisor is the minimal role that gives the monitoring feature while also supporting campaign participation. Reference: Cisco Help, Manage access in Webex Contact Center; Webex Contact Center Data Sheet.

The Exclusive multimedia profile type is used when an agent must handle only one interaction at a time. Cisco's multimedia-profile model controls how many simultaneous contacts an agent can receive and how different media types are blended. A blended profile can allow multiple channels, and a blended real-time profile is designed for voice plus real-time digital interactions under concurrency rules. Voice Only would restrict agents to voice and would not satisfy a team that handles voice, email, and chat. The scenario is not asking to remove digital channels; it says a few agents cannot focus on multiple interactions. Exclusive solves that by allowing the agent to work one contact regardless of channel, preventing simultaneous assignments that could reduce quality or agent performance. This is a tenant and desktop-experience configuration decision, not a queue routing problem. The agent can still be eligible for the configured channels, but the desktop capacity model keeps workload to one active interaction. Reference: Cisco Help, Webex Contact Center Setup and Administration Guide; Manage desktop profiles.