Free GCP-GC-REP Practice Test Questions and Answers (2026)

Average Speed of Answer (ASA) is a standard contact center metric that measures the average time an interaction, such as a call or chat, spends waiting in a queue before it is answered by an agent. This calculation begins when the interaction is placed in the queue and ends when an agent accepts it. ASA is a critical Key Performance Indicator (KPI) used to gauge the efficiency of a contact center's routing and staffing, directly impacting the customer's waiting experience. A lower ASA generally indicates better service accessibility and responsiveness.

A. AHT (Average Handle Time) measures the total duration of an interaction after it is answered, including talk time, hold time, and after-call work.
C. ACW (After Call Work) is the time an agent spends on tasks related to an interaction after it has concluded, not the wait time before.
D. ATT (Average Talk Time) measures only the average duration of the active conversation between the agent and the customer during an interaction.

1. Genesys Cloud CX Documentation, "Metrics definitions": This official glossary defines Average Speed of Answer (ASA) as "The average time an interaction waits in a queue before an agent answers it. Formula: Total time to answer / Number of answered interactions". It also provides distinct definitions for AHT, ACW, and ATT. (Accessed from the Genesys Cloud CX Resource Center).

2. Genesys Cloud CX Documentation, "Queues Performance Summary view": This document details the metrics available in performance views, explicitly listing and defining ASA as the average wait time in queue before an agent answers. (Accessed from the Genesys Cloud CX Resource Center, section on Reports, Views, and Dashboards).

The Agents Interactions Detail view is the most effective tool for this purpose. It provides a granular list of all interactions handled by agents. Supervisors can apply filters for specific agents, one or multiple queues, and the particular wrap-up code(s) of interest. This allows them to isolate and analyze the exact interactions in question, review metrics like handle time and after-call work time, and listen to recordings to identify the root cause of any performance issues associated with that wrap-up code.

A. Agents Wrap-Up Interval Detail: This view name does not correspond to a standard Genesys Cloud report. Views are typically either detail-oriented (listing individual items) or interval-based (aggregating data over time), not both in this manner.
B. Agents Schedule Detail: This view is part of Workforce Management and focuses on schedule adherence and agent activity, not the outcomes or classifications (like wrap-up codes) of specific customer interactions.
C. Agents Wrap-Up Detail: While a wrap-up view exists, it aggregates data by wrap-up code, showing total counts and average times. It does not provide the necessary drill-down to individual interactions to investigate specific performance issues.

1. Genesys Cloud CX Resource Center, "Interactions view": This document describes the Interactions view, which is the primary tool for this task. It explicitly states, "The Interactions view displays details about interactions that occurred during the selected time period. You can filter the view by... queues, users... wrap-up codes." This directly supports the use of this view to isolate interactions based on the criteria in the question.

Source: Genesys Cloud CX Documentation, "Interactions view".

2. Genesys Cloud CX Resource Center, "Wrap-up codes performance view": This document explains that the Wrap-up codes performance view "shows you metrics about your wrap-up codes," such as the number of interactions per code. This confirms that this view provides aggregated data, making it less suitable for investigating individual interaction performance than the Interactions view.

Source: Genesys Cloud CX Documentation, "Wrap-up codes performance view".

Running reports during peak operational hours places a significant load on the Genesys Cloud platform, as the system is concurrently processing live interactions and agent activity. This competition for resources leads to increased report execution times and a higher probability of timeouts or failures. Similarly, when multiple users individually run and save the same report, it generates redundant, resource-intensive queries. This practice unnecessarily multiplies the system load, degrading performance for all users and increasing the likelihood of report failures, rather than running the report once and sharing the results.

A. Adjusting report parameters to include fewer entities is a best practice to reduce data processing load, thereby decreasing runtime and failure risk.
C. Reviewing and using scheduled reports is a recommended strategy to manage system load by running reports during off-peak hours, which improves performance.

1. Genesys Cloud CX Resource Center, "Reporting and analytics best practices."

For Answer B: The section "Run reports during off-peak hours" states, "To improve performance, run reports that include a large amount of data during off-peak hours... Running large reports during peak business hours can cause slow performance."

For Answer D: The section "Share reports" advises, "To avoid running the same report multiple times, run the report once and then share it with other users." This implies that having multiple users run the same report is an anti-pattern that increases system load.

For Incorrect Option A: The section "Limit the amount of data in your reports" recommends, "When you create a report, limit the amount of data that the report includes... For example, create reports that include fewer agents, queues, or interactions."

For Incorrect Option C: The section "Schedule reports to run automatically" recommends this practice to ensure reports are run efficiently, often during off-peak times.

An abandoned interaction is one where the customer disconnects while waiting in a queue before an agent can answer, which is a fundamental contact center metric. Genesys Cloud provides a suite of standard, pre-defined reports, and the metrics available within each specific report type are fixed by the system. Users cannot add or remove metrics from these templates. The process for generating these reports involves navigating to the Reports section, creating a new report instance from a pre-defined list, and then configuring its specific parameters, such as the date range, queues, or agents to include, before running it.

