Genesys Cloud CX: Scripting Certification (GCX-SCR)

✅ Directory
Description: In Genesys Cloud CX, the Directory feature provides a centralized location to manage and access information about internal users within your organization and external contacts. It allows users to search for colleagues, view their presence, and communicate with them. It also supports the management of external contacts, enabling users to add, store, and find contact information for individuals outside the immediate organization. Why this fits: The question explicitly asks where you can "search for people in your organization" and "add external contacts." The Directory in Genesys Cloud CX is precisely designed for these functions, acting as a comprehensive list of all internal users and a repository for managing external contact information.

Genesys Cloud allows scheduling callbacks for a future date and time. The maximum number of days in advance a callback can be set is 30 days. This limit is defined to manage contact center operations and resource allocation effectively.

✅ TRUE
Description: Genesys Cloud CX offers various telephony connection options, including Genesys Cloud CX Voice (their native cloud PSTN service) and Bring Your Own Carrier (BYOC) solutions (BYOC Cloud, BYOC Premises). These options are not mutually exclusive and can be combined within a single Genesys Cloud organization. Why this fits: Genesys Cloud is designed for flexibility in telephony. An organization can configure both Genesys Cloud CX Voice and BYOC Cloud (or BYOC Premises) simultaneously. For example, Genesys Cloud CX Voice might be used for general inbound/outbound calling in regions where it provides optimal quality and cost, while BYOC Cloud could be used for specific regional numbers, specialized carriers, or particular call types where a customer has existing contracts or specific requirements. This hybrid approach allows organizations to leverage the benefits of Genesys's global cloud infrastructure (Genesys Cloud CX Voice) alongside the flexibility and specific carrier relationships offered by BYOC Cloud, optimizing for cost, coverage, and redundancy.

✅ Option A (Correct) Reasoning: Data Actions are Genesys Cloud's dedicated feature for integrating scripts with external systems like CRMs. They allow scripts to make API calls to retrieve and update customer data dynamically, directly addressing the need to read and update CRM information during a call.❌ Why the other choices are incorrect: * Option B is incorrect: Built-in actions manage internal script logic and participant data, but do not provide direct capabilities for external CRM integration for reading/writing data. * Option C is incorrect: Custom actions encapsulate existing script steps for reuse but are not the primary mechanism for external system integration. Data Actions are. * Option D is incorrect: Transfer actions are solely for routing calls to different destinations and have no functionality related to CRM data access or updates.

✅ 2 GB 
Description: The maximum size for a single file upload operation within Genesys Cloud CX. This limit applies to various functionalities, including but not limited to, content management documents, email attachments, and certain data import processes.                                                                            Why this fits: Genesys Cloud CX, as an enterprise cloud platform, implements a maximum file size limit for single uploads to maintain system performance, ensure efficient data handling, and optimize storage utilization. A 2 GB limit is a common and practical ceiling for individual file operations across many cloud services, preventing excessively large files from monopolizing network bandwidth or processing resources during upload. Exceeding this limit typically requires breaking the file into smaller chunks or using specialized large-object storage solutions, which are not part of standard single file upload mechanisms.

✅ Option A (Correct)
Reasoning: The "Scripter > Add To Do Not Call List" action is specifically designed for agents to add phone numbers to the organization's DNC list directly from within a Genesys Cloud script, preventing future outbound calls to those numbers.

❌ Why the other choices are incorrect:

• Option B is incorrect: "Outbound > Create Contact" is used to add a new contact record to an outbound campaign, not for managing the DNC list.
• Option C is incorrect: "Outbound > Schedule Callback" enables agents to schedule a callback for a specific contact at a later time, which is unrelated to DNC management.
• Option D is incorrect: "Blind Transfer" is an action used to transfer an ongoing interaction to another queue or agent without consulting the recipient first.

✅ Organization ID
Description: The Organization ID is a unique, alphanumeric identifier assigned by Genesys to each Genesys Cloud CX organization. It serves as a primary key for identifying your specific Genesys Cloud CX instance within the Genesys ecosystem. Why this fits: When contacting the Genesys Cloud CX support team, providing your Organization ID is the most efficient and accurate way to identify your specific tenant and associated configuration. It ensures that the support agent can quickly locate your account details, access relevant data, and provide targeted assistance without ambiguity, unlike a generic company name which might not be unique or precise enough for technical identification. Genesys Cloud Support explicitly requests this information to streamline the support process.

✅ Option A (Correct)

Reasoning: The Contact List Form component is specifically designed in Genesys Cloud scripts to allow agents to view, verify, and update contact information directly from the campaign's contact list. It presents all relevant contact fields for agent interaction during an outbound call.

❌ Why the other choices are incorrect:

• Option B is incorrect: A Button component triggers an action but does not provide fields for data entry or modification of contact information itself.
• Option C is incorrect: An Input component allows data entry for a single field. While used within a form, it's not the comprehensive component for managing all contact information in a campaign directly.
• Option D is incorrect: A Text component is used to display static or dynamic text; it does not allow agents to input or update any information.

✅ Option B (Correct) Reasoning: Invoke Secure Flow is specifically designed to collect sensitive data like payment information securely via IVR. It routes the caller to a secure application, ensuring the data never touches the agent desktop or Genesys Cloud recording infrastructure, thus preventing exposure to agents. ❌ Why the other choices are incorrect:

• Option A is incorrect: Secure Pause temporarily halts recording during an agent interaction. It is not for IVR-based, agent-less sensitive data collection.
• Option C is incorrect: Blind Transfer simply moves a call to another queue or user without interaction. It does not facilitate secure payment collection.
• Option D is incorrect: Consult Transfer allows an agent to speak with another party before transferring. It is unrelated to secure IVR payment processing.

✅ Option A (Correct)

Reasoning: The Outbound > Create Contact action in Genesys Cloud scripts is specifically designed to allow agents to add new contact records directly to an outbound campaign's contact list, fulfilling the requirement.

❌ Why the other choices are incorrect:

• Option B is incorrect: Outbound > Update Contact List modifies existing contact entries, it does not create new ones.
• Option C is incorrect: Scripter > Add To DNC List adds a number to the Do Not Call list, not new campaign contacts.
• Option D is incorrect: Outbound > Schedule Callback enables scheduling a future call for an existing contact, rather than creating a new one.