GCX-SCR Sample Questions Answers

In Genesys Cloud CX, the permissions required to edit scripts are controlled by roles that include the necessary permissions for interacting with and modifying scripts. The Script Designer role (option C) is specifically created for individuals responsible for creating and editing scripts. It grants full access to the scripting interface and allows for script modifications. The Master Admin role (option D) also has broad permissions across the system, including editing and managing scripts, among other administrative tasks.

References to Genesys Cloud documentation indicate that other roles, like PureCloud User or Outbound Agent, do not have sufficient permissions to modify scripts. The Outbound Admin role manages outbound campaigns but does not include script editing by default.

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

The default page name that the editor automatically adds when you create a new script in Genesys Cloud CX is Start Page. This page serves as the initial landing page of the script, and it typically contains the first set of instructions or content that the agent will see when the script is launched.

A number plan in telephony determines how many and which digits are necessary for call routing. This concept is essential for defining how calls are processed and routed within a telephony system, including Genesys Cloud CX. The number plan dictates the structure of phone numbers, including length and the specific digits required to reach certain destinations, ensuring that calls are directed correctly based on the dialed numbers.

References:

Genesys Cloud CX Telephony and Call Routing 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.

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

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.

To create a script that allows agents to write data to an external CRM, the correct sequence of steps is as follows:

Configure the CRM integration in Genesys Cloud CX: Before any scripting can take place, the CRM must be integrated with Genesys Cloud CX. This integration setup is the foundation that allows data to flow between the two systems.

Create a Script: Once the integration is configured, you can create a new script that will be used by agents to interact with the CRM.

Enable the Data Actions property in the script: This property must be enabled to allow the script to perform data actions, which include sending and receiving data from the CRM.

Configure the respective data action of the configured CRM in Scripts: After enabling Data Actions, you must set up the specific actions that will interact with the CRM, such as writing data to a contact record.

Give necessary permission to agents to view and execute data actions: Finally, you must ensure that agents have the appropriate permissions to execute these data actions, which may involve granting them specific roles or permissions in Genesys Cloud CX.

This sequence ensures that all necessary configurations and permissions are in place before agents start interacting with the CRM through the script.

References:

Genesys Cloud CX Data Actions and Scripting Documentation​​​.

The Best Available Skills ACD evaluation method in Genesys Cloud CX is designed to match the interaction with the first available agent who possesses all the required skills for the interaction. This method ensures that interactions are handled by agents who are qualified to meet the customer's needs, improving service quality and efficiency.

This method is part of the broader ACD (Automatic Call Distribution) system, which routes calls based on various criteria, ensuring that customers are connected with the most suitable agents quickly.

In Genesys Cloud CX, Roles are used to ensure that people within your organization have the rights and permissions they need to perform their tasks. Roles are collections of permissions that can be assigned to users, determining what actions they can perform within the system. For example, a role might allow a user to manage queues, configure scripts, or view analytics. By assigning the appropriate roles to users, administrators can control access and maintain security within the organization.

References:

Genesys Cloud CX Roles and Permissions Documentation​​​.

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

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.

By default, Genesys Cloud CX scripting does not have a separate data type specifically for decimals. Instead, decimals are typically handled as numbers within the existing number data type. This means that decimal values can be used, but they are not explicitly differentiated from integers by a distinct data type in the scripting environment.

References:

Genesys Cloud CX Scripting Data Types Documentation​​​.

Scripts in Genesys Cloud CX can be used for various types of interactions, including inbound and outbound calls, chat sessions, emails, and more. Scripts help guide agents through interactions by providing them with relevant information and prompts based on the interaction context. This flexibility allows scripts to be integrated across different channels, ensuring a consistent customer experience regardless of the interaction type.

Scripts are not limited to outbound campaigns or configuring flows in Architect; they are a versatile tool within the Genesys Cloud CX platform.

Custom templates in the Genesys Cloud script editor are particularly useful when you need to create multiple scripts with similar requirements. These templates allow for consistent design and functionality across various scripts, saving time and ensuring uniformity in how interactions are handled. They are not typically used for one-time scripts or to store visual elements like graphics but are focused on reuse and consistency across multiple scripts.

References:

Genesys Cloud CX Scripting Templates Documentation​​​.