The interviewer changes the meeting time after the candidate confirms
Format: Demo script: proposed custom design.
Scene 1: the old confirmation is still real
Scene context: This proposed scheduling design uses fictional records and dialogue. It is not a working integration or produced video.
Narrator: “The candidate confirmed a Tuesday interview at 10 a.m. in the stated local time zone. The interviewer now asks for 11 a.m. Updating a calendar does not prove the candidate accepted the change.”
Interviewer: “Please move it to eleven. I have another meeting at ten.”
Coordinator: “I will check the revised slot and ask the candidate to reconfirm. Their current confirmation still applies to ten, not eleven.”
Scene context: Proposed check record: Original event version, candidate confirmation source, requested new version, interviewer availability and candidate acknowledgment pending.
Scene 2: reconcile the records
Narrator: “Greenhouse says a change to the calendar event does not update the candidate in the flow it describes. For an external calendar change, it tells staff to send the candidate a new confirmation email. [S04] Check the setup you use. Sending a note does not prove everyone got it.”
Coordinator: “The new slot is available for the interviewer. I have checked the date, time zone, location, and meeting link. I will prepare a clear change message under our communication rules.”
Scene context: The draft must use the checked invite's full date and named time zone. In this scenario, the coordinator asks whether the candidate can move from 10 a.m. to 11 a.m. on that same date and in that same zone. Staff must check the actual date and zone before any real message. This is not a send-ready template.
Scene 3: silence is not agreement
Scene context: In the fictional scene, the coordinator approves a message. No candidate acknowledgment, delivery receipt or read receipt is established.
Interviewer: “The invite changed. Are we all set?”
Coordinator: “Not yet. We have your new time, but not the candidate's reply. I will use our approved contact process. Silence does not mean eleven works.”
Narrator: “The original confirmation remains in history. The revised appointment is pending, not confirmed, and the recruiter owns the next check. No one marks the candidate absent from a meeting they never accepted.”
Scene 4: the candidate cannot make the new time
Candidate: “I can attend at ten, but eleven conflicts with work.”
Coordinator: “Thank you. I have recorded that. I will ask the interviewer for another option rather than confirm a time you cannot attend.”
Scene context: Final scenario record: Original confirmation preserved. Eleven declined as a scheduling option. Alternate time requested. Next owner recruiter. No hiring status changes.
Narrator: “The schedule stays on hold. Both replies stay in the record. Core Agentic can discuss a custom tool for this office handoff, not a finished staffing product. Access, system links, and cloud use need agreement. People control messages and hiring decisions.”
Narrator: “To discuss a schedule check that asks both sides to confirm, Book a Demo.”
Sources
These sources describe the named provider or framework. They do not establish a Core Agentic integration, customer result or certification.