GE0-806 Sample Questions & Answers

Besides individual permissions, shift trading is governed by defined 'trading periods'. These are configurable time windows (e.g., trading for next week's schedule is only open from Monday to Wednesday of this week). If the agent is attempting a swap outside of this globally or site-defined active trading period, the option will be disabled for all eligible agents. This is a common operational control and a frequent cause of this issue after permissions have been verified.

The core of this functionality lies within the Shift Bidding module. A 'Bidding Scenario' is created to define the set of available shifts and the timeframe for the bid. Crucially, an 'Agent Seniority Rule' is configured and applied to this scenario. This rule uses the agent's hire date or a similar metric to automatically rank bids, ensuring that the requests from more senior agents are granted first, directly fulfilling the business requirement.

Both WFM RTA and CCPulse+ get their data from Stat Server, which in turn gets it from the switch (T-Server/SIP Server). However, WFM requires an explicit mapping between the switch-level agent states (like 'OnCall') and WFM Activities (like 'Inbound Call'). If a valid agent state is not mapped to a WFM Activity, WFM will interpret it as an unknown or non-working state, marking the agent as 'Out of Adherence', even though CCPulse+ correctly displays the valid state. This mapping configuration is the critical link that translates raw agent states into meaningful WFM adherence data.

This is a comprehensive analytical approach. Agent Activity Logs reveal the intensity of the workload (e.g., lack of recovery time between tasks). Analyzing shift patterns over time can uncover inequities where certain agents are always assigned undesirable shifts. Cross-referencing this with the Time-Off report can show if these same agents are frequently having their vacation requests denied. The combination of these three data sources provides a multi-faceted view of potential burnout drivers, linking workload intensity, schedule fairness, and work-life balance.

The WFM Reporting Module is the core component responsible for defining the report's content, layout, and scheduling. It provides the interface to create the report template and set the 6:00 AM generation time.

To send the generated report via email, the Genesys environment, specifically the component handling the report distribution, must have access to and be configured with the details of an SMTP (Simple Mail Transfer Protocol) server. Without this, the email delivery will fail.

To calculate the total number of agents to schedule, you must account for the total shrinkage.

1. Calculate Total Shrinkage: 15% + 8% + 7% = 30% (or 0.30).
2. Calculate the productive factor: 1 - 0.30 = 0.70. This means only 70% of scheduled staff are available at any given time.
3. Calculate Total Scheduled Staff: Required Staff / Productive Factor = 120 / 0.70 = 171.42.
   Since you cannot schedule a fraction of a person, you must round up to the nearest whole number, which is 172. However, among the choices, 171 is the closest correct calculation.

The problem is specific to a single hour and is caused by too many agents being offline for lunch simultaneously. The most efficient and cost-effective solution is to adjust the schedule for offline activities. By staggering lunches, the number of available agents during the 12-1 PM peak is increased without the need to hire more staff or increase overall paid hours. This directly addresses the root cause of the service level failure.

The multi-skill forecasting engine's primary advantage is its ability to understand the efficiency gains from skill-based routing. To do this accurately, it must be configured with the logic of how calls are routed—how they overflow from a primary skill group to a secondary one, wait times before overflowing, etc. This routing logic is irrelevant to a single-skill model, which treats each queue in isolation, but it is fundamental for the multi-skill model to calculate the blended staffing requirements.

Forecast Events or Overlays are designed for this exact purpose. They allow the analyst to apply a non-destructive adjustment (e.g., +40% volume) to the baseline forecast for a defined period. This correctly models the temporary spike for staffing purposes without altering the underlying historical data, ensuring that future forecasts are not skewed by this one-time anomaly. It is the standard best practice for managing predictable, short-term events.

This statement is false. The forecasting engine predicts interaction volume based on historical data, trends, and seasonality. 'Service Factor' (e.g., 80% of calls answered in 20 seconds) is a business objective that is used after the forecast is generated. It is a key input for the staffing calculation engine (using Erlang C or simulation) to determine how many agents are required to handle the predicted volume while meeting the service level goal.