{"id":1741,"date":"2019-05-25T13:27:38","date_gmt":"2019-05-25T13:27:38","guid":{"rendered":"https:\/\/nub8.net\/?p=1741"},"modified":"2026-04-08T14:07:07","modified_gmt":"2026-04-08T14:07:07","slug":"chatbots-with-amazon-lex","status":"publish","type":"post","link":"https:\/\/www.nub8.net\/es\/chatbots-with-amazon-lex\/","title":{"rendered":"Chatbots with Amazon Lex"},"content":{"rendered":"<p>Chatbots empower you to unlock a range of benefits, including better-quality customer satisfaction, increased reach, and more profitable service delivery. Combine them with artificial intelligence and analytics, and they become a driving force of customer and employee engagement. Lex, as a fully managed Amazon service, would also scale spontaneously as the bots\u2019 practice increased, meaning developers would only pay for the number of text or voice queries that Lex processes. Lex can be used by developers who want to build their excellent conversational applications, like chatbots.<\/p>\n<h2><strong>Amazon Lex Concepts<\/strong><\/h2>\n<h3><strong>Intent<\/strong><\/h3>\n<p>Intent is a specific goal that the user needs to achieve. To build an Amazon Lex bot, you will need to find a set of actions &#8211; known as &#8216;intents\u2019 &#8212; that you want your bot to fulfill. A bot can have multiple intents.<br \/>\nThere are two kinds of intents:<br \/>\nBuilt-in Intents\u200a\u2014\u200aThese are elementary intents delivered by Lex. You can use them to do normal actions like allowing a user to cancel, get help, etc.<br \/>\nCustom Intents\u200a\u2014\u200aCustom intents are delivered by developers to carry out a precise set of actions.<\/p>\n<h3><strong>Utterances<\/strong><\/h3>\n<p>Utterances are the phrases which are used to raise an intent.<\/p>\n<h3><strong>Slots<\/strong><\/h3>\n<p>To achieve an intent, the Amazon Lex bot wants information from the user. This information is taken in \u2018slots\u2019.<\/p>\n<h3><strong>Prompts<\/strong><\/h3>\n<p>Prompts are the questions which are requested to get input from the user.<\/p>\n<h3><strong>Fulfillment <\/strong><\/h3>\n<p>Fulfillment is the business logic that perform the user\u2019s intent. Lex maintenances the use of Lambda functions for fulfillment.<br \/>\n<img fetchpriority=\"high\" decoding=\"async\" class=\"size-full wp-image-1743\" src=\"https:\/\/nub8.net\/wp-content\/uploads\/2019\/05\/Nub8-AmazonLex-Flow.jpg\" alt=\"Nub8-AmazonLex-Flow\" width=\"794\" height=\"220\" \/><\/p>\n<h2><strong>Difference Amazon Lex vs Amazon Alexa<\/strong><\/h2>\n<p>ALEXA is a consumer product and brand of Amazon. Users know they\u2019re talking to Alexa and they already have a \u2018relationship\u2019 with her.<br \/>\nLex is not to be to mixed up with Alexa. Lex is development platform for conversational solutions. Lex is whats inside Alexa. Lex supports both Speech and Text interfaces. Secondly, Lex has SDKs for Android &amp; iOS, and REST endpoints.<br \/>\nWhile Alexa can be used for a variation of tasks, including shopping and integrating with apps, Lex is intended for companies to provide a service based on what users say to the platform. Still, Lex will help Alexa become smarter and vice versa.<\/p>\n<p><a href=\"https:\/\/www.nub8.net\/es\/services\/\">Nub8<\/a> utilizes its Amazon AWS knowledge and proficiency to analyze, design, develop Lex solutions and services. Our Amazon AWS consultant can help you to develop and integrate chat bots and voice bots with your existing applications and solutions. We build tremendous conversations that provide the best customer engagement that is correct for your business needs.<\/p>","protected":false},"excerpt":{"rendered":"<p>Chatbots empower you to unlock a range of benefits, including better-quality customer satisfaction, increased reach, and more profitable service delivery. Combine them with artificial intelligence and analytics, and they become a driving force of customer and employee engagement. Lex, as a fully managed Amazon service, would also scale spontaneously as the bots\u2019 practice increased, meaning [&hellip;]<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[26],"tags":[32],"class_list":["post-1741","post","type-post","status-publish","format-standard","hentry","category-aws-en","tag-aws"],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/www.nub8.net\/es\/wp-json\/wp\/v2\/posts\/1741","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.nub8.net\/es\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.nub8.net\/es\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.nub8.net\/es\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/www.nub8.net\/es\/wp-json\/wp\/v2\/comments?post=1741"}],"version-history":[{"count":1,"href":"https:\/\/www.nub8.net\/es\/wp-json\/wp\/v2\/posts\/1741\/revisions"}],"predecessor-version":[{"id":11971,"href":"https:\/\/www.nub8.net\/es\/wp-json\/wp\/v2\/posts\/1741\/revisions\/11971"}],"wp:attachment":[{"href":"https:\/\/www.nub8.net\/es\/wp-json\/wp\/v2\/media?parent=1741"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.nub8.net\/es\/wp-json\/wp\/v2\/categories?post=1741"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.nub8.net\/es\/wp-json\/wp\/v2\/tags?post=1741"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}