Genesys GCX-SCR - Genesys Cloud CX: Scripting Certification

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 working on a complex script in Genesys Cloud CX that includes multiple stack containers and components nested within each other, Nesting Indicators are a helpful feature to ensure that you have selected the correct component or container. These indicators visually show the hierarchy of components within the script, making it easier to navigate and edit complex structures.

Using Nesting Indicators helps avoid errors by providing a clear view of how elements are organized within the script, ensuring that modifications are applied to the correct components.

Automatic Call Distribution (ACD) is the system within Genesys Cloud CX responsible for routing interactions (calls, messages, etc.) based on an algorithm that determines the best available agent for the interaction. ACD takes into account factors such as agent availability, skill sets, and proficiency ratings to ensure that interactions are handled by the most qualified agents, thereby optimizing customer service and efficiency.

ACD is a key component in contact centers, ensuring that customer interactions are managed effectively and that resources are used optimally.

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.

The most efficient way to create multiple pages in a script that share a common header section is to create a component template for the header. This template can then be reused on each page, ensuring consistency and saving time. By using a component template, you only need to design the header once and can easily apply it across all pages. This approach also makes updates easier, as changes to the header template will automatically reflect on all pages using that template.

Creating individual headers for each page or duplicating them using a script template would be less efficient and prone to inconsistencies.

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​​​.

In Genesys Cloud CX, the Hardware ID (MAC address) is what binds the phone's settings to a physical phone. When configuring a phone in Genesys Cloud CX, you need to enter the MAC address, which uniquely identifies the physical device on the network. This binding ensures that the phone configuration, including the phone model, base settings, and other details, are correctly associated with the correct physical device.

The MAC address serves as the unique identifier that allows Genesys Cloud CX to apply the appropriate settings to the correct phone, ensuring seamless operation.

In Genesys Cloud CX, you can schedule a callback for more than 30 days in advance. The platform allows flexibility in setting callback times, ensuring that customer interactions can be scheduled according to business needs, even if that requires scheduling far into the future.

The statement that you cannot schedule a callback for more than 30 days in advance is false.

References:

Genesys Cloud CX Callback Feature Documentation​​​.