InsightHireHelp Center

Pipelines & automations

Customize hiring stages, give a position its own interview plan, and automate what happens at each stage.

Pipelines & automations

A pipeline is the ordered list of stages a candidate moves through. An automation is a plain rule on a stage, such as "When a candidate enters Phone screen, send them the Phone screen invite email."

Custom pipelines are an optional feature that InsightHire turns on per organization. Without them, positions use the standard application statuses and have no Board tab or stage automations. Tasks and reminders work either way; see Tasks and search.

Who can do what

  • Organization Admins create and edit shared pipelines, name stage owners, and add, turn off or delete automations.
  • People who manage a position's hiring team can change that position's own interview plan.
  • Everyone with access to a position can move candidates between stages on its Board.

Set up the default pipeline

  1. Open Settings → Pipelines.
  2. If no pipeline exists yet, select Create default pipeline. It starts with New, Reviewing, Screening, Interviewing, Offer, Hired and Rejected.
  3. Drag stages to reorder them. Use Add stage to add one.
  4. For each stage, set the name, color, the application status it stands for, the stage type, an owner role and, if needed, specific owners.
  5. Select Save pipeline.

The stage name is what your team sees on the Board. The application status behind it drives reports, integrations, surveys and other workflows. Statuses also include Reference Check, Offer Pending, Offer Accepted, Offer Declined and Withdrawn.

Saving keeps existing stage owners unless you change them.

Add another shared pipeline

  1. On Settings → Pipelines, select New pipeline. It starts with one Applied stage.
  2. Add and arrange its stages, then select Save pipeline.
  3. Switch between pipelines with the Pipeline picker. The default one is marked (default).

A position uses the default pipeline unless it has its own interview plan.

Give a position its own interview plan

  1. Open the position and go to Settings → Interview plan.
  2. To start from a shared pipeline, pick it under Choose a saved pipeline and select Apply.
  3. Change stages for this position only. For each stage you can set the Stage name, Stage type, Owner role, an Assessment or Interview kit, and Specific owners / panel members.
  4. Select Save interview plan.

Below the interview plan, Organization Admins can add automations that apply to that position only.

Move candidates through the pipeline

  1. Open a position.
  2. Select the Board tab.
  3. Drag a candidate to the right stage.
  4. Review any warning before confirming.

The Board shows candidate counts and time in stage. If your organization requires interview feedback, a move can be blocked until scorecards are submitted.

Moves from Review

By default, moving a card on the Review board does not run stage automations. To change that, turn on Run stage automations from the Review board at the top of Settings → Pipelines. When it is on, dragging a candidate forward on Review runs that stage's automations, including any candidate email. Moving a card backwards never re-runs them, and rejections from Review are not affected.

Set up automation

Organization-wide automations are on Settings → Jobs, under Automation. They attach to the stages of your default pipeline. Use Edit pipeline stages & owners to jump to Settings → Pipelines.

If you have no pipeline yet, Create default pipeline appears here too.

Guided setup

  1. Select Set up automation.
  2. Answer the questions, step by step:
    • Welcome candidates: send an acknowledgement email when they enter a stage.
    • Invite strong candidates: invite candidates who reach a minimum score to book an interview.
    • Keep work moving: notify teammates about candidates waiting too long in a stage.
  3. On Review your plan, read each plain-language rule. Rules you already have are marked and left unchanged.
  4. Select Turn on these automations. Nothing is saved before this.

Add one rule

  1. Find the stage under What happens automatically and select Add.
  2. Pick When:
    • A candidate enters this stage.
    • A candidate leaves this stage.
    • A candidate has been here for a while: after the number of days you set.
    • A candidate scores at least…: when their overall score reaches your bar.
  3. Pick Then:
    • Send them an email: pick one of your email templates.
    • Add to sequence: start them on a running outreach sequence. See Sequences.
    • Move them to another stage.
    • Invite them to book an interview: they pick a time from the interviewer's calendar.
    • Create a task for someone: with an optional due date.
    • Let teammates know: a heads-up, nothing else changes.
    • Suggest rejection (a person confirms): adds them to Ready to reject, with or without a rejection email to send when someone confirms.
  4. Read the preview sentence and save.

Turn a rule off with its switch at any time. Edit or delete it from the row menu.

For Invite them to book an interview, the interviewer is the stage owner: the specific people on the stage, otherwise the hiring-team member in the stage's owner role, otherwise the position's hiring manager. A candidate who already has an open booking link is not sent another one.

Rules chain. When a rule moves a candidate to another stage, that stage's rules run too.

Ready to reject

We never reject a candidate automatically. A Suggest rejection rule doesn't change the candidate's status and doesn't email them. It puts them on Hiring → Ready to reject and lets the stage's owners know (or the position's hiring manager, or an org admin, when the stage has no owners).

On Ready to reject, each row shows the candidate, the position and the rule that suggested it. Then:

  • Confirm rejects them the same way as rejecting from the Pipeline, and sends the rejection email set on the rule. Rules with no email send none. You can select several and use Confirm selected.
  • Dismiss keeps them in the pipeline. We record who dismissed it and when.

If someone moves the candidate to another stage, or rejects, hires or withdraws them before anyone confirms, the suggestion clears itself. Confirming and dismissing need the same access to the position as rejecting from the Pipeline.

Background-check rejections don't use this list. They follow the adverse-action steps in Background checks.

Use automation carefully

  • Start with acknowledgements, tasks and teammate notifications before you add rejection suggestions.
  • Test each new rule with a test candidate, then check the position's Activity.
  • Check Ready to reject often, so candidates aren't left waiting.

Troubleshooting

  • The Board tab or Settings → Pipelines is missing: custom pipelines aren't on for your organization. Contact InsightHire support.
  • A candidate can't be moved: check your access to the position and any pending interview scorecards.
  • An automation didn't run: confirm it is on and the candidate met the trigger. Moves on Review only run automations when the Review-board setting is on.
  • Reports show the wrong stage: check the application status set on that pipeline stage.