Set up a Transfer to Flow action

This action transfers the current interaction to another inbound flow defined for this server and is available from all flow types (inbound, outbound, or in-queue). This is particularly useful when outbound processing needs to send the interaction to inbound processing. You can add a Transfer to Flow action to a flow menu or to a task sequence.  Your flow design dictates how and when you use this action.

  1. From the Toolbox, expand the Transfer category and drag a Transfer to Flow action to the appropriate location in the flow menu or task sequence.
  2. In the Name field, type a meaningful name for the transfer action. This name becomes the name of the transfer node in the flow menu.
  3. [Flow menus only] Set DTMF and optional speech recognition settings:
    1. Click DTMF and choose the key that callers press to enter a caller data entry operation.  
    2. In the Speech Recognition field, optionally add words or phrases that can be associated with menu options.
    3. To allow a user to press this number from any menu to find an extension, select the DTMF goes to this menu choice from any menu check box.
    4. To immediately send the caller to the current menu operation if the speech recognition engine matches the verbal request anywhere in the flow, select the Speech recognition terms go to this menu choice from any menu check box.
  4. Click the Inbound Call Flow list and select the inbound flow to which to transfer the interaction.
  5. (Optional) Under Pre-Transfer Audio, select a prompt, add text to speech, or configure an audio sequence to play to the caller before the system transfers the interaction.
  6. (Optional) Under Failed Transfer Audio, select a prompt, add text to speech, or configure an audio sequence to play to the caller if the transfer action detects a failure.
  7. [Flow tasks only] Configure the transfer action’s Failure path in the event that the call cannot be transferred to the interaction.

    Note: For transfer actions included in secure flows, Genesys Cloud overrides the defined failure path and disconnects the call. The normal consultation VXML transfer type can be problematic in secure flows; therefore, Genesys Cloud uses blind transfers. For more information, see Recommendation for the <transfer> element. This behavior occurs in transfers to ACD, user, external numbers, group, other flows, and voicemail.

  8. Continue building the task per your flow design.