Calendly with multiple calendars: holds read from every account

Anyone whose commitments are spread across more than one account eventually books over something. A client call goes into the work account, a dentist appointment into the personal one, a volunteer commitment into a third, and the booking page only knows about the first. The slot looked free because, from where the booking page was standing, it was.

Calendly does handle more than one calendar, but two separate decisions are involved and they are easy to conflate. One decision is which calendars get read when checking for conflicts. The other is which single calendar new bookings get written into. Getting the first one wrong causes double bookings. Getting the second one wrong causes meetings nobody sees.

Reading and writing are two different settings

Calendly's own help text for connecting a calendar sets out the steps in order: open Availability, then Calendar settings, select the option to connect a calendar account and choose the type, sign in and allow access, then select the calendars Calendly should check for conflicts and choose where new bookings go.

That fourth step is the one that matters and it contains both decisions. The conflict check can cover several calendars at once. The destination is a single choice. Calendly's own wording is explicit about it: if you connect more than one calendar, choose one as your main calendar for bookings.

So the correct mental model is a wide net and a single drain. Everything that could possibly conflict should be inside the net, including calendars you never write to and would not think of as yours: a shared team calendar you are a member of, a subscribed schedule, a household calendar someone else maintains. If a commitment in it can occupy your body at a given hour, it belongs in the conflict check.

The drain is narrower on purpose. New bookings landing in two places would produce duplicates on every device that syncs both. The practical test for choosing it is not which account is most important but which calendar you actually look at during the day, because that is where a booking has to appear to be acted on.

A calendar left out of the conflict check is not simply missing, it is being reported as free time. This is the single most common cause of a double booking on an otherwise correct setup.

The six connection cap, and what counts as one

Calendly's pricing page lists calendar connections as one on the Free plan and six on Standard, Teams, and Enterprise. That is the hard number to plan around, and it is worth being precise about what it counts.

A connection is an account, not a calendar. Signing in to one Google account is one connection, and that account may expose a dozen calendars: your primary one, calendars other people have shared with you, holiday feeds, subscribed schedules. All of those become selectable for the conflict check under that single connection. So six connections is six sign-ins, which for most people is generous even when their calendars are scattered.

The place the cap becomes real is when accounts multiply rather than calendars. Two work accounts from two employers or clients, a personal account, a university or association account, and a spouse's shared account reach five sign-ins without anything unusual happening. That is inside six, but the margin is thinner than the number suggests.

On the free tier the figure is one, and that is the constraint that sends most people to a paid plan. One connection means one account's calendars. Every commitment living in a second account is invisible, and no amount of careful availability configuration fixes it, because availability rules and conflict checks are separate mechanisms. Availability says when you are willing to be booked. The conflict check says whether that willingness is already spoken for. Only the second one reads your calendars.

Standard is listed at $10 per seat per month billed yearly, or $12 billed monthly, and that step is what buys the move from one connection to six. Teams at $16 billed yearly, or $20 monthly, does not add more connections. The number is the same six from Standard upward.

Which platforms count, and the settings under each one

Three calendar platforms can be connected: Google Calendar, Office 365 or Outlook.com, and Exchange. Anything outside that list has to reach one of them first, which for most people means subscribing a feed into Google Calendar and letting the connection pick it up there.

Each connection then carries its own set of options, and they are set per calendar rather than once for the account.

The first pair is the reading and writing choice already described: Calendars to check for conflicts, which accepts several, and Calendar to add events to, which accepts one. Calendly is explicit that it will not add events to any other calendar.

The second is buffers. Turning on the option to include buffers on a calendar writes the padding before and after meetings into that calendar as separate events, which makes the protected time visible to anyone looking at the day rather than existing only inside the booking logic. Deleting one of those buffer events in the calendar also removes it in Calendly, so the two stay in step.

