CCNA Omni Channel Questions

Status-Based capacity assigns unit weights per work item type, so Cases can carry heavier weights than Leads. When an agent's case load consumes their capacity threshold, Omni-Channel withholds new Leads until the workload drops, directly meeting the stated requirement.

Agents can be assigned to multiple queues and can possess multiple skills. Omni-Channel evaluates both queue membership and skills when determining which agents are eligible for a work item, depending on the routing configuration. This allows for flexible routing that considers both organizational structure and expertise. This statement is true and highlights the complementary nature of the two models.

A Routing Configuration only takes effect when linked to the Salesforce Queue that holds the work. Attaching it to the tier-2 case queue causes Omni-Channel to apply that configuration's routing model and capacity settings when cases enter the queue.

Presence Statuses are assigned through Profiles or Permission Sets, which control which statuses each group of agents can select. This satisfies the constraint of making specific statuses available only to defined agent groups rather than the entire org.

Flow routing failures often stem from the wrong flow version being active, so verifying that the active version's Route Work action contains correct parameters ensures the intended routing logic actually executes rather than an outdated or misconfigured version.

Skills-Based Routing matches on an all-skills basis: the routing engine requires one agent to possess every skill attached to the work item. Availability of separate agents holding individual skills is irrelevant, so multi-skill work items remain queued until a single fully-qualified agent is free.

Overflow Routing on the Routing Configuration directly satisfies the push-timeout constraint: when an agent fails to accept a high-priority chat within the push timeout, the routing configuration reassigns it to the designated secondary queue. This is the native mechanism for redirecting unaccepted work, so no queue-level or Omni-Channel flow logic is required.

The Omni-Channel Supervisor's Agents tab exposes each agent's current status and the elapsed duration in that status, refreshed in real time. This directly satisfies the requirement to see how long an agent has remained in 'On Break', which standard reports cannot surface.

Setting the Case service channel capacity to 1 ensures that an agent can only work on one case at a time. This aligns with the requirement that agents handle only one case concurrently. If the capacity were higher, agents could be assigned multiple cases simultaneously, which is not desired. Therefore, this configuration is required to enforce the single-case limit.

Routing Configuration assigns priority values to each work item type, letting you weight cases above chats so high-priority web-to-case submissions are routed first. Adjusting the priority field there directly satisfies the stem's constraint that cases outrank lower-priority chat requests in Omni-Channel routing.

The Route Work action element routes a work item to a queue or agent, and its routing attributes let the flow attach skills derived from VIP status. This satisfies the stem's requirement to assign specific skills during evaluation of incoming chat requests, which generic flow elements cannot do.

Rules define the criteria mapping case fields, such as account region and product type, to required skills. Without at least one active Skills-Based Routing Rule, the routing engine has no logic to evaluate, so cases cannot be matched to skilled agents.

Presence status availability is controlled through the user's profile and permission sets, so assigning statuses this way lets agents in different locations or queue assignments see only the statuses relevant to their role, satisfying the requirement for location- and queue-dependent presence options.

Every Service Channel definition requires a target Salesforce Object, such as Case, Lead, or custom object, because Omni-Channel routes work items from that object's records. Without specifying the object, the channel cannot determine which records to route to agents.

Presence Configurations define which Presence Statuses are available to agents. By assigning a Presence Configuration to a profile or permission set, you control the set of statuses agents can choose from. This directly meets the requirement of limiting agents to predefined statuses like 'Available - Cases' and 'Busy'. It is the correct configuration object for this purpose.

Routing Configurations set the queue's routing model and priority, determining the exact sequence work items are pushed to agents. They satisfy the stem's ordering constraint by defining priority fields and units of work, unlike presence status or capacity, which govern availability rather than delivery order.

Presence Statuses let administrators define which service channels each status makes an agent available for. A custom status can enable chat and phone while leaving email cases excluded, giving agents manual control over simultaneous live-channel capacity.

