Automation

Lead distribution

Automatically and fairly distributes new leads between managers. Takes into account working hours, employee availability and your priorities.

Features

Automatic distribution of leads between managers
Flexible work schedule for each employee
Accounting for employee absence
Uneven distribution of odds
Limit on the number of leads per manager
Suspension of distribution by manager
Distribution of contacts, companies and tasks
Accounting for managers' workload

Installation and setup guide

Detailed guide for working with widget "Lead distribution"

Setting up a schedule

  • Go to Widget Settings
  • Click +.
  • Enter a title for the chart.
  • Click Add.

Important: Kommo account time is used for the distribution schedule.

  • Set up managers’ work schedule
  • You can also create different graph options (for example, 2/2).

Setting up distribution triggers

After installing the widget:

  1. Go to pipeline settings.
  2. Click + at the desired stage.
  3. Enter “Lead distribution” in the search.
  4. Click Add.

Adding managers

  • Add and configure managers for distribution.
  • If managers are not selected, leads will be distributed evenly according to the schedule.
  • In the drop-down list Work schedule select the desired schedule.

Select the types of distributed objects. You can distribute:

  • Contacts
  • Companies
  • Customers
  • Lead tasks
  • Active company leads
  • Active leads of the main contact

Not evenly distributed

If you need to distribute leads not equally, but according to a specific coefficient:
Enable the coefficient balancing option.
Specify the numbers.
For example:

  • Coefficients 40 and 60
  • Out of 6 leads → 2 will go to the manager with a coefficient of 40
  • 4 will go to the manager with a coefficient of 60

Limit on the number of leads

To limit the number of leads for a manager: Enable the “Consider the maximum number of leads per stages” checkbox. Select a pipeline/stage (by default - all active stages in all pipelines). Specify the maximum number of leads for one manager.

  • If the limit is lower, leads are distributed.
  • If the limit is exceeded, leads will not be assigned to this manager.

Always distribute with...

The settings indicate the person responsible for the company/contact.

  • If the owner matches the "Always distribute with..." selected in this setting→ leads are distributed by trigger

If the person responsible is different → the lead is distributed to the person responsible for the contact/company

Suspension of distribution

The manager can turn off distribution (for example, during lunch)

  • By default, distribution is enabled

To pause:

  1. Click on your avatar
  2. Expand the group
  3. Uncheck the checkbox Active for distribution

  • The administrator can also pause and enable distribution

Setting up activity options
In the widget settings, enable the checkboxes:

  1. Enables the activity block
  2. Allows users to change their activity (if disabled, only the administrator can change the activity)

Trigger Recommendations

For stable operation, we recommend adding 2 triggers to the distribution stage:

  1. The first trigger is the condition Responsible: User, under which the distribution should occur.
  2. The second trigger is launch in 3 minutes with the same condition.
This will allow distribute leads if for some reason the first trigger did not work.

Register of statistics

The function allows you to evenly distribute leads between managers, even if these leads come from different pipelines. The main idea is to ensure an overall uniform distribution, despite possible fluctuations in individual pipelines.

How it works:

  1. Single registry for statistics:Instead of keeping separate statistics for each pipeline, we use one common registry. This ledger keeps track of how many leads have been allocated to each manager.
  2. Triggers in each pipeline:In each pipeline where distribution is needed, a trigger is configured. Both triggers (or more if there are more pipelines) refer to the same shared registry.
  3. Distribution accounting: When a lead enters any of these pipelines and is distributed to a manager, +1 is recorded in the general register for this manager.
  4. Making a decision on the following distribution: When a new lead arrives, the function accesses the general register. Based on the current statistics (who received the fewest leads), it determines which manager should allocate the next lead to maintain an overall even distribution.

How to configure?

When setting up a trigger in the Statistics Registry field, you must create a registry. To do this, click on +:

Create registry button

Enter the registry name:

Entering the registry name

Select it from the list of registries:

Selecting a registry from the list

Save the trigger. If you need to collect statistics from several pipelines/stages, select this register in the trigger settings in another pipeline/stage.

If you need to collect statistics from only one trigger, select Current trigger in the registry:

Selecting the current trigger

Redistribution of leads

Redistribution is when, over time, if a lead is not taken into account, it can be redistributed. To do this, you need to:

  • Create a technical field Taken to work with typeFlag

Create/Changetwo stages New application and Accepted for work

When the manager has taken on a lead, he moves it to the next status Taken on. At this stage you need to set the Change field trigger

  • Execute: when entering a stage
  • Select Field Hired
  • In the dropdown list:Filled

When the manager has taken on a lead, he moves it to the next status Taken on. At this stage you need to set the Change field trigger

  • Execute: when entering a stage
  • Select Field Hired
  • In the dropdown list:Filled

When a manager, for example, does not take a lead to work within 10 minutes, it will be redistributed to another manager. At this stage you need to add salesbot

  • Execute: when entering a stageor creation in a stage
  • Create a new bot
  • Select Lead distribution widget
  • Customize widget
  • Next stepBreaker → Timer → 10 minutes
  • Next select Condition If (select field Lead: Taken to Work) Equal to: not filled in Return to the Distribution step
  • In other casesStop the bot