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.