Evaluating AI chatbot solutions for:
- Simple to Configure – e.g. Wizard Walkthrough
- Flexible, and Mature Platform e.g. Executing backend processes
- Cost Effective and Competitive Solutions
- Rapid Deployment to XYZ platforms
The idea is almost anyone can build and deploy a chat bot for your business, small to midsize organizations.
Going through the Amazon Lex build chat process, and configuration of the Digital Assistant was a breeze. AWS employs a ‘wizard’ style interface to help the user build the Chatbot / Digital Agent. The wizard guides you through defining Intents, Utterances, Slots, and Fulfillment.
- Intents – A particular goal that the user wants to achieve (e.g. book an airline reservation)
- Utterances – Spoken or typed phrases that invoke your intent
- Slots – Data the user must provide to fulfill the intent
- Prompts – Questions that ask the user to input data
- Fulfillment – The business logic required to fulfill the user’s intent (i.e. backend call to another system, e.g. SAP)
The Amazon Lex Chatbot editor is also extremely easy to use, and to update / republish any changes.
The challenge with Amazon Lex appears to be a very limiting ability for chatbot distribution / deployment. Your Amazon Lex Chatbot is required to use one of three methods to deploy: Facebook, Slack, or Twilio SMS. Facebook is limiting in a sense if you do not want to engage your customers on this platform. Slack is a ‘closed’ framework, whereby the user of the chat bot must belong to a Slack team in order to communicate. Finally, Twilio SMS implies use of your chat bot though a mobile phone SMS.
I’ve reached out to AWS Support regarding any other options for Amazon Lex chatbot deployment. Just in case I missed something.
There is a “Test Bot” in the lower right corner of the Amazon Lex, Intents menu. The author of the business process can, in real-time, make changes to the bot, and test them all on the same page.
- Is there a way to leverage the “Test Bot” as a “no frills” Chatbot UI, and embed it in an existing web page? Question to AWS Support.
- One concern is for large volumes of utterances / Intents and slots. An ideal suggestion would allow the user a bulk upload through an Excel spreadsheet, for example.
- I’ve not been able to utilize the Amazon Lambda to trigger server side processing.
- Note: there seem to be several ‘quirky’ bugs in the Amazon Lex UI, so it may take one or two tries to workaround the UI issue.
IBM Watson Conversation also contends for this Digital Agent / Assistant space, and have a very interesting offering including dialog / workflow definition.
Both Amazon Lex and IBM Watson Conversation are FREE to try, and in minutes, you could have your bots created and deployed. Please see sites for pricing details.