Using audio filler to improve bot responsiveness
Audio filler plays brief background audio, such as a light melody or soft keystrokes, during the pause between the end of a user's utterance and the start of the bot's response. This masks processing delays and keeps voice conversations feeling natural.
Note
At launch, audio filler is available for bot locales that support speech-to-speech interactions and have unifiedSpeechSettings configured. Support for additional conversation modes will roll out over the next several months.
Available audio filler types
Amazon Lex V2 provides seven built-in filler sounds, organized into two families:
Melody - Chipper Chime
Melody - Curious Crawl
Melody - Rising Ripple
Melody - Patient Ping
Melody - Pondering Pong
Typing - Kinetic Keys
Typing - Quiet Qwerty
Use the Play audio preview button in the Amazon Lex V2 console to hear each option before you save it to a bot locale.
Timing parameters
You can tune three timing parameters to control when audio filler plays and how it transitions into the bot response:
startDelayInMilliseconds-
Time to wait after the end of the user's utterance before starting audio filler playback. Valid range is
500to5000milliseconds. Default is1000. minimumPlayDurationInMilliseconds-
Minimum time audio filler plays after it has started, even if the bot response becomes ready sooner. Valid range is
1000to5000milliseconds. Default is3000. responseDeliveryDelayInMilliseconds-
Silent delay inserted between the end of audio filler playback and the start of the bot's response. Valid range is
200to1000milliseconds. Default is500.
Configuring audio filler
You can configure audio filler when creating or updating a bot locale through the Amazon Lex V2 console, the Amazon Connect Conversational AI designer, or the AWS CLI and SDKs.
Audio filler with AI agent interim messages
Audio filler works alongside AI agent interim messages. When an AI agent sends an interim message to the caller (for example, "Let me look that up for you"), the start delay timer is measured from the end of that interim message rather than from the original invocation. This prevents audio filler from overlapping with the agent's speech and ensures the delay the caller experiences is measured from the most recent audio they heard.
Audio filler with dialog and fulfillment code hooks
Audio filler also plays during the processing gap introduced by Lambda dialog code hooks and fulfillment code hooks. The same timing parameters apply, so callers hear a consistent experience whether your bot delegates processing to an AI agent, a code hook, or both in the same turn.
Best practices for audio filler
-
Match the filler to your brand voice. Use melody fillers for consumer or retail experiences, and typing fillers when users expect the bot to be actively working on a task.
-
Tune the start delay to your latency profile. If most bot responses are faster than
startDelayInMilliseconds, the filler will rarely play. Lower the delay for latency-heavy workloads and raise it for fast-responding bots. -
Keep the minimum play duration short for fast bots. A long
minimumPlayDurationInMillisecondson a fast bot adds perceived latency by holding the filler after the response is ready. -
Test with representative traffic. Validate the filler choice and timing in realistic conversations before rolling out to production.