The Core Problem: Times Are Relative, Messages Are Not

Every remote team has a version of this moment: someone proposes "3pm my time" and three people in three countries open a new tab, type their cities into a timezone converter, and try to figure out if that works. Someone gets it wrong. Someone shows up an hour late. Everyone is a little annoyed about something that should be completely automatic.

When you type "3pm Thursday" in a chat, that message doesn't know anyone's timezone. Every scheduling failure on a cross-timezone team traces back to this: the time was stated in one person's frame of reference, and the other person either didn't convert it, converted it incorrectly, or converted it for a different date than intended.

Step 1: Stop Stating Times in Your Timezone

The first instinct — "I'll just say 3pm EST and they can convert it" — is the source of most scheduling errors. It puts the cognitive load on the recipient and assumes they'll do it correctly, every time, including during DST transitions. Instead, use UTC for technical teams, name every timezone when there are only two parties, or use a tool that shows local times automatically for groups of three or more.

Step 2: Find the Overlap Window First

Before you propose a time, know whether a reasonable overlap exists. London to New York: 2:00 PM to 6:00 PM London (9 AM to 1 PM ET). London to Singapore: 9:00 AM to 11:00 AM London (5 PM to 7 PM SGT). London to Dubai: 9:00 AM to 5:00 PM London (12 PM to 8 PM GST). New York to Los Angeles: 12:00 PM to 6:00 PM ET (9 AM to 3 PM PT). Sydney to London: 7:00 AM to 9:00 AM London (6 PM to 8 PM AEST). Sydney to New York: Very limited — 8 AM to 10 AM ET equals 10 PM to midnight AEST.

Step 3: Propose a Time That Shows Local Times for Everyone

The fastest way to get a "yes" from someone in a different timezone is to show them the time in their timezone in the same message. For email, use a service like timeanddate.com to generate a link that opens in each recipient's local time. For calendar invites, Google Calendar and Outlook both display times in each invitee's local timezone. For WhatsApp, iMessage, or Telegram, this is where most scheduling actually starts, and where native timezone tools don't exist — Wenya is a keyboard that generates scheduling messages directly in chat, showing each person their local time without any app switch.

Step 4: Name the DST Status

Daylight Saving Time changes don't happen on the same date everywhere. The US and UK change clocks within a few weeks of each other but not simultaneously. Australia changes in the opposite season. Some countries — Nigeria, Japan, Singapore, UAE — don't change at all. For any recurring meeting, state DST explicitly when setting it up to prevent months of calendar drift.

Step 5: Confirm With a Local Time, Not a Timezone Label

When someone confirms a meeting, the most common error is confirming the timezone label rather than the actual time. The safest confirmation format: "Confirmed: Thursday 3pm London, 10am New York, 6pm Dubai." Everyone sees their city, their time. No interpretation required.

The Bigger Picture

Cross-timezone scheduling friction is so normalised in remote work that most teams treat it as an unavoidable tax. It isn't. The friction comes from a specific gap: scheduling still starts in chat, but chat has no timezone layer. Wenya is the scheduling keyboard that lives inside WhatsApp, iMessage, and Telegram — so the timezone layer is in the conversation, not in a separate app. Try it at wenyawanna.ai