Skip to content

Amazon Lex and Connect - Language Spanish US

1

Hello! everyone

I have a problem, I have a Amazon Connect with a flow that connect with Amazon Lex, in Connect Everything works fine, and I have Amazon Lex set to Spanish US. When I do this, and execute the deployment with an alias and everything is fine following the documentation, in my flow, the GetCustomerInput container gives me a pure error, not letting me advance. I ran some tests with Lex in English US and everything works fine, except that when I speak to the phone, it gives me a bad transcription. For example, if I say "hello, good day," it translates "Hello India," which makes it impossible for me to work correctly. One thing that does work for me is that if I speak to it in English, everything works perfectly.

3 Answers
2
  1. In you amazon connect contact flow, set the language using the Set Voice block. (You may branch to different set Voice blocks depending on what language the customer has selected.)
  2. In the Set Voice block, check the box that says "Set language attribute".
  3. Reference your bot using the getCustomerInput block
  4. Make sure your bot has a locale (language) for the language you have selected in Connect. (They need to reference the same version of Spanish)
  5. Make sure you have "built" that locale as well (You can see the Spanish version in the bot, but you may not have built the bot for that locale).
AWS
answered a year ago
  • Thank you! the "Set language attribute" checkbox solved it for us

1

It sounds like you're experiencing two separate issues with your Amazon Connect and Amazon Lex integration: one related to Spanish language support, and another related to English transcription accuracy.

For the Spanish US issue: The error you're encountering in the GetCustomerInput container when using Spanish US is likely due to a configuration mismatch. Make sure you've properly set up the following:

  1. Verify that your Lex bot is correctly configured to support Spanish (es-US).
  2. In your Connect flow, ensure you've set the language attribute to 'es-US' in the flow component, even if you've selected a Spanish voice in the 'set voice' block.
  3. Double-check that the Lex alias you're using in Connect points to a version of your bot that includes Spanish language support.
  4. Confirm that the IAM role associated with your Connect instance has the necessary permissions to invoke the Lex V2 bot for the Spanish language version.

For the English transcription issue: The poor transcription quality you're experiencing with English could be due to a few factors:

  1. Audio quality: Ensure that the audio input is clear and free from background noise.
  2. Accent recognition: The system might be struggling with certain accents or pronunciations.
  3. Language model: The Lex bot might need more training data or fine-tuning for better recognition of specific phrases or accents.

To address these issues:

  1. For Spanish: Start with a simplified setup using a basic flow and bot configuration with minimal Spanish language support, then gradually add complexity to identify where the issue occurs.

  2. For English transcription: Consider reviewing and expanding the sample utterances in your Lex bot to improve recognition. You might also want to test with different voices or accents to see if that improves accuracy.

If problems persist after trying these steps, you may need to contact AWS support for more in-depth troubleshooting, as they can access more detailed logs and configuration information.
Sources
Amazon Lex language integration failures in my Amazon Connect instance. | AWS re:Post
Lex v2 with Connect not working | AWS re:Post

answered a year ago
0

Thanks! I try again with new Lex Bot, and I have the same result: I use Spanish US with Lupe { "Results": "Error", "ContactId": "1b5ee9ee-1d6d-416b-bdfc-26720ab27b8b", "ContactFlowId": "arn:aws:connect:us-east-1:590183772384:instance/2a5ceabb-da2a-418b-a99f-c3404fde3f30/contact-flow/5d63fda5-fe6d-44ee-813b-eb8088bc0cb1", "ContactFlowName": "Flow-Spanish-US", "ContactFlowModuleType": "GetUserInput", "Identifier": "Conectar con Lex", "Timestamp": "2025-05-13T19:53:22.291Z", "ErrorDetails": { "ErrorCode": "BadRequestException", "Message": "The service cannot process the request" } } Lex Aliases

Flow Connect

answered a year ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.