Default Tasks

In most cases, you use conversation triggers or routing to direct users to particular conversation tasks. However, you must also configure an initial task and a fallback task.

Initial Task

The initial task runs when the conversation session starts. It activates when you start a conversation by sending the Converse action without the Text parameter (see Start and Continue a Conversation).

The main use of the initial task is to greet your users when they join a conversation session.

To define the initial task, you set the initial_task property in your task configuration JSON to the ID of the task that you want to use. This property is required, and the associated task must exist somewhere in your task configuration file.

For example:

{
   "initial_task" : "GREET",
   "tasks" : [
      {
         "id" : "GREET",
         "pre" : {
            "response" : "Hello and Welcome to the Virtual Assistant. How can I help you?"
         }
      }
   ]
}

Fallback Task

The fallback task runs when there are no existing tasks in the session, for example because all previous tasks are complete.

To define the fallback task, you set the fallback_task property in your task configuration JSON to the ID of the task that you want to use. This property is required, and the associated task must exist somewhere in your task configuration file, even if you have explicit routing such that it is never used.

{
   "fallback_task" : "HELP",
   "tasks" : [
      {
         "id" : "HELP",
         "pre" : {
            "response" : "Is there anything else I can help you with today?"
         }
      }
   ]
}

_HP_HTML5_bannerTitle.htm