Closing the work item tab or session in the console ends the agent's active work, which triggers Omni-Channel to release that agent's capacity immediately. This satisfies the stem's requirement that capacity be freed the moment a chat finishes, rather than waiting for wrap-up or a timeout to expire.

When an agent accepts a chat and then loses connection, Omni-Channel's drop timeout setting governs the work item. Once that timeout elapses without agent activity, the item is automatically returned to the queue for reassignment, satisfying the routing configuration's drop timeout behaviour.

Tab-Based capacity counts each open case tab and chat session against the agent's capacity of 4; with four items already consumed, the new chat cannot be routed and waits in queue until a tab closes.

Skills-Based Routing evaluates the skills required by each work item against agents' skill profiles, then routes to agents whose profiles match. This differs from queue-based routing, which relies on queue membership rather than attribute matching to select the recipient.

The Queues Backlog tab shows real-time queue metrics including the oldest work item's wait time, exposing how long the longest-waiting item has been queued. This satisfies the requirement for real-time supervisor visibility into queue backlog age.

Skills-Based Routing matches work to agents by skill, so assigning French and advanced-tier skills routes VIP cases only to qualified agents. Rules or an Omni-Channel Flow can apply multiple skills simultaneously, meeting both language and certification constraints.

A Queue Routing Configuration lets the administrator define routing settings for a specific queue, including a priority field that orders work items in that queue. By selecting the Case Priority field, High-priority cases are offered before Low-priority cases in the same queue. This is exactly the within-queue ordering the scenario requires.

Presence statuses define which channels an agent receives work from. Creating a status with Chat enabled and Phone excluded lets agents take chat work items while Open CTI phone calls are blocked, matching the stem's temporary requirement.

The routing configuration passes the record ID, such as the Case ID, into the Omni-Channel Flow so the interview can identify and route the correct work item. Without this identifier the flow cannot resolve which record to push, satisfying the stem's routing-initiation constraint.

Agent Work object historical data records each work item's lifecycle, including accept, transfer and close timestamps. It supplies the utilisation and performance detail the administrator needs, satisfying the requirement to analyse Omni-Channel performance across agents and channels.

Omni-Channel Supervisor gives managers a real-time console showing queue metrics, agent capacity and workload, and active work items, enabling live intervention. This satisfies the stem's requirement for the primary function: monitoring rather than historical reporting or routing configuration.

Routing Configurations define which queues and how many work items an agent can receive. If the 'Available - Cases' presence status is not linked to a Routing Configuration that includes the case queue, Omni-Channel has no work to route to the agent. This is the most likely missing link after permissions and presence statuses are confirmed.

Adding the Omni-Channel utility through Lightning App Builder places it in the Console App's utility bar, the fixed footer region that persists across every console tab. This satisfies the stem's requirement that agents access Omni-Channel from inside the Service Console itself, rather than a separate app or page layout.

Push Timing governs the duration an Omni-Channel work offer remains on an agent's screen before the routing system withdraws it and marks it as missed, directly controlling the offer timeout constraint described in the stem.

An inactive Service Channel stops Omni-Channel from routing any work items tied to that channel's object, regardless of agent presence or queue membership. Reactivating the channel restores routing, confirming the channel itself is the routing gate.

Omni-Channel Supervisor provides a real-time dashboard of agent workloads, average handle times and open work items, and can be embedded directly in the Service Console utility bar, satisfying the requirement to view metrics without navigating away.

Skills-Based Routing requires skills to be defined and assigned to agents. The routing configuration must be set to use Skills-Based Routing and then assigned to the work item (e.g., via case record type or queue). This ensures that cases are routed to agents with the matching language skill. This is the standard configuration for skill-based routing.

Overflow Routing triggers on queue-level thresholds: maximum wait time and maximum queue size. When either is exceeded, Omni-Channel diverts new work to a secondary queue, satisfying the stem's high-volume scenario by preventing unbounded waits. Capacity here means queue depth, not agent presence status.

Skills-Based Routing must be enabled in Setup before any routing rules can be created; the feature toggle gates access to the rule builder. Without it, the mandatory prerequisite for matching product-tier certifications cannot be configured.