DEV Community

Michael Lip
Michael Lip

Posted on Originally published at tg.zovo.one

Stop Asking '3pm Where?': A Timezone Converter That Lives in Your Telegram Group

Coordinating a meeting time in a distributed group follows the same script every time: someone says "let's do 3pm tomorrow", someone in Tokyo asks "3pm where?", a screenshot of a world-clock app gets pasted, and it turns out to be wrong because daylight saving moved the offsets last weekend. The information everyone needs is one conversion away, yet the group keeps redoing it by hand.

This post is a practical walkthrough of our Telegram timezone converter guide — how to set it up once with WhenIsItBot so the whole chat stops asking "what time is that for me?".

Step 1: Set your zone once with /tz

Start a DM with @WhenIsItBot and run:

/tz Europe/Warsaw
Enter fullscreen mode Exit fullscreen mode

The bot accepts IANA names (America/New_York), common abbreviations (CET, PST, IST, JST), and raw offsets like +2 or -5:30. It's a one-time setup per account — every later conversion reuses it. Ask each member of the group to spend the ten seconds it takes to do this.

Step 2: Convert for the whole group with /when

Once members have set their zones, add the bot to the group and type:

/when 3pm tomorrow
Enter fullscreen mode Exit fullscreen mode

The bot replies with a card showing that time in every distinct zone set by group members, plus UTC — deduped, up to 12 zones. Crucially, "3pm" is interpreted in your zone, so everyone sees their own local equivalent without doing any math. DST offsets are computed live at query time, so the card stays correct across daylight-saving transitions — the failure mode that sinks pasted world-clock screenshots.

Step 3: Convert in chats where you can't add a bot

Type @WhenIsItBot 3pm tomorrow in any chat's message box and you get a one-off conversion card via inline mode — your zone, UTC, and a default set (New York, London, Tokyo). No bot membership, no admin permissions needed. This is the right move in big channels where adding a bot isn't an option, or in one-off DMs.

Step 4: Quick "is everyone awake?" check with /now

Run /now in the group for the current time in every member zone plus UTC. Before you ping a deadline reminder, this tells you whether it's 2am in Tokyo. It pairs well with recurring reminders in a group: schedule the reminder at a time the /now card confirms is sane for every zone.

Step 5: Save the zones you actually use

If you always coordinate with people in Tokyo and Warsaw, don't retype them: /preset add Asia/Tokyo. Free accounts get 3 presets; Pro users' inline results pull from their saved presets instead of the default city set, so a one-off conversion in an unrelated chat still shows the zones you care about.

How this fits into distributed-team workflows

  • Async standups: posting your update once a day removes most live coordination, but the handoff moment still matters. Combining an async standup bot with /when pins the handoff hour in everyone's local time.
  • Cross-zone standups: if you still run live standups, the standup-across-time-zones playbook covers rotation schemes; /when is the tool that makes the rotation visible in chat.
  • General reminders: timezone math is just one of the jobs a group bot can do — see the full bot guides collection for RSVPs, split bills, habits, and more.

Takeaway

Stop pasting world-clock screenshots. Each member sets a zone once with /tz, and from then on /when 3pm tomorrow answers the question for everyone at once, DST included. For chats where you can't add the bot, the inline @WhenIsItBot 3pm card covers you. The full Telegram timezone converter guide has the Pro /team presets and free-tier limits if you need to go deeper.

Top comments (0)