Internal Comms & Meetings

How to schedule meetings across timezones with AI

Internal Comms & Meetings3 AI tools7 steps6 friction points

Want an agent to handle this on your live data? See the Starch version →

Scheduling meetings across timezones is a coordination tax that compounds fast. When your team spans San Francisco, London, and Singapore, or you're booking calls with investors and partners scattered across multiple regions, every meeting involves at least one person doing timezone math in their head, someone double-checking a world clock, and a few back-and-forth emails before a time slot lands. It's not complex work, but it's relentless and error-prone.

The workflow feels like an AI problem because the hard part is arithmetic and pattern-matching, not judgment. Converting 9am PST to CET, finding overlap between three people's working hours, drafting a polite 'does this work for you?' message — all of that looks like exactly what an LLM should handle instantly. Add calendar management and email threading and you have a workflow that operators spend real time on every week.

ChatGPT, Claude, and Gemini can meaningfully help here today. They're fast at timezone conversions, good at drafting scheduling emails, and can reason about working-hour overlap when you give them the right inputs. The ceiling is that they have no connection to your actual calendar, inbox, or the other person's availability — so the heavy lifting stays with you.

Skip the manual work → See the Starch version

Internal Comms & Meetings3 AI tools7 steps6 friction points

AI walkthrough

How to do it with AI today

A practical walkthrough using ChatGPT, Claude, and other off-the-shelf LLMs — what they're good at, what you'll have to do by hand.

Tools that work for this

ChatGPTClaudeGemini

Step-by-step

1 Open ChatGPT or Claude and paste in the attendee list with each person's city or timezone offset — this is the raw input the model needs to do useful work.

2 Ask the model to identify overlapping working hours across all timezones, specifying what counts as 'working hours' for each region (e.g., 9am–6pm local time).

3 Ask it to output a table of candidate meeting windows showing the local time for each attendee — this gives you something you can read at a glance instead of doing the mental conversion yourself.

4 Paste the overlap windows back in and ask the model to draft a scheduling email proposing 2–3 specific options, including the local time for each recipient so they don't have to convert.

5 When a time is confirmed, ask the model to write the calendar invite description, including the timezone-explicit start time for each attendee and a link to a world clock if you want one.

6 If the first round of options doesn't work, paste the constraints into the same thread and ask for the next-best windows given the new restrictions.

7 Use Gemini if you're deep in Google Workspace — it integrates with Gmail and Calendar more tightly than the others, though it still won't read the other attendees' actual availability.

Prompts you can copy

My team is in San Francisco (PST), London (GMT), and Singapore (SGT). Find working-hour overlap windows this week assuming 9am–6pm local time for each. Show each window in all three local times.

Draft a scheduling email proposing three meeting times for next Tuesday–Thursday. I'm in New York (EST), the recipient is in Berlin (CET). Include local times for both of us in each option. Keep it under 100 words.

We need a 45-minute call between someone in Tokyo (JST) and someone in Chicago (CST) during normal business hours. What days and times work next week? Show me the top three options with both local times.

The 3pm GMT slot didn't work. The Chicago attendee can't do before 10am CST. What's the next-best overlap window for GMT, CST, and IST given 9am–6pm working hours?

Write a calendar invite description for a meeting at 10am PST / 1pm EST / 6pm GMT / 7pm CET. Include a sentence with all four local times so every attendee can confirm they have the right time.

Reality check

Where this gets hard

The walkthrough above works — until your numbers change, the LLM hallucinates, or you have to re-paste everything next month.

No connection to your actual calendar — you have to manually check your availability and everyone else's, then paste the constraints in yourself every time.

The model doesn't know when the other person is free, only when their timezone says it's business hours. You still need the back-and-forth to confirm a slot.

Nothing persists between scheduling conversations — next week you're re-explaining your team's timezones and working-hour preferences from scratch.

Drafts need manual copying into Gmail or Outlook; there's no handoff from the LLM to your inbox, so you're still doing the paste-and-send step every time.

Timezone edge cases (daylight saving transitions, half-hour offsets like IST or NPT, regional variations) can trip up models if you're not specific — outputs need a sanity check before you send.

If you're coordinating recurring meetings across a rotating attendee list, there's no memory of prior decisions, no pattern learning, and no way to automate the cadence — it's a manual prompt run every single time.

Tired of the friction?

Starch runs the whole workflow on live data — no copy-paste, no hallucinated numbers, no re-prompting next month.

See the Starch version →

Starch alternative

The same workflow on Starch

Starch is an agentic operating system — it lets an agent build persistent apps and automations connected to your live calendar and inbox, so scheduling across timezones stops being a manual prompt-and-paste workflow and becomes something that just runs.

The Scheduling app connects directly to your Google Calendar and syncs your real availability — attendees see your actual open slots in their local timezone, not a manually curated list you typed into a prompt.

The Email Triage app (called Email Agent in the App Store) reads your inbox on a schedule and can draft timezone-aware scheduling replies automatically — you review and send, instead of writing from scratch each time.

Describe a scheduling automation in plain English — for example, 'when I get a meeting request from a contact outside the US, draft a reply proposing three overlap windows based on my current calendar availability' — and Starch builds it.

Meeting Notes captures and transcribes each call once it's booked, auto-assigns action items, and archives everything searchably — so the scheduling work you did to get people on a call isn't wasted when the conversation ends.

Connect Google Calendar and Calendly from Starch's integration catalog; Starch syncs both on a schedule so any app or automation you build always reflects current data, not a snapshot you copied last Tuesday.

Build a team timezone dashboard by describing it: 'Show me a view of my team's local times updated in real time, with my next three meetings and what time they land for each attendee.' Starch builds that surface — you don't rebuild it each Monday.

Get closed-beta access →

Toolkit