Select your cookie preferences

We use essential cookies and similar tools that are necessary to provide our site and services. We use performance cookies to collect anonymous statistics, so we can understand how customers use our site and make improvements. Essential cookies cannot be deactivated, but you can choose “Customize” or “Decline” to decline performance cookies.

If you agree, AWS and approved third parties will also use cookies to provide useful site features, remember your preferences, and display relevant content, including relevant advertising. To accept or decline all non-essential cookies, choose “Accept” or “Decline.” To make more detailed choices, choose “Customize.”

Use alternate intent attributes in Amazon Lex - Amazon Connect

Use alternate intent attributes in Amazon Lex

Usually you configure flows to branch on the winning Lex intent. However, in some situations, you might want to branch on an alternate intent. That is, what the customer might have meant.

The following image shows the Properties page of the Check contact attributes block. It is configured to check a Lex attribute.

The properties page of the Check contact attributes block.
  1. Intent name is the name of an alternate intent in Lex. It's case sensitive and must match what's in Lex exactly.

  2. Intent Attribute is what Amazon Connect is going to check. In this example, it's going to check the Intent Confidence Score.

  3. Conditions to check: If Lex is 70% certain the customer meant the alternate intent instead of the winning intent, branch.

PrivacySite termsCookie preferences
© 2025, Amazon Web Services, Inc. or its affiliates. All rights reserved.