Transfer to Secure Flow action
Use the Transfer to Secure Flow action in the menu to transfer an 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.
To successfully execute the call flow, the selected user must have logged into PureCloud at least once.
This action is available in menu choices and task sequences for inbound, outbound, and in-queue flows. Menu choices contain common settings such as DTMF and speech recognition.
|Secure Call Flow||Select the secure flow to which to transfer the interaction.|
|Invocation Data||The variable name used to pass information into the secure flow from an IVR or script.|
Click to change the default timeout, in seconds or milliseconds. Use the + or – buttons, or manually enter the desired value.
|転送前オーディオ||Optionally configure a prompt to play before transferring the interaction.|
|Failed Transfer Audio||Optionally configure a prompt to play if the transfer action detects a failure.|
These outputs allow the flow author to map the results of any resulting errorType and errorMessage.
Note: Click the arrow next to Failure Outputs to expand or collapse the list of variables.
Define success and failure paths
Ends the flow and returns the call to the secure flow.
This path indicates that there was an error executing the action or there was a problem processing the results from a bridge or data action. Specify the action if Architect is not able to transfer the call. For example, a play audio action to indicate that the action wasn’t successful, a transfer action to send the caller to an agent or representative for assistance.
Note: If the network experiences connectivity issues, the action automatically takes this failure path.