A. A queue report tracks all interactions that enter a queue, including those that are abandoned or flow out, not just those handled by an agent.
C. This statement is too general. While agent reports focus on agent activity, the term "any interactions an agent worked with" is imprecise; for example, consultation interactions are tracked differently from interactions an agent directly handles.

1. Genesys Cloud CX Resource Center, "Metrics definitions": The metric nAbandon is officially defined as "The number of interactions that entered a queue but disconnected before an agent answered." This directly supports option B.

2. Genesys Cloud CX Resource Center, "About reports": This document states, "Genesys Cloud includes several predefined reports that you can use to get historical data about your contact center." This confirms that reports are based on pre-defined templates with a fixed set of metrics, supporting option D.

3. Genesys Cloud CX Resource Center, "Create and run a report": The procedure for generating a report is outlined as: "1. Click Performance > Reports. 2. Click Create Report. 3. In the Create Report panel, select the report you want to create... 4. Configure the report...". This workflow directly validates option E.

4. Genesys Cloud CX Resource Center, "Queue Performance views and reports": The documentation for queue reports lists metrics such as Offered, Answered, Abandon, and Flow Out, demonstrating that they count more than just interactions handled by an agent. This invalidates option A.

In Genesys Cloud CX reporting, an incoming call that enters an ACD queue is formally counted under the "Offered" metric (API name: nOffered). This metric is fundamental to contact center analytics as it represents the total number of interactions presented to a specific queue for handling by agents. It serves as the primary measure of customer demand or workload for that queue. While terms like "Inbound" or "Incoming" describe the call's direction, "Offered" is the specific, quantifiable metric used in performance views and reports to track this activity.

A. Inbound: This term describes the direction or type of interaction (e.g., inbound vs. outbound) but is not the specific metric for a call entering a queue.
B. Incoming: This is a general, descriptive adjective, not the formal name of a metric used in Genesys Cloud CX reports.
D. Calls Received: This term is ambiguous. The closest official metric, nReceived, counts interactions answered by an agent, which is a subset of the total calls offered to the queue.

1. Genesys Cloud CX Resource Center, "Metrics definitions": The official glossary defines the metric nOffered as "The number of interactions that entered a queue." This directly confirms that "Offered" is the correct term for an interaction being presented to the system for handling. (Search for "nOffered" in the metrics definitions page).

2. Genesys Cloud CX Resource Center, "Queues Performance Summary view": This official documentation describes the standard view for monitoring queue activity. The "Offered" column is a primary metric displayed, defined as "The number of interactions offered to the queue." This demonstrates the term's practical application in standard reports. (See the "Columns" section for the Queues Performance Summary view).

3. Genesys Cloud CX Resource Center, "Interaction details view": In the lifecycle of an interaction, the journey shows a segment where the interaction is "Offered" to a queue before it is answered, abandoned, or flows out. This further solidifies "Offered" as the specific event name. (See documentation on "View an interaction's details").

The User Status Detail report in Genesys Cloud is designed to provide a granular breakdown of the time an agent spends in various statuses throughout a specified interval. This includes key performance indicators related to their activity while on queue. The report specifically tracks the total duration an agent was in the "Interacting" state (actively handling a communication), the "Idle" state (on queue and available, but waiting for an interaction), and the "Not Responding" state (being alerted for an interaction but failing to answer it).

The "False" option is incorrect because the primary purpose of the User Status Detail report is to provide exactly this level of detail about an agent's time allocation, including their queue-specific activities. Official documentation explicitly lists these metrics as available columns within the report.

1. Genesys Cloud Resource Center. (n.d.). User status detail view. Retrieved from https://help.mypurecloud.com/articles/user-status-detail-view/

Section: Available columns.

Details: This official documentation page lists the metrics available in the User Status Detail view. It explicitly includes:

Interacting: "The total time that the agent spent in the Interacting status."

Idle: "The total time that the agent spent in the Idle status."

Not Responding: "The total time that the agent spent in the Not Responding status."

2. Genesys Cloud Resource Center. (n.d.). Agent status and presence. Retrieved from https://help.mypurecloud.com/articles/agent-status-and-presence/

Section: On Queue statuses.

Details: This document defines the core agent statuses that are tracked and reported on. It clarifies that "Idle" means an agent is on queue and ready for interactions, "Interacting" means the agent is handling a communication, and "Not Responding" is a specific routing status when an agent does not answer an offered interaction. The User Status Detail report is the tool used to aggregate time spent in these defined states.

The Genesys Cloud CX agent interface is designed to provide a persistent and personalized user experience. When an agent customizes the interaction view by resizing panels or adjusting column widths, these changes are automatically saved to their user profile. This ensures that the customized layout is maintained not only when the agent navigates to other views and returns but also across subsequent login sessions.

The "False" option is incorrect because it misrepresents the functionality of the Genesys Cloud CX user interface. The platform is explicitly designed to save user layout preferences to enhance usability and efficiency, eliminating the need for agents to reconfigure their workspace repeatedly.

