Timezones
The part that quietly wastes the most meetings
Most no-shows in international B2B are not people changing their mind. They are people
who wrote down the wrong hour. Someone proposes “3pm”, the other side reads it
in their own timezone, and a discovery call evaporates.
ScheduleMeeting never shows a bare time. Internally every booking is a UTC instant. On
the way out it is converted to whoever is looking (the invitee on the booking page,
the host in the dashboard, each recipient in their email), and the timezone name is
printed next to it every single time.
On first visit a booking page reads the visitor's timezone from their browser and reloads
into it, so the very first calendar they see is already correct. If they are travelling,
or booking on behalf of a colleague elsewhere, a selector covering every IANA timezone
lets them switch, and the whole month recalculates.
Daylight saving is handled by the same mechanism rather than by arithmetic. Because the
stored instant is absolute and conversion happens at render time, a meeting booked before
a DST change still resolves to the right local hour after it.