home / use cases / back-office operations / interview-scheduling

Interview scheduling without the email ping-pong

Your Aivell emails each candidate real time options — slots where every interviewer is actually free — books the room and the invites the moment one is picked, sends prep material, nudges the silent, and confirms everyone the day before. Reschedules follow your rules, and applicant data never leaves your network.

Watch the demo

starts when: A candidate is ready to be scheduled for interview

The problem

Scheduling one interview means aligning a candidate who answers at 11 PM, two interviewers with hostile calendars, and a meeting room. Multiply by five candidates for the role, add a reschedule or two, and the recruiter has spent an afternoon playing calendar tetris by email. Across professions, 43% of people burn three or more hours a week just on scheduling meetings — recruiting is that problem with a stranger on one side.

The cost is not only time. Slow scheduling loses candidates: the strong ones have other processes running, and every extra day of “checking with the team” is a day for a competitor’s offer to arrive first.

How your Aivell does it

  1. The candidate gets real options, fast. The moment someone is marked ready, the Aivell reads the panel’s calendars and emails three slots that genuinely work — respecting your rules about Fridays, buffers and working hours.
  2. A pick becomes a booking instantly. Room reserved, invites out to everyone, prep material attached for the candidate and the CV summary for the panel. No human relaying between inboxes.
  3. Silence and reschedules follow procedure. Quiet candidates get one nudge, then the recruiter hears about it. Reschedules are accommodated twice; the third one becomes Chiara’s decision, not an infinite loop.
  4. The edge cases pause for people. An evening-slot request, an interviewer suddenly unavailable — the chore stops and puts the question on the recruiter’s phone, answered in one tap between meetings.
  5. Nobody no-shows unwarned. The day before, the candidate gets a confirmation and the panel a reminder — the cheap habit that saves the expensive empty room.

Guardrails keep the automation polite by construction: it can book interview rooms and interview slots but cannot touch anyone’s other meetings, and external email is physically limited to the candidate on file. The scheduling logic itself — how many options, how much patience, whose Fridays are sacred — is a chore in plain language. Change your process, change the sentence.

The chore, as you'd write it.

No flowcharts, no code — a chore is just a message to your Aivell, in your own words. It shapes it into a solid, guarded procedure and follows it to the letter. This one:

Giulia Aivell · schedule first interviews ● active

when a candidate is marked ready, email them three time options

offer only slots where both interviewers are free — check the calendars first

Chiara never interviews on fridays, and the panel needs 30 minutes between interviews

when the candidate picks, book the room, invite everyone, attach the prep sheet

no reply in three days — nudge once; after a week, tell the recruiter

two reschedules are fine; the third goes to Chiara to decide

the day before, confirm with the candidate and remind the panel

You
Got it — I'll start right away, and check with you whenever something needs a human.
Giulia Aivell

The tools it uses.

Connected with single-click passkeys — no copied tokens, no OAuth hell.

Calendar finds real slots, books rooms and invites
Email talks to candidates and the panel

Sensible guardrails.

Every tool can be limited to exactly what this chore needs. For this one, you might set:

Calendar May book the interview rooms and the panel's interview slots. Moving or cancelling anyone's other meetings is blocked.
Email External mail goes only to the candidate's address on file — no other outside recipients, ever.

Questions, answered.

What keeps it from offering slots that aren't actually free? +

It reads the interviewers' calendars before every offer, not after. The three options a candidate sees are real availability at that moment — including your quirks, like Chiara's no-Friday rule and the 30-minute buffer between interviews.

Candidates are protected by GDPR. Is their data safe here? +

Safer than with any scheduling SaaS — names, CVs and correspondence are processed on a box inside your office and never shipped to a cloud AI. Applicant data staying home is the whole design, not a setting.

A candidate wants a slot outside normal hours. What then? +

The chore pauses rather than improvises. The recruiter gets the request on their phone and settles it with a single tap — allow it this once, or offer alternatives. Exceptions stay human decisions.

What about candidates who go quiet? +

One nudge after three days, and after a week the recruiter gets a short heads-up instead of discovering the silence a month later. How patient to be is your call — it is one line in the chore.

Related.

What is an Aivell?

An Aivell is an on-premise AI colleague: a small box that plugs into your network, runs its own AI onboard and takes the repetitive work off your desk. Prompts, documents, data — nothing ever leaves your office. Unplug the internet: it keeps working.

You describe each task as a chore, in plain language. Your Aivell turns it into a solid, guarded procedure and runs it in the background — with guardrails on every tool, a complete audit trail, and approvals in your hand when you want them. One-time setup, fixed monthly fee. No tokens, no overages.

Watch the demo

onboard inference · air-gapped · fixed monthly fee