Calendly group scheduling: one slot for a room full of people

Searching for Calendly group scheduling usually means one of two different jobs. Either one person needs to run a session that thirty people attend, or several colleagues need to be in the same meeting with one outside guest. Calendly treats those as separate products with separate names, separate plan requirements and separate limits, and picking the wrong one is the most common reason a booking page behaves unexpectedly.

There are also two behaviours in group events that are not obvious until a session is already scheduled: how confirmations are delivered, and which settings freeze the moment the first person books.

Four event types, and which one means "group"

Event types in Calendly are reusable meeting templates. There are four, and only one of them is called Group.

Event type	Who is in the meeting	Plans
One-on-one	One host, one invitee	All plans
Group	One host, many invitees in the same slot	Standard, Teams, Enterprise
Collective	Several hosts, one invitee, when all hosts are free	Standard, Teams, Enterprise
Round Robin	One-on-one meetings rotated across teammates	Teams, Enterprise

Group is the one for webinars, training sessions, info sessions, workshops, museum or campus tours, group fitness classes and university admissions sessions. One host, many attendees, one time slot, and the slot stays open until every spot is filled.

Collective is for panel interviews, discovery calls and any meeting where an invitee needs two or more people from the same organisation present at once. Calendly intersects the hosts' availability and only shows times when everyone is free. On Teams and Enterprise, a Collective event can also draw from multiple host groups.

Round Robin is not group scheduling in the attendee sense at all. It rotates individual meetings across a team based on availability or assignment rules, which is what a sales or support rota needs.

The seat rule is the part that surprises people. For Collective and Round Robin, every host has to be a Calendly user with a paid seat of their own. Invitees never need an account or a seat, no matter which event type is used.

The invitee limit, and the two places it lives

A group event's capacity is set in the event type editor under the Invitee limit section, reached from the Scheduling page through the three dots menu on the event card.

The range is wider than most people expect: a minimum of 2 and a maximum of 9,999 invitees per slot. Set it to 50 and up to 50 people can book the 1 p.m. session. There is also a Display remaining spots option, which shows attendees a live count of how many places are left, and that single checkbox does more for registration rates on a filling session than any wording change to the event description.

The trap is what happens to sessions that are already on the calendar. Changing the Invitee limit on the event type only affects future bookings. Raising the cap does not open extra places on a session that has already been scheduled.

To change capacity on an existing meeting, the edit happens somewhere else entirely: the Calendar page, then the meeting itself, then Edit invitee limit under Invitees, then Apply. Anyone who has raised a limit on the event type and watched a session stay full has been editing the wrong object.

Confirmations arrive by email, not as calendar invites

This is the single most important behavioural difference between group events and every other event type, and it explains most no-show complaints.

Group events use email confirmations rather than calendar invitations. Each invitee receives their own .ics file attached to the confirmation. Most calendar apps add that file automatically, and if one does not, the attendee can download it again from the confirmation email or the confirmation page.

The consequence is that those .ics files are static copies. If the event changes, the file already sitting in an attendee's calendar does not update for anyone else. A one-on-one meeting behaves like a normal calendar invite, where a reschedule propagates. A group session does not.

In practice that means two things for anyone running sessions with more than a handful of attendees. Treat the time as fixed once invitations have gone out, and if it genuinely has to move, send the change over email as well rather than assuming calendars will catch it. For a paid workshop, that is the difference between a full room and half of one.

What freezes after the first booking

Once a single person has booked a group event, three settings lock and show as a greyed out box: the event language, the location, and the duration.

There is no in-place edit for those. The documented route is to duplicate the event type, change the language or duration on the copy, cancel the original meeting from the Calendar page, then rebook each invitee against the new event type using Book meeting and entering their details.

That is a manual re-entry per attendee, which is fine for six people and unworkable for sixty. The implication for anyone setting up a recurring webinar is to get duration and location right before publishing the link, and to treat the first booking as the point of no return rather than the start of a test period. Running one dummy booking on a duplicate event type before sharing the real link costs two minutes and prevents the whole problem.

