Skip to content

Eliminate back-and-forth scheduling emails with a timezone-smart assistant

Coordinate multi-attendee meetings across London, New York, and Tokyo while honoring focus blocks, buffer windows, and DST transitions.

Copy the prompt and paste it into the AI assistant you already use.

Rules for a reliable AI scheduling assistant

  1. 01

    Delegate timezone math strictly to IANA code tools

    Never let an LLM calculate UTC offsets in prose—pass explicit IANA identifiers (`America/New_York`, `Europe/London`) into deterministic calendar code.

  2. 02

    Confirm ambiguous city or abbreviation inputs

    Clarify ambiguous labels like `CST` (Central US vs China) or `IST` (India vs Ireland/Israel) cleanly and echo both timezones on confirmation.

  3. 03

    Never leak private calendar event titles externally

    Expose strictly Busy/Free availability blocks to scheduling logic so external guests can never probe why Tuesday 2 PM is unavailable.

  4. 04

    Respect daily energy caps and buffer padding

    Cap external calls at your configured daily max (e.g., 4 calls/day) and enforce 15-minute breathers around long executive reviews.

Questions and answers

Why do so many AI scheduling experiments book meetings an hour off in March or October?

The US and Europe switch Daylight Saving Time on different Sundays in spring and autumn—relying on static `+5 hour` prompt rules fails without IANA calendar libraries.

How do you use an AI scheduling assistant over email without looking rude to VIPs?

Instead of dropping a cold Calendly link on a board member, have the assistant draft three clean personalized slot options directly in your email composer.

What if zero overlapping normal business hours exist across 3 continents?

Propose the least-painful shoulder window (e.g., 07:30 SF / 15:30 London / 23:30 Singapore) transparently and offer rotating fairness for recurring syncs.

Learn more

Related guides and background articles for this task