← All tutorials
Sales automation

Booking: 30-min Product Demo, Sales Call, or Onboarding

Answer: Booking is LeadFlow’s own slots (30-min Product Demo, 45-min Sales Call, 60-min Onboarding). Taken slots return a conflict notice. Every booking becomes a lead — not a generic scheduler for your customers’ calendars.

Hardcoded LeadFlow slots — 30-min Product Demo, 45-min Sales Call, 60-min Onboarding. Taken slots return a conflict notice. Every booking becomes a lead.

The Booking view is LeadFlow’s own scheduling page — 30-min Product Demo, 45-min Sales Call, or 60-min Onboarding. Choose a topic and pick an available time slot — each booking creates a lead, a meeting activity, a Jitsi room, and a calendar file (.ics). It is not a generic scheduler you hand to customers for their own calendars.

Pick a topic and time

  1. 1Open the Booking view.
  2. 2Choose a topic: Product Demo (30 min), Sales Call (45 min), or Onboarding (60 min).
  3. 3Pick a date — only upcoming business days are offered; weekends are not listed.
  4. 4Pick a time from the available slots (09:00–16:30).
  5. 5Enter name, email, and optional notes, then confirm. That creates a LeadFlow lead — it is not a slot on the visitor's own calendar.

Taken slots return a conflict notice

Taken slots on the calendar are disabled. If two people confirm the same slot, the second request gets a 409: “That time slot is already booked. Please choose another.”

Bookings become leads

Every confirmed booking creates a lead record plus a meeting activity on the timeline — so the meeting is already in your pipeline before it happens. LeadFlow also emails a calendar invite with the Jitsi link when email delivery is configured (Resend accepted — not an inbox receipt); otherwise the confirmation screen offers the video link and an .ics download. You can manage and update booking statuses from the view.

Pro tip: LeadFlow’s booking slots are its own (Product Demo, Sales Call, Onboarding) — not a scheduler you paste onto a customer site. See playbooks for the follow-up path after a call.

Next steps