Event permissions, which control who can view, edit or share the event, are available from the Standard plan upward.

What group scheduling costs

Calendly's published pricing, billed yearly, puts multi-person event types behind the first paid tier.

Plan	Price per seat	Group and Collective	Round Robin
Free	$0	Not included	Not included
Standard	$10 per month billed yearly, $12 monthly	Unlimited	Not included
Teams	$16 per month billed yearly, $20 monthly	Unlimited	Unlimited
Enterprise	From $15,000 per year, minimum 50 seats	Unlimited	Unlimited

The Free plan allows unlimited one-on-one meetings, one event type and one calendar connection, and it includes meeting polls and one-off meeting links, but multi-person event types are not part of it. For a single person running occasional sessions, Standard at $10 per seat per month billed yearly is the whole cost, since attendees never need seats.

The jump to Teams is worth reading carefully, because it buys rotation and routing rather than capacity. If the requirement is genuinely "many people in one room with one host", Standard covers it. Teams matters when meetings need distributing across colleagues, when event types need to be managed centrally, or when a team landing page with its own link is required.

Shared event types and team event types are also worth separating. Shared event types can be created by any host unless an admin restricts it, and they suit quick collaboration across an organisation. Team event types are created by owners, admins and team managers, and they appear on a team landing page with a custom link.

Automations, and the trigger that is not there

Reminders and follow-ups for group events are handled through Automations, which is where most of the practical value sits: a reminder the day before a session and a follow-up with materials afterwards.

Two limits apply. The Event is canceled trigger is not currently supported for group events, so cancellation messaging has to be handled manually. And changes to Automations only apply to future meetings; sessions created before the change keep the settings they were created with.

That second rule catches people who add a reminder after opening registration. The attendees who booked first will not receive it. Set the reminders up before the link is shared, and check them against a session that was created after the change rather than the earliest one on the calendar.

When the group has to pick the time, not the host

Group event types assume the host owns the slot and attendees fit around it. A large amount of what people call group scheduling is the opposite problem: five colleagues and no obvious hour that works for all of them.

Calendly lists meeting polls and one-off meeting links on every plan including Free, and a poll is the right tool for that case. Several candidate times go out, everyone marks what works, and the host confirms one. Nothing is held on the calendar until the decision is made, which is exactly the behaviour wanted for a one-off internal meeting.

The distinction is worth being deliberate about, because using the wrong one creates work. A Group event type for an internal meeting means guessing the time and hoping enough people accept. A poll for a public webinar means asking two hundred strangers to vote on a time, which nobody will do.

The rough rule: if the event exists whether or not any particular person attends, it is a Group event type. If the event only exists once the specific people agree, it is a poll.

Collective sits between the two and is frequently the honest answer for small groups inside one organisation. Instead of asking four colleagues when they are free, a Collective event type reads all four calendars and shows the invitee only the times that already work for everyone. No voting, no follow-up thread, and no meeting placed on top of something that was already booked. The cost is that all four need paid seats, which is the trade that decides it.

Where the booking page stops and the calendar starts

A booking page decides when people can reach the calendar. It does not do anything about what the day looks like once they have.

That gap is where most of the damage from group sessions actually happens. A 90 minute workshop at 2 p.m. looks like a free morning and a free late afternoon in a month view, and it is neither, because the setup and the follow-up are not on the calendar. Calendly checks connected calendars for conflicts, and on paid plans it can read up to six of them per user, but it only knows about blocks that already exist.

Two habits close it. Block the preparation and the recovery time as real events rather than holding them in memory, which a desktop calendar makes fast enough to actually do, and attach travel time to anything that happens in a room rather than on a link. A calendar that handles entering events in one line and calculates travel time from the previous location is doing the part a scheduling link cannot.

What to change first

Before touching plans or limits, confirm which of the four event types the situation actually needs, because Group, Collective and Round Robin sit on different tiers and solve different problems. Then set duration and location correctly before the first booking, since those lock permanently.

If the sessions are frequent enough that the surrounding blocks matter more than the booking link, compare what a native desktop calendar handles on the Caltimate side before adding another seat.