Skip to main content

Creating Multi-step tasks

This helps you capture detailed information, create checklists, or walk users through structured workflows without creating separate tasks

Dylan Main avatar
Written by Dylan Main
Updated over a month ago

Introduction

Multi-step tasks (also called subtasks) let you break down a complex task into smaller, guided steps. Each step can include instructions, questions, or inputs that need to be completed before the parent task is marked complete.

This helps you capture detailed information, create checklists, or walk users through structured workflows without creating a separate task for each piece.


When to Use SubTasks

  • For customer handoffs or onboarding steps with multiple questions

  • For customer-facing forms like user acceptance testing (UAT)

  • For internal checklists that require multiple confirmations before completion


Steps to Follow

1. Open Task Builder

  1. Navigate to your Project or Playbook.

  2. Select a task, then choose Edit to open the Task Builder.


2. Add Subtasks

  1. From the left-hand panel, drag components into the center Preview area.

  2. Choose from options like:

    • Multiple choice (single or multi-select)

    • Yes/No questions

    • Text inputs

    • Videos or instructions (informational only)

    • Adobe eSign requests

  3. Give each step a name, add a description (optional), and configure answer options.


3. Use Branching Logic (Optional)

  • For Yes/No or choice-based questions, you can define branching logic.

  • Example:

    • If answer = Yes, direct the user to “Assign a Champion” step.

    • If answer = No, skip ahead to a different subtask.

  • This helps skip unnecessary steps and keep tasks relevant.


4. Preview the Multi-Step Task

  • Use the Preview pane to see all subtasks in sequence.

  • Confirm branching logic works as expected.


5. Complete from the Portal View

  • When assigned, users see each subtask listed by step name with instructions or questions.

  • They can save progress as they move through the steps.

  • Once all subtasks are completed, the parent task is marked complete automatically.


Tips & Troubleshooting

  • Internal vs. Customer-Facing: Mark tasks as internal if only your team needs to respond.

  • Use automation: Answers collected in subtasks can be used in automation to update records or trigger actions in external systems.

  • Keep steps focused: Each subtask should ask one clear question or action to avoid confusion.


Did this answer your question?