Independent study lab
This is an independent, free, learning-only student project. It respects every company and vendor. Trademarks belong to their owners. It is not affiliated with or endorsed by Amazon Web Services, Cisco, Genesys, Salesforce, Twilio, or any other company. If you have a concern, the page will be removed or corrected promptly through the contact form. Nothing here is sold. There are no ads. The author is happy to volunteer for any organization.
Slots become attributes or they vanish — Learn it in 5 minutes
About five minutes of reading
The agent cannot see a slot you did not copy.
After Lex returns, copy the slot values into contact attributes with names the CRM expects. Confirm the slot was filled. An empty slot with a successful intent is normal when the question was optional.
Session attributes can pass context into the next Lex turn. They are not a database.
- Validate the account id in Lambda. Do not trust a spoken string as authorization.
- Barge-in and touchtone buffering change what the caller can interrupt.
- Log the intent and the confidence behavior you actually configured.
- Keep the bot alias stable. Pointing production at a draft alias is how Friday breaks.
Number on this page: Aliases 100. Lex V2 aliases per instance, adjustable
Sources and go deeper
- Flow block definitions in the flow designer in Connect Customer - Amazon Connect Customer AWS docs. last checked 2026-10
- Add an Amazon Lex bot to Connect Customer - Amazon Connect Customer AWS docs. last checked 2026-10
- What is Amazon Lex V2? - Amazon Lex AWS docs. last checked 2026-10
- Use the flow designer in Connect Customer to create flows - Amazon Connect Customer AWS docs. last checked 2026-10
- Amazon Lex - Wikipedia Wikipedia. last checked 2026-10
- Interactive voice response - Wikipedia Wikipedia. last checked 2026-10