Interview scheduling
Interview scheduling looks simple until several people, calendars, time zones, locations, and interview formats are involved. A recruiter may spend multiple calls finding a slot, then repeat the date and instructions after a candidate changes availability. An unanswered scheduling call slows the process even when both sides want to proceed.
An AI phone agent can handle the defined scheduling exchange: identify the candidate and opening, check approved availability, offer appropriate choices, confirm the selection, and record the result. It should not decide whether someone receives an interview or move a candidate between hiring stages unless the recruiting team's own system and rules have already authorized that action. Broader recruiting operations belong in the industry guides; this page stays with the calendar function.
A concrete interview scheduling call
Suppose a candidate calls after receiving an invitation to schedule.
Agent: Thank you for calling Northstar Recruiting. I am the company's AI scheduling assistant. I can help arrange the interview you were invited to book. May I have your name and the role listed in the invitation?
Caller: Sam Ortiz, for the operations coordinator role.
Agent: Thank you. I found the approved scheduling path for that role. The interview is a video call with the recruiting team. Which time zone should I use when reading available times?
Caller: Pacific time.
Agent: I have openings on Tuesday morning and Wednesday afternoon. Which window works better?
After Sam selects a time, the agent repeats the day, date, time, time zone, format, and contact details. It creates the booking only after explicit confirmation and describes it as booked only after the calendar operation succeeds. If no listed time works, the agent records the candidate's availability and routes the exception to the recruiting coordinator instead of creating a slot outside the approved calendar.
This call is different from job applicant screening. The decision to interview has already been made by people; the agent coordinates an authorized next step.
How to configure the workflow on ThunderPhone
Separate scheduling policy from conversational wording. The connected calendar or scheduling account should expose only the availability and operations this agent needs. The prompt should then define how to use them.
A practical prompt outline includes:
- the opening disclosure and the employer or agency name;
- the identifiers needed to match the caller to the correct role and scheduling path;
- allowed interview types, durations, calendars, locations, and formats;
- how many choices to read aloud and how to handle the caller's time zone;
- confirmation rules for the selected slot, name, phone number, email address, and meeting format;
- a rule never to promise a booking before the connected operation succeeds;
- the approved process for no availability, rescheduling, cancellation, accessibility requests, interviewer changes, and duplicate appointments; and
- the conditions for a callback, Slack notification, cold transfer, or warm transfer.
Attach Cal.com or Google Calendar for the scheduling branch. Keep connection permissions narrow: the interview agent needs only the operations required for its assigned flow. Google Sheets can support a coordination queue, while Slack can notify recruiters about exceptions. REST or webhooks can deliver call outcomes to an existing recruiting system. If the organization exposes approved tools through Zapier MCP or another remote MCP server, add the server by URL, synchronize its tools, and attach only the relevant connection. Remote MCP servers must support streamable HTTP.
Add approved interview instructions to the agent's knowledge base: location, arrival process, video-call expectations, documents to bring, and a safe contact path for questions. ThunderPhone accepts text, Markdown, CSV, PDF, and DOCX documents, with per-agent selection. Do not place changing availability in a static document when the connected scheduling system is the source of truth.
Use an inbound demo U.S. number for testing, recognizing that demo numbers are inbound-only and not intended for production. Production numbers can be brought through supported direct VoIP connections or manual SIP configuration. Verified imported numbers support inbound and outbound calls. Cold transfer is available for immediate routing; attended warm transfer requires an eligible production number with outbound SIP capability.
Run tests for successful booking, ambiguous identity, no matching invitation, no suitable times, a time-zone misunderstanding, duplicate bookings, cancellation, and calendar failure. Browser mic tests, AI-caller simulations, reusable scenarios, graded call logs, and regression suites are available. Simulations are billable real calls, and the charge is shown before a run.
What to measure
Useful measures describe whether the schedule is correct and whether people had to repair it:
- invited candidates who complete a booking;
- bookings with corrected names, email addresses, dates, or time zones;
- duplicate or unmatched appointments;
- no-availability and exception handoffs;
- scheduling operation failures;
- rescheduling or cancellation requests completed under the approved flow; and
- candidate calls that require recruiter rework.
Grade calls for identity checks, manageable option presentation, explicit confirmation, and accurate closing summaries. Compare the call record with the calendar result instead of treating a spoken “done” as proof. For broader calendar handling, see appointment scheduling by phone and rescheduling and cancellations. The glossary entry on appointment setting explains the underlying workflow.
Where a human remains necessary
Recruiters should handle eligibility, advancement, interviewer substitutions, panel coordination, special arrangements, and any exception not represented in the scheduling rules. A human also needs to resolve conflicting calendar data or a candidate record the agent cannot identify safely. The agent should capture the request and provide a clear next step, not improvise an interview or imply a hiring outcome.