300-830 Practice Questions

Repository: Customer Session Record.

Segment Data: Contact Start Timestamp and Queue Duration.

Profile Variable: ANI, Agent Login, and Final Queue Name.

The report needs one row for each call, the caller's number, queue timing, and final agent. Cisco Analyzer separates data into repositories and data classes. Customer Session Record is the proper repository because it represents the end-to-end customer contact session and contains the contact session identifier needed for a list of calls. Contact Start Timestamp and Queue Duration are segment-level metrics that describe when the contact began and how long it waited in the queue. ANI, Agent Login, and Final Queue Name are profile or reporting variables that identify the caller's number, the final handling agent, and the queue outcome. Burn Index, abandoned service-level count, and idle code fields are not part of this requested report. Agent Activity Record would be appropriate for agent state history, but this report is customer-contact centered. Customer Activity Record is useful for detailed contact activities, but the drag-and-drop target asks for the repository and field groupings shown. Reference: Cisco Help, Cisco Webex Contact Center Analyzer User Guide; Webex Contact Center Analyzer Stock Reports.

userId: $.data.users[?(@.phoneNumber == '+1 (555) 123-4567')].userId

currentPage: $.data.currentPage

The JSONPath mapping must match the structure shown in the API response. The userId variable is not a simple top-level property; it sits inside the users array. The expression must filter the users array for the object whose phoneNumber equals +1 (555) 123-4567 and then return that object's userId. That is why the filtered JSONPath expression using $.data.users[?(@.phoneNumber == '+1 (555) 123-4567')].userId is the correct mapping. The currentPage variable is directly under data, so the correct expression is $.data.currentPage. Expressions such as $.currentPage miss the data wrapper, and $.data.currentPage.number assumes currentPage is an object with a number property, which the response does not show. $.data.user[0] .userId is also wrong because the array name in the response is users, not user, and it would take the first user rather than the matching phone number. Reference: Webex Connect Help, Custom Node Integration; Webex Connect flow data parsing guidance.

A chat digital channel handled by Webex Contact Center agents needs a channel object of type Chat and an asset assigned to that channel. Cisco's digital channel setup model uses assets to represent external channel identities, such as a web chat asset, email asset, SMS asset, or social asset. The channel then connects that asset to Webex Contact Center routing so the conversation can be created, queued, and delivered to agents. Assigning a phone number is relevant to voice or SMS-style channel designs, not to a Web Chat asset. Creating an Email channel or Social Channel would build the wrong media type and would not make a chat widget route as chat. The two required steps therefore match the platform object model: create a channel with Chat as the channel type and assign the appropriate asset to that channel. Once that is done, flows and Queue Task nodes can route the chat to Webex Contact Center agents. Reference: Cisco Help, Set up digital channels in Webex Contact Center; Webex Connect Help, Livechat.

Cisco protects Webex Contact Center APIs with rate limiting per client ID so that one application cannot exhaust shared platform capacity. The current default limit represented in this question is 30 requests per second and 1800 requests per minute for a given client I

D.