Connect LabAmazon Connect study

Lex V2

Fallback is a route, not a failure

Learn it in 5 minutes

HTML

About five minutes of reading

Callers who say something unexpected are still customers.

Point the fallback intent at a short prompt and a queue, or at a callback when the queue is long. Looping the same question more than twice trains people to hang up.

Use Check queue status or Get metrics if you want the fallback to behave differently when nobody is staffed.

  • Timeout and error are different from fallback. Connect them separately.
  • A DTMF escape key should exist even in a speech bot.
  • Test with noise, with silence, and with an accent the bot has not heard.
  • Do not send fallback into another bot with no exit.

Number on this page: Tries 2. Then a person or a callback

Confirm before relying. Prices, quotas, and exam names change. Use the source linked on this page.

Visual

HTML
Fallback is a route, not a failure

Both need a next block.

Worked example

HTML
  1. Miss. Fallback intent.
  2. Once more. A shorter prompt.
  3. Then. Queue or callback.
  4. Log. Count the misses.

What usually goes wrong: A fallback intent that plays 'I didn't get that' forever.

Quiz

HTML

Question 1

Which term matches this description? Attaches a Lex V2 alias to the instance. The flow still has to select that alias.

Show the cited answer

Attaches a Lex V2 alias to the instance. The flow still has to select that alias. The term is Terraform aws_connect_bot_association.

Terraform Registry: connect_bot_association community. last checked 2026-10

Question 3

Which term matches this description? Timeout and error are different from fallback. Connect them separately.

Show the cited answer

Timeout and error are different from fallback. Connect them separately. The term is Fallback is a route, not a failure (1).

Use the flow designer in Connect Customer to create flows - Amazon Connect Customer AWS docs. last checked 2026-10

Sources

HTML

Use the flow designer in Connect Customer to create flows - 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

A fallback intent that plays 'I didn't get that' forever.

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