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

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

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.

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

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

In Genesys Cloud CX Scripting, templates play a vital role in creating reusable elements for various scripts, streamlining the development process.

Script Templates: These are entire scripts that have been packaged for reuse. They serve as a starting point for new scripts, allowing users to replicate existing scripts quickly without having to rebuild them from scratch. This is particularly useful for creating standardized scripts across different campaigns or use cases.

Component Templates: These refer to parts of a page that can be reused in other scripts. Component templates are particularly helpful when you need to reuse specific UI elements or layouts across multiple scripts. For instance, if a script has a specific layout or a component, such as a customer information panel, that needs to appear in multiple scripts, you can create a component template for it. This ensures consistency and saves development time.

References:

Genesys Cloud CX Scripting Documentation​​​.

In Genesys Cloud CX, when managing multiple organizations with similar script layouts, you can export scripts from one organization and import them into another. This process allows you to maintain consistency across organizations without having to recreate the scripts from scratch.

Exporting Scripts: This involves saving the script from Org A in a format that can be transferred.

Importing Scripts: You can then import the saved script into Org B, ensuring that the script's layout, components, and logic are retained.

This method is highly efficient for administrators managing multiple organizations with similar needs.

References:

Genesys Cloud CX Scripting Documentation​​​.

The key components and functionalities of scripts used to present information to agents in Genesys Cloud CX include:

Visual controls: These are interactive elements like buttons, dropdowns, and checkboxes that agents can use to interact with the script.

Text: Text components are used to display information, instructions, or data to the agents within the script.

Navigational Aids: These help agents move through the script logically, guiding them from one section or page to another.

Graphics: Graphics can be used to enhance the visual presentation of the script, making it more engaging and easier to follow.

These components are integral to designing effective scripts that aid agents in their tasks by providing the necessary tools and information in a user-friendly format.

References:

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

References:

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

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.

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.

In Genesys Cloud CX, a Component Template contains one or more visual components that can be inserted into a script page. These templates are designed to provide reusable UI elements that can be consistently applied across different scripts. Using component templates helps in maintaining uniformity and speeding up the script creation process by allowing script designers to easily drag and drop pre-defined components into their scripts.

Component templates can include items such as buttons, text fields, and other interactive elements that are commonly used within the scripts.