Skip to main content

Book calls

Booking runs on a self-hosted Cal.com instance — every booking is a real event, ingested the moment it's made, with automatic reminders.

Ways a call gets booked​

  • A lead books themselves — via the public Book a call page, the "Book a call" CTA on the marketing site, or a booking block on a page generated specifically for them (a /sites/{slug} demo page).
  • You book it manually — directly in Cal.com, or by sending a lead your booking link from anywhere in the app.

Either way, the booking lands in Appointments (/appointments) the moment Cal.com's webhook delivers it — this app never polls Cal.com.

Source attribution​

The Appointments table has a Source column: which of CallHQ's own booking links a lead came through (e.g. a specific generated site), or Direct for a booking made straight through the public page or marketing site with no prior identity attached. This is populated automatically — a booking link tied to a known lead records a hint before handing off to Cal.com, and the webhook picks it back up once the booking lands. There's nothing to configure.

Reminders​

Every booking automatically schedules a confirm touch plus T-24h and T-1h reminders. The Appointments drawer (click View on any row) shows the full reminder timeline for that booking — sent, pending, or superseded (if the booking was rescheduled).

Troubleshooting​

A booking never showed up? Check Tools (/tools) for Cal.com's live status first, and confirm the webhook is actually pointed at this app — Cal.com is genuinely live in this deployment, so a missing row is a real delivery problem, not a mock no-op.