ML 12129 image001
This post walks you through a few new features that make it simple to design a conversational flow entirely within Amazon Lex that adheres to best practices for IVR design related to retry prompting. We also cover how to configure a DTMF-only prompt as well as other attributes like timeouts and barge-in.
When designing an IVR solution, it’s best practice to provide an initial prompt that is short and to the point in order to allow a customer to get through the voice interaction quickly. If the system doesn’t understand, it needs to provide a more detailed prompt to guide the user to provide the required information. Should that fail, it’s best practice to fall back to DTMF, and ask the caller to enter the information using their dial pad.
Sometimes, we may also want to define a slot value as voice or DTMF only in order to provide more control over how the system accepts input.
Amazon Lex now lets you set session attributes to control voice and DTMF input modes. You can control voice and DTMF configuration for each slot separately for the initial prompt and each retry prompt using the new advance retry settings. There is also a new setting: Play the messages in order. This sets the message variations for a slot to play in the order they have been entered instead of randomly.
The following short video provides an overview of the concepts covered in this post.
To demonstrate these new features, we deploy a new Amazon Lex bot starting with the BookTrip example bot. We modify the configurations for capturing the CheckinDate
slot value. We then integrate the bot into an Amazon Connect contact flow for testing.
To implement this solution, you need the following prerequisites:
To start building your bot, complete the following steps:
BookHotel
intent.BookHotel
intent.CheckInDate
block.You can use an existing Amazon Connect instance, or create a new instance. To integrate the Amazon Lex bot, complete the following steps:
Welcome to Octank travel and hospitality. How can we help you today?
I want to book a hotel.What city will you be staying in?
New YorkWhat day do you want to check in?
Hedgehog. (You can say anything here that is not interpreted as a date.)What day do you want to check in? You can say things like tomorrow, Next Sunday, or November 13th.
Hedgehog.Please enter the day you want to check in using four-digit year, two-digit-month, and two-digit day.
Sunday. (This will be transformed to the corresponding date. Even though the prompt asked for DTMF, voice is still enabled. If you want to disable voice for this specific retry attempt, this can be done in the advanced retry settings of the bot.)How many nights will you be staying?
Four.What type of room would you like, queen, king, or deluxe?
King.Okay, I have you down for a four-night stay in New York starting {CheckInDate}. Shall I book the reservation?
Yes
Notice how the three slot prompts were played in order.
You can now add session attributes that are sent to the Amazon Lex bot.
x-amz-lex:allow-audio-input:BookHotel:CheckInDate
to False.x-amz-lex:allow-audio-input:BookHotel:CheckInDate
to True (or just remove it, since the bot is configured to allow voice per default) and set x-amz-lex:allow-interrupt:*:*
to False.You’re now able to speak the date, but you can’t interrupt the prompt that is asking for the date.
For a list of these and other attributes that you can use to disable DTMF input or modify the timeouts for voice and DTMF, refer to Configuring timeouts for capturing user input.
You can also set session attributes in the Get customer input block using external or user-defined attributes. This makes it possible to store the configuration for your Amazon Lex bots externally, and fetch them using an AWS Lambda function. You can also update these attributes based on business rules. This would, for example, allow you to let a customer opt-in to setting all interactions to DTMF only if they’re calling from a noisy environment.
When you’re done using this solution, delete the Amazon Lex bot and release the phone number if you claimed a new one.
These recently released features make it easier to design a conversational flow entirely within Amazon Lex that adheres to best practices for IVR design related to retry prompts. These new attributes also make it possible to define the behavior of an Amazon Lex bot through configuration, allowing changes to be made without updating and redeploying contact flows.
Try out these new features to see how they can provide a better customer experience in your contact center!
You can find the workflow by scrolling down on this page: https://comfyanonymous.github.io/ComfyUI_examples/flux/ submitted by /u/comfyanonymous…
Machine learning practitioners spend countless hours on repetitive tasks: monitoring model performance, retraining pipelines, data…
This post is divided into four parts; they are: • Why Attention Masking is Needed…
Artificial intelligence (AI) is an umbrella computer science discipline focused on building software systems capable…
With advances in generative AI, there is increasing work towards creating autonomous agents that can…
Amazon Bedrock Guardrails provides configurable safeguards to help build trusted generative AI applications at scale.…