Hybrid work

As a follow up to this, the process above actually won’t work for us as we need to apply daily and weekly meeting limits to each event type and global meeting limits per day and per week to ensure smooth operations and service delivery to our clients.

By creating two separate calendly events for the same type of meeting clients could book double the number of that type of meeting each week than desired, which defeats the purpose of the meeting limits.

So, we desperately need a workable solution to hybrid work that allows us to still apply all of our meeting limits.

Hi ​@Jason55355 - Definitely a lot to consider here, I’ve added some notes/information below you can reference, hopefully this gets you a bit closer to what you’re wanting to configure. In a pinch, you can always contact our support team who would be more than happy to setup a call and go over your use case as well!

 

Clarifying what Calendly can and can’t do today

1. Location-based availability (the big one)
   Calendly doesn’t currently support conditional availability based on the invitee’s chosen location inside a single event type — for example, “show these hours if they pick remote, but only office-day hours if they pick in-person.” Today, that behavior can only be approximated by using separate event types per location and wiring them together with routing or links.
    

2. Routing forms 
   The good news: you shouldn’t need to build 28 separate routing forms. A single routing form can contain many routes (rules), each pointing to a different event type.

   • You could have one form that asks:
     • “Which adviser would you like to meet with?”
     • “What type of meeting?”
     • “How would you like to meet? (Remote / In-person)”
   • Then create routes like: [Adviser A + Initial + Remote → Event Type X] OR [Adviser A + Initial + In-person → Event Type Y], and so on.
     Still needs some thorough configuration, but it’s one form with multiple routes, not 28 distinct forms to manage.
      

3. Meeting limits (per event and across all events)
   Calendly now supports two layers of meeting limits:

   • Per-event-type limits – cap how many times that specific event type can be booked per day/week/month (what you’re already using).
   • Host-level limits across all event types – cap how many total meetings can be booked with a host per day/week/month, across all of their event types.

   These work together: whichever limit is reached first blocks new bookings for that host in that time frame.

   What we don’t have yet is a way to say “treat these two event types (e.g., ‘Initial – Remote’ and ‘Initial – In-person’) as a single bucket for a shared limit, but keep them separate from my other meeting types.” The only “shared” bucket today is all meetings for that host.

Let me know if you have any questions on these! Like I mentioned before, it might be a good idea to speak with our support team who can get more insight into your account/setup and recommend processes from there!
 

Finally, I’ve flagged this thread and your use case for our product team, hopefully we have some more direct features in the future!

Hi David,

Thank you for your response and good to know about the routing options being more flexible than I first thought. However, it doesn’t appear there is a useful solution for our use case yet.

I reached out to the support team as you suggested, but they just repeated the same options you did.

I do appreciate that you’ve flagged the thread with the product team, thank you. The support team said they’ve done the same. We’ll see what happens from here.