Integrations

Appointment reminders need cancellation and timezone state before they send

October 14, 2026 · Integrations

A reminder job should not only know that an appointment once existed. It should know whether the event is current, cancelled, rescheduled, moved across timezones or replaced by another booking. Otherwise automation keeps speaking after the calendar has changed.

Original appointment reminder diagram showing event status, timezone, reschedule checks, cancellation suppression and reminder send decision.
Original explanatory illustration created for Quarro, October 14, 2026. · Original PNG diagram authored for this article. No third-party photos, logos, screenshots, fonts, or stock assets embedded.

The answer: remind from current event state

A reminder job should not only know that an appointment once existed. It should know whether the event is current, cancelled, rescheduled, moved across timezones or replaced by another booking. Otherwise automation keeps speaking after the calendar has changed. The result is familiar: customers get a reminder for an appointment they already moved.

Calendars carry more than start time

The Google Calendar API Events reference includes event properties such as status, start and end date-time values, timeZone, recurring event references, updated time and reminders. Those fields are a reminder that appointment automation should read the current event state, not just copy the first start time into a separate queue.

Store a reminder decision, not only a send time

A robust reminder record should point to the event version it checked, the event status, local appointment time, recipient preference and reason the reminder is still eligible. If the event changes after the reminder is queued, the job should recheck before sending.

Handle cancellation and reschedule explicitly

Cancellation should suppress future reminders and optionally send a separate cancellation notice. Reschedule should update the message and avoid sending both the old and new reminder. Recurring appointments need special care because one instance may change while the series remains active.

Test around timezone boundaries

Test daylight saving changes, travel between locations, all-day events, recurring series exceptions and last-minute cancellations. The practical takeaway: reminder automation is a calendar-state workflow. It should send because the appointment is still valid, not because a timer woke up.

Sources