Subtasks Overview

This video takes you inside the customer portal to show what the subtask experience looks and feels like for your customers — and then flips to the back-end task builder so you can see how it's all constructed in OnRamp.

What You'll Learn

This video walks through a real task in the customer portal — showing how subtasks appear, how customers move through them step by step, and how branching logic works to show different paths based on customer responses. It then shows the same task inside OnRamp's task builder so you can see how it was built.

Chapter Breakdown

🗂 Task Structure in the Portal

At the top of each task in the customer portal, customers see the task name, who it's assigned to, and its due date. Below that, the subtasks appear as collapsible steps. Customers expand each subtask, complete the required action, and click Save and Continue to progress. After each save, they're dropped directly into the next subtask — keeping the experience linear and guided.

🔀 Branching — Different Answers Lead to Different Paths

Subtask responses can control what appears next. In the video example, selecting an answer (like "Yes, I need admin training") triggers a new subtask to appear — asking a follow-up question like how many team members need that training. This branching behavior means customers only see the subtasks that are relevant to their specific situation, rather than a one-size-fits-all list.

📋 Multi-Action Subtasks (Form-Style)

Not all subtasks are single-action steps. Some subtasks contain multiple inputs grouped together — for example, a file download, a yes/no question, and a table where the customer can add team members row by row. The table step is one example of this: it lets customers add multiple entries (like team members) within a single subtask, without needing to click Save and Continue after each one. The customer completes all inputs inside that subtask before moving on.

🏗 Inside the Task Builder (Back End)

The second half of the video flips to the internal OnRamp task builder to show the same task from the admin's perspective. You can see how each subtask maps to what the customer experienced — including the Dynamics selection step, the file download, the yes/no question, and the table item. Understanding this connection between the customer view and the builder view makes it much easier to design tasks that feel intuitive on the customer side.

In the next video, we'll go deeper into the specific subtask types you can create in the task builder.

📺 Continue learning: Visit the OnRamp Tutorials YouTube Playlist for the full collection of video walkthroughs.