{"id":26919,"date":"2021-02-19T09:57:37","date_gmt":"2021-02-19T09:57:37","guid":{"rendered":"https:\/\/developer.kore.ai\/v9-1\/?p=26919"},"modified":"2021-08-17T11:06:48","modified_gmt":"2021-08-17T10:06:48","slug":"intent-scoping-using-group-node","status":"publish","type":"post","link":"https:\/\/developer.kore.ai\/v9-1\/docs\/bots\/how-tos\/intent-scoping-using-group-node\/","title":{"rendered":"Intent Scoping using Group Node"},"content":{"rendered":"
\r\n\t
\r\n\t\t
\r\n\t\t\t

Adding contextually relevant sub-intents is one of the important elements in building conversational bots. Contextually relevant intents could be required for various purposes like taking a different path in the dialog flow, amending previously provided entity values, etc.<\/p>\n

We have seen how to use the contextual data in combination with the interruption handling to achieve a more natural and human-like interaction with the bot in How to Manage Context Switching<\/a>.\u00a0This feature primarily aims to let you define the interruption behavior across any two intents. Defining behavior for contextual relevant intents with custom fulfillment behavior can be difficult using this feature.<\/p>\n

With the objective of simplifying the contextual NLU, the Group node functionality has been enhanced with intent scoping, training, and fulfillment configuration, refer here for details<\/a>.<\/p>\n

In this How-To, we will explore a scenario in a Flight Booking Bot which includes digressions, amending input values, and contextual follow-ups queries. We will be using the Group Node to achieve all this easily and from a single place.<\/p>\n\r\n\t\t<\/div>\r\n\t<\/div>\r\n

<\/div><\/div>\r\n\t
\r\n\t\t
\r\n\t\t\t

Problem Statement<\/span><\/h2>\n

During the course of booking a flight ticket:<\/p>\n

    \n
  1. the user might change their mind regarding the destination, and\/or the travel date;<\/li>\n
  2. the user might want to check for weather information, that is not part of the book flight task, before confirming the booking;<\/li>\n
  3. the user might have a follow-up question regarding their booking;<\/li>\n
  4. the user may choose to cancel the task.<\/li>\n<\/ol>\n\r\n\t\t<\/div>\r\n\t<\/div>\r\n
    <\/div><\/div>\r\n\t
    \r\n\t\t
    \r\n\t\t\t

    Prerequisites<\/span><\/h2>\n

    In this how-to, we are using a Flight Details bot with the following dialog tasks<\/p>\n

      \n
    1. Book Flight<\/strong> dialog which\n
        \n
      1. prompts the user for source, destination, date of travel, and web check-in options;<\/li>\n
      2. display a booking confirmation message (for simplicity we have not added the service call to do the actual booking);<\/li>\n
      3. check if the user needs any further assistance;<\/li>\n
      4. end the conversation.<\/li>\n<\/ol>\n

        \"\"<\/a><\/li>\n

      5. Weather Report<\/strong> dialog which\n
          \n
        1. prompts the user for the location they want the weather report;<\/li>\n
        2. display the weather report message (for simplicity we have not added the service call to do the actual weather lookup);<\/li>\n<\/ol>\n

          \"\"<\/a><\/li>\n<\/ol>\n\r\n\t\t<\/div>\r\n\t<\/div>\r\n

          <\/div><\/div>\r\n\t
          \r\n\t\t
          \r\n\t\t\t

          Implementation<\/span><\/h2>\n

          Amend Entities<\/span><\/h3>\n

          Let us look at the case where the user might want to change the destination and\/or travel date.
          \nFollowing are the steps to achieve the same:<\/p>\n

          Step 1: Group the nodes for sub-intent scoping<\/strong>:<\/p>\n

          The first step would be to define the scope for the sub-intent which would trigger changes to the destination and travel date.<\/p>\n

            \n
          1. The user should be able to change the destination or the travel date any time during the conversation but before the actual booking, hence the scope would be entity nodes.
            \nUsing the mouse, select the entities forming a Group Node.<\/li>\n
          2. Name<\/strong> the Group, say Travel Details Group<\/em>
            \n            \"\"<\/a><\/li>\n<\/ol>\n\r\n\t\t<\/div>\r\n\t<\/div>\r\n\r\n\t
            \r\n\t\t
            \r\n\t\t\t

            Step 2a: Define sub-intents, train and set behavior properties for destination and travel date changes
            \n<\/strong><\/p>\n

            Next, we need to define the sub-intents, add training, and optionally set the conditions when the sub-intent should be identified, and the bot behavior in such a case.<\/p>\n

            Let us first consider the case of enabling changes to destination and travel date:<\/p>\n

              \n
            1. From the Entity Group window, click the Add Intent<\/strong> button\n
                \n
              1. Create Intent<\/strong> for allowing a change in travel date and destination\n