“Call me at nine tomorrow” is incomplete scheduling information when a candidate and recruiter are in different time zones. Resolve the full date and named zone before creating a callback.
Store the intended local time, zone identifier, and resulting absolute instant. Keep the candidate's stated preference so a reviewer can see the original request if daylight-saving rules or travel plans affect interpretation.
Avoid fixed-offset shortcuts
The IANA time-zone database tracks changing local-time rules. Use maintained time-zone support in the implementation instead of assuming one offset applies year-round or that an abbreviation identifies one place.
Ask a focused clarification when the caller says “my time” or uses an ambiguous abbreviation. Confirm whether they mean their current location or the location where they will attend the interview.
Work through a fictional travelling candidate
A candidate usually lives in one city but will be travelling next week. They ask for a callback at nine on Tuesday in their destination's local time. The agent confirms the named destination zone and full date before scheduling.
It reads back the commitment in that local context and records the recruiter-facing conversion. If the candidate later changes travel plans, the request should trigger a reviewed update rather than silently shifting the original instant.
| Time-zone case | Required behavior |
|---|---|
| “Tomorrow at nine” | Full date and zone clarified |
| Ambiguous abbreviation | Named zone or location confirmed |
| Daylight-saving boundary | Current rule-based conversion |
| Candidate travelling | Intended attendance location clarified |
| Calendar update fails | Pending status, no false invitation claim |
Verify the invitation, not only the calculation
Check the created event's instant, displayed zone, candidate contact, recruiter, and vacancy context. Notifications can still contain the wrong wording even when the stored timestamp is correct.
Extra clarification adds a conversational turn but prevents missed callbacks. A fixed-offset implementation is simpler while failing around rule changes and travel. Use tested date handling and include boundary scenarios in verification.
Keep time-zone collection administrative. Limited availability should not become a speculative signal about candidate commitment. Review interview availability intake for the broader workflow boundary.
Questions about time-zone callbacks
Is a city name always enough?
It may resolve the intended zone, but clarify if the location or date remains ambiguous. Avoid guessing from a phone number.
Should confirmations show both zones?
Use a clear candidate-facing local statement and, where useful, the named zone. Staff can receive the corresponding recruiter context separately.
What if the local time is ambiguous or nonexistent?
Use the implementation's tested handling and ask the candidate to choose a valid unambiguous time. Do not silently select an arbitrary interpretation.