We’d like to request the ability to set a combined daily limit that applies across both Round Robin (distribution) links and 1:1 scheduling links for each rep.

Example scenario:

If a rep should only take a maximum of 5 calls per day, the system should stop routing new calls once they reach this total, regardless of whether the calls came through a distribution or a 1:1 link.

We're using CP for our support team. This is a key functionality to ensure our reps have manageable call loads each day.

Adding this feature would allow CP to open up more use cases.

Merged with https://suggest.chilipiper.com/admin/v3#ng!/ideas/46716799. Ideas are different but in very similar context.

Currently, you can cap the number of meetings per day but you can't cap the number of hours booked per day. For example, if I want only allow two hours to be booked per day for one meeting type, I can't do that today. I would have to put a limit of four 30-minute meetings per day.

You can set a schedule to align the two hour requirement but I don't want to timebox our customers. I want to give them the flexibility to book whenever they want to.

This would be incredibly helpful when someone is in multiple queues. If we have meeting type cap set at 3, but they are mapped into 4 queues, they could in theory get stacked with 12 meetings.

It is critical for us to be able to limit the # of meetings a single rep can get. We have people in onboarding we don't want to be receiving more than a certain number of meetings booked in a week

However, since these reps have lots of availability on their calendar, they get many meetings routed to them, even if their weights are very low - which is the opposite of what we aim for

We would like to have the feature of putting a cap on the number of hours that can be scheduled to a user per day. This would be an option to turn off the cap for meeting types, and change to a user-based cap instead.Our use case:Our team performs training on over 100 training courses. Training courses have different durations, from 1 to 3 hours, depending on the course. We want each of our trainers to have a daily limit of 5 hours of training. We want to provide our customers a larger range of times for scheduling their training, as our customers are all over the US and UK. Therefore, we do not have trainers on a fixed schedule for specific times of the day that they can train; training can be booked throughout their entire shift.Current Chili Piper Setup: Each course is a separate queue in Chili Piper, which allows us to assign trainers to each course based on their skills. Each training course has different duration and pre-requisites, so we also have a different meeting type for each queue so that we can account for the duration differences and send a unique invitation for each. The issue: When we try to limit how many hours a trainer can be booked every day, we cannot easily do this when there are multiple meeting types that they can handle, each with different durations. The limits in the meeting type are rendered useless, referring to the setting "Cap the number of times an Assignee can be booked to {integer} meetings every {time period}". So we have to set each of our trainer's working hours to a specific time of the day that they can train.Proposed solution: If, instead of having a cap based on meeting type, we could apply a limit of the number of hours that a user could be scheduled, we could offer more availability to our customers, have better utilization, and provide more flexibility to our trainers in their daily schedule.Our previous system, Acuity, was able to accommodate this. I would love to see it in Chili Piper as well.

Id like for there to be customizable host booking limits (by user) within a specific meeting type. From a capacity management perspective this would reduce friction between meeting types and queues