Shift availability is time-bound information, not a general statement that a worker accepts every future assignment. The receptionist should capture the relevant dates, location, role context, and candidate's stated limits accurately.
Define whether the workflow updates availability, collects interest, or accepts a specific offered assignment. Those are different actions. Do not let a generic “available” answer become an automatic placement or employment decision.
Keep each availability statement scoped
Record effective dates, days and windows, intended time zone, location flexibility, relevant role or client context, and when staff should reconfirm. Ask only approved administrative questions and avoid collecting personal explanations for unavailable times unless the process genuinely requires them.
If the candidate changes one date, update that portion rather than replacing the entire availability profile. Preserve the source and timestamp so recruiters know how current the statement is.
Work through a fictional weekly update
A worker says they can take evening shifts next week but cannot work Friday. The agency serves two client sites, and travel flexibility differs. The agent clarifies the intended site context and records the stated windows.
It does not assign a Friday shift, infer permanent evening availability, or treat a declined site as a negative suitability signal. A recruiter reviews actual assignments through the approved process.
| Availability update | Required handling |
|---|---|
| One-week window | Effective dates stored |
| Exception on one day | Exception preserved explicitly |
| Several sites | Site preference or flexibility scoped |
| Shift offered separately | Acceptance distinguished from availability |
| Conflicting old profile | Staff review or approved replacement rule |
Verify downstream updates
Check the actual destination field or note and any recruiter task. A call summary alone may not update the system used to plan shifts. Keep write outcomes separate from the candidate's statement, especially after a timeout.
Structured windows improve matching but can oversimplify nuanced answers. A short note for exceptions may be useful alongside structured values. The organization should review how downstream systems use availability so an administrative update does not silently change hiring or assignment status.
Test overnight shifts, local-date changes, and candidates correcting an answer. Review time-zone callbacks for date and zone handling.
Questions about staffing availability
Does stating availability accept a shift?
Not automatically. A specific assignment needs its own approved offer and acceptance process.
Can the agent ask why a shift is unavailable?
Use only approved necessary questions. Workable alternatives are often enough for scheduling.
What should recruiters receive?
The exact scoped availability, exceptions, effective period, relevant client or role context, source time, unresolved questions, and any failed update requiring action.