23min

Amazon Lex

Your Persona can be configured to connect to an Amazon Lex V1 bot without any development being required in UneeQ Creator. If you don't have access to the Creator, please contact your Customer Success representative, or email help@uneeq.com for assistance connecting your integration.



Connect Lex in UneeQ Creator

In UneeQ Creator, edit the Persona you wish to connect to Lex. Selecting Amazon Lex in the Conversation Platform drop down will present you with the following fields.

Document image
Field
Description
Example
Access Key ID
Required in order to sign the requests made to AWS Lex on your behalf. To get this information, sign into your AWS console as an IAM user. In the navigation bar on the upper right, choose your account name or number and then choose "My Security Credentials". You can find more information on managing your access keys here.
ATNQXXXXXXXXXXXCWM5
Secret Access Key
Required in order to sign the requests made to AWS Lex on your behalf. To get this information, sign into your AWS console as an IAM user. In the navigation bar on the upper right, choose your account name or number and then choose "My Security Credentials". You can find more information on managing your access keys here. We take the security of your Secret Access Key seriously. We encrypt this key when you save your Persona, and these credentials cannot be seen in Creator.
lpQZJVxxxxxxxxxxxxYEFpoxxxxxxxdU4JP
Bot Name
The name of the bot you wish to connect. You can find your list of bot names in Lex's home page.
Alexa
Bot Alias
Optional. A Bot Alias is created when your bot is published, allowing you to work with different versions of your bot. If you want to connect to a specific version of your bot, you can define the Alias you want to connect to here. See here for more information on Aliases.
Alexa
Region
The AWS region in which your Lex bot is running. You can find your region next to your username in the top right of the navigation bar. You can find a list of AWS regions here.
us-east-2
Welcome Intent
Optional. If you want your Digital Human to automatically speak a welcome intent when a user starts a session, you can define the name of the Lex Intent you wish to trigger as your welcome message here.
welcome

Once you have connected your Lex bot, you can test your conversation by selecting Try on the Personas screen.



Using Lex

Intent Responses

Requests your users make to your Persona while in conversation will be sent to your bot to be matched to an Intent. The Intent Response is used to define how your digital human speaks to your users in reply.

Use the Message field to define what you want your digital human to speak:

Document image

Use the Custom Markup field to define any instructions you wish to pass with the spoken response, if required:

Document image



Message Containers

UneeQ honors the first Message container, and the first Custom Markup container within an Intent Response. If you have additional containers in your Intent Response, they are discarded to ensure your digital human does not interrupt itself.

Incorrect use of Message Containers

In this incorrect example, the second Message container would be discarded and that response would never be spoken.

Document image

If you wish to ensure multiple spearate responses are spoken in a specific sequence, Unsolicited responses can be used for this purpose.

SSML and Behavior Language with Lex

At this time, it is not possible to combine both SSML, and UneeQ's Behavior language when using Lex.

SSML and Behavior language can both be used separately from each other, but cannot be combined into the same Message field (Lex will display a SSML validation error).

✔️ Correct use of SSML & Behavior Language with Lex

XML
|

OR

XML
|

Incorrect use of SSML & Behavior Language with Lex

XML
|