AI-generated summary
Genesys Cloud enables configuration of Transfer to Voicemail actions for routing interactions directly to user, queue, or group voicemail within inbound, outbound, and in-queue flows. The action requires voicemail enablement at both the organization and individual user levels, with Edge and Media Tier version 1.0.0.6166 or later.
Transfer to Voicemail can be added to flow menus or task sequences and supports configurable pre-transfer and failed transfer audio prompts using text-to-speech or audio sequences, along with failure path handling for tasks. For call flow menus, DTMF and optional speech recognition settings are available with the ability to enhance recognition by adding words or phrases associated with menu options. In secure flows, blind transfers are used instead of consultations, with automatic call disconnection if transfer fails.
Configuration requires selecting transfer targets (users, queues, groups, or other destinations), audio settings, and failure handling procedures. Transfer targets can include optional callee names and callback numbers specified through string expressions. For queue transfers, administrators can define voicemail greetings and callback settings. Best practice recommends pairing callback actions with audio sequences and collect input data actions to allow callers to provide alternative callback numbers.
Voicemail recordings support a maximum 3-minute message length, with callers able to end recording via DTMF input, speech recognition menu options (Send Message, Review, Rerecord, Cancel), or by disconnecting. System-generated prompts for message completion and maximum length notifications are non-configurable with speech recognition enabled by default. When callers leave voicemail while queued, the interaction retains its original voice interaction priority for routing to the next available agent.
Configuration limitations include that users without configured voicemail appear grayed out and cannot be selected. If selected users or queues are removed from the system without updating the transfer action, the flow fails at that step. In secure flows, defined failure paths are overridden with automatic call disconnection. Transfer actions can be assigned meaningful names and integrated into broader flow design workflows with continued task building upon configuration completion.