Amazon Lex integrations FAQs

Why can’t I install the Lex or Lex V2 integration?

  • Amazon Lex and Lex V2 are premium applications. You cannot install a premium application until you update your Genesys Cloud subscription, by purchasing a license to use the application in your organization. To purchase a premium app, contact Genesys Cloud Sales. For more information, see About premium applications.

Why can’t I activate my Lex or Lex V2 integration?

  • Genesys Cloud may be unable to access your AWS account with the credentials that you provide. Check that you copied the ARN correctly from the console, and that you configured the IAM role correctly. For more information, see Troubleshoot Amazon Lex integrations.

The integration incurs a “per invocation” Lex or Lex V2 charge. What defines a Lex invocation?

  • A per invocation charge occurs when you call Lex from Architect. You can design your Lex bot to prompt and capture information through multiple utterances within a single Lex invocation.

Why can’t I see any bots or aliases in Architect after I activate my Lex or Lex V2 integration?

  • Make sure that a Lex or Lex V2 bot has been created in the AWS console and received an alias.
  • Verify your AWS account. If you configured separate test and production accounts, be sure that you check for the bots in the correct account.
  • Verify that the IAM role has the correct permissions. For more information, see Troubleshoot Amazon Lex integrations.
  • For Lex V2, confirm that your bots were created in the correct AWS region. For example, us-east-1 for US, eu-west-1 for EU. For Lex V2, make sure that your integration’s advanced configuration is either {}, or that you include the region in which the bots are associated. For more information, see Configure and activate the Lex V2 integration in Genesys Cloud.

Why do I get an error message when a flow calls into a Lex or Lex V2 bot?

  • Verify that the IAM role has the permission to run bots. For more information, see Troubleshoot Amazon Lex integrations.
  • Verify that the bot still exists in your AWS account.
  • Verify that the Lex integration is still active in Integrations.

Why don’t updates I make to a Lex or Lex V2 bot in the AWS console appear in Architect?

  • If you publish a new version of a bot, make sure to give it an alias, or make sure that an existing alias is updated to use the new version of the bot.
  • Refresh your cache.
  • When you revalidate the flow or refresh the Genesys Cloud page, it may take a minute or two to update.

Why can’t I add a second Amazon Lex or Lex V2 integration?

  • Currently Genesys Cloud allows one Amazon Lex and one Lex V2 integration each per organization. However, you cannot add more than one Amazon Lex V1 and more than one Amazon Lex V2 integration.
  • To use a different AWS account with the Amazon Lex integration, change the integration’s credential to the ARN that corresponds with the new account.

Why can’t I get DTMF to work with my Amazon Lex integration?

The Genesys Cloud and Amazon Lex integration does not support DTMF. However, the Genesys Cloud and Amazon Lex V2 integration does support DTMF capability. For more information, see About the Amazon Lex V2 integration.