Skip to content

Booking time appears incorrectly

Updated November 1, 2026 · 3 min read

A wrong booking time is usually a time zone mismatch between your schedule, the buyer's browser, an outside calendar, a daylight-saving change or an old confirmation. Convert each time to UTC and compare before you edit anything.

On this page

Gather the facts first

  • Booking reference, the chosen date and time, your time zone, the buyer's, and the device or browser zone.
  • The time shown in the public picker, the Tapmy record, your calendar and the notification.
  • Do not reschedule or ask the buyer to pay again until you know which record is correct.
  • Hide private calendar titles, attendees and meeting links.

How do I find out why the time is wrong?

  1. Convert to UTC. Turn both local times into UTC using the actual date, since daylight-saving offsets change.
  2. Check your schedule zone. The right local hour saved under the wrong zone shifts every slot.
  3. Check the buyer's setup. Compare browser, device and network time zones. In-app browsers can differ from the main one.
  4. Check connected calendars. Look at the calendar's time zone, the event start, sync direction, duplicate events and whether that calendar is the source of truth.
  5. Check messages. Compare confirmation and reminder times with the live booking. Queued notifications can keep a pre-reschedule time.
  6. Fix the proven source, then retest. Change only what you proved was wrong. View the same slot signed out on another device and send the buyer one clear correction.

What a good result looks like

  • The public picker, the Tapmy booking, your calendar and the buyer's confirmation all show the same moment.
  • You and the buyer each see a clear local time with the zone.
  • The fix creates no duplicate booking or payment.
  • Future slots follow the right daylight-saving offset.

Reading the pattern

  • Off by exactly one hour. Suspect daylight saving and date-specific offsets before adjusting by hand.
  • Off by several hours. Look for a wrong regional zone, browser detection or a calendar setting.
  • Only reminders are wrong. The booking may be right while queued or cached messages are stale.
  • Only one device is wrong. Check its clock, time zone, in-app browser, VPN, locale and cache.

What to note for support

Record every displayed time and named zone, the UTC equivalents and offsets, the date, device zone, Tapmy and calendar references, notification times, integration status and which source you corrected.

Next steps

Run a test booking and a reschedule across two time zones. If it still looks wrong, contact Tapmy Support with the booking URL, safe references, the exact time and time zone, your browser and device, and expected versus actual result. Never share private calendar content, meeting secrets, passwords, codes or card data.