You want to create a call flow to get the customer’s unique identification number. Select the correct action to accomplish the task.

The "Collect Input" action is the standard tool within Genesys Cloud Architect for gathering information directly from a caller. This action plays a prompt (e.g., "Please enter your customer identification number followed by the pound key") and then collects the caller's DTMF (keypad) or speech input. The collected data is stored in a variable, which can then be used for subsequent actions in the flow, such as looking up customer records or routing the call. This directly accomplishes the task of getting the customer's unique identification number.

A. Data Table Lookup: This action retrieves data from a pre-configured data table within Genesys Cloud. It does not collect new information from the caller.

C. Collect Data: This is not a valid action name in Genesys Cloud Architect. The correct and specific action for this purpose is "Collect Input."

D. Call Data Action: This action is used to query an external data source (like a CRM or web service) via a Data Action integration, not to collect input directly from the caller.

1. Genesys Cloud CX Resource Center, "Collect Input action": This document explicitly states, "The Collect Input action gathers information from a caller. For example, you can use this action to obtain an account number or a case number." This directly supports the use of "Collect Input" for the specified task.

Source: Genesys Cloud CX Resource Center, Architect section, under "Toolbox > Data".

2. Genesys Cloud CX Resource Center, "Look up data in a data table action": This document describes the action's purpose as finding and retrieving information from a data table based on a specific lookup value, confirming it does not collect caller input.

Source: Genesys Cloud CX Resource Center, Architect section, under "Toolbox > Data".

3. Genesys Cloud CX Resource Center, "Call Data Action": This documentation details how to use this action to "access external data within an interaction flow." It is for data dips into external platforms, not for gathering input from the caller.

Source: Genesys Cloud CX Resource Center, Architect section, under "Toolbox > Data".