In the image provided, the correct tab to add variables to the script is labeled as number 3. This tab represents the "Variables" section where you can define new variables that will be used in your script. Variables are crucial in scripts as they allow for dynamic content, enabling personalized interactions based on data such as customer names, account details, and other context-specific information.

When you want to save a variable's value to external storage in Genesys Cloud CX, you should enable the Output property for that variable. The Output property designates that the value of the variable can be exported or sent out of the current script, which is necessary for saving data to external systems like a CRM or database.
This setting is crucial for ensuring that data collected or processed in the script is correctly passed on to other systems for further use.
References:
* Genesys Cloud CX Scripting Variables Documentation.

HTML, JavaScript, or CSS knowledge is not a prerequisite for configuring Genesys Cloud CX Scripts. The scripting interface in Genesys Cloud CX is designed to be user-friendly, allowing users to create and configure scripts using a visual editor without needing to know web development languages like HTML, JavaScript, or CSS. The platform abstracts these complexities, making it accessible to users with varying technical backgrounds.
References:
* Genesys Cloud CX Scripting Documentation.

In Genesys Cloud CX, when creating custom scripts, the correct syntax to display dynamic data, such as a customer's first name, involves using double curly braces {{ }}. This syntax is used to reference data variables within the script.
* {{Outbound.First Name}}: This syntax correctly refers to the "First Name" attribute from the Outbound object in the script. When the script is run, this placeholder will dynamically display the customer's first name based on the data provided in the Outbound Campaign.
Using the correct syntax is crucial for ensuring that the data is pulled correctly and displayed as intended in the script.
References:
* Genesys Cloud CX Scripting Documentation.