GCX-SCR Genesys Cloud CX: Scripting Certification Questions and Answers

Files uploaded to a workspace in Genesys Cloud CX cannot be shared with non-members of the Genesys Cloud organization. Workspace files are restricted to members within the organization for security and collaboration purposes, preventing external access to sensitive or proprietary information. Thus, sharing files with users outside the Genesys Cloud CX organization is not possible directly from the workspace.

=========================

To add a scheduled callback option to your script in Genesys Cloud CX, the components that need to be bound together are the Date/Time Input and a Button .

Date/Time Input : This component allows the agent or customer to select a specific date and time for the callback.

Button : This component is used to submit the selected date and time, triggering the scheduling of the callback.

These two components work together to enable the scheduling functionality within the script, allowing for the seamless setup of callbacks based on the user ' s input.

References:

Genesys Cloud CX Scripting Components Documentation​​​.

In Genesys Cloud CX, once you set the page name in a script, you can change it later if needed. The platform allows for flexibility in managing and editing scripts, including renaming pages to better reflect their content or purpose as the script evolves.

References:

Genesys Cloud CX Scripting Documentation​​​.

In Genesys Cloud CX Scripting, the Validation tab in the right pane is crucial as it lists all the errors in the script and helps you locate them quickly. This feature is part of the integrated development environment (IDE) within Genesys Cloud CX, which aids developers in identifying and resolving issues in their scripts effectively. The validation process checks for various syntax errors, configuration mismatches, and other potential issues that might cause the script to fail during execution. This helps ensure that scripts are error-free and function as intended before they are deployed.

The Validation tab is an essential tool in the Genesys Cloud CX scripting environment, providing a streamlined way to detect and correct errors, thereby improving the accuracy and reliability of customer experience automation.

References:

Genesys Cloud CX Scripting Documentation​​​.

The correct syntax to display " 10$ " using the variables value and currency in Genesys Cloud CX scripting is {{value}}{{currency}} . This syntax correctly concatenates the two variables without any additional characters or spaces, ensuring that the result is displayed as " 10$ " on the script page.

To configure a script that allows agents to create a contact in the contact list in Genesys Cloud CX, the following sequence should be followed:

Create a Script : Start by creating a new script that will serve as the framework for the agent ' s interaction.

Enable Outbound features : Before the script can interact with outbound services, outbound features must be enabled in the script settings.

Associate a contact list with the script : The script needs to be associated with a specific contact list to ensure that contacts can be added directly to the correct list.

Invoke the " Outbound Create Contact " action with appropriate variables : Finally, add the " Outbound Create Contact " action to the script and configure it with the appropriate variables to capture the necessary contact details from the agent.

This order ensures that the script is correctly set up to interact with the contact list and allows agents to add new contacts as needed.

References:

Genesys Cloud CX Scripting Documentation​​​.

UUI (User-to-User Information) is the script property used for exchanging or passing data from one application to another that is unrelated to the call itself. UUI data is often used in scenarios where information needs to be transferred alongside a call but is not directly related to the telephony functions, such as passing customer data between different systems within an organization.

This capability is essential for integrating various systems and ensuring that relevant data accompanies interactions throughout different touchpoints.

In Genesys Cloud CX, when creating custom scripts, the correct syntax to display dynamic data, such as a customer ' s first name, involves using double curly braces {{ }} . This syntax is used to reference data variables within the script.

{{Outbound.First Name}} : This syntax correctly refers to the " First Name " attribute from the Outbound object in the script. When the script is run, this placeholder will dynamically display the customer ' s first name based on the data provided in the Outbound Campaign.

Using the correct syntax is crucial for ensuring that the data is pulled correctly and displayed as intended in the script.

References:

Genesys Cloud CX Scripting Documentation​​​.

In Genesys Cloud CX, once a custom field is created on a user ' s profile, it cannot be deleted via the Admin interface. This restriction ensures that profile data integrity is maintained and that data linked to custom fields is not accidentally lost or compromised. While you can update or modify custom fields, deleting them entirely from the admin interface is not an option.

=========================

The Secure Pause action in Genesys Cloud CX is used to temporarily stop the recording of an interaction, particularly when sensitive information, such as payment details, is being collected. This action is essential for compliance with data protection regulations like PCI-DSS, ensuring that sensitive data is not recorded or stored.

Using Secure Pause ensures that the recording is automatically resumed after the sensitive information has been captured, maintaining the integrity of the interaction while protecting customer data.

The Markdown Component in Genesys Cloud CX allows you to easily format text using Markdown syntax. This component is specifically designed for handling text formatting within scripts, enabling the use of Markdown to add styling such as bold, italics, headings, lists, and more. This provides a flexible and user-friendly way to enhance the visual presentation of text in scripts.

In Genesys Cloud CX, the Set Participant Data action is the correct choice for transferring data to scripts during a call flow. This action allows you to set specific data attributes for the participant (such as a customer or agent) that can then be accessed by scripts running during the interaction.

The Set Participant Data action is typically used to pass information gathered during an interaction, such as caller input or data fetched from external sources, so that it can be used in scripts to customize the experience further. This is crucial for dynamic and personalized script content based on the interaction context.

For more details, you can refer to the Genesys Cloud CX documentation on call flows and scripting, which explains how to use the Set Participant Data action effectively in various scenarios.

References:

[Genesys Cloud CX Call Flow Documentation]

[Genesys Cloud CX Scripting Documentation]

When dealing with billing amounts passed as string values in a script, the correct approach is to convert the string values to numbers and then add them using a Dynamic Number variable. This ensures that the values are treated as numerical data, allowing for accurate addition and calculations.

Using a Dynamic Number variable after conversion from string to number is the best practice for handling and manipulating numerical data within a script.

References:

Genesys Cloud CX Scripting Variables and Data Types Documentation​​​.

Scripts in Genesys Cloud CX are classified by several features that enhance their usability and flexibility:

A. Labels based on interaction type : Scripts can be categorized and labeled according to the interaction type (e.g., voice, chat, email), making it easier to identify and manage them.

C. Utilization of visual controls : Genesys Cloud CX allows the use of various visual controls (buttons, inputs, checkboxes) to enhance user interaction within scripts, enabling agents to interact seamlessly.

D. Integration of text and graphics : Scripts can integrate both text and graphical elements, allowing for a richer, more interactive experience for agents and customers alike. This can include images, links, and dynamic content.

Options B and E are not core classifications for Genesys Cloud CX scripts.

When a new user in Genesys Cloud CX, such as John Camper, does not receive the invitation email, the best course of action is to resend the invite . This option allows you to send the invitation email again without needing to create a new user or escalate the issue unnecessarily. Resending the invite is a straightforward process that can be performed directly from the Genesys Cloud CX admin interface. It ensures that John will receive the necessary instructions to activate his account and access Genesys Cloud CX features.

This action avoids duplication of users and unnecessary delays, providing a quick resolution to the issue.