1. Genesys Cloud CX Resource Center, "Customize the agent interface."

Reference Section: Main body text.

Content: The documentation states, "You can customize the agent interface by resizing the panels. Genesys Cloud CX saves your changes, so that the next time you log in, the panels appear as you last configured them." This confirms that changes are persistent even across logins, which by extension means they persist when navigating between views within a single session.

URL: https://help.mypurecloud.com/articles/customize-the-agent-interface/

2. Genesys Cloud CX Resource Center, "Interactions panel."

Reference Section: "Customize the interactions panel" subsection.

Content: This section details specific customizations within the interactions panel, noting, "You can also customize the interactions panel by changing the width of the columns in the interaction list. Genesys Cloud CX saves your changes." This reinforces the principle that user-initiated layout changes are saved and persist.

URL: https://help.mypurecloud.com/articles/interactions-panel/

The statement is false. In Genesys Cloud CX, when a user manually deletes a report from the Reports view, the action is permanent. The report is removed from the system and cannot be recovered or downloaded. There is no "archived list" for manually deleted reports from which a user can retrieve them.

The "True" option is incorrect because it misrepresents the report deletion process in Genesys Cloud CX. The platform treats manual deletion as a final, irreversible action, not as a move to an accessible archive.

1. Genesys Cloud CX Resource Center, "Reports view" article.

Section: Delete a report

Content: The documentation explicitly states: "When you delete a report, Genesys Cloud removes it from the list. You cannot recover a deleted report." This confirms that the deletion action is permanent and does not move the report to a recoverable or downloadable archive.

Reference Link: https://help.mypurecloud.com/articles/reports-view/ (Navigate to the "Delete a report" section).

The statement is incorrect. In Genesys Cloud CX, the "Reports" feature is specifically designed to provide historical data and analytics. It allows users to analyze past contact center performance, agent activity, and interaction trends over specified date ranges. Real-time information is monitored through separate tools, primarily the Performance Dashboards and dynamic Views.

The statement "True" is incorrect because it fundamentally misrepresents the purpose of the reporting function within Genesys Cloud. While the platform offers robust real-time monitoring capabilities, these are delivered through dashboards and views, not the historical "Reports" feature. Conflating these two distinct functions is a misunderstanding of the platform's architecture.

1. Genesys Cloud CX Resource Center, "Reports, views, and dashboards overview": This document explicitly distinguishes between the tools. It states, "Reports provide a historical, aggregate view of data... Use reports to see long-term trends and gain deep insight into your contact center performance." It contrasts this with dashboards and views, which are used for "real-time monitoring."

Source Location: Genesys Cloud CX Resource Center > Reporting and analytics > Reports > Reports, views, and dashboards overview.

2. Genesys Cloud CX Resource Center, "About reports": This page clarifies the nature of the data provided in reports. It explains, "Genesys Cloud reports provide historical data about your contact center's performance. You can view default and created reports from the Reports page." This directly contradicts the claim that reports provide only real-time information.

Source Location: Genesys Cloud CX Resource Center > Reporting and analytics > Reports > About reports.

3. Genesys Cloud CX Resource Center, "Agent performance summary report view": The documentation for any specific report, such as the Agent Performance Summary, demonstrates its historical nature by detailing the requirement to select a date/time interval for the data. The first step in running such a report is to "Click the Interval box to select a date and time range," confirming its function is to analyze past data, not current, real-time activity.

Source Location: Genesys Cloud CX Resource Center > Reporting and analytics > Reports > Available reports > Agent performance summary report view.

The Agent Activity Summary Report is designed to provide a comprehensive overview of how agents spend their time while logged into Genesys Cloud. This report specifically tracks and aggregates the duration an agent spends in various statuses, including Idle (available but not engaged in an interaction) and Not Responding (failing to answer an alerting interaction). It summarizes this data, allowing supervisors to measure non-productive time and agent availability effectively.

A. The Agent Metrics Report focuses on interaction-specific performance data like average handle time and after-call work, not the duration of agent presence statuses.
C. The Agent Login-Logout Details Report primarily tracks session information, such as login and logout timestamps, and total time logged on, not a breakdown of activity statuses.
D. The Agent Quality Details Report is part of Quality Management and provides data on agent evaluations, scores, and coaching, which is unrelated to agent status times.

1. Genesys Cloud CX Resource Center. (n.d.). Agent Activity Summary Report. Retrieved from Genesys Cloud documentation.

Reference Point: The document states, "The Agent Activity Summary report shows a summary of agent activity, including the time that agents spent logged on, on queue, interacting, and in other statuses." The "other statuses" category explicitly includes Idle and Not Responding.

2. Genesys Cloud CX Resource Center. (n.d.). Reports view. Retrieved from Genesys Cloud documentation.

Reference Point: The overview of available reports in this section clearly distinguishes the purpose of each report type. It describes the Agent Activity Summary as tracking time in statuses, while describing the Agent Metrics report as focusing on interaction handling metrics, confirming the distinct functions of options A and B.