Practical guide

Make the appointment timezone unmistakable

Last materially reviewed 2026-09-23

Quick answerConfirm which timezone the customer sees and which timezone staff use before relying on matching clock times.
What to know

A clock time needs a location in time

A displayed 10:00 is ambiguous when the customer and provider are in different timezones. Decide whether a service is location-bound or remote and make the displayed timezone clear. Even a local appointment can be booked by someone traveling. Do not assume a browser’s current location matches where the customer will be on the appointment date. A calendar label should help people understand the commitment rather than make them perform an unstated conversion.

What to know

Compare the relevant settings

Trafft documents timezone controls for employees and booking-page display. Inspect the combination used by your actual configuration. A correct business timezone does not by itself prove every customer-facing message uses the same display convention. Review the booking page, confirmation and calendar invitation together. This guide does not claim a particular default is appropriate for every account; the required outcome is agreement about the same instant.

What to know

Use dates around a clock change

Prepare fictional appointments on ordinary dates and around a daylight-saving transition relevant to your audience. Compare the intended local time with the displayed customer and staff times. Avoid publishing a conversion formula that assumes every country changes clocks on the same date. These are acceptance-test suggestions, not timezone database guarantees. If an ambiguous or nonexistent local time appears, investigate it before allowing customers to rely on the slot.

What to know

Keep the explanation visible

Use plain wording such as the named business timezone where that is the chosen convention. Do not hide essential timing information in a long policy page. When rescheduling, repeat the date and timezone rather than sending only a new clock time. If your service crosses several regions, include a manual review route for unresolved cases. A missed appointment caused by unclear time display is an operational problem even when the underlying timestamp is technically valid.

Continue when useful

Next: A booking collision test you can explain to the team

Test the last available resource and a non-conflicting request; accepting everything and blocking everything are both failures.

Open A booking collision test you can explain to the team →

Sources used for this page

These records support the facts and comparisons above. Merchant-controlled records are labelled so you can separate product claims from independent evidence.

  1. Trafft booking settings — Merchant documentation · trafft.com · Merchant-controlled · checked 2026-09-23
  2. Trafft employee configuration — Merchant documentation · trafft.com · Merchant-controlled · checked 2026-09-23