- Newest
- Most votes
- Most comments
Based on your description of the challenges with your Amazon Connect voice bot, I can provide some recommendations for both the voice quality and latency issues.
Voice Quality Improvements
For the robotic-sounding voice issue with Amazon Polly Neural TTS:
-
Verify Neural Engine Settings: Ensure that the engine parameter is explicitly set to "neural" in your voice settings. The default engine is "standard" if not specified, which could explain why you're still getting robotic-sounding speech despite selecting a neural voice.
-
Use SSML Tags for Special Words: For words that need to sound more natural, consider using SSML tags with phonetic pronunciation. This can help with specific words that might otherwise sound robotic even when using Neural TTS.
-
Voice Selection in Connect: Make sure your Amazon Connect instance is configured to "Use the best available voice" in your instance settings, and verify that your "Set Voice" block settings are properly configured to work with Lex V2.
Latency Reduction Strategies
To address the 5+ second delay in your voice bot responses:
-
Minimize Conversation Latency: Use latency-optimized inference for foundation models like Amazon Nova Pro to maintain natural conversation flow.
-
Select Efficient Foundation Models: Consider using smaller, faster foundation models that can deliver quick responses while maintaining quality.
-
Implement Prompt Caching: Utilize prompt caching to optimize for both speed and cost efficiency, especially in complex scenarios requiring knowledge retrieval.
-
Deploy TTS Fillers: Use natural filler phrases (such as "Let me look that up for you") before intensive operations to maintain user engagement while the system processes longer-running calls to your foundation models.
-
Proper Versioning and Aliases: Avoid using the "testbotalias" in production. Create proper versions and aliases for your Lex bot to improve speed and reduce delay.
-
Architectural Considerations: The current delay is likely occurring in the Bedrock → Lambda → Lex → Polly chain. For real-time voice interactions, consider:
- Using Amazon Connect Contact Lens real-time streaming or Kinesis Video Streams for accessing live voice
- Implementing Amazon Transcribe Streaming for real-time speech-to-text conversion
- Setting up a lightweight WebSocket or API Gateway layer that stays open throughout the call for faster round trips
- Region Selection: Consider the trade-off between advanced capabilities like low-latency features and prompt caching (which may only be available in certain regions) versus selecting a region geographically closer to your end-users.
For truly real-time two-way bot conversations, you might want to explore Amazon Connect's External Voice Transfer feature, which allows Connect to SIP conference the call with your bot, letting your bot handle the media while Connect maintains control of the call.
By implementing these recommendations, you should be able to achieve a more natural-sounding voice bot with reduced latency, improving the overall customer experience.
Sources
Voice in Amazon Lex still sounds robotic and delayed even after setting Joanna (NTTS) | AWS re:Post
Building intelligent AI voice agents with Pipecat and Amazon Bedrock – Part 1 | Artificial Intelligence
Is it possible to get real-time voice from a call with just a lambda? | AWS re:Post
answered a year ago
Please try Generative voices in Polly - they are the most natural ones in the offering: https://docs.aws.amazon.com/polly/latest/dg/generative-voices.html
answered a year ago
Relevant content
- AWS OFFICIALUpdated 3 years ago
- AWS OFFICIALUpdated 2 months ago
