A meeting across time zones is booked only when the prospect can see and use the slot you intend. Start with the prospect's location, compare local working hours, and inspect the invitation from the recipient's side. When a scheduler shows the seller's zone, the prospect can choose an inconvenient time, skip the meeting, or lose trust before it begins.1 Treat the time zone as booking data from the start. Use this operating rule: locate, compare, display, confirm.
Establish the locations
Get a location you can check before offering a slot. A country alone may leave too much room for error, especially when the prospect works remotely or moves between offices.
Ask, "What time zone are you in, and what three times work for you in your calendar this week?"2
Capture the region and time zone in the contact record for meeting logistics.3 Enter the cities for everyone involved in the meeting.4 If you are checking manually, open the meeting planner and enter the meeting date and locations involved.5
Keep the prospect's stated location beside the booking record so you can compare it with the scheduler's display when creating the meeting.
Compare the shared window
Test each candidate slot against every participant's local day. A seller-side view can make a workable time look acceptable while placing the prospect outside their normal hours.
A timetable can show each hour as a row and each city as a column.6 Use its traffic light view to identify the best times.7 Scan for rows with the most green and yellow.8 Green means the time falls within standard 8 a.m. to 5 p.m. business hours.9 Yellow means the time is outside normal work hours while still within waking hours.10 Red means most people are likely to be asleep.11 Avoid red slots.12
Use green as the normal choice. Offer a yellow slot only when the prospect has accepted the inconvenience or when the available window leaves no better option. If every slot creates a burden for one person, surface that constraint before booking and agree who will carry it.
Google Calendar lets users toggle on time zones for other locations.13 When scheduling an event, it shows the meeting start time in other time zones, which helps expose an invitation that would land at an unreasonable hour.14
Show the prospect's time zone
The booking page should remove mental conversion from the prospect's task. The time shown at selection should be the time the prospect expects to see on their own calendar.
A scheduling page's available times can appear according to the contact's time zone settings.15 Set that display before sending the link, then open the page as the prospect would and check the visible zone. If the meeting is in person, lock the time zone to the event location.16
Keep the page display and the final event consistent so the prospect sees their local time at both points.
Confirm the invitation
The last check happens after the slot is chosen and before the invitation is sent. Read the event from the recipient's point of view, including the date, local time, time zone, and meeting link.
E-calendars automatically update the meeting time and time zone to match attendees' locations.17 Time zone scheduling errors still occur widely, especially among companies with international teams.18 Send the invitation in the recipient's time zone.19
Compare the event once on the seller's calendar and once in the recipient's local time. If either view looks surprising, stop the send and correct the event. A short confirmation can also state the local time zone in plain language so the prospect has a reference outside the calendar interface.
Handle recurring and unusual schedules
A single meeting needs a correct conversion. A recurring meeting needs a rule for sharing the inconvenience when no time works well for everyone.
Rotate meeting time zones so people who work away from headquarters do not always adapt to headquarters time.20 Remote sessions may take place outside typical business hours depending on the participant's local time zone.21 When that happens, name the local hour directly and get agreement before creating the series.
What not to do
- Do not use a state field as a universal time zone source; automatic calculation from state is supported only within the United States or Canada.22
- Do not assume automatic calculation has run when a manual time zone is already stored; it occurs only when there is no previous manually set time zone value.23
- Do not book on your own clock without translating it, because a 10 a.m. booking in New York for a California prospect becomes 7 a.m. locally.24