- Newest
- Most votes
- Most comments
Additional Solution for Voice Contacts:
Since the "Initialize bot with message" feature is chat-only, you can achieve similar functionality for voice contacts by using a Lambda function before your Get Customer Input block. Here's how:
Approach: Use Lex PutSession API
Add an "Invoke AWS Lambda function" block before your Get Customer Input block
In your Lambda function, use the Lex PutSession API to initialize the bot session with the desired message/intent:
answered 8 months ago
Hello,
I see that Initialize bot with message with Lex in the Get Customer Input block errors out when you use the flow with a call. However, it works as expected with a chat.
The "Initialize bot with message" feature is specifically designed for chat contacts only and is not supported for voice interactions. When this feature is used with a voice contact flow, it will result in an error and route the contact to the error branch, which is the behavior you are currently observing.
This is documented in the AWS documentation titled ‘Flow block in Amazon Connect: Get customer input’ [+], which states that entering a custom message manually or dynamically to initialize the Lex bot is only support by chat contacts.
[+] "How to configure this block" →"Configure for Amazon Lex input" → "Initialize bot with message" - https://docs.aws.amazon.com/connect/latest/adminguide/get-customer-input.html#get-customer-input-properties
I hope this information helps.

hi, @Thomas_R I'm trying to configure as your way, but the Lex always treats me as new conversation. Below is my sample code to get code from user, I ensure that the bot ID/AliasID are the same in Get User Input Block
Please help me check and let me know if there is any extra steps I need to do Thanks,