{"id":266,"date":"2020-09-24T19:51:45","date_gmt":"2020-09-24T19:51:45","guid":{"rendered":"https:\/\/machine-learning.webcloning.com\/2020\/09\/24\/expanding-amazon-lex-conversational-experiences-with-us-spanish-and-british-english\/"},"modified":"2020-09-24T19:51:45","modified_gmt":"2020-09-24T19:51:45","slug":"expanding-amazon-lex-conversational-experiences-with-us-spanish-and-british-english","status":"publish","type":"post","link":"https:\/\/salarydistribution.com\/machine-learning\/2020\/09\/24\/expanding-amazon-lex-conversational-experiences-with-us-spanish-and-british-english\/","title":{"rendered":"Expanding Amazon Lex conversational experiences with US Spanish and British English"},"content":{"rendered":"
\n

Amazon Lex<\/a> provides the power of automatic speech recognition (ASR) for converting speech to text, along with natural language understanding (NLU) for recognizing user intents. This combination allows you to develop sophisticated conversational interfaces using both voice and text for chatbots<\/a>, IVR bots, and voicebots.<\/p>\n

This week, we\u2019re announcing Amazon Lex support for British English and US Spanish. With British English, your conversational bots can be localized to understand the British English accent, while delivering responses in Amazon Polly<\/a> voices designed to sound like UK English speakers. Brilliant!<\/p>\n

With support for US Spanish, you can develop applications for the second-most widely spoken language in the United States. Amazon Lex can now accurately recognize written and spoken Spanish, while providing responses using Amazon Polly\u2019s natural sounding US Spanish voices. Listo!<\/p>\n

In this post, we consider a hypothetical appliance manufacturer in the United States. Customers calling into their service center to schedule or change a repair appointment may prefer to speak in English or Spanish. The application for this use case allows callers to select their preferred language by saying \u201cEnglish\u201d or \u201cEspa\u00f1ol\u201d when prompted. You want to provide them with the best customer service experience, no matter whether it is their washing machine or their lavadora that needs repair.<\/p>\n

We show you how to create an Amazon Connect<\/a> call center experience that supports both US English and US Spanish. Customers can schedule, change, and cancel appointments, using a fully automated solution that converses with them in their preferred language.<\/p>\n

Building a multi-language conversational experience<\/h2>\n

This post uses the following sample conversations:<\/p>\n

Agent:<\/strong> Thank you for calling. To continue in English, say \u201cEnglish,\u201d for Spanish, say \u201cEspa\u00f1ol.\u201d<\/p>\n

US English<\/u><\/em><\/p>\n

Agent:<\/strong> I can schedule or change a repair appointment. How can I help?<\/p>\n

User:<\/strong> I want to get my dishwasher fixed.<\/p>\n

Agent:<\/strong> What city are you in?<\/p>\n

User:<\/strong> Philadelphia<\/p>\n

Agent:<\/strong> I have technicians available next week. When would you prefer to have them visit?<\/p>\n

User:<\/strong> September 24th at noon<\/p>\n

Agent:<\/strong> OK, you are all set for your dishwasher repair in Philadelphia on the 24th of September at noon.<\/p>\n

US Spanish <\/u><\/em><\/p>\n

Agent:<\/strong> Puede reservar o cambiar una cita de reparaci\u00f3n. \u00bfC\u00f3mo puedo ayudar?<\/p>\n

User:<\/strong> Me gustaria programar una cita<\/p>\n

Agent:<\/strong> Para qu\u00e9 tipo de aparato?<\/p>\n

User:<\/strong> Refrigerador<\/p>\n

Agent:<\/strong> En que ciudad estas?<\/p>\n

User:<\/strong> Brooklyn<\/p>\n

Agent:<\/strong> En que fecha te gustaria que vinieran?<\/p>\n

User:<\/strong> 24 de Septiembre<\/p>\n

Agent:<\/strong> Bien, ya est\u00e1 todo listo para la reparaci\u00f3n de su refrigerador en 24 de Septiembre, 2020.<\/p>\n

To support these conversation models, you need to create Lex bots with relevant user intents. In this post, we create intents for ScheduleAppointment<\/code>, ModifyAppointment<\/code>, and CancelAppointment<\/code> (and in Spanish, ReservarCita<\/code>, ModificarCita<\/code>, CancelarCita<\/code>).<\/p>\n

Deploying the sample Lex bots<\/h2>\n

To create the sample bots, perform the following steps. For this post, you create two Amazon Lex bots: AppointmentBot_enUS<\/code> for US English, and AppointmentBot_esUS<\/code> for US Spanish. To follow along with this post, you can create these Lex bots yourself on the Amazon Lex console, or import them directly.<\/p>\n

    \n
  1. To import the bots, download the US English bot<\/a> and the US Spanish bot<\/a>\n<\/li>\n
  2. On the Amazon Lex console, choose<\/li>\n
  3. Select the zip<\/strong> that you downloaded, and choose Import<\/strong>.<\/li>\n
  4. When the import process is complete, choose AppointmentBot_enUS<\/strong>, and choose<\/li>\n
  5. When the build it complete, go back to the Amazon Lex console main window, and choose Import<\/strong>.<\/li>\n
  6. Select the zip<\/strong> that you downloaded, and choose Import<\/strong>.<\/li>\n
  7. When the import process is complete, choose AppointmentBot_esUS<\/strong>, and choose<\/li>\n<\/ol>\n

    At this point, you should have two working Lex bots: one for US English, and one for US Spanish.<\/p>\n

    Creating your Amazon Connect instance<\/h3>\n

    In this section, we integrate the bots with an Amazon Connect cloud-based call center instance. The first step is to create the Amazon Connect instance:<\/p>\n

      \n
    1. On the AWS Management Console<\/a>, choose Amazon Connect<\/strong>.<\/li>\n
    2. If this is your first Amazon Connect instance, choose Get started<\/strong>; otherwise, choose Add an instance<\/strong>.<\/li>\n
    3. For Identity management<\/strong>, choose Store users within Amazon Connect<\/strong>.<\/li>\n
    4. Enter a URL prefix, such as appointment-bot-############<\/code>, where ############ is your current AWS account number.<\/li>\n
    5. Choose Next step<\/strong>.<\/li>\n
    6. For Create an administrator<\/strong>, enter a name, password, and email address.<\/li>\n
    7. Choose Next step<\/strong>.<\/li>\n
    8. For Telephony Options<\/strong>, leave both call options selected by default.<\/li>\n
    9. Choose Next step<\/strong>.<\/li>\n
    10. For Data storage<\/strong>, choose Next step<\/strong>.<\/li>\n
    11. Review the settings and choose Create instance<\/strong>.<\/li>\n<\/ol>\n

      Associating your bots with your Amazon Connect instance<\/h3>\n

      Now that you have an Amazon Connect instance, you can claim a phone number, create a contact flow, and integrate your contact flow with the two Lex bots you created in the prior step. First, associate your bots with your Amazon Connect instance:<\/p>\n

        \n
      1. On the Amazon Connect console, open your instance by choosing the Instance Alias<\/strong>\n<\/li>\n
      2. Choose Contact flows<\/strong>.<\/li>\n
      3. From the drop-down list, choose AppointmentBot_enUS<\/strong>. If you don\u2019t see the bot in the list, make sure you have selected the same Region you used when you created your Lex bot.<\/li>\n
      4. Choose + Add Lex Bot<\/strong>.<\/li>\n
      5. From the drop-down list, choose AppointmentBot_esUS<\/strong> and choose + Add Lex Bot<\/strong>.<\/li>\n<\/ol>\n

        Configuring Amazon Connect to work with your bot<\/h3>\n

        Now you can use your bots with Amazon Connect. First, claim a phone number for your Amazon Connect instance:<\/p>\n

          \n
        1. On the Amazon Connect console, choose Overview<\/strong>.<\/li>\n
        2. Choose the Amazon Connect<\/strong>\n<\/li>\n
        3. Choose the Login URL<\/strong> link, and enter the user name and password you specified earlier.<\/li>\n
        4. On the Amazon Connect console, for Step 1<\/strong>, Choose Begin<\/strong>.<\/li>\n
        5. For your phone number, choose a country, Direct Dial or Toll Free, and a phone number.<\/li>\n
        6. Choose Next<\/strong>.<\/li>\n
        7. If you want to test your new phone number, try it on the next screen or choose Skip for now<\/strong>.<\/li>\n<\/ol>\n

          For this post, you can skip the hours of operation, creating queues, and creating prompts. For more information on these features, see the Amazon Connect Administrator Guide<\/a>. Now let\u2019s import the contact flow.<\/p>\n

            \n
          1. Download and unzip the sample Amazon Connect contact flow for this post: manage_repairs.zip<\/a>.<\/li>\n
          2. On the Amazon Connect console, go to Step 5<\/strong>, Create contact flows<\/strong>, choose View contact flows<\/strong>.<\/li>\n
          3. Choose Create contact flow<\/strong>.<\/li>\n
          4. From the drop-down at the top right side of the page, choose Import flow (beta)<\/strong>.<\/li>\n
          5. Choose Select<\/strong> and select the manage-repairs.json<\/code> file you downloaded, and select Import<\/strong>.<\/li>\n
          6. Choose Save<\/strong>, and then Publish<\/strong>.<\/li>\n<\/ol>\n

            Your contact flow should look like the following screenshot.<\/p>\n

            \"\"<\/p>\n

              \n
            1. Choose the Routing<\/strong> icon from the side menu, and choose Phone numbers<\/strong>.<\/li>\n
            2. Choose your phone number to edit it, and change the contact flow or IVR to the Manage Repairs<\/code> contact flow you just created.<\/li>\n
            3. Choose Save<\/strong>.<\/li>\n<\/ol>\n

              Your Amazon Connect instance is now configured to work with your Amazon Lex bots. Try calling the phone number to see how it works!<\/p>\n

              Conclusion<\/h2>\n

              With the addition of British English and US Spanish language support, along with US English and Australian English, Amazon Lex allows you to create bots that can converse with users in their native language. You can combine Amazon Lex with Amazon Connect to create streamlined, multi-language call center user experiences in minutes. The additional language support in Amazon Lex is available at the same price, and in the same Regions, as US English. You can try these languages via the console, the AWS Command Line Interface<\/a> (AWS CLI), and the AWS SDKs.<\/p>\n

              \n

              About the Authors<\/h3>\n

              \"\"Claire Mitchell <\/strong>is a Design Consultant with the AWS Professional Services Conversational AI team. Occasionally she spends time exploring speculative design practices, textiles, and playing the drums.<\/p>\n

              \u00a0<\/p>\n

              \u00a0<\/p>\n

              \u00a0<\/p>\n

              \u00a0<\/p>\n

              \"\" Brian Yost<\/strong> is a Senior Consultant with the AWS Professional Services Conversational AI team. In his spare time, he enjoys mountain biking, home brewing, and tinkering with technology.<\/p>\n

              \u00a0<\/p>\n

              \u00a0<\/p>\n

              \u00a0<\/p>\n

              \u00a0<\/p>\n

              \"\"<\/strong>As a Product Manager on the Amazon Lex team, Harshal Pimpalkhute<\/strong> spends his time trying to get machines to engage (nicely) with humans.<\/p>\n

              \u00a0<\/p>\n<\/p><\/div>\n","protected":false},"excerpt":{"rendered":"

              https:\/\/aws.amazon.com\/blogs\/machine-learning\/expanding-amazon-lex-conversational-experiences-with-us-spanish-and-british-english\/<\/p>\n","protected":false},"author":0,"featured_media":267,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[3],"tags":[],"_links":{"self":[{"href":"https:\/\/salarydistribution.com\/machine-learning\/wp-json\/wp\/v2\/posts\/266"}],"collection":[{"href":"https:\/\/salarydistribution.com\/machine-learning\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/salarydistribution.com\/machine-learning\/wp-json\/wp\/v2\/types\/post"}],"replies":[{"embeddable":true,"href":"https:\/\/salarydistribution.com\/machine-learning\/wp-json\/wp\/v2\/comments?post=266"}],"version-history":[{"count":0,"href":"https:\/\/salarydistribution.com\/machine-learning\/wp-json\/wp\/v2\/posts\/266\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/salarydistribution.com\/machine-learning\/wp-json\/wp\/v2\/media\/267"}],"wp:attachment":[{"href":"https:\/\/salarydistribution.com\/machine-learning\/wp-json\/wp\/v2\/media?parent=266"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/salarydistribution.com\/machine-learning\/wp-json\/wp\/v2\/categories?post=266"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/salarydistribution.com\/machine-learning\/wp-json\/wp\/v2\/tags?post=266"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}