Implementing Cisco Collaboration Cloud Customer Experience 300-830 Exam Questions

RONA must expire before voicemail answers. Cisco's voice channel guidance for Webex Contact Center and Webex Calling explains that, when agents use Webex Calling endpoints, unanswered contact center calls should be redirected back to the contact center queue before the endpoint's voicemail rule answers. If voicemail answers first, the customer call is effectively consumed by the agent's mailbox instead of being requeued for the next available agent. Setting the RONA timer shorter than the voicemail ring interval causes the contact center platform to classify the offered contact as no-answer and requeue it. Direct calls to the agent still follow the normal Webex Calling voicemail configuration, so voicemail continues to work for non-contact-center calls. Making RONA longer than voicemail is exactly the wrong direction. Two lines may help operational separation but are not required for this behavior. Disabling voicemail would break the stated requirement that direct unanswered calls roll to voicemail. Reference: Cisco Help, Set up voice channels for Webex Contact Center. 

Bridged Transfer is the correct node because the requirement is not simply to send the caller away; the administrator must connect the caller to an external IVR while keeping Webex Contact Center call control and then resume the original flow. Cisco's Flow Designer documentation distinguishes Bridged Transfer from Blind Transfer. A blind transfer is terminal: once the call is transferred to the external number, the flow ends and the original flow logic no longer controls the interaction. A Bridged Transfer, by contrast, is designed for scenarios where the caller is temporarily connected to an external destination and then returned to the flow after the external interaction completes. An HTTP Request node is only for data exchange with an external service and cannot bridge media to an IVR. A GoTo node is internal flow navigation and cannot connect the caller to an external IVR. The call-control behavior in the scenario is therefore specifically the Bridged Transfer use case. Reference: Cisco Help, Build and manage flows with Flow Designer; Understand Routing and Queueing in Webex Contact Center.

Out dial 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 Out dial is enabled on the desktop profile, the administrator selects the outdial entry point and, where applicable, the Out dial 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.