Service Reminders
Connecting

Appointment reminders

Book a vehicle service appointment and follow its reminders, 24 hours and 2 hours before the visit. A customer never receives the same reminder twice: if the service crashes in the middle of a send, the reminder is reclaimed when its lease expires and finished without being sent again.

Book a service appointment

Remind by

Why a reminder can't go out twice

  1. One row per reminder. UNIQUE (appointment, revision, type) on the reminder table.
  2. One worker per attempt. Claimed with FOR UPDATE SKIP LOCKED, leased until processing_until, every write fenced by a claim token.
  3. One hand-off per key. The idempotency key is committed to notification_delivery before the provider is called; a retry finds it and sends nothing.

Reminders by status

last 15 appointments

Service log

live, same lines as the server

No log lines yet. Book an appointment and the create and send lines show up here.

Appointments

refreshes every 2 s
#CustomerAppointmentReminders

No appointments yet. Book one on the left.