A customer asks for nine tomorrow morning, but the appointment appears an hour away from their expectation. Storing a timestamp accurately does not help if the application interpreted the wrong local time.
AI booking needs an explicit time zone and a policy for daylight-saving transitions. The model should collect intent; deterministic date-time logic should resolve it.
Preserve the local meaning as well as the instant
Record the requested local date, local time, named time zone, and resolved instant. A fixed UTC offset alone does not describe future daylight-saving behaviour.
Confirm which location the appointment belongs to. A caller's phone number or current travel location is not reliable evidence of the service location's time zone.
| Situation | Clarification or validation |
|---|---|
| “Tomorrow at nine” | Resolve against the correct local date |
| Caller and office differ | State which local time is being offered |
| Clock moves forward | Reject or clarify nonexistent local times |
| Clock moves backward | Resolve ambiguous repeated times explicitly |
These are implementation cases, not a reason to make the conversation recite technical zone identifiers. The customer needs a clear date, time, and location.
Use the scheduler's documented time representation
Google's calendar event concepts distinguishes timed and all-day events. Check your chosen provider's rules for timestamps and time zones rather than passing a natural-language string directly into a write.
Keep relative phrases out of persistent confirmation records. “Next Friday” becomes difficult to interpret after the call, especially near midnight. Save the resolved date and retain the original phrase when useful for investigation.
Treat recurring visits as a separate decision
“Every Tuesday at nine” usually expresses a local scheduling intention. A series built by repeatedly adding fixed hours can drift relative to local clocks when offsets change.
Use a tested recurrence model and define how the business handles holidays and exceptions. The recurring-appointment article covers those choices.
Test the calendar boundary dates
Use fictional appointments around local midnight and both clock-change transitions where applicable. Test a caller abroad, two office locations, and a date corrected halfway through the conversation.
Compare the spoken confirmation, stored event, staff calendar, and reminder. All four should describe the same appointment. A correct backend timestamp can still be displayed incorrectly in a notification template.
Booking time-zone questions
Should every appointment be displayed in UTC?
Use storage and display rules appropriate to the application, while making the customer's local appointment clear.
Can an offset replace a named zone?
It may identify one instant's offset, but it does not encode future regional clock rules.
What should a pilot include?
Include a cross-zone caller and relevant boundary dates in the acceptance checklist.