Find the one slot three diaries agree on
Candidate, hiring manager and tech interviewer, each with their own constraints and none of them looking at the others' calendars. The overlap gets found for you — and when a decline arrives, the replacement options are drafted before the gap in the day becomes a lost week.
Rahul Kapoor — Calder Rail tech screen
3 diaries · 1 overlap
| Who | Tue 10 | Tue 15 | Wed 11 | Thu 09 | Thu 14 |
|---|---|---|---|---|---|
Rahul Kapoor Candidate | No | Free | Free | No | Free |
Priti Nandy Hiring manager | Free | Busy | Free | Free | Busy |
Sam Iredale Tech interviewer | Busy | Free | Free | Busy | Free |
Wednesday 11:00 is the only column where all three work. Finding that by email takes nine messages and two days.
Works with
- Google Calendar
- Outlook
- Zoom
- Google Meet
- Calendly
- Gmail
Google Calendar is the one part of this desk with real event triggers — seven of them, including attendee responses — which is why the reschedule half genuinely reacts rather than waiting for a sweep. Calendly can generate a booking link but cannot create a calendar event, so where a real invite is needed the event is written to Calendar or Outlook.
The chore
How this goes right now
Three people need to be in a room, or on a call, at the same time. The candidate can't take meetings before ten because they're currently employed and their manager sits behind them. The hiring manager is in back-to-backs until Thursday. The tech interviewer has a calendar that says free but is actually on a customer site all Tuesday, which you only discover by asking. There is exactly one hour in the week that works and finding it takes nine emails.
Then somebody declines. It is Wednesday morning, the interview is Wednesday at eleven, and the tech interviewer has been pulled into an incident. The candidate has already told their current employer they're at the dentist. Now you have ninety minutes to either find a replacement interviewer, move the whole thing, or make the call yourself about whether it can run with two people instead of three — and every one of those options requires talking to somebody who isn't answering.
The reschedule is the expensive half and it's the half nobody builds for. Booking an interview is a puzzle. Re-booking one is a puzzle where all the pieces have already moved and someone has taken time off work under a small lie. Do it twice to the same candidate and you have taught them, quite reasonably, that this process is disorganised — which is the moment they start being honest with the other agency about their availability and vague with you.
The difference
Same three diaries, without the nine emails
Booking is the easy half. What changes most is the morning something falls over, when the options arrive before the panic does.
Try it
Walk through it yourself
This is the actual shape of the workflow — the same trigger, the same steps, the same draft waiting for your say-so. Click through it.
Schedule and reschedule interviews
Sam Iredale declined — Wed 11:00
This one is genuinely event-driven. Google Calendar publishes an attendee-response trigger, so a decline is picked up the moment it lands rather than waiting for a morning sweep — which matters when the interview is in two hours.
What it does
Read what just broke and how urgent it is
Tech screen at 11:00 today, 1h 52m away. Sam declined with "pulled into incident". Rahul and Priti have both accepted and neither knows yet.
Google CalendarLook for a stand-in who could actually cover it
Two other engineers listed as tech interviewers for Calder Rail. Dev Raman is free 11:00–12:30 today. Marta Cole is not.
Google CalendarWork out the fallback times across all three diaries
If it has to move: Thursday 09:00 works for Rahul and Priti but not Sam. Friday 14:00 works for all three. Nothing else this week.
Google CalendarDraft both routes so you can pick one
Option A: ask Dev to cover, interview runs as planned, nobody's morning is disturbed. Option B: move to Friday 14:00, with notes to all three. Neither sent.
Gmail
Draft list — nothing has been sent
Wed 11:00 tech screen — 1h 52m to fix it
- Recommended
Option A — Dev Raman covers, keep 11:00
Free until 12:30 and has interviewed for this role twice. Candidate never finds out anything happened. Draft ready to send to Dev.
- Fallback
Option B — move to Friday 14:00
The only slot all three share this week. Costs Rahul a second morning off and pushes the decision past the weekend.
- Waiting on you
Rahul Kapoor — not yet told
Accepted the invite yesterday. Has taken the morning off. Nothing goes to him until you've picked a route.
- No action
Priti Nandy — still holding 11:00
Free either way. Her diary stays blocked until you decide, so the slot isn't lost while you think.
Take Option A and ask Dev to cover?
You can take either route, or write your own. If Dev covering isn't right — maybe this candidate specifically asked for Sam, or Dev interviewed them at a previous company — that's context worth acting on, and it's exactly why nothing goes out without you.
Covered, with the candidate none the wiser
Dev is asked and the invite updated once he accepts. Rahul's morning is undisturbed. If he'd said no, it falls back to the Friday option with the reschedule notes already written. The one thing that never happens on its own is a change reaching the candidate — a moved interview is a message they should get from you.
The rescue, not just the booking.
Anyone can find a slot once. The value is what happens when somebody drops out at nine in the morning.
How it works
What it's actually doing
Two jobs that look like one. Finding the slot is arithmetic across calendars; rescuing a broken one is having the options ready before you need them.
- 1
- Google Calendar
- OuOutlook
Reads every diary that has to agree
Candidate constraints you've recorded, the hiring manager's calendar, and whichever interviewers are on the panel. The overlap is computed rather than negotiated by email.
- 2
- ZoZoom
- GoGoogle Meet
- Google Calendar
Writes an invite that's actually usable
Video link generated, the brief and CV attached, the address and the interviewer's name in the body. The details a candidate needs at 10:55 shouldn't be in a different email.
- 3
- Google Calendar
Notices a decline as it happens
The attendee-response trigger is real, so a cancellation surfaces while there's still time to act. This is the half that earns its place.
- 4
- Gmail
- Google Calendar
Has the rescue drafted before you open it
Stand-in interviewers who are genuinely free, fallback slots across all three diaries, and the messages written both ways so picking one takes seconds.
It finds the time. Telling a candidate their interview moved is your job.
Scheduling is arithmetic and it can have that. What it doesn't get is the part where a person who booked time off work is told the plan changed — because how that lands determines whether they stay in your process, and it should come from the consultant they trust.
Step one
It drafts
Step two — you
You read it and approve
Step three
Only then does it send
No change reaches a candidate on its own
Moving or cancelling an interview always waits for you. A candidate who finds out from a calendar notification that their morning was wasted is a candidate you've lost for reasons that had nothing to do with the job.
It doesn't decide who interviews
Stand-ins are surfaced as options with their availability. Whether Dev is the right person for this candidate is a judgement involving history you hold and it doesn't.
It won't book over a soft hold
A tentative block or a slot marked as held is treated as taken. Filling somebody's provisional time because it technically read as free is how you lose an interviewer's goodwill for a quarter.
It never cancels
It can propose moving something and draft every message involved. Actually pulling an interview out of three diaries is a decision with consequences for real people's days.
Setup
What setting this up involves
- 1
Connect
- Google Calendar or Outlook — yours, and the interviewer diaries you can see
- Zoom or Google Meet, for the video link on the invite
- Gmail or Outlook, so invites and reschedules come from you
- Calendly, if you use booking links for first-stage calls
- 2
Tell it how you work
- Which calendars are real interviewer availability, and which are just noise
- Your buffer rules — no interviews before ten, nothing back-to-back, travel time for on-sites
- Who can stand in for whom, per client and per role
- What goes in an invite: link, CV, brief, address, dress code
- How urgent a decline has to be before it interrupts you rather than waiting
- 3
Then it runs
About 35 minutes, once
The panel and stand-in mapping is most of it, and it's per client rather than per role, so it's written once and reused. Buffer rules take two minutes and save the most obvious mistakes.
Edge cases
Where it's careful, and what it won't do
What it handles
A candidate who can't take calls at work
Constraints you've recorded — nothing before ten, nothing on Wednesdays, lunchtimes only — are applied before any slot is proposed, so you don't offer times that quietly cost someone their cover story.
Time zones across a panel
An interviewer in Dublin, a manager in Manchester and a candidate mid-relocation. Slots are computed in each person's own zone and written into the invite so nobody does the arithmetic at 08:55.
A decline that isn't urgent
Something declined for a fortnight away doesn't interrupt you — it joins the list. A decline ninety minutes out does. The difference is the entire point.
Diaries that lie
An interviewer whose calendar is permanently free but who is never actually available can be weighted or excluded, so proposals reflect the reality of a team rather than its calendar hygiene.
What it does not do
Tell the candidate anything changed
Reschedules and cancellations always go through you. That message is about trust, not logistics.
Cancel or move an interview by itself
It proposes and drafts. Removing something from three diaries stays a human decision.
Choose the interviewer
Availability is arithmetic; suitability isn't. Stand-ins come as options with the constraint shown, and you pick.
Handle a client's own scheduling system
Where a client insists interviews are booked through their internal tool, it can prepare everything but the booking itself. Nothing exists to drive those systems from here.
Time back
Three to six hours a week, and the reschedules stop costing candidates
- Time back
- 3–6 hrs a week
- Spent on
- Filling the next role
- What it costs
- $49 / monthGrowthplan — see what’s included
How that’s worked out: Based on eight to twelve interviews arranged a week at roughly twenty minutes each of genuine back-and-forth, plus one or two reschedules that eat a morning. The hours are real, but the reason desks adopt this is the second number: a rescued interview is a process that doesn't slip a week, and a week is usually the margin between your offer and somebody else's.
Fair questions
The questions consultants ask first
We can't see the client's calendars, so how can this work?
It works with whatever you can see, and degrades honestly rather than guessing. Where you have visibility of a hiring manager's diary — which is common on retained and embedded work — it computes the real overlap. Where you don't, it works from the times that manager has offered you and your own panel's availability, which is still better than doing it in your head. It never proposes a slot on a calendar it can't actually see.
Isn't a scheduling link simpler than all this?
For a first call with your own diary, yes, and you should use one. Links stop working the moment three people have to agree, because you'd need to expose a client's calendar to a candidate, and no hiring manager will accept that. That constraint is precisely what makes second-stage scheduling expensive, and it's the case this is built for.
What actually happens if it gets a reschedule wrong?
It can't send one. Every reschedule and cancellation waits for you to choose a route, and nothing reaches the candidate without your approval. The failure available to it is proposing an option you reject — a stand-in who's wrong for the candidate, a Friday slot that doesn't suit. You'd see that when you read it, which takes about ten seconds because the constraint on each option is shown.
More off the same desk
Other things that keep falling off the list
Chase candidate availability
Every candidate sitting on an availability request gets a nudge with real slots in it, before the client's window closes and you have to ask for new ones.
Send interview prep packs
The day-before pack assembled per interview — link, interviewer, format, address — so nobody arrives underprepared because you were busy.
Write up interview notes
The write-up drafted from the recording, in your format, quoting what was actually said — so notes exist while you still remember the call.
Chase hiring manager feedback
Every interview with no feedback after 48 hours gets a nudge drafted to the client, and you get one list of what's outstanding across the desk.
Keep the ATS current
Stage moves and notes drafted from what actually happened in your mail and diary, so Friday isn't spent typing last week into a system.
The same scheduling problem elsewhere
FAQ
Questions worth answering properly
Is the reschedule half really immediate, or is it polled?
Genuinely event-driven. Google Calendar publishes an attendee-response trigger, so a decline is picked up as it arrives rather than on a sweep. That's unusual on this desk — most recruiting workflows are scheduled polls because no ATS publishes any trigger at all — and it's the reason this page can promise something the others deliberately don't.
Does it send the invite itself?
It writes the invite with the video link, attachments and joining details in place, and you send it. First bookings are usually approved in a couple of seconds. Reschedules always need you, because a candidate being told their morning moved is a conversation, not a notification.
Can it find a replacement interviewer?
It surfaces who's genuinely free from the stand-in list you've set per client, with their availability shown. Whether that person is right for this candidate — history, seniority, whether they've met before — is yours to judge, and the option is presented for you to accept or reject rather than acted on.
How does it handle candidates who can't talk during work hours?
Constraints you record against a candidate are applied before any slot is proposed. Nothing before ten, lunchtimes only, no video from the office — all of it filters the options rather than being remembered by you at the point of booking.
What if the client books interviews in their own system?
Then the booking itself stays with them and this covers everything around it — finding the overlap, preparing the details, spotting a decline and drafting the recovery. Composio publishes nothing that can drive a client's internal scheduling tool, and pretending otherwise would just move the problem.
Will it double-book someone whose calendar looks free?
Tentative blocks and held slots are treated as taken, not as available. Some interviewers keep calendars that are technically empty and practically full, and you can weight or exclude those so proposals match how a team actually works.
Book the interview, and keep it when it wobbles
Connect the calendars you can see and set your panel per client. The next decline arrives with the options already drafted.
Start free