Loading...
Loading...
Loading...
Architect offers several transfer actions for use in flow menus and task sequences:
Transfer to ACD sends the interaction to the ACD assignment service for Genesys Cloud. ACD processing uses a first in, first out (FIFO) algorithm with a language skills component. With FIFO processing, Genesys Cloud sends the interaction that arrives the earliest to the first available resource. The language component restricts the pool of available agents to those agents who are fluent in the appropriate language. You can add an ACD transfer to a call flow menu or to a call, message, or email flow’s task sequence. Your flow design dictates how and when you use this action. For more information, see Set up a Transfer to ACD action.
The Transfer to User action sends an interaction to a specific person or agent. You can add this action to a flow menu or to a task sequence. Your flow design dictates how and when you use this action.
To successfully execute the call flow, the selected user must have logged into Genesys Cloud at least once.
This operation transfers a call to a telephone number outside your organization. For example, use this option to route interactions to an after-hours call center or to transfer interactions that come in after hours to a different office. The flow author presets the destination telephone number. The caller has no control over the destination.
The Transfer to Group action sends an interaction to a specific Genesys Cloud group. You can add this action to a flow menu or to a task sequence. Your flow design dictates how and when you use this action.
To successfully execute the call flow, the selected user must have logged into Genesys Cloud at least once.
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.
This action transfers the current interaction to a published flow that contains secure data. If the selected flow is removed from the system and no longer exists, and you do not update this transfer action, the flow will fail at this action step. If you select an unpublished flow, Architect sends a warning message. 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.
To set up a Transfer to Secure Flow action, follow these steps:
Use this action to transfer the current interaction directly to a Genesys Cloud user's, queue's, or group's voicemail. Transfer to voicemail is available for inbound, outbound, and in-queue flow types. You can add a Transfer to Voicemail action to a flow menu or to a task sequence. When you implement this action, consider the following:
Get user feedback about articles.