What are the default roles that permit you to edit scripts? (Choose two.)
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.
Reference 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.
Which of the following best defines the ACD evaluation method Best Available Skills?
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.
An agent is handling a call as part of an outbound dialing campaign and needs to transfer the caller to another agent but also wants to pass info about the interaction to the second agent. Select the correct statement.
When an agent is involved in an outbound dialing campaign and needs to transfer a call to another agent while also passing interaction information, the most appropriate method is to use the Notes section in Genesys Cloud CX. The Notes section allows agents to input relevant details about the interaction, which can then be viewed by the next agent handling the call. This is a simple and efficient way to pass context between agents during a transfer. Options A and B involve updating customer data, but this is not the most direct or recommended method for passing interaction-specific information during a transfer.
You are a contact center administrator and are required to create a script to allow agents to write data to an external CRM. Select the correct sequence.
1. Create a Script.
2. Configure the CRM integration in Genesys Cloud CX.
3. Give necessary permission to agents to view and execute data actions.
4. Configure the respective data action of the configured CRM in Scripts.
5. Enable the Data Actions property in the script.
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.
Genesys Cloud CX Data Actions and Scripting Documentation.
You cannot schedule a callback for more than 30 days in advance.
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.
Genesys Cloud CX Callback Feature Documentation.
Leonora
4 days agoLucina
1 months agoJules
2 months agoHubert
3 months agoNicolette
3 months agoKina
4 months agoRyan
4 months agoCherilyn
4 months agoDomingo
5 months agoEvangelina
5 months agoChaya
5 months agoGertude
6 months agoGretchen
6 months agoAaron
6 months agoGretchen
7 months agoMargret
7 months agoMarcelle
7 months agoJosephine
7 months agoMiles
7 months agoCarisa
8 months ago