Genesys GCX-GCD - Genesys Cloud CX: Developer Certification

A query endpoint provides real-time access to the most up-to-date data and returns the requested information immediately. This is ideal for scenarios where the user requires immediate responses.

A jobs endpoint, on the other hand, is designed for scenarios where bulk export of data is required. It processes requests asynchronously and provides a response when the export is complete, making it suitable for larger data sets that don't require an immediate response.

In Genesys Cloud CX, a notification channel remains active for 24 hours. If the channel is not renewed within this period, attempts to use it will result in a 400 error. To maintain an active channel beyond 24 hours, you must resubscribe to the topics before the channel expires. This can be achieved by sending aPOSTrequest to/api/v2/notifications/channels/{channelId}/subscriptionswith an empty array as the body, effectively extending the channel's validity for another 24 hours. Implementing a recurring task to perform this resubscription every 23 hours is recommended to ensure continuous operation.

Automatic Call Distribution (ACD) reduces wait time by efficiently routing incoming calls to the next available and most appropriate agent, minimizing idle time and ensuring quicker response for each customer.

In Genesys Cloud CX, a fatal question on an Evaluation Form is designed to reflect a critical requirement. If the evaluator scores “No” on such a question, the agent receives a zero for the entire evaluation, regardless of other responses.

In Genesys Cloud CX, if a WebSocket connection is closed due to any issue, events are not automatically queued and sent once the WebSocket is reopened. Instead, the client is responsible for detecting the disconnection and re-establishing the connection. Upon reconnection, the client must resubscribe to the necessary topics to continue receiving events. Any events that occurred during the downtime are not automatically resent; therefore, implementing a robust reconnection and resubscription strategy is crucial to ensure no critical events are missed.

In Genesys Cloud CX, access to telephony features, including the ability to make and receive calls, is controlled by roles and permissions. If the required telephony-related permissions are not assigned to the user's role, the phone call icon will not appear in the interface.

In Genesys Cloud CX, users require administrative privileges to access and manage organization settings. This access is typically granted through the Admin role, which provides the necessary permissions to view and modify organization-wide configurations. Agent and Supervisor roles do not inherently possess these permissions.

In the Genesys Cloud CX Notifications API, ping/pong messages are used to check the healthof the WebSocket connection. These messages help detect if the socket is still open or if it has been dropped, enabling appropriate client-side handling.

This statement is not true. In Genesys Cloud CX, numbering plans (or dial plans) can be created automatically using default settings or manually configured as needed. They are flexible and can be modified based on organizational requirements, but manual creation is not mandatory.

When contacting the Genesys Cloud CX support team, you represent your organization using the Organization ID, which uniquely identifies your Genesys Cloud instance and helps support quickly access your account details.