Automations

Your hiring process, followed to the letter.

Some steps never change: invite every Ideal fit to the interview, remind people who didn’t finish, start onboarding the moment someone is hired. Tell Eva once, in your own words. It does it that way for every candidate, at 3 a.m. too.

Your AI employee

Standing instructions, for every shift.

A good colleague learns how your team works and does it that way without being asked. Automations are those instructions for Eva: what to do when something happens, for which jobs, and when to hand over to a person.

Eva runs it

  • Starts it the moment something happens: an application, a passed call, a finished interview, a move on the board
  • Checks each If against the candidate as they are right then
  • Waits the hours or days you set, then carries on
  • Sends emails between 8am and 7pm where the job is
  • Logs every step, on the automation and on the candidate’s page

Your team decides

  • What each automation does, and which jobs it runs on
  • Publishing each version, and switching it on or off
  • Every hire, and every rejection

How it works

From a sentence to a running automation.

Five steps, and a person approves each one that matters.

01 · Describe

Say what should happen. Eva builds it.

Tell Eva in your own words, like you’d brief a colleague. It looks up what it needs, builds the automation from the blocks and shows it on the canvas. If it isn’t sure what you mean, it asks first.

02 · Shape

Change it on the canvas, or just ask.

Drag blocks, connect them, set a Yes and a No path. Or tell Eva what to change: it changes only that, marks it on the canvas, and leaves everything else as it was.

03 · Test

See what it would do with your own candidates.

Before anything runs, try it on the last 30 days: exactly how many candidates it would have reached and what it would have done for each. It’s only a test, so nothing is sent.

04 · Switch on

Publish it, then switch it on.

Every change is published as a version with a title, and you can go back to an earlier one any time. A draft can’t run, and a new automation stays paused until someone on your team switches it on.

05 · Every run

Every step, on the record.

Each automation has its own history of runs, and each candidate’s page shows what ran for them, block by block. You always know why someone got an email.

01 · Describe

Say what should happen. Eva builds it.

Tell Eva in your own words, like you’d brief a colleague. It looks up what it needs, builds the automation from the blocks and shows it on the canvas. If it isn’t sure what you mean, it asks first.

02 · Shape

Change it on the canvas, or just ask.

Drag blocks, connect them, set a Yes and a No path. Or tell Eva what to change: it changes only that, marks it on the canvas, and leaves everything else as it was.

03 · Test

See what it would do with your own candidates.

Before anything runs, try it on the last 30 days: exactly how many candidates it would have reached and what it would have done for each. It’s only a test, so nothing is sent.

04 · Switch on

Publish it, then switch it on.

Every change is published as a version with a title, and you can go back to an earlier one any time. A draft can’t run, and a new automation stays paused until someone on your team switches it on.

05 · Every run

Every step, on the record.

Each automation has its own history of runs, and each candidate’s page shows what ran for them, block by block. You always know why someone got an email.

The blocks

Eight blocks, for the whole hiring flow.

From the application to the first shift. Each automation runs on the jobs you choose, and every job has its own board, with the stages your team works in.

When

What starts it: someone applies, passes the AI call, finishes an AI interview, is moved to a stage, or has a start date coming up.

If

Checks the candidate: AI screen fit, a dealbreaker, must-haves met, the AI interview, the stage, onboarding. Yes and No can each lead on, or end there.

Wait

Hours or days before the next block.

Send an email

An email to the candidate, filled in with their first name, the job and the company.

Move to stage

Moves them to a stage of the job’s own board.

Invite to AI interview

Sends one of your AI interviews, done on their own time.

Start onboarding

Sends the start link with the documents the job’s onboarding asks for.

Tell the team

An email to your admins and recruiters, when someone needs a person.

Where to start

Automations teams start with.

Ask Eva for any of these, then change them to fit how you work.

Ideal fits to the interview

When an Ideal or Good fit passes the AI call, invite them to the AI interview straight away.

Reminder to finish applying

A day after someone applies, if they haven’t done the AI call yet, a friendly reminder with their link.

Onboard new hires

When someone is moved to Hired, start their onboarding and tell the team.

First-day reminder

Three days before a start date, an email with where and when to come.

Interview done, ready to review

When a candidate finishes the AI interview, move them to In review and let the team know.

Dealbreaker alert

A day after someone applies, if a dealbreaker came up in their AI call, a person takes a look.

Always on, whatever an automation says

Nobody is rejected by an automation

There’s no block for it. A person always decides.

Sending hours

Candidate emails go out between 8am and 7pm where the job is; anything due at night waits for the morning.

No spam

At most 3 emails per candidate from one automation.

Only from now on

Switching one on never acts on anything that happened before.

Tell Eva once. It does it every time.

Join the waitlist and we’ll set up your first automations with you.