Book the interview in one message, not eleven

The scheduler connects to Google Calendar and to Microsoft 365, reads free and busy time for each interviewer on the panel, and intersects it with the interview length, the buffer either side, and the working hours configured for that person. Only the intersection is offered.

Interviewers can be marked required or optional, which matters for a panel of four where two are genuinely needed and two are useful. A slot that works for the required interviewers is offered even when an optional one is busy, and the optional interviewer is invited anyway with their conflict visible to the coordinator rather than silently ignored.

The gap between offering slots and the candidate replying is where double-bookings are made. Surhires places a hold on the offered times in the panel's calendars, visible to them as tentative, so a colleague looking for a free hour sees the block. The hold expires on a timer you set, releasing the time if the candidate has not chosen.

The candidate receives a link and picks a slot themselves, on their own phone, in their own time zone, without an account or a login. The moment they choose, the unselected holds release, the real invitation goes out, and the record moves. What the recruiter does is nothing, which is the point.

Interviews move. A client emergency, a candidate's own interview elsewhere, a sick child. In an email-driven process a reschedule means starting the whole negotiation again, and it is the point at which a candidate most often goes quiet.

Rescheduling from the interview record cancels the old slot in every calendar, offers fresh availability, and notifies everybody with the reason once. The interview keeps its identity, so the record shows that this interview moved rather than showing one cancelled interview and one new one. A count of how many times an interview has slipped is exactly the signal the pipeline view uses to flag a requisition that is drifting.

A confirmed interview is not a completed interview. Reminders go out at intervals you configure, typically a day before and again a couple of hours before, carrying the time in the candidate's own time zone, the location or joining link, the interviewer names and anything they were asked to bring or prepare.

The channel follows the candidate's preference and their consent state. Email works everywhere. WhatsApp reminders are generally available for the India market at Wave 1 and reach the US market in Wave 2 once template approval clears. A candidate who has opted out of a channel is not reminded on it, and a candidate with no channel available is surfaced to the recruiter as a call to make rather than being quietly left unreminded.

Every interview sits on the requisition and on the candidate record with its stage, panel, time, outcome and feedback. Interviewers are prompted for a structured scorecard rather than a paragraph in a reply, because structured feedback is the only kind that compares across a panel and the only kind that supports a decision if it is ever questioned.

Outcomes feed the pipeline directly. Interview-to-offer conversion by client, by recruiter and by job type comes from these records, and so does the interviews-slipped panel on the Placement Pipeline Command Centre. Nobody types a number into a report; the report is made of the bookings.

Single-interviewer and small-panel scheduling ships today, along with multi-round sequences where a second stage is arranged after the first concludes. What is being extended is the harder case: a panel of several interviewers with different required and optional roles, split into consecutive sessions on the same day, where a change to one session has to cascade through the rest without unbooking the whole day.

That work is under way rather than finished. If your process routinely runs four-person panels in a single-day loop, ask us about the current state during the trial instead of taking this paragraph as a promise. Everything else on this page is shipping now.