> ## Documentation Index
> Fetch the complete documentation index at: https://docs.jobin.cloud/llms.txt
> Use this file to discover all available pages before exploring further.

# How to move candidates to a pipeline stage automatically

> Set a stage entry rule so candidates move to a stage on their own when they are assigned, contacted, reply, or show interest.

To move candidates automatically, open a stage's automations on the job's pipeline and set **Assign stage** to an event, such as **First human reply**. Candidates then move to that stage when the event happens in one of the job's linked sequences.

## What this gets you

* Your pipeline stays accurate with no dragging cards around.
* Everyone on the team sees the same up-to-date picture, which matters when a client is watching.
* Moves become the trigger for what happens next, such as starting a follow-up sequence.

## Before you start

* A [sequence linked to the job](/how-to/link-a-sequence-to-a-job.md). The rule listens to that sequence's outreach.

## Steps

1. Open the job and go to its pipeline board.
2. Open the stage's automations: select the stage name, or open the **Stage actions** menu on the column and choose **Stage automations**. The panel is titled *\[Stage] automations* and saves as you edit.
3. In the **Assign stage** card (*How do contacts get here*), read the sentence *Move contacts to \[stage] when ...* and choose the event.
4. Pick one of: **Contact assigned to sequence**, **First successful outreach**, **First human reply**, or **Interested**. **Manual only (disabled)** turns the rule off.
5. Check the sequence named after the event. If more than one sequence is linked to the job, each shows as an alternative, and you can remove one with the cross next to it.
6. Repeat on the other stages you want to automate.

## Tips

* **First human reply** ignores automatic responses such as out-of-office messages.
* **Interested** fires when a reply is identified as interested, so pair it with [Reply Identification](/how-to/handle-replies-automatically.md).
* Candidates are only moved forward in the pipeline, never backward.
* If no sequence is linked to the job, the stage shows a warning, and **Link Sequence** lets you fix it on the spot.

## Ideas to get more from it

* Send **First human reply** candidates to a Replied stage and review that list first each morning.
* Use **Interested** to feed a short-list stage you share with a client.
* Combine with a stage sequence that books interviews for everyone who arrives.

## Related

* [Job pipelines guide](/job-pipelines.md)
* [How to link a sequence to a job](/how-to/link-a-sequence-to-a-job.md)
* [How to start a sequence when a candidate reaches a stage](/how-to/start-a-sequence-when-a-candidate-reaches-a-stage.md)
* [How to move candidates through a pipeline](/how-to/move-candidates-through-a-pipeline.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.