Amazon Connect & Lex V2 Voice
I have been creating a customer journey using V2 to ask for the reason for a call and then an account number. In V2 when calling from lex the additional required slot of account number is not executed. So the question of account number is never requested from the customer. I thought I was something I was doing but reverted to a test in V1 and it worked fine. Has anyone also come across this or am I missing something in version 2?
When adding the slot to your intent you can mark it as mandatory to fulfil the intent.
This way you can either collect the Slot directly on the intent or if it has not been part of pass a followup question to the customer directly asking for the account number.
For example you can create a sample utterance:
Customer: I have a question about my account with the number {AccountNumber}
Where "AccountNumber" represents your slot and it will be filled on the first utterance.
Also you can have:
Customer: I have a question about my account
And the Slot "AccountNumber" is being marked as required for this intent with a Prompt "What is your account number?".
In this case the conversation would go:
Customer: I have a question about my account Bot: What is your account number? Customer: It's 123456789
Relevant questions
Amazon Connect & Lex V2 Voice
asked 2 months agoIs there a way to grab a user's voice utterance from an Amazon Lex V2 bot using Lambda calls?
asked 3 months agoHow can I pass a required field from my ipad application to Amazon Lex?
Accepted Answerasked 2 years agoAmazon Lex V2: How to identify slack user-id in lambda connected to Amazon Lex v2 bot
asked a month agoDelete BotAlias created in Amazon Lex.
asked 3 months agoAMAZON.LastName not able to recognise last name given in Prompt in AWS LEX V2
asked 10 days agoBest slot type for collecting an account number in a Lex bot
asked 2 years ago[Issue] Lambda LexEvent returns "null" values from Lex v2 Request
asked 5 months agoV2 Lex Order Flowers Lambda error
asked 2 months agoV2 Lex OrderFlowers Blueprint Lambda Error
asked 2 months ago