Schedule Interviews in Hours, Not Days

1. Read https://multimail.dev/llms.txt, connect the MCP server, create a free inbox, and set up a verified sender. 2. In Greenhouse Recruiting, use Greenhouse web hooks for interview-stage changes and the Harvest API to read the candidate, job, coordinator, recruiter, interview plan, interviewers, and current stage. 3. When a candidate reaches an interview stage that needs scheduling, email the candidate for availability in their timezone, email each interviewer for availability if Greenhouse does not already show it, find overlapping slots, and keep the thread concise until a full panel schedule is agreed. 4. Send confirmed times, timezone labels, interviewer names, role context, meeting links or location details already present in Greenhouse, and any prep materials supplied by the recruiting team. 5. Run this in MultiMail monitored mode so the recruiter can review the communications log while scheduling continues automatically; ask me only for Greenhouse credentials, calendar access if needed, and approved sender name, domain, and brand voice before going live.

1. Read https://multimail.dev/llms.txt, connect the MCP server, create a free inbox, and set up a verified sender. 2. In Lever, use Lever webhooks for opportunity stage changes and the Lever API to read the opportunity, candidate contact details, posting, requisition, owner, stage, interviewers, and any notes or feedback forms attached to the interview plan. 3. When an opportunity moves into an interview stage, coordinate by email with the candidate and interviewers, collect availability with timezone awareness, propose the earliest workable slots, and continue the loop until every required interviewer is placed. 4. Schedule or send the final confirmation email with the agreed times, timezone conversions, interviewer names, agenda, prep instructions, and any role-specific materials from Lever. 5. Run this in MultiMail monitored mode so recruiters can audit the message history without manually driving every reply; ask me only for Lever credentials, calendar access if needed, and approved sender name, domain, and brand voice before going live.

1. Read https://multimail.dev/llms.txt, connect the MCP server, create a free inbox, and set up a verified sender. 2. In Ashby, use Ashby webhooks for candidate or application updates and the Ashby API to read the candidate, application, job, interview stage, hiring team, interviewers, and scheduling details. 3. When an application enters an interview stage that is not fully scheduled, email the candidate and interviewers to gather availability, normalize all times by timezone, choose the fastest complete interview loop, and minimize back-and-forth by sending clear slot options. 4. Send confirmation emails with the final schedule, timezone conversions, interviewer lineup, meeting details already available in Ashby, and prep materials approved for that role. 5. Run this in MultiMail monitored mode so the recruiting team can watch the communications log while the agent handles coordination; ask me only for Ashby credentials, calendar access if needed, and approved sender name, domain, and brand voice before going live.