Interview Scheduling Automation for Recruiters: From Six Emails to One

Scheduling one interview is six emails and a calendar puzzle: find slots across three panel calendars, offer them, wait, book, send invitations with the right links, remind, and then do most of it again when the candidate asks to move. Recruiters who track their week find a third of it here. Every reschedule restarts the thread.

Calendar links do not solve it; they hand the puzzle to the candidate and produce slots nobody on the panel wanted. This post is about automating scheduling the way a good coordinator does it, using the interview scheduling blueprint.

Three slots, not a link

A good coordinator offers three specific times: spread across days, inside everyone's working hours, avoiding lunch and back-to-back interviews, at least a day away. The automation computes those three from live free/busy across every panel member and sends them in one email, written for the stage: who the candidate will meet, the format, what to prepare.

The candidate clicks one. Both sides get the invitation with the video link or room, the panel gets the CV and the scorecard, and the ATS stage updates itself.

The eight steps

1. Read the stage. Moving a candidate to an interview stage in Greenhouse, Lever or Ashby starts scheduling for that stage's panel: duration, format, who.
2. Find common slots across the panel's Google or Outlook calendars for the next ten working days.
3. Offer the slots in one email from the recruiter's address.
4. Book the chosen slot on every calendar, with the interview kit attached for the panel.
5. Remind. Candidate: 24 hours and 2 hours before, by email and SMS if they gave a number. Panel: 30 minutes before, with the CV and scorecard link.
6. Handle changes. A reply asking to move, cancel or ask a question is understood and acted on in the same thread; new slots are offered without the recruiter.
7. Sync the ATS. Scheduled, rescheduled, completed or no-show written back; the scorecard opened for the panel.
8. Report. Time from stage change to booked, reschedule rate, no-show rate by role and stage.

Reschedules are the real cost

Half of interviews move at least once. By hand, each move is a fresh round of emails and a fresh chance to lose the candidate to a faster process. The automation reads "can we do Thursday instead" in the same thread, offers three new slots in minutes, and updates everyone. This single step is where most of the recruiter's week comes back.

Reminders, and why panels need them too

Candidates who get a reminder the day before and two hours before, with a one-tap way to reschedule, show up. That alone moves no-show rates from roughly one in four to one in ten on volume roles. Less obviously, panels who receive the CV and the scorecard thirty minutes before run better interviews and fill in the scorecard the same day, which is what makes the next stage schedulable.

Guardrails that keep the panel on your side

• Working hours and "focus" blocks are respected; nothing is booked over them.
• No slot less than 24 hours away unless the recruiter allows it for the stage.
• One thread per candidate: every change lands in the same email conversation.
• SMS only with a number the candidate gave, opt-out honoured.
• The recruiter is copied on every candidate-facing message and can take over any thread by replying; the automation then steps back.

Where the standard version stops

Per recruiter, up to 200 interviews a month, one calendar system, and the ATS's own webhook and API. An agency scheduling against client panels in several calendar systems, full loops booked as one sequence with dependencies, or an ATS without an API are custom builds; the blueprint page says so before you pay.

Scheduling is the third blueprint in the recruiter package, after resume screening and candidate outreach. Together they cover the three jobs that fill a recruiter's week; each also runs on its own. See AI HR agents for the wider set.

Sources and further reading

• Greenhouse, Harvest API — stage changes and scheduled-interview write-back: https://developers.greenhouse.io/harvest.html
• Google, Calendar API: free/busy queries — the availability call behind the three slots: https://developers.google.com/calendar/api/v3/reference/freebusy/query