# Virtual Assistant task steps and branches

Guide a visitor through ordered questions and actions, choosing the next step from their answer.

*Release 3.3 · developer, operator, visitor*

**Settings › Bots › Virtual Assistant › Tasks**

## What it is

A task guides a visitor through a sequence of questions, messages and actions. Each answer can lead to a different step. A task can also call another task and continue according to that task's result.

## Who uses it and why

- Operators send an available task to collect information or guide a visitor through a process.
- Visitors answer questions and use the choices offered by the task.
- Developers work with a **Bot Trainer** to connect integration results to the appropriate task branches.

## Where to find it

With the **Bot Trainer** role, configure tasks in **Settings › Bots › Virtual Assistant › Tasks**. Open a task version and review **Task Steps** and each **Step Action**. Operators use task controls in the conversation pane; visitors interact in the chat pane or supported messaging channel.

## How it works

1. INSIDE starts an enabled task and selects its first enabled step in the configured order, unless the start specifies another step.
2. The visitor sees the question and its input controls. Message or action steps can continue without an answer.
3. INSIDE checks a submitted answer and chooses its configured completion branch. Picklist and Boolean answers can have different branches for different choices.
4. A permitted skip follows the skip branch. Without a specific skip action, the task moves to the next step.
5. The selected action continues the sequence or ends it with a result.

**Step Action** includes **Move To Next Step**, **Move To Previous Step**, **Replay Current Step**, **Jump to Another Step**, **Jump to Another Task** and **End Task**. Integration and scheduling actions provide additional routes.

When a task calls another task, its return actions decide what happens after success, failure or an unavailable result. Ending a task does not necessarily end the conversation. The end action controls whether to close it, transfer it or continue with another task.

## Configure it

A **Bot Trainer** adds and orders steps, then sets the completion and skip actions for each one. Set a branch for every visitor choice and a suitable return action for tasks or integrations that can fail. Preview the paths, publish the intended version and check that the task is enabled.

For manual use, enable **Operator can Send Task** and review its team and channel restrictions. Automated starts come from the relevant event, pre-chat or channel configuration.

### Fields

| Field | Where | Required | What it is for |
|---|---|---|---|
| Step Action | Settings › Bots › Virtual Assistant › Tasks | Yes | Chooses whether an answer advances, repeats, jumps to another step or task, runs an integration or ends the task. |

### Permissions

| Permission | Lets you |
|---|---|
| Bot Trainer | Configure task steps and their answer branches. |

## Limits and good to know

- A visitor normally has one active task at a time. A paused task still counts as active and can prevent another task starting.
- Disabled steps do not take part in the normal ordered sequence.
- Completing a step with an existing answer follows a separate path that does not repeat ordinary answer side effects.
- A successful task result describes the task's outcome. It does not confirm delivery of an email, SMS or other external action.
- Channel support affects how questions and controls appear. Check the journey on each channel you use.

## Depends on and works with

### This feature uses

- **Requires** [Virtual Assistant task setup](ENG-009.md): Execution needs an authored task with enabled steps and configured branches.
- **Requires** [Virtual Assistant task drafts and publishing](ENG-010.md): A task must have a published, enabled version before it can run.
- **Configured in** [Virtual Assistant task data fields](ENG-012.md): Field definitions determine how submitted answers are validated and stored.
- **Configured in** [Existing answers in Virtual Assistant tasks](ENG-013.md): Existing-answer choices can advance a step without asking again.
- **Configured in** [Virtual Assistant task messages and identity](ENG-014.md): Task and step content defines the questions and messages sent during execution.
- **Configured in** [Virtual Assistant task pauses and handover](ENG-015.md): Task-control and handover actions determine when execution pauses, resumes, cancels or transfers.
- **Configured in** [Virtual Assistant task actions](ENG-016.md): Configured answer actions determine the business updates and outbound messages performed.
- **Configured in** [Task integrations, appointments and embedded pages](ENG-017.md): Integration actions and their return branches determine how external results continue the task.
- **Configured in** [Virtual Assistant task validation and retries](ENG-028.md): Configured help and failure routes determine how execution recovers from invalid input.
- **Configured in** [Visitor event updates to customer context](ENG-007.md): Visitor-event actions select tasks for automatic starts and can request a forced restart.
- **Configured in** [Virtual Assistant tasks started by Autopilot](ENG-027.md): AI task functions select the task and stored prerequisites used for an AI handoff.
- **Works better with** [Pre-chat survey for visitors](VX-008.md): Pre-chat intake can use a task before a conversation begins.
- **Works better with** [Chat tasks and topics for visitors](VX-017.md): The visitor chat pane displays task questions and controls.
- **Works better with** [Virtual Assistant tasks in messaging channels](CHN-004.md): Messaging channels present supported task questions in channel-specific formats.
- **Related** [Starting, ending and expiring chats](CHAT-001.md): Ending a task and closing its conversation have separate outcomes.

