{"id":18055,"date":"2018-07-22T08:58:00","date_gmt":"2018-07-22T08:58:00","guid":{"rendered":"https:\/\/developer.kore.ai\/v9-2\/?post_type=docs&#038;p=14962"},"modified":"2021-08-14T08:55:30","modified_gmt":"2021-08-14T07:55:30","slug":"interruption-handling-context-switching-intents","status":"publish","type":"post","link":"https:\/\/developer.kore.ai\/v9-2\/docs\/bots\/bot-intelligence\/interruption-handling-context-switching-intents\/","title":{"rendered":"Dialog Management"},"content":{"rendered":"<section class=\"l-section wpb_row height_auto\"><div class=\"l-section-h i-cf\"><div class=\"g-cols vc_row type_default valign_top\"><div class=\"vc_col-sm-12 wpb_column vc_column_container\"><div class=\"vc_column-inner\"><div class=\"wpb_wrapper\">\r\n\t<div class=\"wpb_text_column \">\r\n\t\t<div class=\"wpb_wrapper\">\r\n\t\t\t<p>Human conversations are characterized by twists and turns, and no two directions are ever the same. Natural conversations often tend to go beyond linear intent resolution paths defined in the bots. Ideally, a user allows the bot to take a user intent to its logical conclusion before initiating another, but that is not always the case.<\/p>\n<p>Consider the following conversation for example:<\/p>\n<p><a ref=\"magnificPopup\" href=\"https:\/\/kore-wordpress.s3.us-east-2.amazonaws.com\/developer.kore.ai\/v9-2\/wp-content\/uploads\/sites\/26\/20210622060432\/intelligence_DM1.png\"><img loading=\"lazy\" decoding=\"async\" class=\"alignnone size-full wp-image-27860\" src=\"https:\/\/kore-wordpress.s3.us-east-2.amazonaws.com\/developer.kore.ai\/v9-2\/wp-content\/uploads\/sites\/26\/20210622060432\/intelligence_DM1.png\" alt=\"\" width=\"507\" height=\"503\" srcset=\"https:\/\/kore-wordpress.s3.us-east-2.amazonaws.com\/developer.kore.ai\/v9-2\/wp-content\/uploads\/sites\/26\/20210622060432\/intelligence_DM1.png 507w, https:\/\/kore-wordpress.s3.us-east-2.amazonaws.com\/developer.kore.ai\/v9-2\/wp-content\/uploads\/sites\/26\/20210622060432\/intelligence_DM1-150x150.png 150w, https:\/\/kore-wordpress.s3.us-east-2.amazonaws.com\/developer.kore.ai\/v9-2\/wp-content\/uploads\/sites\/26\/20210622060432\/intelligence_DM1-300x298.png 300w, https:\/\/kore-wordpress.s3.us-east-2.amazonaws.com\/developer.kore.ai\/v9-2\/wp-content\/uploads\/sites\/26\/20210622060432\/intelligence_DM1-100x100.png 100w\" sizes=\"auto, (max-width: 507px) 100vw, 507px\" \/><\/a><\/p>\n<p>It includes an entity value for the bot to proceed with the current intent, while also presenting a new user requirement or intent.<\/p>\n<p>Bots must account for this by allowing users to pause a task, start and complete another task, and seamlessly return to the original task without losing important contextual data and conversation continuity.<\/p>\n<p>Kore.ai provides you with granular control over hold and resume functionality at the bot, task, and node levels, and allows you to control context switching rules and behaviors. You can handle such interruptions in intent flows by providing a whole range of options to define the task-switching experience.<\/p>\n<p>The <b>Manage Interruptions <\/b>option can be set up at the bot, task, and node levels to ensure the configurations are layered to suit your various business requirements. You can also add conditional exceptions between tasks with the ability to pass contextual data between them.<\/p>\n<p>The following sections describe:<\/p>\n<ul>\n<li>The various Manage Interruption configurations,<\/li>\n<li>The hierarchy of the setups at bot, task, and node levels.<\/li>\n<\/ul>\n\r\n\t\t<\/div>\r\n\t<\/div>\r\n<div class=\"w-separator size_small with_line width_default thick_1 style_solid color_border align_center\"><div class=\"w-separator-h\"><\/div><\/div>\r\n\t<div class=\"wpb_text_column \">\r\n\t\t<div class=\"wpb_wrapper\">\r\n\t\t\t<h3><span class=\"ez-toc-section\" id=\"Manage_Interruptions\"><b>Manage Interruptions<\/b><\/span><\/h3>\n<p>The <b>Manage Interruptions<\/b> options allow you to select if and how a user can switch to another task and also the exit strategies. The configuration for Manage Interruptions is done either at the bot Level or at the task or dialog level. We will discuss the settings at the <em>Bot Level<\/em> in this section. These settings can be overridden at the task level as discussed in the <a href=\"#Interruptions_Hierarchy\">Interruptions Hierarchy section<\/a>.<\/p>\n<p>You can access the interruption settings from the <strong>Build &gt; Intelligence &gt; Manage Interruptions<\/strong> page.<br \/>\n<a ref=\"magnificPopup\" href=\"https:\/\/kore-wordpress.s3.us-east-2.amazonaws.com\/developer.kore.ai\/v9-2\/wp-content\/uploads\/sites\/26\/20210622060852\/intelligence_ManageInterruptions.png\"><img loading=\"lazy\" decoding=\"async\" class=\"alignnone size-full wp-image-27862\" src=\"https:\/\/kore-wordpress.s3.us-east-2.amazonaws.com\/developer.kore.ai\/v9-2\/wp-content\/uploads\/sites\/26\/20210622060852\/intelligence_ManageInterruptions.png\" alt=\"\" width=\"1366\" height=\"768\" srcset=\"https:\/\/kore-wordpress.s3.us-east-2.amazonaws.com\/developer.kore.ai\/v9-2\/wp-content\/uploads\/sites\/26\/20210622060852\/intelligence_ManageInterruptions.png 1366w, https:\/\/kore-wordpress.s3.us-east-2.amazonaws.com\/developer.kore.ai\/v9-2\/wp-content\/uploads\/sites\/26\/20210622060852\/intelligence_ManageInterruptions-300x169.png 300w, https:\/\/kore-wordpress.s3.us-east-2.amazonaws.com\/developer.kore.ai\/v9-2\/wp-content\/uploads\/sites\/26\/20210622060852\/intelligence_ManageInterruptions-1024x576.png 1024w\" sizes=\"auto, (max-width: 1366px) 100vw, 1366px\" \/><\/a><\/p>\n<p>The platform provides options for <i>Interruptions Behavior<\/i>\u00a0under the following three categories:<\/p>\n<ul>\n<li><b>Allow interruptions<\/b>: Provides options for you to choose for holding a task and options to resume it later.<\/li>\n<li><b>Do not allow interruptions<\/b>: Stops new tasks from interrupting the current task.<\/li>\n<li><strong>Allow the end user to select the behavior<\/strong>: Seeks end-user confirmation to switch to a new task and provides several resume options for you to pick from.<\/li>\n<\/ul>\n<p><strong>NOTE<\/strong>: When the user inputs after a session has ended, i.e. after at least 15 minutes of inactivity, and if the input is within the previous session context, it is treated as an interruption scenario. If instead, the user comes back with a new utterance, then the old context is discarded and a new conversation is started.<\/p>\n\r\n\t\t<\/div>\r\n\t<\/div>\r\n\r\n\t<div class=\"wpb_text_column \">\r\n\t\t<div class=\"wpb_wrapper\">\r\n\t\t\t<h4 id=\"allowHR\"><b>Allow Interruptions<\/b><\/h4>\n<p>Once you allow for task interruption, you need to specify the bot behavior in such scenarios as what should happen to the current task, where should the conversation go once the interruption task has been completed, etc.<\/p>\n<p>Following are the options under <b>Allow interruptions.<\/b><\/p>\n<table>\n<thead>\n<tr>\n<th>Option<\/th>\n<th>Description<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td><b>Hold the current task and resume back once the new task is completed<\/b><\/td>\n<td>This option lets the bot switch to a new intent as soon as it is detected irrespective of the current intent flow. When you select this option, the Resume Options section appears providing further choices to define how to resume the on-hold task once the new intent task is completed.\u00a0 Refer to the <a href=\"#resume\">Resume Options<\/a> section below for details.<\/td>\n<\/tr>\n<tr>\n<td><b>Discard the current task and switch to new<\/b><\/td>\n<td>When you select this option, the bot discards the current task and switches to a new task soon after it encounters another intent. The bot sends a message to notify the user before switching to the new task and the current task would be discarded. You can customize the message from the <strong>Manage Response <\/strong>setting.<\/td>\n<\/tr>\n<tr>\n<td><strong>Switch to a new task without any notification to the user and discard the current task<\/strong><\/td>\n<td>When you select this option, the bot discards the current task and switches to a new task soon after it encounters another intent. The bot does not notify the user about the switch and does not resume the current task later.<\/td>\n<\/tr>\n<tr>\n<td><b>Continue with the current task and add a new task to the follow-up task list<\/b><\/td>\n<td>When you select this option, the bot continues on the current task even if it encounters a new intent. It, however, adds the new intent to the Follow-up intents array.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n\r\n\t\t<\/div>\r\n\t<\/div>\r\n\r\n\t<div class=\"wpb_text_column \">\r\n\t\t<div class=\"wpb_wrapper\">\r\n\t\t\t<h4><b>Do not allow interruptions<\/b><\/h4>\n<p>When you select this option, the bot level <b>interruptions<\/b>\u00a0is turned off. However, you may override this behavior for selected tasks, linked dialogs (exceptions), or node levels. Refer to the <a href=\"#Interruptions_Hierarchy\">Interruptions Hierarchy <\/a>section below for more information.<\/p>\n\r\n\t\t<\/div>\r\n\t<\/div>\r\n\r\n\t<div class=\"wpb_text_column \">\r\n\t\t<div class=\"wpb_wrapper\">\r\n\t\t\t<h4><b>Allow the end user to select the behavior<\/b><\/h4>\n<p>When you select this option, the bot presents the end-user with a confirmation message asking if the user wants to switch to a new task. The bot switches to the new task only if the end-user chooses to do so. You can customize the confirmation message sent to the user by clicking the <b>Manage Response <\/b>link next to the option.<\/p>\n<p>You need to define a <em>Resume<\/em> option that the bot should take if the user decides to switch the task. Refer to the <a href=\"#resume\">Resume Options<\/a> section below for details.<\/p>\n\r\n\t\t<\/div>\r\n\t<\/div>\r\n\r\n\t<div class=\"wpb_text_column \">\r\n\t\t<div class=\"wpb_wrapper\">\r\n\t\t\t<h4 id=\"resume\"><b>Resume Options<\/b><\/h4>\n<p>Once you allow the task to be put on hold and proceed with the interruption task, you must configure the <em>Resume<\/em> option i.e. how the on-hold task should be handled once the interrupting task is completed.<\/p>\n<p>&nbsp;<\/p>\n<table>\n<thead>\n<tr>\n<th>Option<\/th>\n<th>Description<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td><strong>Get confirmation with the user before resuming an on-hold task<\/strong><\/td>\n<td>After executing the new task,\u00a0the bot gives Yes or No options to the user to return to the last on-hold task. You can write a custom message for the user by clicking the <b>Manage Response<\/b> link next to the option.<br \/>\n<b>Example:<\/b><\/p>\n<pre>User: Hi\r\nBot: Hello!\r\nUser: Can you book me a flight for tomorrow?\r\nBot: From which city are you flying?\r\nUser: Los Angeles\r\nBot: Where to?\r\nUser: By the way, what\u2019s the weather forecast for tomorrow?\r\nBot: Please enter the name of the city for the forecast.\r\nUser: Los Angeles\r\nBot: Weather Forecast for Los Angeles\r\nDate: March 15\r\nTemperature: 25 C\r\nCondition: Mostly Sunny\r\nBot: Should I continue with the task 'Book Flight'?\r\nUser: Yes\r\nBot: Enter the name of the destination airport<\/pre>\n<\/td>\n<\/tr>\n<tr>\n<td><strong>Notify the user with a message that the on-hold task is being resumed<\/strong><\/td>\n<td>Notifies the user with a message and resumes the last task that\u2019s kept on hold without user confirmation.<br \/>\nYou can customize the notification message by clicking the <b>Manage Response<\/b> link next to the option.<br \/>\n<b>Example:<\/b><\/p>\n<pre>User: Hi\r\nBot: Hello!\r\nUser: Can you book me a flight for tomorrow?\r\nBot: From which city are you flying?\r\nUser: Los Angeles\r\nBot: Where to?\r\nUser: By the way, what\u2019s the weather forecast for tomorrow?\r\nBot: Please enter the name of the city for the forecast.\r\nUser: Los Angeles\r\nBot: Weather Forecast for Los Angeles\r\nDate: March 15\r\nTemperature: 25 C\r\nCondition: Mostly Sunny\r\nBot: Resuming interrupted task Book Flight\r\nBot: Enter the name the of the destination airport<\/pre>\n<\/td>\n<\/tr>\n<tr>\n<td><strong>Resume the on hold task without any specific message to the user<\/strong><\/td>\n<td>Directly resumes the last task that\u2019s kept on hold soon after the current task is executed.<br \/>\n<b>Example:<\/b><\/p>\n<pre>User: Hi\r\nBot: Hello!\r\nUser: Can you book me a flight for tomorrow?\r\nBot: From which city are you flying?\r\nUser: Los Angeles\r\nBot: Where to?\r\nUser: By the way, what\u2019s the weather forecast for tomorrow?\r\nBot: Please enter the name of the city for the forecast.\r\nUser: Los Angeles\r\nBot: Weather Forecast for Los Angeles\r\nDate: March 15\r\nTemperature: 25 C\r\nCondition: Mostly Sunny\r\nBot: Enter the name of the destination airport<\/pre>\n<\/td>\n<\/tr>\n<tr>\n<td><strong>Always resume the on hold task without any specific message to the user if the task is ended in a single response<\/strong><\/td>\n<td>Sometimes, the switched-over tasks end with a single bot response. For example, in the weather forecast example above, if the user had directly entered <em>By the way, what\u2019s the weather forecast for LA tomorrow?<\/em>\u00a0the bot would have merely responded with the forecast, with no further steps.<br \/>\nIn such cases, if you select this option, the bot switches back to the task on hold without any confirmation or notification, regardless of the option you\u2019ve chosen.<\/p>\n<div class=\"alert alert-info\"><b>Note<\/b>: The switching happens directly, without any notification to the end-user.<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p><b>On Hold Quantity <\/b><br \/>\nYou can select the number of tasks that you want to keep on hold from the <b>On Hold Quantity <\/b>field. The bot keeps a maximum of this number of tasks on hold and ignores the tasks once this value is reached.<\/p>\n<p>For example, if you specify the On Hold Quantity as 1 and if a third intent comes into play, the bot will not allow the new task to be initiated regardless of interruptions options.<\/p>\n<div class=\"alert alert-info\"><b>Note<\/b>: Tasks always resume in reverse chronological order. So, if you kept task 2 on hold after task 1, task 2 resumes before task 1.<\/div>\n\r\n\t\t<\/div>\r\n\t<\/div>\r\n\r\n\t<div class=\"wpb_text_column \">\r\n\t\t<div class=\"wpb_wrapper\">\r\n\t\t\t<h3><span class=\"ez-toc-section\" id=\"Interruptions_Hierarchy\"><b>Interruptions Hierarchy<\/b><\/span><\/h3>\n<p>Apart from defining the generic interruptions options at the bot level, you can customize these options at the dialog task or dialog node level. When you set up the Hold and Resume options in more than one levels, the order of precedence of the settings works as follows:<br \/>\n<a ref=\"magnificPopup\" href=\"\/wp-content\/uploads\/sites\/26\/hierarchy.png\"><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter wp-image-14976\" src=\"\/wp-content\/uploads\/sites\/26\/hierarchy.png\" alt=\"\" width=\"494\" height=\"370\" \/><\/a><\/p>\n<h4><b>Node Level Settings<\/b><\/h4>\n<p>You can customize the interruptions settings at the node level. If you customize the settings for a node, this configuration takes the highest precedence.<\/p>\n<p>To customize the interruptions settings for a node:<\/p>\n<ol>\n<li>Open the dialog task and then the node to change settings.<\/li>\n<li>Click the <strong>instance tab<\/strong> and select <b>Advanced Controls<\/b>.<\/li>\n<li>Under the <b>Interruptions<\/b>\u00a0section, select<strong> Customize for this node<\/strong> and make the necessary configurations. These configurations are the same as discussed above for the bot-level <a href=\"#Manage_Interruptions\">Interruptions Settings<\/a>.<br \/>\n<a ref=\"magnificPopup\" href=\"https:\/\/kore-wordpress.s3.us-east-2.amazonaws.com\/developer.kore.ai\/v9-2\/wp-content\/uploads\/sites\/26\/20210622074445\/intelligence_ManageInterruptions_entity.png\"><img loading=\"lazy\" decoding=\"async\" class=\"alignnone size-full wp-image-27868\" src=\"https:\/\/kore-wordpress.s3.us-east-2.amazonaws.com\/developer.kore.ai\/v9-2\/wp-content\/uploads\/sites\/26\/20210622074445\/intelligence_ManageInterruptions_entity.png\" alt=\"\" width=\"461\" height=\"387\" srcset=\"https:\/\/kore-wordpress.s3.us-east-2.amazonaws.com\/developer.kore.ai\/v9-2\/wp-content\/uploads\/sites\/26\/20210622074445\/intelligence_ManageInterruptions_entity.png 461w, https:\/\/kore-wordpress.s3.us-east-2.amazonaws.com\/developer.kore.ai\/v9-2\/wp-content\/uploads\/sites\/26\/20210622074445\/intelligence_ManageInterruptions_entity-300x252.png 300w\" sizes=\"auto, (max-width: 461px) 100vw, 461px\" \/><\/a><\/li>\n<\/ol>\n<h4><b>Dialog Level Settings<\/b><\/h4>\n<p>The dialog level Interruptions customizations have higher priority over bot level settings but rank lower than the node level customizations or any exceptions.<\/p>\n<p>To customize the Interruptions settings for a dialog:<\/p>\n<ol>\n<li><strong>Open the Dialog task<\/strong>\u00a0you want to customize.<\/li>\n<li>On the top-right of the dialog builder, click the <strong>more options icon<\/strong> and then click <b>Manage Interruptions<\/b>.<\/li>\n<li>Under the Interruptions Behavior section, select <b>Customize for this task<\/b> and make the necessary configurations. These settings are the same as discussed above for the bot Level <a href=\"#Manage_Interruptions\">Interruptions<\/a>.<br \/>\n<a ref=\"magnificPopup\" href=\"https:\/\/kore-wordpress.s3.us-east-2.amazonaws.com\/developer.kore.ai\/v9-2\/wp-content\/uploads\/sites\/26\/20210622074742\/intelligence_ManageInterruptions_dialog.png\"><img loading=\"lazy\" decoding=\"async\" class=\"alignnone size-full wp-image-27870\" src=\"https:\/\/kore-wordpress.s3.us-east-2.amazonaws.com\/developer.kore.ai\/v9-2\/wp-content\/uploads\/sites\/26\/20210622074742\/intelligence_ManageInterruptions_dialog.png\" alt=\"\" width=\"697\" height=\"637\" srcset=\"https:\/\/kore-wordpress.s3.us-east-2.amazonaws.com\/developer.kore.ai\/v9-2\/wp-content\/uploads\/sites\/26\/20210622074742\/intelligence_ManageInterruptions_dialog.png 697w, https:\/\/kore-wordpress.s3.us-east-2.amazonaws.com\/developer.kore.ai\/v9-2\/wp-content\/uploads\/sites\/26\/20210622074742\/intelligence_ManageInterruptions_dialog-300x274.png 300w\" sizes=\"auto, (max-width: 697px) 100vw, 697px\" \/><\/a><\/li>\n<\/ol>\n<div class=\"alert alert-info\"><b>Note<\/b>: If you do not customize Interruptions settings at the node or task level, the bot level settings come into play.<\/div>\n\r\n\t\t<\/div>\r\n\t<\/div>\r\n<div class=\"w-separator size_small with_line width_default thick_1 style_solid color_border align_center\"><div class=\"w-separator-h\"><\/div><\/div>\r\n\t<div class=\"wpb_text_column \">\r\n\t\t<div class=\"wpb_wrapper\">\r\n\t\t\t<h3><span class=\"ez-toc-section\" id=\"Manage_Behavior_for_FAQs\">Manage Behavior for FAQs<\/span><\/h3>\n<p>You can choose whether FAQs should honor the interruptions settings or if FAQs should be always responded to.<\/p>\n<p><a ref=\"magnificPopup\" href=\"https:\/\/kore-wordpress.s3.us-east-2.amazonaws.com\/developer.kore.ai\/v9-2\/wp-content\/uploads\/sites\/26\/20210622070203\/intelligence_ManageInterruptions_FAQ.png\"><img loading=\"lazy\" decoding=\"async\" class=\"alignnone size-full wp-image-27864\" src=\"https:\/\/kore-wordpress.s3.us-east-2.amazonaws.com\/developer.kore.ai\/v9-2\/wp-content\/uploads\/sites\/26\/20210622070203\/intelligence_ManageInterruptions_FAQ.png\" alt=\"\" width=\"1363\" height=\"635\" srcset=\"https:\/\/kore-wordpress.s3.us-east-2.amazonaws.com\/developer.kore.ai\/v9-2\/wp-content\/uploads\/sites\/26\/20210622070203\/intelligence_ManageInterruptions_FAQ.png 1363w, https:\/\/kore-wordpress.s3.us-east-2.amazonaws.com\/developer.kore.ai\/v9-2\/wp-content\/uploads\/sites\/26\/20210622070203\/intelligence_ManageInterruptions_FAQ-300x140.png 300w, https:\/\/kore-wordpress.s3.us-east-2.amazonaws.com\/developer.kore.ai\/v9-2\/wp-content\/uploads\/sites\/26\/20210622070203\/intelligence_ManageInterruptions_FAQ-1024x477.png 1024w\" sizes=\"auto, (max-width: 1363px) 100vw, 1363px\" \/><\/a><\/p>\n<p>The flag <strong>Interruption Behavior for FAQs<\/strong> will allow you to:<\/p>\n<ul>\n<li>Always identify and respond to FAQs when interruptions are enabled. This is the default setting.<\/li>\n<li>Always identify FAQs when interruptions are enabled and proceed as per the Hold and Resume settings.<\/li>\n<\/ul>\n\r\n\t\t<\/div>\r\n\t<\/div>\r\n<div class=\"w-separator size_small with_line width_default thick_1 style_solid color_border align_center\"><div class=\"w-separator-h\"><\/div><\/div>\r\n\t<div class=\"wpb_text_column \">\r\n\t\t<div class=\"wpb_wrapper\">\r\n\t\t\t<h3><span class=\"ez-toc-section\" id=\"Manage_Behavior_for_Ambiguous_Intents\">Manage Behavior for Ambiguous Intents<\/span><\/h3>\n<p>You can handle ambiguous intents during a conversation flow by setting the flag <strong>Behavior for Ambiguous Interruptions<\/strong>. It allows you to:<\/p>\n<p><a ref=\"magnificPopup\" href=\"https:\/\/kore-wordpress.s3.us-east-2.amazonaws.com\/developer.kore.ai\/v9-2\/wp-content\/uploads\/sites\/26\/20210622070657\/intelligence_ManageInterruptions_Ambig.png\"><img loading=\"lazy\" decoding=\"async\" class=\"alignnone size-full wp-image-27866\" src=\"https:\/\/kore-wordpress.s3.us-east-2.amazonaws.com\/developer.kore.ai\/v9-2\/wp-content\/uploads\/sites\/26\/20210622070657\/intelligence_ManageInterruptions_Ambig.png\" alt=\"\" width=\"1365\" height=\"627\" srcset=\"https:\/\/kore-wordpress.s3.us-east-2.amazonaws.com\/developer.kore.ai\/v9-2\/wp-content\/uploads\/sites\/26\/20210622070657\/intelligence_ManageInterruptions_Ambig.png 1365w, https:\/\/kore-wordpress.s3.us-east-2.amazonaws.com\/developer.kore.ai\/v9-2\/wp-content\/uploads\/sites\/26\/20210622070657\/intelligence_ManageInterruptions_Ambig-300x138.png 300w, https:\/\/kore-wordpress.s3.us-east-2.amazonaws.com\/developer.kore.ai\/v9-2\/wp-content\/uploads\/sites\/26\/20210622070657\/intelligence_ManageInterruptions_Ambig-1024x470.png 1024w\" sizes=\"auto, (max-width: 1365px) 100vw, 1365px\" \/><\/a><\/p>\n<ul>\n<li>Present the ambiguous intents to the end-user and proceed as per the Hold and Resume Settings. In case the user selects a task and the interruptions setting is:\n<ul>\n<li><em>Continue the current task and add a new task to the follow-up task list<\/em>, then the current task will be kept on hold and the new task will be initiated.<\/li>\n<li><em>Allow the end-user to select the behavior<\/em>, then the new task will be initiated without asking the user since the selection has been already made.<\/li>\n<li>All other <em>hold<\/em> options will be applied as usual.<\/li>\n<\/ul>\n<\/li>\n<li>Do not present ambiguous intents to the end-users and continue on the current task. This is the default setting.<\/li>\n<\/ul>\n\r\n\t\t<\/div>\r\n\t<\/div>\r\n<div class=\"w-separator size_small with_line width_default thick_1 style_solid color_border align_center\"><div class=\"w-separator-h\"><\/div><\/div>\r\n\t<div class=\"wpb_text_column \">\r\n\t\t<div class=\"wpb_wrapper\">\r\n\t\t\t<h3><span class=\"ez-toc-section\" id=\"Manage_Behavior_for_Small_Talk\">Manage Behavior for Small Talk<\/span><\/h3>\n<p>You can handle small talk during a conversation flow by setting the flag <strong>Interruption Behavior for Small Talk<\/strong>. It allows you to:<\/p>\n<p><a ref=\"magnificPopup\" href=\"https:\/\/kore-wordpress.s3.us-east-2.amazonaws.com\/developer.kore.ai\/v9-2\/wp-content\/uploads\/sites\/26\/20210617051752\/SmallTalk_interruptions-1.png\"><img loading=\"lazy\" decoding=\"async\" class=\"alignnone size-full wp-image-27737\" src=\"https:\/\/kore-wordpress.s3.us-east-2.amazonaws.com\/developer.kore.ai\/v9-2\/wp-content\/uploads\/sites\/26\/20210617051752\/SmallTalk_interruptions-1.png\" alt=\"\" width=\"1366\" height=\"768\" srcset=\"https:\/\/kore-wordpress.s3.us-east-2.amazonaws.com\/developer.kore.ai\/v9-2\/wp-content\/uploads\/sites\/26\/20210617051752\/SmallTalk_interruptions-1.png 1366w, https:\/\/kore-wordpress.s3.us-east-2.amazonaws.com\/developer.kore.ai\/v9-2\/wp-content\/uploads\/sites\/26\/20210617051752\/SmallTalk_interruptions-1-300x169.png 300w, https:\/\/kore-wordpress.s3.us-east-2.amazonaws.com\/developer.kore.ai\/v9-2\/wp-content\/uploads\/sites\/26\/20210617051752\/SmallTalk_interruptions-1-1024x576.png 1024w\" sizes=\"auto, (max-width: 1366px) 100vw, 1366px\" \/><\/a><\/p>\n<ul>\n<li><em>Respond to Small Talk and resume the on-hold task<\/em>\u00a0\u2013 this is the default setting.<\/li>\n<li><em>Execute the Small Talk using Hold &amp; Resume settings<\/em>.<\/li>\n<\/ul>\n\r\n\t\t<\/div>\r\n\t<\/div>\r\n<div class=\"w-separator size_small with_line width_default thick_1 style_solid color_border align_center\"><div class=\"w-separator-h\"><\/div><\/div>\r\n\t<div class=\"wpb_text_column \">\r\n\t\t<div class=\"wpb_wrapper\">\r\n\t\t\t<h3><span class=\"ez-toc-section\" id=\"Manage_Behavior_for_User_Authorization\">Manage Behavior for User Authorization<\/span><\/h3>\n<p>When a user gives any input at a prompt message for authorization that is not relevant, the following flow is followed:<\/p>\n<ul>\n<li>If Small Talk intent is identified, then the Small Talk\u2019s response is displayed, and the authorization is re-prompted.<\/li>\n<li>The platform checks for the presence of any intents (tasks or FAQs) in the user utterance, irrespective of the configurations set for Manage Interruptions:\n<ul>\n<li>If the intent is identified, confirmation to discard the current task and trigger the new task is sought.<\/li>\n<li>If multiple intents are identified, an ambiguity dialog along with the option to ignore the utterance and continue with the current task is presented.<\/li>\n<\/ul>\n<\/li>\n<li>If no intent is identified, then the user is re-prompted with the authorization link.<\/li>\n<\/ul>\n\r\n\t\t<\/div>\r\n\t<\/div>\r\n<div class=\"w-separator size_small with_line width_default thick_1 style_solid color_border align_center\"><div class=\"w-separator-h\"><\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/section>\n","protected":false},"excerpt":{"rendered":"Human conversations are characterized by twists and turns, and no two directions are ever the same. Natural conversations often tend to go beyond linear intent resolution paths defined in the bots. Ideally, a user allows the bot to take a user intent to its logical conclusion before initiating another, but that is not always the...","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[47],"tags":[],"class_list":["post-18055","post","type-post","status-publish","format-standard","hentry","category-bot-intelligence"],"_links":{"self":[{"href":"https:\/\/developer.kore.ai\/v9-2\/wp-json\/wp\/v2\/posts\/18055","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/developer.kore.ai\/v9-2\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/developer.kore.ai\/v9-2\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/developer.kore.ai\/v9-2\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/developer.kore.ai\/v9-2\/wp-json\/wp\/v2\/comments?post=18055"}],"version-history":[{"count":31,"href":"https:\/\/developer.kore.ai\/v9-2\/wp-json\/wp\/v2\/posts\/18055\/revisions"}],"predecessor-version":[{"id":30933,"href":"https:\/\/developer.kore.ai\/v9-2\/wp-json\/wp\/v2\/posts\/18055\/revisions\/30933"}],"wp:attachment":[{"href":"https:\/\/developer.kore.ai\/v9-2\/wp-json\/wp\/v2\/media?parent=18055"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/developer.kore.ai\/v9-2\/wp-json\/wp\/v2\/categories?post=18055"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/developer.kore.ai\/v9-2\/wp-json\/wp\/v2\/tags?post=18055"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}