Skip to main content

Work with secure call and bot flows

Series: Secure flows in Architect

Previous suggested step: Secure flow scenarios

In Architect, a flow assumes secure functionality when processing a secure action or when a variable’s content is marked as secure. When it consumes secure data, a key icon appears.

Within a task, the key icon indicates that an action or an action beneath it is either secure or consumes secure data.

Notes:
  • Secure flows impact agent analytic metrics, including time in IVR, average time in IVR, agent handle time, average agent handle time, and agent talk time. For more information, see .
  • If a bot session is initiated from a secure call flow, the bot inherits the secure characteristics of the secure call flow, preventing a certain level of logging and recording of data to keep PCI/PII compliance.

To help familiarize yourself with secure flows in Architect, see  and . For more information on configuring and designing secure flows, review the following sections: