Working Across Time Zones? Your Reminders Now Adapt Automatically
The Timezone Problem
Every reminder tool has a timezone problem. You set a reminder for "9am" — but 9am where? On the device you're holding right now? At home when you travel? UTC?
Most apps solve this by anchoring to your device timezone, which breaks the moment you cross a timezone boundary. Your reminder fires at 9am local, which is now 3am back home — or vice versa.
NagMeLater stores your timezone in your profile. Every reminder you set is interpreted in that timezone, regardless of where the server is running or where your device happens to be right now.
How Auto-Detection Works
When you first message NagMeLater, it guesses your timezone from your phone number's country code:
- +91 (India) → IST (UTC+5:30)
- +1 (US/Canada) → Eastern Time (UTC-5 / UTC-4)
- +971 (UAE) → Gulf Standard Time (UTC+4)
- +44 (UK) → GMT / BST
- +65 (Singapore) → SGT (UTC+8)
This works correctly for the vast majority of users. If it's wrong — or if you're in a country with multiple timezones — override it manually.
Setting Your Timezone
Send any of these to set your timezone:
City names, common aliases (Pacific, Eastern, IST, GMT), and IANA timezone identifiers (e.g. America/Chicago, Asia/Kolkata) all work. Once set, every future reminder uses this timezone automatically.
No app, no account. Save the number, send a message, done.
When You Travel
If you're traveling and want reminders in your destination timezone, update it when you land:
When you return home, update it again: "timezone Mumbai." The change applies to all new reminders — existing ones fire at the time they were originally set (in the timezone that was active when you set them).
Common Timezone Commands by Region
| What you send | Timezone set |
|---|---|
| timezone Mumbai / IST / India | Asia/Kolkata (UTC+5:30) |
| timezone Dubai / UAE | Asia/Dubai (UTC+4) |
| timezone Singapore | Asia/Singapore (UTC+8) |
| timezone London / UK | Europe/London |
| timezone New York / Eastern | America/New_York |
| timezone Pacific / LA | America/Los_Angeles |
| timezone Sydney / AEST | Australia/Sydney |
Frequently Asked Questions
How does NagMeLater know my timezone?
It guesses from your phone number's country code on first contact. Indian numbers (+91) default to IST, UAE numbers (+971) to Gulf Standard Time, and so on. You can override this at any time with 'timezone Mumbai' or any city/zone name.
What if my auto-detected timezone is wrong?
Override it immediately: text 'timezone [your city]' and NagMeLater will update your profile. All future reminders use the new timezone.
Can I set a reminder in a different timezone from my own?
Not directly — reminders are always interpreted in your stored timezone. To set a reminder in a different timezone, switch your timezone first, set the reminder, then switch back.
What happens to recurring reminders when I change timezones?
Existing recurring reminders continue to fire at the UTC time they were originally set. So 'every day at 8am IST' will keep firing at 8am IST (2:30am UTC) even if you switch to London time. Re-set them if you want the local-time to shift.
Does NagMeLater handle daylight saving time?
Yes — IANA timezone identifiers automatically handle daylight saving. If you're in 'America/New_York', the system correctly shifts between EST (UTC-5) and EDT (UTC-4) at the standard DST boundaries.