The third is the sync direction that catches people out. With cancellations and reschedules syncing enabled, declining or deleting a booked meeting in the calendar cancels it in Calendly, and changing its date or time in the calendar reschedules it there too. Changes an invitee makes in their own calendar do not affect the meeting. That is the setting that decides whether the calendar on the desk is the authoritative copy or merely a mirror.

One destination for every event type

There is a limit here that is easy to design around once it is known and frustrating to discover late. Connected calendars apply to the whole account, not to individual event types. There is no way to send coaching bookings into one calendar and internal meetings into another.

For anyone who wanted separation by purpose, the separation has to happen after the booking lands, either by moving events or by colour and calendar rules in the desktop application. That is a second argument for the calendar on the Mac doing the sorting rather than the booking page.

What invitees can and cannot see

A reasonable worry about pointing a booking page at a personal calendar is what the person booking will see of it. Calendly's calendar connections page addresses this directly, stating that it cross-checks all your calendars, shows only available appointment times, and never exposes your calendar contents to invitees.

That means the conflict check is one-directional from the invitee's point of view. A busy block removes a slot from the page. The title of the thing making you busy, its guests, its location and its notes do not travel. A personal calendar full of medical appointments can safely be inside the net.

What does travel is the booked event itself. Calendly states that scheduled meetings are added directly to the host and invitee calendars, which means the person booking sees the event they created and the details they supplied, on their own calendar, as they would with any invitation.

Checking more than one person's calendars

"Multiple calendars" sometimes means multiple people rather than multiple accounts, and that is a different feature on a different plan.

Reading colleagues' calendars so a booking only lands when everyone is free is what the Collective format does. Calendly's pricing table lists multi-person meeting types as unavailable on Free and unlimited on Standard and above. Rotating a booking to whichever colleague is free is Round Robin, which the same table lists as unavailable on Free and on Standard, and unlimited on Teams and Enterprise.

The connection cap then applies per person rather than per team. Each teammate connects their own accounts, up to six each, and each of them decides which of their calendars are read. A Collective event that keeps offering a time one colleague cannot make is almost always a case of that colleague having a commitment in an account they never connected.

Seats follow the same logic. Calendly's pricing page states that seats are required for users who connect calendars and host meetings, and that invitees do not require an account or a seat. The bill scales with the number of people whose calendars are being read, not with the number of people booking.

Where multiple calendars still cost you time

Job	Handled by the booking page	Handled by the calendar on your desk
Not being booked over	Yes, for every connected calendar	Yes
Seeing all accounts at once	No, the page has no view	Yes
Choosing which accounts to look at right now	No	Yes, by saving and switching sets
Knowing when to leave for the next commitment	No	Yes, from the event location
Writing a new event into a chosen account	Only for bookings it created	Yes, for anything

The gap in the middle column is the one people feel daily. A booking page that reads six accounts still gives you nothing to look at. The question "what does Thursday look like across all of this" is answered by the calendar application, not by the scheduling service, and if that application only shows one account then the accounts have been merged for booking purposes and left scattered for human purposes.

A desktop calendar closes that half. Connecting as many accounts as you have and showing them side by side or one at a time, with a chosen default for new events, is what multiple account support is for, and saving combinations such as work and personal and switching between them in one action is what calendar sets do. The point is not tidiness. It is that a slot you can see is a slot you will not agree to twice.

The other half is the one no connection count touches. Two commitments in different accounts can both be visible, both be in the conflict check, and still be impossible because they are forty minutes apart across a city. Door-to-door travel time and time-to-leave alerts are what turn a gap on the screen into a gap you can actually cross.

What to change first

List every account that holds a commitment, then check that each one is connected and that each calendar inside it is ticked for the conflict check. That single pass removes most double bookings, and on the Free plan it will also tell you immediately whether one connection is enough, because the cap is one account.

Then decide where you look during the day and make that calendar the destination. If the answer is that you look in several places, the accounts need bringing together on the desktop rather than only inside the booking page, which is what Caltimate does on the Mac.