Who this is for: Recruiters building sequences who want to include manual actions — calls, research, follow-ups — as part of a structured outreach flow.
What a Task step is
A Task step is a manual to-do item that gets created for the sender when a recipient reaches that point in the sequence. Unlike email or LinkedIn steps that execute automatically, a Task step pauses the sequence for that recipient and waits for the assigned recruiter to complete the task before the next step fires.
Tasks are how you build human touchpoints — calls, LinkedIn profile reviews, personalised research — into an otherwise automated sequence without losing the structure and tracking that makes sequences useful.
Configuring a Task step
Click the Task step card to open the configuration panel. The available fields are:
Field | Details |
Task Title | Required. The name that appears in the recruiter's task list. Be specific — "Call [First Name] to discuss role fit" is more actionable than "Follow up". |
Task Type | The category of action — e.g., Call, Email, LinkedIn, Research, Custom. Affects how the task is grouped and filtered in the Tasks page. |
Notes | Optional. Internal notes or instructions for the recruiter completing the task. Not visible to the recipient. |
Priority | Low, Medium, or High. Controls sort order on the Tasks page and can be used to filter urgent tasks. |
Reminder | Optional in-app or email reminder. Follows the same rules as the Tasks module. Custom date selection is not available — only preset options. If the delay is set to 0 (Due Immediately), reminder options are limited to No Reminder and At Task Due Time. |
Skip if not completed by due date | Toggle. When on, the task is automatically skipped if the sender hasn't completed it by the due date — advancing the recipient to the next step without manual intervention. When the delay is 0, this toggle is disabled. |
Delay | Sets the task's due date — the number of days after the previous step completes before this task is due. Range: 0 (Due Immediately) to 365 days. |
Skip weekends while counting | Toggle. When on, Saturday and Sunday are excluded from the delay count. |
Who the task is assigned to
Tasks are always assigned to the sender of the recipient — whoever is assigned to send outreach to that person in this sequence. This is set at the sequence level via the Sender Priority configuration and does not change per step.
An info icon in the configuration panel confirms this: "Task will be assigned to the allocated sender of the recipient."
By default, tasks are created as assigned by Recruiterflow Sequences (not by the user who built the sequence). The assigned sender sees the task in the Tasks tab under the sequence as seen in the image.
When the task is created and how it advances the sequence
Tasks in sequences follow a specific timing model — different from automated steps:
The task is created when the previous step completes — not when the sequence is launched, and not when the step is configured. If the previous step is an email with a 3-day delay, the task appears in the sender's task list 3 days after the email sends.
Completing the task starts the delay clock for the next step. The next step's delay doesn't start counting from when the task was created — it starts from when the task is marked complete. So a 2-day delay after a task means 2 days after the task is done, not 2 days after it was due.
Skipping the task also advances the sequence — whether manually skipped by the recruiter or auto-skipped via the skip-on-overdue toggle.
The skip-on-overdue toggle — when to use it
The Skip if not completed by due date toggle is the mechanism for keeping a sequence moving even when a recruiter doesn't get to the task in time.
Toggle ON: If the task isn't completed by its due date, Recruiterflow automatically skips it and advances the recipient to the next step. The task is marked as skipped in the Tasks tab. Use this when the task is a value-add but not a blocker — you'd rather keep the sequence moving than stall a recipient indefinitely waiting on a manual action.
Toggle OFF (default): The recipient stays in Pending Action status until the recruiter manually completes or skips the task. The sequence does not advance on its own. Use this for tasks that genuinely must happen before the next step — e.g., a qualification call before sending a detailed proposal.
Where tasks appear
Tasks created by sequences are visible in the Tasks tab inside the sequence only. It shows all tasks created by this sequence, filterable by status, type, due date, and assigned recruiter. See Managing Sequence Tasks.
Required to launch
Only one field is required for a Task step to pass launch validation: Task Title, Task Type and Priority. All other fields are optional. A Task step without a title will block the sequence from launching.