Booking page showing the wrong time zone? How to fix it
On this page
Why is my booking page showing the wrong time zone?
The displayed guest zone may differ from the zone you intended, or the host schedule may interpret weekly hours in a different location. Identify which one is wrong. Two different local clock readings can also describe the same appointment correctly, so don't change offered hours until you've compared the dated instant.
You'll need the event URL, the selected date and zone, and the schedule attached to that event. The cross-time-zone scheduling guide explains the general model; this page isolates a display or setup mismatch.
We initialise the guest display using the browser's reported time zone. The guest can select another zone on the booking page, so the browser's first choice isn't the only one available.
If you searched for "Calendly wrong time zone", the diagnostic distinction still helps, but this page describes our implementation. We haven't verified Calendly's current time-zone settings in the supplied research.
Which zone controls the hours I offer?
The event's assigned schedule determines how its weekly hours are interpreted. Check that schedule using the Availability button beside + Create on the Events page. A guest display setting translates the resulting appointment times; it doesn't redefine which local workday the host intended to offer in the first place. For a conversation spanning dated San Francisco and Berlin hours, check the shared workday before repeating a familiar start in another season.
For example, a schedule offering 09:00 to 12:00 in Asia/Karachi describes a Karachi morning. Selecting Europe/London as the guest display doesn't turn the offer into a London morning; the corresponding local times are earlier.
| Place to check | Job | Error it can explain |
|---|---|---|
| Assigned schedule's zone | Interprets weekly availability | Host hours were entered for the wrong location |
| Guest page's selected zone | Displays candidate times to the visitor | Visitor sees an unexpected local clock |
| Calendar application's display | Shows the resulting appointment | Calendar view differs from guest display |
| Appointment date | Determines the applicable zone rules | Comparing two different occurrences |
We store the schedule zone with its hours. If you have several schedules, inspect the one the event uses instead of editing a similarly named schedule that isn't assigned to it.
Can different dates and times describe the same booking?
Yes. A conversion can cross midnight, so the same appointment can appear on two calendar dates. Include the date. When you compare "09:00" and "23:00" without including their named zones and calendar dates, a correct conversion can look like a fourteen-hour scheduling error.
The following values were computed with Luxon from 2026-11-17 at 09:00 in Asia/Karachi. Each row represents the same instant, using the named IANA zones shown.
| Named zone | Local date | Local time |
|---|---|---|
| Asia/Karachi | 17 November 2026 | 09:00 |
| Europe/London | 17 November 2026 | 04:00 |
| America/New_York | 16 November 2026 | 23:00 |
Method: construct the Karachi date and time in Luxon, then use setZone for London and New York. These are dated conversions, not offsets promised for every day of the year. The New York-to-São Paulo meeting planner compares dated working-hour overlap; confirm individual calendars after choosing a candidate window. For a conversation spanning dated New York and Johannesburg hours, check the shared workday before repeating a familiar start in another season.
The IANA time-zone definition explains why location names are safer than a fixed abbreviation when you're arranging future appointments. Use the actual appointment date when checking a conversion.
We don't infer a guest's location from their email address or the country code of a phone number. Ask them to inspect the visible zone instead of trying to identify their current location from contact details.
Should I change my schedule when I travel?
Change the schedule zone only when you want its weekly hours to follow the new local location. Decide deliberately. If you still intend to offer your normal home-office hours while traveling, changing the zone can change the actual instants those written hours describe.
Suppose the agreement is "available during Karachi office hours". Keep those hours attached to Asia/Karachi and view them in your travel location when planning the day. If the agreement becomes "available during my local morning", edit the schedule accordingly and inspect future dates.
We support multiple schedules and date overrides, which can make a temporary travel pattern clearer than repeatedly altering the normal weekly hours. Confirm which events use the schedule before applying the change.
Don't assume changing offered hours reschedules existing appointments. Review accepted meetings individually; their guests need an explicit arrangement if an agreed time must move.
What if changing the guest zone still shows no times?
Inspect the selected date in the new zone and then check availability rules. A display correction doesn't create a valid appointment. Notice, a booking window or existing conflicts can still exclude every start on that date even after the time-zone label is correct. The San Francisco-to-Tel Aviv meeting planner compares dated working-hour overlap; confirm individual calendars after choosing a candidate window. The San Francisco-to-Singapore meeting planner compares dated working-hour overlap; confirm individual calendars after choosing a candidate window.
Use the empty booking page checklist when the problem is missing choices instead of a shifted clock.
| Symptom | First check | Next action |
|---|---|---|
| All guest times look consistently shifted | Guest selector | Select the intended named zone |
| Host morning appears as the wrong work interval | Assigned schedule zone | Correct the host's intended hours and zone |
| Date differs but instant matches | Midnight conversion | State both dates in messages |
| Only some dates differ by an hour | Date-dependent zone rules | Compare each affected date |
Review Google Calendar time-zone settings if the mismatch is in your calendar display. For the final test, make a 30-minute appointment, inspect its start and end in the host's zone and the guest's zone, and check the date beside each. Cancel the test afterwards.
We translate valid starts for the guest and re-check them at submission. Review the booking account's terms, then create a testable time-zone-aware offer if you're starting a new schedule.
Steps
Record the appointment date and zones
Note the event URL, meeting date, selected guest zone and the schedule zone. Include the date shown beside each clock reading.
Inspect the guest time-zone selector
Choose the intended named zone on the booking page. Refresh the comparison using that zone instead of assuming the browser detected the guest location correctly.
Open Events and choose Availability
Open the schedule assigned to the event and inspect its time-zone field. Weekly hours are interpreted in that schedule zone.
Compare one confirmed appointment
Use the same appointment instant when comparing a booking confirmation and calendar display. Different dates or recurring occurrences are not a valid comparison.
Retest after correcting the right setting
Change the setting responsible for the mismatch, then make one controlled booking. Verify the date and local start at both ends before canceling the test.
Frequently asked questions
Does a client seeing a different clock time mean the booking moved?
No. A single appointment can display different local dates and times in different zones. Compare the dated appointment in both named zones before rescheduling it or changing the host's offered weekly hours. Compare the full date and instant in each zone before changing the appointment, since different local hour labels can describe the same agreed start.
Should I use EST for every meeting with New York?
Choose the named zone America/New_York when you mean New York local time across the year. A fixed abbreviation can describe only one offset, while the location's applicable offset depends on the appointment date. Use America/New_York with the appointment date, especially for a meeting scheduled across the period when that city's abbreviation changes between standard and daylight time.
Why should I test around midnight?
A zone conversion can cross a date boundary even when the appointment is the same instant. Include the calendar date beside the time in your test so an evening on one side isn't mistaken for a different booking the next morning.
Related pages
- How to schedule meetings across time zones
Schedule across time zones with named zones and dated conversions. See Karachi and New York meeting times change across March 2026 daylight saving.
- How to change and show time zones in Google Calendar
Check calendar, event and guest time zones without guessing menu paths. Use a dated London-to-Karachi example to catch booking mistakes.
- What is an IANA time zone (tz database)?
An IANA time zone names local clock rules, such as Europe/London. Compare it with UTC+00:00 and check two dates before setting future availability.
- Why does my booking page show no available times?
Diagnose an empty booking page: schedule, duration, notice, window, conflicts, holidays and vacation. Test one variable without opening your whole day.
- Best time to meet: San Francisco and Tel Aviv (2026)
Compare San Francisco and Tel Aviv: 0 shared office hours, clock changes and ranked meeting windows for 2026.
- Best time to meet: San Francisco and Singapore (2026)
Compare San Francisco and Singapore: 0 shared office hours, clock changes and ranked meeting windows for 2026.
Create your free booking link
Sign in with Google, create an event and share your link.
Create your free link