A booking page can show the right available slots and still produce the wrong appointment in the customer’s mind. “Tuesday at 3” is incomplete until the page establishes which Tuesday, which time zone and whether the meeting happens online or at a physical venue.
Automatic time-zone detection is useful, but the displayed assumption still needs to be visible. A traveler may be booking for a future location. Someone arranging an appointment for another person may need a different zone from the device they are using.
Treat the time zone as part of the appointment, alongside the date and location. Carry that meaning through selection, confirmation and any later change.
Decide which local time matters
For a virtual sales consultation, showing available times in the invitee’s chosen zone usually makes the choice easier to interpret. The host can see the same instant in their own calendar’s zone.
For an in-person appointment, the venue’s local time is the useful reference. A person booking a London appointment while traveling in New York should be able to understand when to arrive in London. Showing only the current device’s local time can make that decision harder.
Calendly’s time-zone documentation describes automatic invitee-zone detection and a way for invitees to select another zone. It recommends locking in-person event types to the event location’s zone. Those documented options illustrate why the meeting format should guide the display choice.
Name the format before the buyer selects a time. “Video consultation” and “Appointment at our London showroom” tell the customer what kind of time interpretation to expect. A location revealed only after booking can change the practical meaning of the whole offer.
Put the zone beside the available times
Keep the zone label close to the slot list, where the buyer is making the decision. A distant footer label is easy to overlook, especially when a calendar is embedded in a longer service page.
Use a recognizable place or zone name and let the customer inspect or change it where appropriate. A numeric offset can be helpful supporting detail, but it should not be the only clue a nontechnical buyer receives.
When the chosen zone changes, update both the time and the date if necessary. The same appointment can fall on a different calendar day in another location. Preserve the selected appointment only if the interface can make the changed display clear; otherwise ask the buyer to confirm the newly displayed slot.
Avoid showing one zone above the calendar and another beside the final button without explaining the relationship. The customer should not have to perform a conversion to establish what they are agreeing to.
A worked example across a daylight-saving change
Consider a hypothetical virtual consultation held at 3 p.m. London time on three different dates. The following conversions were calculated for the named zones, Europe/London and America/New_York, using their date-specific rules.
| Appointment date in 2026 | London time | New York time |
|---|---|---|
| October 20 | 3 p.m. BST | 10 a.m. EDT |
| October 27 | 3 p.m. GMT | 11 a.m. EDT |
| November 3 | 3 p.m. GMT | 10 a.m. EST |
The middle row is the useful warning. A fixed rule that New York is always five hours behind London would produce the wrong displayed time for that date. The appointment system needs the zone and the appointment date, rather than a permanent offset copied into page text.
These rows are illustrative conversion checks, not a recurring-event policy. A recurring meeting needs an explicit decision about which local time stays fixed as time zones change. A one-off booking page should still calculate each available date correctly.
For an in-person London appointment on October 27, the clearest primary display would remain 3 p.m. at the London venue. An optional New York equivalent can help a traveler plan, but should not displace the time they need when they arrive.
Confirm the complete appointment
Before the final booking action, show the service, full date, time, zone, duration and location or meeting format together. If payment is part of the booking, keep that commitment visible in the same review.
After submission, confirm whether the appointment is booked or merely requested. A service that requires manual acceptance should not use the same final wording as an immediately confirmed appointment.
The GOV.UK confirmation-page pattern recommends explaining the next step and timing, with a reference and contact route. For a booking, apply that principle to the actual appointment: confirm the details that are settled and explain anything the customer is still waiting to receive.
A fictional confirmed video consultation might read: “Your consultation is booked for Tuesday, October 27, 2026, at 11 a.m. New York time. The meeting is online.” The corresponding London view would show the same instant as 3 p.m. The two displays should agree about the appointment even though their clock times differ.
Check the calendar handoff separately
A correct confirmation page does not prove that the calendar event is correct. Inspect the event created by the booking flow and how it appears in the calendar products your customers actually use.
Check the date, start time, end time, location and meeting link. Make sure a calendar invitation does not describe a pending request as a confirmed appointment or retain an old location after the customer changed the meeting type.
Calendly notes that an invitee’s calendar application can display an invitation in UTC when it cannot detect the intended local zone. That is a reason to inspect both the invitation and the readable confirmation, rather than assuming they present identical wording.
Provide a way to recover the appointment details without making the buyer book again. A missed email or unfamiliar calendar display should lead to a status or assistance route, not an unnecessary duplicate reservation.
Preserve the meaning when appointments change
A rescheduling page should identify the current appointment before asking for a replacement. Repeat the zone used for the new slot and make clear when the change is complete.
If the customer switches from a virtual consultation to an in-person visit, revisit the display assumption. The venue’s local time and address become central to the decision. Carrying over a device-local label without explanation can leave the customer with the wrong arrival time.
A location change may also change the zone. Keep the new venue, date and time together, and let the customer inspect them before confirming. The same rule applies when staff change an appointment on the customer’s behalf: the resulting communication needs to describe the actual new arrangement.
Use a small but demanding acceptance set
Review a virtual booking from another zone, an in-person booking made while traveling, a date near a daylight-saving change and a slot whose converted time crosses midnight. Include a manual zone change before submission and a reschedule afterward.
For each case, ask the buyer to explain when and where they will attend. Compare that answer with the stored appointment and the calendar invitation. A correct timestamp alone is insufficient if the page communicates a different local expectation.
The form-optimization guide covers the wider submission journey. Booking pages add one particularly unforgiving detail: a time that looks familiar can still be wrong. Make the zone visible at the decision and preserve it through the handoff to the customer’s calendar.