Flow block: Set whisper flow
Description
A whisper flow is what a customer or agent experiences when they are joined in a voice or chat conversation. For example:
-
An agent and customer are joined in a chat. An agent whisper might display text to the agent telling them the name of the customer, for example, which queue the customer was in, or let the agent know they're talking to club member.
-
An agent and customer are joined in a call. A customer whisper might tell the customer that the call is being recorded for training purposes, for example, or thank them for being a club member.
-
An agent and customer are joined in a chat. Using a contact attribute, an agent whisper flow records which agent is being connected to the conversation. This attribute is then used in a disconnect flow to route the contact back to the same agent if the customer has a follow-up question after the agent disconnects.
A whisper flow has the following characteristics:
-
It's a one-sided interaction: either the customer hears or sees it, or the agent does.
-
It can be used to create personalized and automated interactions.
-
It runs when a customer and agent are being connected.
For voice conversations, the Set whisper flow block overrides the default agent whisper flow or customer whisper flow by linking to a whisper flow you create.
For chat conversations, you need to include a Set whisper flow block for default agent or customer whispers to play. For instructions, see Set the default whisper flow for a chat conversation.
How the Set whisper flow block works
-
For inbound conversations (voice or chat), the Set whisper flow block specifies the whisper to be played to customer or the agent when they are joined.
-
For outbound voice calls, it specifies the whisper to be played to customer.
-
A whisper is one direction, which means only the agent or customer hears or sees it, depending on the type of whisper you selected. For example, if a customer whisper says "This call is being recorded," the agent does not hear it.
-
A whisper flow is triggered after the agent accepts the contact (either auto-accept or manual accept). The agent whisper flow runs first, before the customer is taken out of queue. After this is completed, the customer is taken out of queue and the customer whisper flow runs. Both flows run to completion before the agent and customer can talk or chat with each other.
-
If an agent disconnects while the agent whisper is running, the customer remains in queue in order to be re-routed to another agent.
-
If a customer disconnects while the customer whisper is running, the contact ends.
-
If an agent whisper flow or customer whisper flow includes a block that chat does not support, such as Start/Stop media streaming or Set voice, chat skips these blocks and triggers an error branch. However, it doesn't prevent the flow from progressing.
-
Whisper flows don't appear in transcripts.
-
Whispers can be a maximum of 2 minutes long. After that point, the contact or agent is disconnected.
Supported channels
The following table lists how this block routes a contact who is using the specified channel.
Channel | Supported? |
---|---|
Voice |
Yes |
Chat |
Yes |
Task |
Yes |
Flow types
You can use this block in the following contact flow types:
-
Inbound flow
-
Customer Queue flow
-
Transfer to Agent flow
-
Transfer to Queue flow
Properties

If you choose to Select a flow, you can only select from flows that are type Agent Whisper or Customer Whisper.
For information about using attributes, see Use Amazon Connect contact attributes.
Configuration tips
-
In a single block, you can set either a customer whisper or an agent whisper, but not both. Instead, use multiple Set whisper flow blocks in your flow.
-
If you use a Play prompt block instead of a Set whisper block in an agent whisper flow or customer whisper flow, in a voice conversation the prompt is audible to both the agent and the customer. In a chat, however, only the agent or customer sees the Play prompt text.
-
Make sure your whispers are able to complete within two minutes. Otherwise, calls will be disconnected before being established.
-
If agents appear to be stuck in the "Connecting..." state before being forcefully disconnected from calls, make sure that your configured whisper flows meet the two minute maximum.
Configured block
When this block is configured, it looks similar to the following image:
