Skip to main content

Appointments — how this works

In the app: /appointments

How it works

Every row is a real Cal.com booking, ingested via Cal.com's own webhook the moment someone books — this page never polls Cal.com itself. Reminder rows (confirm/T-24/T-1) are scheduled internally off each booking's time.

Data source

src/lib/booking/appointmentsRepo.ts, populated by the Cal.com webhook route.

Troubleshooting

A booking never showed up? Check /tools for Cal.com's live status and confirm the webhook is actually configured to point at this app — Cal.com is genuinely live here, so a missing row is a real delivery problem, not a mock no-op.

Vendors: calcom — check Tools for live/mocked status.

Who can see this: admin, closer, setter