Developing a continuing company cleverness dashboard for the Amazon Lex bots

You’ve rolled away an interface that is conversational by Amazon Lex, with a target of enhancing the consumer experience for the clients. So Now you desire to monitor how good it is working. Are your prospects finding it helpful? Exactly How will they be using it? Do they enjoy it adequate to keep coming back? How will you analyze their interactions to add more functionality? With no clear view into your bot’s user interactions, concerns such as these may be hard to answer. The current launch of conversation logs for Amazon Lex makes it simple to obtain near-real-time exposure into just exactly exactly how your Lex bots are performing, centered on real bot interactions. With discussion logs, all bot interactions could be kept in Amazon CloudWatch Logs log teams. You should use this conversation information to monitor your bot and gain actionable insights for improving your bot to enhance the consumer experience for the customers.

In a previous article, we demonstrated just how to enable discussion logs and make use of CloudWatch Logs Insights to evaluate your bot interactions. This post goes one action further by showing you the way to integrate having an Amazon QuickSight dashboard to get business insights. Amazon QuickSight enables you to effortlessly produce and publish interactive dashboards. It is possible to pick from a considerable collection of visualizations, maps, and tables, and include interactive features such as for example drill-downs and filters.

Solution architecture

In this company cleverness dashboard solution, you are going to make use of an Amazon Kinesis information Firehose to constantly stream discussion log information from Amazon CloudWatch Logs to an amazon bucket that is s3. The Firehose delivery flow employs A aws that is serverless lambda to transform the raw information into JSON information documents. Then you’ll usage an AWS Glue crawler to automatically discover and catalog metadata because of this information, therefore with Amazon Athena that you can query it. A template is roofed below which will produce an AWS CloudFormation stack for you personally containing a few of these AWS resources, along with the required AWS Identity and Access Management (IAM) roles. By using these resources in position, you may then make your dashboard in Amazon QuickSight and connect with Athena being a data source.

This solution lets you make use of your Amazon Lex conversation logs information to generate live visualizations in Amazon QuickSight. As an example, utilising the AutoLoanBot through the mentioned before post, you are able to visualize individual needs by intent, or by intent and individual, to get a knowledge about bot use and individual pages. The dashboard that is following these visualizations:

This dashboard shows that re re re payment task and loan requests are many greatly utilized, but checking loan balances is utilized notably less often.

Deploying the answer

To have started, configure an Amazon Lex bot and enable conversation logs in america East (N. Virginia) Area.

For the instance, we’re utilizing the AutoLoanBot, but you should use this solution to construct an Amazon QuickSight dashboard for just about any of the Amazon Lex bots.

The AutoLoanBot implements an interface that is conversational allow users to start that loan application, check out the outstanding stability of these loan, or make that loan re payment. It includes the intents that are following

• Welcome – reacts to a short greeting from the consumer
• ApplyLoan – Elicits information like the user’s title, target, and Social Security Number, and produces a brand new loan demand
• PayInstallment – Captures the user’s account number, the very last four digits of these Social Security quantity, and re re payment information, and operations their month-to-month installment
• CheckBalance – utilizes the user’s account quantity plus the final four digits of the Social Security quantity to give you their outstanding stability
• Fallback – reacts to any needs that the bot cannot process utilizing the other intents

To deploy this solution, finish the steps that are following

1. After you have your bot and discussion logs configured, use the following key to introduce an AWS CloudFormation stack in us-east-1:
2. For Stack title, enter title for the stack. This post makes use of the true title lex-logs-analysis:
3. Under Lex Bot, for Bot, enter the title of one’s bot.
4. For CloudWatch Log Group for Lex discussion Logs, enter the true name for the CloudWatch Logs log team where your discussion logs are configured.

This post utilizes the bot AutoLoanBot and also the log team car-loan-bot-text-logs:

1. Select Upcoming.
2. Include any tags you might wish for the CloudFormation stack.
3. Select Upcoming.
4. Acknowledge that IAM functions is likely to be produced.
5. Select Create stack.

