Draft the invitation, hold the thread beside the slot it moved, and stop the booking the moment a candidate asks for something a coordinator, not a calendar, has to answer.
An invitation goes out, and the reply that came back is kept beside the slot it moved.
02
A reply reads as a preference, and it is held as a possible request until a human says otherwise.
Reason
03
A candidate names a barrier in plain words, and the booking stops rather than quietly moving.
04
A follow-up lands on an open request, and it is answered as that request, not as a status query.
05
A slot set is offered, and the wider set it was drawn from is recorded next to it.
Decide
06
A thread turns toward pay history or convictions, and the agent stops and hands the thread over.
07
A recorder is proposed for a panel, and the thread waits on consent from each party named in it.
Out
08
A thread goes quiet with a request open, and that silence is raised rather than closed as attrition.
09
Take write actions in a calendar only within the approval boundaries agreed at implementation.
→Product statement
Drafting, holding and recording belong to the agent. Answering a request belongs to a named coordinator, who carries it into the interactive process and owns it there.
Example workflow
One thread, invitation to confirmation
AgentHuman
1Requisition and panel receivedPanel members, room or link, candidate contact and the requisition it belongs to
2Invitation drafted and stampedThe slots offered, the wider set they were drawn from and the day the invitation was sent
3Reply read and classedThe message exactly as written, the class assigned to it and the confidence behind that class
4Controls appliedRequest screens, prohibited-topic checks, consent checks and classification confidence
No human action required
Stages 1 to 4 run unaided, and no interview is confirmed at any of them — the agent is drafting, and the coordinator lane opens at the reply gate.
5DecisionSplits at the reply gate
Plain logistics reply
Goes to the named coordinator to confirm.
Anything that may be a request
Adds a coordinator read before a slot moves.
Coordinator review
The thread is held with the message as written, the slots offered and the day it arrived.
Confirm · Append note · Send to coordinator review
Confirmed — by the named coordinator▼
6Calendar and applicant records updatedOnly where write access and retention policy allow it
7Outcome evaluatedClassification accuracy, request handling, coordinator corrections and what review found
Corrections
Every coordinator correction is counted back into the evaluation suite.
What should not run autonomously
Human approval stays in control
Outside the boundary — human approval required8 items
Answering a request for reasonable accommodation.
Deciding whether an accommodation is reasonable.
Judging what counts as an undue hardship.
Confirming an interview with a candidate.
Automation boundaryAgent acts unaided
✓Draft the invitation and stamp the day it went.
✓Record the message as written and not the classification given to it.
✓Escalate a possible accommodation request to the named coordinator.
✓Hold the booking open while a request is unresolved.
No interview is confirmed except by a named coordinator, inside the agreed boundaries.
Ruling that a message is only a scheduling preference.
Telling a candidate what the process can accommodate.
Approving the slot set a candidate is offered.
Changes to the calendar, the record or the routing rules.
Example output
One scheduling thread, annotated
This serves a recruiting team who may have to account for one candidate message to an agency many months after it arrived; below is one thread exactly as the agent leaves it.
Scheduling thread · single candidateIllustrative example
Message
Classed as
Requisition
Evidence of record
Confidence
Held for
Panel interview, stocking role
Read as a possible request
Message kept verbatim
Candidate reply, 3 August 2026
Held unconfirmed
The named coordinator, by name
As receivedBuilt from the candidate reply and the invitation it answered, and it claims nothing beyond them.
What the thread holdsCandidate replyInvitation sentSlots offered
Why no confirmation hereAnswering an accommodation request is a judgement for a coordinator.
ActionConfirmAppend noteSend to coordinator review
What the score decidesBelow the configured threshold a thread gets a coordinator read before a slot moves.
Value
Where AI adds value
The same four claims, placed at the point in the workflow where each one applies.
Where the value landsValue 01 – 04
Each threadFrom the message that carries it
03Evidence
Where the message is used
The agent does not decide what a candidate meant, only what the candidate wrote, when it arrived and which slot moved after it — the record a named human may have to stand behind months later.
01Approved path
It arrived in the wrong box
A candidate may ask in plain English, and the EEOC guidance of 17 October 2002 says the request need not mention the ADA or use the phrase reasonable accommodation.
02Human review
What was checked, and not found
An eCFR full-text search on 27 August 2026 returns nothing for interview scheduling, for scheduling of interviews or calendar invitation, while reasonable accommodation, job applicant and reschedule return hits, and what answers schedule an interview is food-stamp and visa rules, not employment.
04Build an evidence trail
The message, the slot it concerned and the coordinator who read it stay together.
Integrations
Typical integrations
Five system groups connect to the same agent. Which of them are in scope is decided in discovery.
Applicant tracking systemGreenhouse · Lever · Workday Requisition and candidate records
Calendar and conferencingGoogle · Outlook · Zoom Panel availability and room holds
Candidate messagingEmail · SMS · the candidate portal Replies, follow-ups and free text
Agent
Interview scheduling and coordination
Reads the thread Drafts the invitation Holds for the coordinator
Accommodation and accessInterpreter rosters · access notes Arrangements already on the file
Integration availability depends on the client's existing systems and API access.
Agent controls
Six sorts between the model and the coordinator
Six sorts down one chute, the last the tightest. What lands is set out in the map below.
L6 · Outermost — last line of defenceInward → L1 · closest to the model
L6Rollback / safe modeNarrow the agent to invitation drafting when evaluation or production signals degrade.Roll back
L5Version monitoringTrack model, prompt and classification rules, and note the version each thread was read under.Track
L4TraceabilityRecord each thread, the message as written, the slots offered and each read of the file.Record
L3Coordinator releaseHold the thread for a named coordinator; the hold governs confirmation, not whether the class was right.Gate
L2Topic guardrailsTest each outbound draft against the prohibited-topic list, and refuse a message that reaches for pay history or convictions.Restrict
L1Confidence routingRoute a low-confidence class to a coordinator read before a slot is moved.Require review
Model coreThread read — the message, the class assigned, the slots offered and the invitation behind them
L1 – L2Test whether a thread may move
L3Leaves the answer to a named coordinator
L4 – L5Keep the slot and the message behind it
L6Routes the thread to a coordinator when signals degrade
How Nestack evaluates it
Evaluate the whole thread — not only the invitation that goes out.
Coverage runs the whole depth of the workflow, and every layer is cut by slice.
Surface — the invitation a candidate opens
Depth of coverage ▼
E1Final-output evaluationDid the invitation carry the accommodation question it is permitted to ask?
E2Step-level evaluationDid the agent read the reply, the thread behind it and the live requisition?
E3Tool evaluationDid it move the correct event on the correct calendar?
E4Confidence calibrationDo low-confidence classes actually attract more coordinator corrections?
E5Slice evaluationHow does performance change across specific reply types?
E6Business outcomeHow many threads needed a correction before the coordinator confirmed?
Floor — the message a thread rests on
Failure modes
Where each failure originates in the agent
Seven failure modes, set at the stage where each first becomes visible.
Agent lifecycleDirection of processing →
01 · Retrieval1 mode
UC-07
Booking page unusable
The handoff page cannot be driven, and silence follows.
Stage gathersThe panel, the rooms, the thread and the reply
02 · Reasoning2 modes
UC-01
Request read as a reschedule
A legal request is filed as a change of time.
UC-04
Slot set that quietly selects
Neutral filters narrow who can attend at all.
Stage proposesThe message, the class and the slots offered
03 · Tool / write2 modes
UC-03
Prohibited topic raised
The thread reaches for pay or conviction history.
UC-05
Recorder without all-party consent
A panel is captured before each party agreed.
Stage writesOnly where write access and approval policy allow it
04 · Output1 mode
UC-02
Acknowledged, then dropped
The escalation has no owner and the thread ends.
Stage returnsThe invitation a candidate opens and answers
05 · Change / Version1 mode
UC-06
Retention on one default
One setting deletes what another rule requires kept.
Stage tracksModel, prompt, routing rules and hold periods
Sev-1 · a request answered as a rescheduleSev-2 · an escalation nobody ownsSev-3 · a thread held back for a read
A thread-level accuracy figure can read clean while free-text accommodation replies carry most of the correction. Nestack reports the correction rate by reply type, and not only in total.
Slice performance — reported separately, not only in aggregateIllustrative example
Slice
Failure rate
Lift
Lift vs. threshold
Status
Free-text accommodation replies
11.5%
3.7×
Review
Multi-state panel threads
8.1%
2.6×
Review
Reschedule-and-follow-up threads
5.1%
1.6×
Watch
Plain confirmation replies
2.3%
0.7×
Normal
Bar: correction-rate lift vs. plain-confirmation baseline · scale 0–4.0× · tick marks the 2.0× review threshold2 of 4 slices over threshold
Evidence-linked improvement
What a dropped follow-up costs
A cycle ends when the request answered as a reschedule is a standing case. That suite is what the next panel booked is measured against.
Improvement cycle · five stagesSwitchback — the path turns at Improve and returns at Learn
01Detect
Correction rate rises on free-text accommodation replies.
02Diagnose
The interview that never happened, because somebody said she would look into the interpreter and then did not, is worked backwards until one cause is left standing.
03Improve
Invitations go out numbered, and the threads behind them travel attached.
04Verify
A single unread request case stops the whole panel confirming.
05Learn
The case stays on, and the routing rules are redrawn beside it.
Learn → DetectThe return edge. The next panel booked is measured against a suite one case longer.
Typical build scope
Twelve workstreams across six weeks
The build scope read against the delivery timeline. Week structure follows the six-week plan — discovery, sources, thread handling, evaluation, integration, then production validation and handover.
WorkstreamWeek 1Week 2Week 3Week 4Week 5Week 6
01Automation-boundary work and escalation routing rules.
02Calendar, tracker and messaging sources.
03Reply-classification and thread-coverage mapping work.
04Candidate thread ingestion.
05Thread, slot and requisition binding.
06Request flagging and review routing.
07Coordinator confirmation workflow.
08Applicant-tracking integration.
09Request and follow-up cases.
10Guardrails and invitation controls.
11Thread-trail instrumentation.
12Deployment, documentation and Agent Care handover.
12 workstreams · 6 weeks · bar shows the weeks a workstream is active — several run in parallelFinal scope and sequence confirmed in discovery
Engagement tiers
What each tier includes
Rows are the capabilities named in each tier's scope. Higher tiers include everything below them.
Capability✓ in scope · — not at this tierPilotOne requisition, one cycleProductionProduction recruiting workflowAdvancedMultiple requisitions / regions
Introduced at Pilot
Invitation drafting to your templates✓✓✓
Named coordinator confirmation✓✓✓
Panel-availability baseline✓✓✓
Introduced at Production
Reporting by request class—✓✓
Coordinator review workflow in your systems—✓✓
Approved calendar write-back—✓✓
Calendar-and-tracker integration—✓✓
Introduced at Advanced
Multi-jurisdiction rule sets——✓
Cross-panel interview packs——✓
Large candidate volumes——✓
Multi-panel coordination controls——✓
Build priceFrom $5,000From $8,000Custom quote
Final build priceConfirmed after discovery based on integrations, workflow complexity, thread volume, approval controls and deployment requirements.
Separate from buildBuild pricing is separate from recurring Agent Care, which covers managed monitoring, evaluations, incidents and verified improvements after launch.
What we need from you
What you bring, and what we build with it
Each input maps to a piece of build scope and a week in the delivery timeline.
You bringWe build with it
01Your live requisitions and the panel behind each one→Thread capture and message retentionWeek 1
02Representative candidate threads and invitations→Source binding, classification logic and the thread baselineWeek 2
03Your interview calendar and the coordinators it names→Escalation mapping, thread binding and the automation boundaryWeek 1
04Access to relevant APIs, feeds or exports→Calendar, tracker and messaging assessment, then integration setupWeek 2
05Threads you would not want read back→Follow-up cases and the evaluation roundWeek 4
06What no invitation may assume→Request flagging, review routing, guardrails and release controlsWeek 3
07A named coordinator who confirms the interview→Release to the named coordinator, then pilot and production validationWeeks 5–6
Nothing else is requiredDeployment, documentation and Agent Care handover are ours.
Delivery timeline
Four phases across six weeks
Widths here track the work and not the grid, which is why one band sits under another in week five.
PhaseW1W2W3W4W5W6
DiscoveryW1
BuildW2 – W3
EvaluateW4 – W5
Pilot & LaunchW5 – W6
Week focusW1Escalation discovery, thread capture and the automation boundaryW2Source integration and the panel-availability baselineW3Reply classification, routing logic and release controlsW4Evaluation suite, request cases and failure-mode testingW5Applicant-tracking integration, pilot threads and targeted correctionsW6One interview cycle run under the recruiting lead, then Agent Care handover
Reading the bandNo bar runs past the weeks its own work is named for, and week five is shared on purpose.
At the end of W6When the thread record validates, Agent Care assumes the agent.
DurationSix-week plan shown · typical delivery 4–6 weeks depending on scope confirmed in discovery.
Next step · HR AI agent
Build an interview scheduling agent around the sentence your last thread never kept.
Show us one requisition you schedule each month and the replies the last panel produced. If a candidate asked for something in plain words and the only trace is a moved calendar entry, the record an agency would ask for may not exist. A dropped follow-up comes back as a finding.
