Automatic distribution of leads according to the given parameters?

Question

CRM

1. Limit
Each Responsible is allocated a certain number of Leads (the number N, which can be adjusted by the manager in the application).
Until the moment when the Responsible converts the Lead into a Rejection or into a Contact + Deal, the Responsible does not receive new leads.
Additional description of the example.
The Responsible has 20 leads in the work
One converted, it became 19, the system saw this and allocated him another new lead from the lead pool.
2. Everyone is the same
Uniform distribution of leads
Here the algorithm is quite simple, it is similar to the algorithm in telephony, for incoming calls. All equally.
Example:
50 calls per day + 50 requests from the site = 100 Leads
Leads are distributed evenly between 5 Responsibles
. Each Responsible has 10 calls and 10 requests
. The numbers are given as an example to understand the logic and type of Leads
. A call is a Lead and an application from the site is also a Lead, but they have a different type.
That is, the division in style - one Responsible 20 requests from the site, and the second 20 calls - will not be correct.
3. The best - the best!
According to the conversion statistics from Lead to Completed Deal, the best employee (Top-5) is determined.
And first of all, Leads go to these employees, because it is these employees who are most likely to convert these leads into actual money
4. Time or number limit
The time interval or the number in the time interval is set, and each Responsible receives a Lead for processing.
Examples of what the conditions might look like:
- 1 Lead every 15 minutes
- 4 Leads per hour (similar to the above example)
- 40 leads during the working day
- etc.
The essence of the algorithm is to link the number of leads to a period (time / day / month, etc.)
Something like this, I've been fighting for a couple of days and I can't think of anything, I did the distribution among online managers, everything is also through the BP by time , but how to bind to the parameters of the manager here is a snag