Calendly Scheduling Basics

Why it matters: Scheduling friction loses leads, and double-bookings lose trust. A thoughtful event type with correct availability, buffers, and questions makes booking effortless.

By the end you can:

• Define an event type's purpose and details
• Set availability, buffers, and notice correctly
• Test the invitee experience across time zones
• Design confirmation and reschedule paths

Learn (15 min)

1. Design the event type (5 min)

An event type is a bookable meeting: name, duration, location (in person, phone, video), description, and booking questions. Write the page so a stranger understands what it is and how to prepare. Example: "20-Minute Headshot Planning Call: we'll confirm team size, location, and timing."

2. Availability, buffers, and conflicts (5 min)

Set working hours that reflect reality. Connect every calendar that can create conflicts. Use buffers around meetings and minimum scheduling notice (e.g., 4 hours) so you aren't booked at the last minute. Test how slots look to an invitee in another time zone, and preview mobile.

3. Routing and confirmation (5 min)

For teams, decide whether bookings go to one host, rotate, or are chosen by the invitee. Ask only questions you need, since each one lowers completion. Customize confirmation and reminder messages, and make cancel/reschedule obvious.

Apply (15 min)

Worked example (3 min). 20-minute intro call. Availability Tue–Thu 10–4 ET. 10-minute buffer after. 4-hour minimum notice. Location: phone. Questions: "Company name" (required), "How many people need headshots?" (required). Confirmation: what to have ready; includes a reschedule link. Calendars connected: work + personal (busy only).

Lab (7 min): Spec an event type.

1. Write the name, description (2 sentences), and duration.
2. Set availability, buffer, minimum notice, and daily cap.
3. Write two booking questions and justify each.
4. Write confirmation text, then list how you'd test a Pacific-time invitee.

Deliverable: An event-type spec. You're done when: Each setting prevents a specific problem you can name.

Check yourself (5 min)

1. What does an event type represent?
2. Why connect calendars?
3. Why test time zones?
4. Scenario: No-shows are high. What two settings or messages would you change?
5. Why limit booking questions?

Reference

Common mistakes

Cheat sheet: Define meeting → set availability → connect calendars → buffers/notice → test invitee flow.

Key terms: event type, availability, buffer, notice, routing.

Interview prompts: How would you design scheduling for a team with different services?

Go deeper: Calendly API introduction · Event types reference · Calendly event-type help

Next: Lesson 26 — syncing Calendly to your CRM.