Skip to main content
One task, one job. When your process has several steps with different goals, such as qualifying, then booking, then following up, give each step its own task and connect them. Each task stays short, and you can test and fix it on its own.

​
When to split

Split into separate tasks when the steps have different goals, different information to collect, different tools, or a different moment when the job is done. Keep a single task when they don’t: a very long task that tries to do everything tends to skip steps and mix rules.

​
How a lead moves to the next task

Tasks hand leads over through their final stages:
  1. Open the task and go to Stages.
  2. Edit a final stage and, under Continue with another task, choose a task belonging to the same Agent. Tasks from other Agents are not offered. Choose Do not transfer if the lead’s journey ends there.
  3. In Landing stage, choose where the lead starts in the next task. By default it’s the first stage.
  4. Turn on Silent transfer (not for calls) if the next task should wait for the lead to write instead of sending a message.
When a lead reaches that stage, it leaves the task and starts in the next one:
  • The conversation history and the information already collected go with it, so the next task can use them.
  • When the previous task asked the lead something or sent a link less than 2 minutes before the transfer, on a messaging channel, the next task waits for the lead’s answer instead of writing. Inside the WhatsApp 24-hour window, it continues the conversation instead of sending a template. See What the lead sees after a transfer.
  • The next task follows its own instructions, stages, and schedule.
  • The previous task’s pending follow-ups stop. Meetings the lead already booked, and their reminders, stay in place.
You can also ask for all of this in the agent’s chat: “Split this into a qualification task and a booking task, and pass qualified leads to booking.”

​
Where new conversations start

The task that no other task hands leads to is where new conversations start. When you test the agent, it’s marked Entry point. When the agent has two or more tasks, the Router decides which task takes each new inbound lead: always the same task, or the task that fits what the lead writes. Each task can say when a lead should go to it, under Routing in the task’s settings. If you leave it empty, Nexor uses the task’s instructions to decide. You can also set this up from your own systems with the inbound router API. It reads and changes the router’s settings and rules, tests a message without sending anything, and connects numbers and inboxes to the agent.

​
Example: qualify, book, follow up

​
Plan the hand-offs first

Before creating the tasks, fill in one block per task. It helps you avoid loops and makes clear who owns each lead.
  • Every lead should end in a task that owns the final result.
  • Hand leads forward. Avoid A → B → A unless there’s a clear reason to go back.
  • Name tasks by their job: “Qualification”, “Booking”, not “Task 2”.

​
Test the whole flow

Open Test this agent, start in the first task, and move the conversation toward its final stage. Check that the next task takes over and follows its own rules. See Test your agent.

​
Next

Go-live checklist

What to check before your agent talks to real leads.

Agents and tasks

What the agent shares with its tasks and what each task controls.
Last modified on October 19, 2026