Verify scheduling before timezone bugs become support tickets.
The appointment is booked—but for the wrong date, time, or timezone.
The problem
The appointment is booked—but for the wrong date, time, or timezone.
When this breaks after deploy, the cost shows up as lost revenue, locked-out users, support load, or silent data mistakes — not as a red unit test in CI.
What can break
- wrong date stored
- wrong time slot
- timezone shift off by hours
- confirmation shows different time than booked
The critical flow
- 1date selection
- 2time selection
- 3event creation
- 4display confirmation
- 5timezone-sensitive fixture
What Endia checks
Date selection
Selected calendar date matches the booking payload
Time selection
Selected slot matches the confirmation time
Event created
Event appears on the calendar after create
Confirmation matches
Confirmation copy matches selected date/time
Timezone fixture
Displayed local time matches the fixture timezone rule
Logical time correct
Stored ISO instant is consistent with the displayed slot
What evidence you get
Screenshots of picker + confirmation, step trace, and the release check result.
How it fits the Vercel preview gate
Protect booking flows on previews where timezone bugs are easy to miss visually.
Try the protected flow (controlled fixture)
Neutral demonstration fixture — not a customer app, not live production data. Walk the flow Endia would record and replay on a Vercel preview.
Fixture timezone: America/Indiana/Indianapolis
Known limitations
- Recurrence is not implemented in this fixture.
- Timezone coverage uses a controlled fixture offset, not every IANA zone.
Protect a flow like this
Sign in to record your critical journey and run it on every Vercel preview.