### Used by

- **Required by** [Chat tasks and topics for visitors](VX-017.md): Workflow execution determines the current step and next action.
- **Required by** [Existing answers in Virtual Assistant tasks](ENG-013.md): Existing answers are reused when a running task evaluates its current step.
- **Required by** [Virtual Assistant task pauses and handover](ENG-015.md): Pause, resume and cancellation act on an active task.
- **Required by** [Virtual Assistant task actions](ENG-016.md): Actions run as part of task execution.
- **Required by** [Task integrations, appointments and embedded pages](ENG-017.md): Integration actions run within the task sequence.
- **Required by** [Task notes and operator reminders](ENG-024.md): The task must reach and execute the configured action.
- **Required by** [Virtual Assistant usage](ENG-025.md): Running tasks create and update task and step activity.
- **Required by** [Virtual Assistant tasks started by Autopilot](ENG-027.md): Normal task execution runs the selected steps and actions after handoff.
- **Required by** [Virtual Assistant task validation and retries](ENG-028.md): Recovery applies to the visitor's currently running task and step.
- **Required by** [Virtual Assistant tasks in messaging channels](CHN-004.md): Task execution collects replies and advances through steps.
- **Configures** [Live show RSVP, reminders and follow-up](RTC-026.md): The selected callback task steps determine its follow-up questions and actions.
- **Configures** [Event, link and Virtual Assistant reports](REP-013.md): Task branches and end statuses define the journeys and outcomes shown in task and intent reports.
- **Enhances** [Visitor activity and availability](VIS-011.md): A running workflow can keep a conversation available when the visitor goes away.
- **Enhances** [Visitor popups and embedded content](VX-016.md): A popup click can trigger a configured task.
- **Enhances** [Appointment booking for visitors](VX-023.md): A task can open booking and continue according to completion or cancellation.
- **Enhances** [Video Feed for visitors](VX-025.md): A configured offline video action can run a task.
- **Enhances** [Custom bots and FAQ bots](ENG-020.md): An active task affects bot expiry and tasks can invoke bot intent responses.
- **Enhances** [FAQ bot training and automatic replies](ENG-021.md): Tasks can request eligible automatically approved intent responses.
- **Enhances** [Broadcast acceptance and queue action reports](REP-007.md): Queue actions can start Virtual Assistant tasks whose use and success are reported.
- **Enhances** [Media callbacks and embedded form results](EXT-021.md): An active task step can continue from an accepted embedded-form result.
- **Related** [Virtual Assistant task setup](ENG-009.md): Published task definitions supply the ordered steps and branches used during execution.
- **Related** [Virtual Assistant task data fields](ENG-012.md): Execution validates submitted field answers before continuing to the next task branch.
- **Related** [Virtual Assistant task preview](ENG-018.md): Preview simulates task paths without establishing their live execution or external results.

## FAQ and troubleshooting

**Why will a second task not start?**

Check whether this visitor already has a running or paused task. Resume, complete or cancel that task as appropriate before starting another.

**Why did the visitor miss a step?**

Check that the step is enabled, the previous branch points to it and the existing-answer rule does not skip it automatically.

**Why did the task return to an earlier question?**

Review **Replay Current Step**, **Move To Previous Step** and jump actions on the selected answer or return branch.

**Why is the conversation still open after the task finishes?**

Task completion and conversation closure are separate. Review the configured **End Task** action.