Loading tutorials…
Loading tutorials…
Calendly has four event types and most teams misuse three of them. This walks through what each one is actually for, the configuration that matters, and the routing logic that turns event types into a real demo-booking engine.
Who this is forSales managers, RevOps, or solo founders who already have Calendly connected and now need to build the right event types for demos, group webinars, executive intros, and round-robin lead distribution.
What you'll need
Step 1
One-on-One = 1 host, 1 invitee. Group = 1 host, N invitees. Collective = N hosts, 1 invitee (must all be free). Round-Robin = pool of hosts, 1 picked per booking.
One-on-One: the default. One host (you or one rep), one invitee. Use for demos with a single rep, discovery calls, intro chats. 80% of Calendly events should be this.
Group: one host, multiple invitees attend the same event. Webinar-style. Use for product webinars, group onboarding sessions, office hours. The slot stays open until cap is reached.
Collective (Teams plan): multiple hosts, one invitee, all hosts must be free at the same time. Use for handoffs where a prospect needs to meet both AE + SE, or AE + CSM. Slots are extremely scarce because all calendars must align.
Round-Robin (Teams plan): a pool of hosts, Calendly picks one per booking based on rules. Use for demo-booking when any of your 3-5 AEs can take the meeting. This is the workhorse for scaling sales teams.
Rule of thumb: if you're confused about which to pick, the answer is almost always One-on-One. Don't reach for Collective or Round-Robin until you have the use case.
Step 2
Most demo bookings are One-on-One. Get the duration, location, questions, and confirmation copy right and you have a template you can clone.
Click "Create" → "One-on-One." Name it something the prospect sees ("Product Demo with Sarah" not "Sarah Demo 30 min v2").
Set duration: 30 min for first demos, 45 min for technical deep-dives, 15 min for intro calls. Don't do 60-min demos unless explicitly a deep-dive — most demos that need 60 minutes should be split into demo + follow-up.
Location: pick the conferencing tool you connected (Zoom/Meet/Teams). For in-person meetings, set "In person" with a default address.
Event link: customize to something readable (`/demo`, `/intro`, not `/30min-meeting-abc123`).
Description: 1-2 sentences setting the agenda. "30-min walkthrough of [product]. Bring a question or use case."
Once dialed in, this becomes your template — clone for variations rather than rebuilding.
Step 3
Add 2-4 questions for high-intent events. Skip questions for low-friction events. Required questions drop booking rate ~5% each.
In the event type → Invitee Questions, add the questions you need to qualify and prep.
Standard set for demos: (1) Company website (required) — auto-fills CRM, (2) Team size or use case (optional) — prep info, (3) "Anything specific you'd like to see?" (optional) — agenda input.
Don't add: "Budget," "Timeline," "Decision authority" — these belong in a routing form (next tutorial), not the booking flow. Asking them at booking drops completion rate 20-30%.
Every required question drops booking-completion rate by ~5%. Be honest about which are truly required.
For low-friction events (15-min intro, customer onboarding), keep it to name + email only.
Step 4
Override the default schedule when an event type needs different hours. Demos = wider hours. Customer calls = narrower. Webinars = fixed times.
In the event type → Availability, you can override the default schedule for this specific event type.
Common pattern: "Demo" event uses wider availability (8 AM-7 PM to catch all time zones), "Customer Success Check-in" uses narrower (10 AM-4 PM local).
Set event-specific buffers if needed: a 60-min strategic call probably needs a 30-min buffer (more prep), while a 15-min intro can have a 5-min buffer.
Daily limit per event type: cap demos at 4/day per rep so they have time for prep + follow-up. The default is unlimited, which leads to back-to-back hell.
Date range: by default, prospects can book up to 60 days out. For demos, narrow this to 14-21 days — meetings booked 6 weeks out have 40%+ no-show rates.
Step 5
Group events let multiple invitees attend the same slot. Set a max-attendees cap and consider whether to require pre-questions.
Create → Group event. Name it ("Product Office Hours," "Onboarding Webinar — Tuesdays").
Set "Max invitees per slot" — 10 for intimate office hours, 100+ for a webinar.
Duration is usually 30-60 min for office hours, 45-60 for webinars.
Set the location: for webinars use a Zoom Webinar account (not regular Zoom — different product), for small office hours Zoom Meeting is fine with "Generate unique URL" turned OFF (everyone joins the same room).
Add a brief description that sets expectations — "Bring questions about [product]. Recorded and sent to attendees."
Step 6
Collective events require all listed hosts to be free at the same time. Slots are scarce — use only for true 2-person meetings.
Create → Collective. Add the hosts (e.g., AE + Solutions Engineer).
Calendly will only show slots where ALL hosts are free simultaneously. Expect 30-50% fewer available slots than a single-host event.
For SaaS B2B demos with a technical evaluation: AE owns the conversation, SE handles deep technical Q&A. Don't default to Collective — only use when the SE genuinely needs to be live.
Confirmation email + calendar invite goes to all hosts. SE will see every meeting on their calendar — set expectations internally about whether they need to attend live or can review the call recording.
Step 7
Round-Robin assigns each booking to one rep from a pool. Use "Maximize availability" for fastest booking; "Optimize for equal distribution" for fair load.
Create → Round-Robin. Add the reps in the pool (e.g., 3-5 AEs). Each rep must have their calendar connected to Calendly.
Pick the assignment logic: "Maximize availability" (Calendly picks the rep with most open slots — fastest booking experience) or "Optimize for equal distribution" (fair load across reps — slower booking).
For inbound demos, "Maximize availability" usually wins — speed-to-meet correlates with conversion. For account-based pools where you want even pipeline distribution, use "Equal distribution."
Set host priority: if you want senior reps to take enterprise deals first, you'd configure that via routing forms (separate tutorial) rather than baking it into Round-Robin logic.
Test by booking 3-5 test slots from different browsers. Verify the rotation is working as expected.
Step 8
Write a one-page internal doc: which event types exist, what each is for, who owns it. Prevents sprawl.
In Notion, Google Doc, or your wiki, create a one-page "Calendly Event Types" doc.
List each event type: name, purpose, who it routes to, link, and "when to use vs. when not to."
Add a rule: "Before creating a new event type, ask in #revops if an existing one works."
Review quarterly. Delete or archive event types that haven't been booked in 90 days.
Common mistakes
One event type per rep instead of one Round-Robin pool
What goes wrong: Marketing has to maintain 5 different demo URLs (one per AE). When a rep leaves or joins, every landing page and email template breaks. Lead distribution becomes manual.
How to avoid: For any pool of reps doing the same job, build ONE Round-Robin event type. Marketing shares one link. Calendly handles distribution.
Using Collective when Round-Robin works
What goes wrong: Available slots crash because every listed host must be free simultaneously. Demos book 2-3 weeks out. Pipeline velocity tanks.
How to avoid: Use Collective only when both people genuinely must be live (e.g., contract negotiation with AE + Legal). For demos with optional SE, do Round-Robin to AE and have AE pull in SE as needed.
No daily limit on demo event types
What goes wrong: Top AE has 9 demos in one day. Quality of every demo drops. Show-rate drops because reminders blur together. No follow-up gets sent. Conversion crashes.
How to avoid: Cap demos at 4-5/day per rep. Use buffers (15 min pre + post) to enforce real prep time.
Demo event types bookable 60 days out
What goes wrong: Prospect books a demo for 5 weeks from now while they're hot. Lead goes cold. They cancel or no-show. You've wasted attribution and follow-up cycles.
How to avoid: Set "Maximum scheduling notice" to 14-21 days for demos. Forces prospects to commit while intent is high.
Required qualifying questions on a low-intent event
What goes wrong: You add "Budget" + "Timeline" + "Decision authority" as required to your demo booking page. Booking-completion rate drops 30-40%. Real buyers bail.
How to avoid: Use a routing form (next tutorial) to qualify BEFORE the booking page. Keep the booking flow itself to 2-3 light questions max.
Event-type naming chaos
What goes wrong: Sales has 23 event types named "30 min meeting," "30 min meeting v2," "Sarah's demo," "Demo (old)," etc. Reps don't know which to share. Marketing links break.
How to avoid: Name event types by audience + duration + purpose: "Inbound Demo (30 min)," "Customer QBR (45 min)," "Partner Intro (15 min)." Archive everything else.
Recap
Done — what's next
How to set up Calendly routing forms (qualify before booking)
Read the next tutorial
Hand it off
Building event types once is a project. Keeping them clean, well-routed, and aligned with CRM as your team grows is a job. EverestX demand-gen specialists set up Calendly event types + routing + CRM sync as a package — typically $400-800/mo at $14-16/hr depending on team size.
See specialist rates
Round-Robin = a pool of hosts, Calendly picks ONE per booking. Collective = ALL listed hosts attend every booking. Round-Robin scales demo distribution; Collective is for genuinely 2-person meetings (AE + Legal contract review). Most teams want Round-Robin 95% of the time.
Not within the Round-Robin event itself — but yes via routing forms. You build a routing form that asks 1-2 qualifying questions, then sends Enterprise leads to one Round-Robin (senior AEs) and SMB to another (junior AEs). Covered in the routing forms tutorial.
Standardize unless you have a reason. 30-min default works for 90% of demos. Use 15-min for low-friction intros (cold inbound) and 45-min for explicit technical deep-dives. Don't fragment into 6 durations — it confuses reps and marketing.
Each rep's availability is in their own zone — Calendly handles the conversion. If an East Coast prospect books at 9 AM ET, Calendly will route to whichever rep is genuinely free at 9 AM ET (which might be a West Coast rep at 6 AM their time — so set their availability to start at 9 AM PT, etc.).
Yes — in the booking confirmation email, Calendly Analytics, and your CRM (if integrated). For Round-Robin reporting, use Calendly Analytics on Teams plan or build a HubSpot/Salesforce dashboard from the synced meeting data.
Calendly
If every prospect can book your most expensive AE's calendar, you're paying for tire-kicker demos. Routing forms qualify leads first, then route the qualified ones to the right rep — and redirect everyone else to a self-serve path.
Calendly
Team scheduling in Calendly is where solo accounts hit a wall. Pools, priority, ownership, and re-routing all live here. Done well, it scales to 20+ reps cleanly. Done badly, every new rep is a config migration project.
Calendly
The Calendly-HubSpot integration is one of the simpler ones — until you scale and realize half your contacts are duplicates because no one configured the matching rules. Here's the right setup the first time.
Calendly
DIY Calendly is fine when you're a solo founder. The moment you have multiple reps, routing logic, or a CRM that needs to stay clean, you're past the DIY ceiling. Here's the honest framework for when to make the call.