Processing queue

After installation, go to Settings.

Specify the events and stages of the pipelines from which leads will fall into the queue.

If necessary, select the fields that will appear in the queue.

If you enable the “Unsorted” checkbox, then all leads from this stage will automatically fall into the queue.

To ensure that the average response time takes into account only working hours and excludes weekends, set up managers' work schedule.

In the settings, you can specify which events trigger leads to be queued (by default, all leads).

After installing the widget, service fields are automatically created:

in the lead: n_last, n_speed, n_mess_contact, n_mess, n_mess_type, n_accept
in the contact: n_mess_last_pip

⚠ These fields cannot be deleted - otherwise the widget will not work.

1. “Answered” - removes the lead from the queue.
2. “Transfer” - opens a list of pipelines for transferring a lead to another pipeline.

When you click on the “Answered” button the lead is removed from the queue, and a note is written in the commentary to the lead.

When you click on the “Transfer” button a drop-down menu will appear with all the account’s pipelines.

• When you click on the name of the pipeline, the functionality will create a lead in the selected pipeline and add it to the processing queue.
• In the future, all new client requests will by default fall into this pipeline before being transferred to another.
• This way you can organize the work of several departments.

The widget can be filtered by managers (the filter is saved in the browser).

The widget allows you to distribute applications according to managers’ workload:

Example: If the system assigns a request to Ivan Petrov, and he is busy for 30 minutes, the client waits for half an hour. With the “For review” queue, a free manager can take an application immediately → response time is reduced.

• Available employees themselves select applications “For review” from the queue.
• This speeds up the reaction and makes distribution more efficient than when strictly assigned to a specific manager.

When installing the solution, the n_accept field is automatically created.

Trigger setup:

1. Go to pipeline → Configure.
2. Click Add trigger at the desired stage (for example, “New order”).
3. In the window, select the Edit Field action.

1. Set the condition (for example: if owner = administrator).
2. In the list of fields, select n_accept → the value “filled”.

Result:

Result:

• A lead marked “For review” appears in the queue.
• A checkbox is included in the n_accept field.
• The “Accept” buttons appear in the lead (the manager becomes responsible) and “Transfer”.

The widget can be switched to compact mode to focus on the queue and follow a standard workflow.

• number of applications processed per day,
• number of applications per month for each manager.

The Queue Reset button allows you to clear and refresh the queue - this may be necessary if the data in the queue is out of date.

To reset the queue, you need to go to the widget settings.

• overdue,
• relevant for today,
• scheduled for tomorrow.