Scheduling runs itself now.

The Recruiting Coordination Agent takes a scheduling request from “let’s schedule” through to a booked interview: outreach, availability, booking, rescheduling, and reminders. It also handles the breaks in that process, such as a last-minute interviewer decline or a candidate who stops replying. Your team steps in for the decisions you choose to keep, and whenever the agent cannot finish inside the rules you set.

Interview scheduling in candidate.fyi runs when you ask it to. The Recruiting Coordination Agent is handed a scope, like a req, a stage, or a team, and owns the job from there without being asked. It keeps chasing, rebooking, and negotiating until every interview is booked inside your SLA.

You set a time-to-interview target per role, such as fully scheduled within eight business days. The agent paces every outreach and follow-up against the deadline and escalates before it slips. If a target isn’t achievable with current interviewer availability, it tells you upfront.

You choose which of these situations the agent may handle on its own. When an interviewer declines and the agent is allowed to act, it looks for someone who can take that time, then for another time that still meets your deadline, books it, and tells your coordinator what changed. When a candidate stops responding, it follows up a limited number of times and then hands the request to your team.

You decide how much of the scheduling work the agent handles on its own, and how much it brings to your team first. It can book and message people, or it can look into a situation and recommend the next step without making the change. You can set that differently for different kinds of candidate requests. Every step is written in a plain-language thread your team can redirect while the work is in progress.

No. Interviewers hear from the agent in Slack or email, and candidates hear from it by email in your brand’s tone. It understands natural replies like “morning next week, not Wednesday.”