2개 답변
- 최신
- 최다 투표
- 가장 많은 댓글
0
In the flow are you setting the correct voice that matches the bot, and setting the 'set language attribute'?
답변함 2달 전
0
Validate that the Lex bot works independently by testing it on the Lex console. This helps determine if the issue is with the bot itself or the Connect integration.
Some common reasons for integration failures are exceeding resource quotas when associating the bot, issues with IAM permissions for the CLI association, timeouts during the Lex session, or the contact flow taking the error path instead of returning the Lex response.
Ensure the Lex intents are properly identified with the customer inputs in the contact flow. Also check that the Lex alias and language match what is configured in Connect.
Keep it SIMPLE in the beginning...
관련 콘텐츠
AWS 공식업데이트됨 2년 전- AWS 공식업데이트됨 일 년 전
Yes, am setting 'English (United Kingdom)' (matches the Bot) and 'Set language attribute'.
Really odd - early version of the Bot works (essentially the Dentist Appointment booking sample) by updating the alias but the current version fails every time. Same sort of thing as the Dentist sample but different slots and modded Lambda.
Feels quite poor that it just fails without any explanation.