Troubleshoot appointment timezone and date display
Resolve appointments appearing on the wrong day or time across staff, client, calendar, reminder and report views. The guide then takes you through the correct route, the checks to complete before making changes, the workflow in order, and the evidence to review afterwards.
What you’ll accomplish
Resolve appointments appearing on the wrong day or time across staff, client, calendar, reminder and report views. It uses Britixo's permission-aware appointment, availability, status and integration flow rather than an unconnected diary entry.
How the module flow works
Appointment date/time is interpreted with stored timezone and CRM/server context.
Google, Outlook and ICS receive timezone data and may display according to the calendar user's local settings.
Cron reminders and date-based filters rely on server processing boundaries.
Follow these steps
- Record the appointment's stored date, time and timezone.
- Compare CRM, server, staff and customer timezone settings.
- Check remote calendar event timezone.
- Check daylight-saving status.
- Correct the appointment through Edit and retest reminders/reports.
Fields and decisions to review
How to confirm it worked
After this workflow completes, Britixo keeps the appointment and its supported relationships connected. Reopen the appointment and verify the saved status, date, timezone, customer or lead, service, provider, attendees, reminder state, calendar or meeting reference, invoice reference and history that apply to this feature. External email, SMS, Google, Microsoft or payment outcomes must be checked separately from the Britixo database save.
- Open the saved appointment and confirm the final status and source.
- Check the participant, provider, timing and timezone from the full detail page.
- Review the relevant table filter, calendar, history, report or linked invoice instead of relying only on a success message.
Controls, checks and common mistakes
- Do not manually offset the time to compensate for a configuration error.
- Test around daylight-saving transitions.
- Use a fresh ICS or remote update after correction.
- Use the least destructive correction and retain the appointment history when the booking existed operationally.
- Never bypass a permission, availability, approval, client-access or verification control by changing an unrelated route or setting.
