Invoke Lex Intent without sample utterances or initial response - Amazon Connect Call flow

How I Solved Integrating Lex without Sample Utterances or Initial Response

1. Lambda Function Integration

First, integrate an "Invoke AWS Lambda function" block before the "Get customer input" block in your Amazon Connect flow.

2. Initiate a Text Request

Initiate a RecognizeTextCommand from inside your Lambda function. Ensure the text sent does not include any Sample Utterances from your Lex intent, to prevent unintended triggering of the initial response or first slot. Example implementation in Node.js:

try {
    const command = new RecognizeTextCommand({
      botId: "your_bot_id",
      botAliasId: "your_bot_alias_id",
      localeId: "ja_JP",
      sessionId: "your_session_id",
      text: "BYPASS_LEX_INITIAL_RESPONSE"
    });
    const response = await client.send(command);
    console.log("Lex response:", response);
    return response;
} catch(error) {
    console.error("Error communicating with Lex:", error);
    throw error;
}

3. Dynamic Integration of Slot Prompt Text

Lambda Function and Session Attributes

When the Lambda function processes the RecognizeTextCommand, it generates a response containing attributes such as messages and sessionState. These include sessionAttributes that are sent back to Amazon Connect. Here's an example of how you might structure the Lambda's JSON response:

return {
    lexSlotPrompt: response.messages?.[0]?.content,
    lexStep: response.sessionState?.sessionAttributes?.step
}

Accessing Data in Amazon Connect

Within Amazon Connect, dynamically access the attributes received from the Lambda response in the External Namespace (lexSlotPrompt and lexStep in this example). These attributes can be utilized to guide the interaction with the customer in subsequent steps.

Dynamically Setting Prompts in "Get Customer Input" Block

Utilize the lexSlotPrompt text retrieved from the External Namespace to dynamically populate the "Get customer input" block in Amazon Connect. Configure this block to employ the Text-to-speech or chat text option. Set the source to Set dynamically, specify the Namespace as External, and the Key as lexSlotPrompt. The user will be prompted accurately with the message sent back from Lex. See the below image for reference:

4. Continuation of Dialogue Handling by Lex

After the user responds in the "Get customer input" block, Lex takes over control of the interaction. It manages the dialogue, progressing through slots and intents based on the user's input. When Lex completes the interaction, it sends back a response that includes session attributes under the Lex Namespace, which can be utilized in the Amazon Connect flow as needed. (Assumes that Lex is properly connected to the "Get customer input" block and attached to the Connect instance)

By adhering to these steps, you ensure a seamless function of the setup, with Lex and Lambda configurations effectively managing and processing user inputs based on dynamically incorporated prompts.

Hi Selva,

You can. You would need to use Lambda to "warm" your Lex bot. In this scenario, your Lambda would act as the entity initiating the conversation with Lex. Assuming you are using Lex V2, use Lambda to call the "RecognizeUtterance" API. You will need to pass obvious parameters (botId, botAliasId, localeId, etc), along with a sessionId and the inputStream. The inputStream must match an utterance that is configured on the intent you want to start the conversation with. The sessionId will be used to keep the conversation context for the end-user Lex is interacting with.

Happy to assist further if needed.

I don't see a way. You could use conditional branching (assuming v2), but you need that initial utterance to start the whole process to be able to branch. What are you trying to accomplish? Are you looking to have a single bot instead of a bunch of different smaller bots?

david

Is this still the case that I have to use a Lambda API to set this? Similarly, I have a lex bot in Connect Flow that gets invoked twice but on the second go I already know the intent, I just want to re-elicit the slot variable for the already fulfilled intent. I was hoping for a way tell the Lex bot through a variable setting what intent it is...i.e. SIMPLE versus API call.

Hi, I wonder if it possible to trigger the intent without the need to use a Lambda. if that intent doesn't have utterances assigned to it?