After a few momemts, your stack ought to be complete and retain the resources that are following

• A Firehose distribution stream
• An AWS Lambda change function
• A CloudWatch Logs log group when it comes to Lambda function
• An S3 bucket
• An AWS Glue crawler and database
• Four IAM functions

This solution makes use of the Lambda blueprint function kinesis-firehose-cloudwatch-logs-processor-python, which converts the data that are raw the Firehose delivery flow into specific JSON information documents grouped into batches. To learn more, see Amazon Kinesis information Firehose Data Transformation.

AWS CloudFormation should also provide successfully subscribed the Firehose delivery flow to your CloudWatch Logs log team. You can view the membership within the AWS CloudWatch Logs system, as an example:

As of this true point, you ought to be in a position to test thoroughly your bot, see your log information moving from CloudWatch Logs to S3 through the Firehose delivery flow, and query your discussion log information making use of Athena. You can use a test script to generate log data (conversation logs do not log interactions through the AWS Management Console) if you are using the AutoLoanBot,. To install the test script, choose test-bot. Zip.

The Firehose delivery flow operates every minute and channels the info towards the bucket that is s3. The crawler is configured to operate every 10 minutes(you can also anytime run it manually through the system). Following the crawler has run, you can easily query important computer data via Athena. The screenshot that is following a test question you can test into the Athena Query Editor:

This query indicates that some users are operating into dilemmas wanting to check always their loan stability. You are able to setup Amazon QuickSight to do more in-depth analyses and visualizations with this information. To get this done, finish the following actions:

1. Through the console, launch Amazon QuickSight.

If you’re perhaps not already making use of QuickSight, you can begin with a free of charge test making use of Amazon QuickSight Standard Edition. You will need to offer a merchant account title and notification email. Along with selecting Amazon Athena as an information source, be sure to through the S3 bucket where your discussion log information is kept (you are able to find the bucket title in your CloudFormation stack).

Normally it takes a short while to create your account up.

1. As soon as your account is prepared, choose New analysis.
2. Select Brand Brand Brand New information set.
3. Select Anthena.
4. Specify the information supply auto-loan-bot-logs.
5. Select Validate connection and confirm connectivity to Athena.
6. Select Create repository.
7. Choose the database that AWS Glue created (which include lexlogsdatabase into the true name).

Incorporating visualizations

You will include visualizations in Amazon QuickSight. To produce the 2 visualizations shown above, finish the steps that are following

1. Through the + include symbol at the top of the dashboard, select Add visual.
2. Drag the intent industry to your Y axis from the artistic.
3. Include another artistic by saying the initial two actions.
4. In the second visual, drag userid to your Group/Color industry well.
5. To sort the visuals, drag requestid to your Value field in every one.

You can california cash advance easily produce some extra visualizations to gain some insights into how good your bot is doing. For instance, it is possible to effectively evaluate how your bot is giving an answer to your users by drilling on to the needs that dropped until the fallback intent. For this, replicate the visualizations that are preceding change the intent dimension with inputTranscript, and put in a filter for missedUtterance = 1 ) The after graphs reveal summaries of missed utterances, and missed utterances by individual.

The screen that is following shows your term cloud visualization for missed utterances.

This sort of visualization offers a powerful view into just just how your users are getting together with your bot. In this instance, you could utilize this understanding to enhance the CheckBalance that is existing intent implement an intent to assist users put up automatic re re payments, industry basic questions regarding your car loan solutions, and also redirect users up to a sibling bot that handles home loan applications.

Summary

Monitoring bot interactions is crucial in building effective interfaces that are conversational. It is possible to know very well what your users want to achieve and just how to streamline their consumer experience. Amazon QuickSight in tandem with Amazon Lex conversation logs makes it simple to produce dashboards by streaming the discussion information via Kinesis Data Firehose. You are able to layer this analytics solution along with all of your Amazon Lex bots – give it a go!