Interview Scheduling Automation Slots offered, booked and rescheduled without the recruiter
When a candidate moves to interview, they get three real slots the same day — and every change is handled in the same thread.
- Installed for you · one-time$249
- Run for you$197/month
- Custom build · this process$2,000–3,500 one-time
- Starts whenATS stage change (candidate moved to interview)
Per recruiter, up to 200 interviews a month, one calendar system. Panels across several companies (agency), interview loops with sequential rounds booked together, or an ATS without an API are a custom build. Custom builds start at $2,000 site-wide; this band is for this process and its integrations.
Interview Scheduling Automation is an automation Agentmelt installs in Twilio. The free template is a file you import yourself; the kit ($49) adds the setup guide and prompts. Installed for you costs $249 one-time and is live within two working days of access, with a recorded walkthrough and 30 days of fixes. Run for you costs $197/month, with setup and maintenance included. A custom build of this process is $2,000–3,500 one-time; custom builds start at $2,000 site-wide. No call is needed for any option. Written by Max Zeshut; last revised 2026-09-21.
Reference stack: Claude + n8n. Node names are on each step; the file is under the template.
Founder at Agentmelt
Reviews every build before it goes live; the workflow escalates to a person, never past one.
What is interview scheduling?
Interview scheduling automation is a workflow that removes the six-email calendar puzzle from every candidate at every stage: it reads the stage from the ATS and the panel's real calendars, offers the candidate three slots that work for everyone across time zones, books the one they pick with the right meeting links, reminds both sides the day before, and handles “can we move it?” in the same thread — updating the ATS at every step. An AI step reads the candidate's reply when it is not a slot choice; everything else is rules. The recruiter sees the confirmed interview and spends the saved hours on candidates.
- Scheduling one interview is six emails and a calendar puzzle, repeated for every candidate at every stage.
- Panel interviews take a week to book because four calendars never line up in one email.
- Candidates in other time zones get slots at 3 am.
- One interviewer cancels and the whole loop has to be rebuilt by hand.
- The ATS stage is updated on Friday, if someone remembers.
If two of these are yours, this is the process to look at first. Free audit — or read on.
What it looks like once it runs.
Scheduling an interview is six emails and a calendar puzzle, repeated for every candidate at every stage. The workflow reads the panel's calendars, offers the candidate three slots that work for everyone, books the one they pick, sends invitations with the right links, reminds both sides the day before, and handles 'can we move it' in the same thread without the recruiter touching it. The ATS stage updates itself, and no-shows drop because the candidate had a reminder and an easy way to reschedule.
- 10:15 A candidate is moved to the interview stage. The panel, duration and format are read.
- 10:16 Free time across every panel member for the next ten working days is found, avoiding lunch and back-to-backs.
- 10:17 One email from the recruiter offers three slots, who they will meet and what to prepare.
- On a click The event is on every calendar with the link and the CV; reminders go out 24 and 2 hours before.
- “Can we move it?” Understood and re-offered in the same thread; the ATS is kept in sync.
Recruiters spend a third of their week on scheduling: finding slots across three calendars, chasing candidate replies, moving interviews, updating the ATS by hand. Every reschedule restarts the whole thread.
A candidate moved to 'interview' gets slot options within minutes, books in one click, and both sides get the invitation and a reminder. Reschedules take one reply. The recruiter's calendar stops being a switchboard.
Trigger, then 8 steps.
All eight steps run without anyone; a person sees only what the guardrails escalate.
ATS stage change (candidate moved to interview)
Read the stage
Candidate, role, interview stage, the panel for that stage, duration, and whether it is video or on-site.
Find common slots
Free/busy across every panel member for the next ten working days, inside their working hours, avoiding lunch and back-to-back blocks; three options, spread across days.
Offer the slots
One email from the recruiter with three buttons or links, the format, who they will meet, and what to prepare — written for the stage, not a template dump.
Book
The chosen slot becomes an event on every calendar with the video link or room, the candidate's CV attached for the panel, and the interview kit.
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 the scorecard link.
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.
Sync the ATS
Interview scheduled, rescheduled, completed or no-show is written back to the candidate's record; the scorecard is opened for the panel.
Report
Time from stage change to booked, reschedule rate, no-show rate by role and stage, so the recruiter sees where the process drags.
No step waits for a person.
What the workflow hands to someone, by rule:
- Panel working hours and blocked times are respected; the workflow never books over a 'focus' block or outside hours.
- Candidates are never offered a slot less than 24 hours away unless the recruiter allows it for the stage.
A candidate moved to 'interview' gets slot options within minutes, books in one click, and both sides get the invitation and a reminder
A candidate moved to 'interview' gets slot options within minutes, books in one click, and both sides get the invitation and a reminder.
No decisions needed. Anything the guardrails flag is handed to a person; the rest ran alone.
Each pattern page explains it in plain words and lists every automation that uses it.
The template is built on n8n (how the n8n AI Agent node works); the same steps run on Make, Zapier or plain code. The tool is chosen to fit your accounts, you own the result, and the template comes in all three formats.
Data it touches
- ATS stages and panels
- Panel calendars (Google, Outlook)
- Candidate contact details
- Interview kits and scorecards
- Video-conferencing links
Guardrails
- Panel working hours and blocked times are respected; the workflow never books over a 'focus' block or outside hours.
- Candidates are never offered a slot less than 24 hours away unless the recruiter allows it for the stage.
- Every change is written to the same email thread, so the candidate has one conversation, not five.
- 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.
Three slots, not a calendar link
A scheduling link hands the puzzle to the candidate and produces slots nobody on the panel wanted. Offering three specific times — spread across days, inside everyone's working hours, avoiding back-to-back interviews — is what a good coordinator does, and it books faster. The workflow computes those three from live availability every time.
Reschedules are the real cost
Half of interviews move at least once. Each move by hand is a fresh round of emails and a chance to lose the candidate. Handling 'can we do Thursday instead' in the same thread, automatically, with new slots offered in minutes, is where most of the recruiter's week comes back.
Reminders halve no-shows
Candidates who get a reminder the day before and two hours before, with a one-tap way to reschedule, show up. Panels who get the CV and the scorecard thirty minutes before run better interviews. Both are cheap; both are usually skipped when a person is doing the scheduling.
What it connects to.
| Tool | Role in this workflow |
|---|---|
| n8n | Orchestration, calendar logic, reminders, ATS sync |
| Claude | Understanding replies and drafting the candidate-facing messages |
| Greenhouse / Lever / Ashby | Stages, panels, write-back |
| Google Calendar / Outlook | Availability and bookings |
| Twilio | SMS reminders |
Want this running without building it?
$197/month
We set it up in your tools, run it on our servershost it on our n8n cloud (or deploy it to your own n8n, Make or Zapier), watch it, and fix it when something changes. Setup included, cancel monthly; the automation stays yours if you leave.
$2,000–3,500 one-time
Your systems, your rules, your edge cases. A one-off build delivered into your accounts to keepon Claude and n8n, delivered into your accounts to keep, with documentation and a recorded walkthrough.
Per recruiter, up to 200 interviews a month, one calendar system. Panels across several companies (agency), interview loops with sequential rounds booked together, or an ATS without an API are a custom build.
Also sold one-time, installed in your own accounts, as part of the recruiters package and the hr teams package and the hr managers package — do it yourself $49 · installed for you $249 · done for you $490.
When this becomes a custom build.
The subscription covers the standard version — $197/month, setup and maintenance included. Three things move it to a custom build ($2,000–3,500 one-time), delivered into your accounts to keep. If one of them is you, say so on the audit and the plan prices both.
An agency scheduling against client panels in several calendar systems.
Full loops — several rounds booked as one sequence with dependencies.
An ATS or HRIS without an API, where write-back has to go through files or a browser.
Running the standard version first is the usual path: the exceptions it logs in the first month are the scope of the custom build, with your own numbers. How custom builds work.
Frequently asked questions.
Does it work with Outlook calendars?
Yes — Google Calendar and Microsoft 365 are both standard. Mixed panels (some on each) are fine.
What if a candidate asks a question instead of picking a slot?
The reply is classified; questions about format, location or preparation are answered from the interview kit; anything else goes to the recruiter with the thread.
Can the candidate still email the recruiter directly?
Always. The recruiter is copied on every message and any reply from them takes the thread over; the automation steps back until the recruiter hands it the next stage.
How does an AI interview scheduling agent work?
It reads the stage from the ATS and the panel for that stage, checks the interviewers' real calendars, offers the candidate three slots that work across time zones, books the one they pick with the meeting links, sends the reminders and the preparation, and handles reschedules in the same thread — updating the ATS at every step. The AI's only job is understanding a reply that is not a slot choice; the availability, the booking and the reminders are rules.
Can it coordinate panel and multi-round interviews?
Panels, yes — finding the slot across four interviewers and a candidate is where it pays most, and when one interviewer cancels it re-solves the puzzle and re-offers. Full loops booked as one sequence with dependencies between rounds are a custom build; the standard workflow handles one stage at a time.
Which ATS and calendars does interview scheduling automation work with?
Greenhouse, Lever and Ashby on the ATS side; Google and Microsoft calendars; Zoom, Google Meet and Teams for the links; email or SMS to the candidate. An ATS without a usable connection works through exports and is a custom build.
What this blueprint is built on.
Vendor documentation the steps rely on, and the rules the guardrails are written against.
- Greenhouse — Harvest API developers.greenhouse.io/harvest.html
- Google — Calendar API: free/busy query developers.google.com/calendar/api/v3/reference/freebusy/query
- Twilio — Programmable Messaging docs www.twilio.com/docs/messaging