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.

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.

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

In Genesys Cloud CX, a script cannot be deleted if it is currently assigned to an active outbound dialing campaign. The system prevents deletion to ensure that ongoing operations are not disrupted. This measure protects the integrity of the campaign, ensuring that agents continue to have access to the necessary scripts during interactions.

Before attempting to delete the script, you must first unassign it from the campaign or ensure that the campaign is no longer active.

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

To add multiple pages to your script in Genesys Cloud CX, you would use the tab indicated as number 3 in the provided image. This tab provides access to the components and functionalities needed to manage and navigate between different pages within a script.

This is essential for creating scripts with complex flows that require the user or agent to navigate through multiple stages or sections within a single interaction.

References:

Genesys Cloud CX Scripting Documentation​​​.

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