300-830 Practice Questions

Webex App state synchronization is configured under the Desktop > Webex App configuration area, where the administrator enables Webex App integration, enables state synchronization, and maps Webex availability states to Webex Contact Center idle codes. The requested behavior is specific: when an agent is on a non-contact-center Webex App call, Agent Desktop must move to the configured WebexAppCall idle state. Cisco's documentation identifies the Webex availability state as On a Call for this situation, not Outgoing Call. Therefore, On a Call must be mapped to the WebexAppCall idle code. The idle code must already exist in Webex Contact Center; it does not need to be added to a desktop layout, because idle codes are assigned through desktop profile configuration rather than layout JSON. The option that places state synchronization under Collaboration in the desktop profile does not match the stated Control Hub path. The three required actions are enabling the Webex App integration, mapping On a Call, and enabling State Synchronization. Reference: Cisco Help, Manage desktop profiles; Integrate Webex Contact Center CRM Connector for Microsoft Dynamics 365, state synchronization section.

A supervisor's recording management role is operational quality management, not platform retention administration. Cisco documents supervisor recording workflows around locating and reviewing interactions, filtering recording lists based on criteria, and tagging recordings for later review or quality processes. Those tasks support team compliance and coaching without giving the supervisor destructive or tenant-wide policy authority. Retention policy management is a governance-level setting controlled by administrators or compliance roles, not ordinary supervisors. Permanently deleting recordings is similarly a high-risk compliance operation and would not be granted as a standard supervisor capability in a least-privilege model. Searching for agent interactions, filtering the list of recordings, and applying descriptive tags are the correct day-to-day recording management activities. They let the supervisor find relevant calls, classify them, and support quality monitoring while preserving administrative separation of duties. Reference: Cisco Help, Supervise your agents and teams; Webex Contact Center Data Sheet; Webex Contact Center Setup and Administration Guide.

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.

See mapping below

After 180 seconds, agents from other sites must be able to take the call: Create agent-based teams; Add a Call Distribution Group that uses the remaining agents' team after the specified delay.

Only agents with a language ranking of > = 5 can take the call: Create a skill profile and set Type to Proficiency in the Skill Definition settings; Define skill requirements for the Queue activity where the caller's spoken language is > = 5.

The completed mapping follows Cisco's two different routing constructs. For the 180-second requirement, the call first targets the local or primary agents and then expands after a delay. Cisco documents Call Distribution Groups as the method used by non-skill queues to define levels of teams that become eligible after configured intervals. That is why an agent-based team plus a delayed call distribution group is the right match; a capacity-based team is used for unmanaged destinations and does not represent normal agent routing. The language-ranking requirement is different. It must be handled through skills and proficiency. Cisco documents skill definitions, skill profiles, and queue skill requirements as the pieces used to limit routing to agents with matching skill values. Therefore the skill definition must use Proficiency and the Queue activity must define the language requirement of at least 5. A Best Available Agent queue alone is insufficient unless the skill requirement is actually applied. Reference: Cisco Help, Understand Routing and Queueing in Webex Contact Center; Create queues and configure routing patterns.