GCX-SCR Practice Questions

The Consult Transfer action in a contact center allows agents to transfer interactions seamlessly

without needing to remember the destination. This type of transfer allows the agent to consult with

the destination party before completing the transfer, ensuring that the interaction is handled

smoothly and that the receiving party is fully informed.

This feature is particularly useful in complex customer service scenarios where context needs to be

preserved during the transfer.

Reference:

Genesys Cloud CX Interaction Management Documentation​​​.

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.

It is possible to transfer data to and from scripts in Genesys Cloud CX. This capability is fundamental

to creating interactive and dynamic scripts that can respond to real-time information and update the

system based on user inputs. Data can be passed into scripts from external sources such as databases

or other services, and data collected during an interaction can be sent back to the system for further

processing or storage.

This data transfer allows for scripts to be highly customizable and context-sensitive, enhancing the

overall effectiveness of customer interactions.

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.

Reference:

Genesys Cloud CX Scripting Documentation​​​.

In Genesys Cloud CX scripts, several built-in variables are available by default, providing essential

data that can be used within the script. The built-in variables include:

Agent Name: This variable holds the name of the agent who is currently using the script. It is often

used to personalize the interaction or for logging purposes.

Queue Name: This variable contains the name of the queue from which the interaction was routed. It

helps in identifying the source of the interaction and can be used to tailor the script based on the

queue's context.

Language: This variable stores the language preference of the customer or the interaction, allowing

the script to present content in the appropriate language.

These variables are readily accessible within scripts and are integral to creating dynamic and context-

aware interactions.

Reference:

Genesys Cloud CX Scripting 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.

Reference:

Genesys Cloud CX Callback Feature Documentation​​​.

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.

Reference:

Genesys Cloud CX Scripting Data Types Documentation​​​.

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.

Reference:

Genesys Cloud CX Telephony and Call Routing Documentation​​​.

By default, Line Recording is indeed disabled in Genesys Cloud CX. This default setting is designed to

comply with various regulatory and privacy requirements, where recording communications without

explicit consent or necessity could lead to legal issues. Administrators must manually enable Line

Recording based on organizational needs and after ensuring that all necessary legal and compliance

measures are in place.

Genesys Cloud CX allows detailed configurations for recording, including setting up policies that

dictate when and how interactions are recorded, ensuring that only necessary communications are

recorded and stored.

In Genesys Cloud CX Scripting, once a variable has been created and assigned a data type, you

cannot modify its data type later. This design is intentional to prevent errors that might occur if a

variable's type were changed after it was already in use. Variables in Genesys Cloud CX scripting are

strongly typed, meaning the type of data they hold is fixed upon their creation.

To change the type of a variable, you would need to create a new variable with the desired type and

then use that instead. This ensures that the script's logic remains consistent and avoids runtime

errors that could arise from unexpected data types.

This behavior is consistent with best practices in many scripting environments where strict typing is

enforced to maintain stability and predictability in scripts.

For more details on variable handling in Genesys Cloud CX, you can refer to Genesys Cloud CX

Scripting documentation that explicitly states these constraints to help developers write more

reliable and error-free scripts.

Reference:

[Genesys Cloud CX Scripting Documentation]