Connect LabAmazon Connect study

Lex V2

Slots become attributes or they vanish

Learn it in 5 minutes

HTML

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

Visual

HTML
Slots become attributes or they vanish

Picture from this room.

Worked example

HTML
  1. Fill. Lex slot.
  2. Copy. Set contact attributes.
  3. Check. Empty versus filled.
  4. Show. Whisper or workspace.

What usually goes wrong: Reading the slot in the agent whisper from a name that Lex never wrote.

Quiz

HTML

Question 1

Which term matches this description? The bot service Get customer input calls. Connect stores intent and slots on the contact.

Show the cited answer

The bot service Get customer input calls. Connect stores intent and slots on the contact. The term is Lex V2.

Add an Amazon Lex bot to Connect Customer - Amazon Connect Customer AWS docs. last checked 2026-10

Question 2

Which term matches this description? Slots are empty when the caller hangs up mid-prompt. Handle that.

Show the cited answer

Slots are empty when the caller hangs up mid-prompt. Handle that. The term is Get customer input is the Lex block (2).

Flow block definitions in the flow designer in Connect Customer - Amazon Connect Customer AWS docs. last checked 2026-10

Sources

HTML

Flow block definitions in the flow designer in Connect Customer - Amazon Connect Customer AWS docs. last checked 2026-10

The prose is a study paraphrase. The link is the source of the facts.

Ecosystem

HTML

Glossary

  • Lex V2 The bot service Get customer input calls. Connect stores intent and slots on the contact.
  • Intent What Lex thinks the caller wants. The flow branches on it.
  • Slot A value Lex fills, such as an order id. The flow copies it into an attribute.
  • Terraform aws_connect_bot_association Attaches a Lex V2 alias to the instance. The flow still has to select that alias.

Mind map

Open the Lex V2 mind map

Sister technologies

Self-service only works if the intent you branch on is the intent Lex actually returned.

Config and troubleshooting

Reading the slot in the agent whisper from a name that Lex never wrote.

The bot must be associated with the instance before Get customer input can select it. IntegrationType is LEX_BOT and IntegrationArn is the alias ARN.

IntegrationAssociation Lex in Connect

CloudFormation study snippet
Resources:
  LexAlias:
    Type: AWS::Connect::IntegrationAssociation
    Properties:
      InstanceId: !GetAtt CampusInstance.Id
      IntegrationType: LEX_BOT
      IntegrationArn: arn:aws:lex:us-west-2:123456789012:bot-alias/BOTID/ALIASID

Integration map

Join records on ContactId. The integration map room lists the seams.

Cross-platform bridges

A CUCM calling search space is not a routing profile, but the profile is the closest idea of 'who can receive what'. A partition is not a Connect object. A UCCX CSQ and a UCCE skill group map to a queue. Precision steps map to routing criteria. A script, an Architect flow, and an Avaya vector map to a contact flow.

Open the mapping room

Future hooks

Hooks you can adopt later: EventBridge contact events, the CTR stream, agent events, Kinesis Video, Customer Profiles events, Cases, Show view, data tables, External Tool, and the flow language JSON in your pipeline. Live Sync and Agentic CX are the 2026 hooks for guided and agentic experiences.

Sources and go deeper

sources.json