Complete Task Queue Setup in Bitrix24 Streams

We often see tasks pouring in faster than the team can handle. Without a queue, everything mixes up: an urgent client request gets lost among routine inquiries, and a critical bug waits while an employee finishes a low-priority task. Queues in Bitrix24 streams bring order to the incoming flow: tasks line up by priority, are processed in a defined order, and the backlog stays under control.

One logistics client approached us: their support stream received 200 tasks per day, and 70% were lost. We implemented a priority queue with escalation after 15 minutes for critical bugs. Within a week, response time dropped threefold, overdue tasks fell to 5%, and monthly SLA penalty savings reached 200,000 rubles. The client got a transparent SLA and a tool to monitor team workload.

How the Queue Works in Bitrix24 Streams

When a task arrives in a stream and cannot be immediately assigned (all executors are busy, task limit reached), it enters the queue. The queue is a buffer between requesters and executors. Bitrix24 supports three sorting modes:

• FIFO (First In, First Out) — tasks are processed strictly in order of arrival. Simple, suitable for homogeneous requests.
• By Priority — high-priority tasks are processed first, regardless of arrival time. A critical bug that arrived 5 minutes ago overtakes a normal task waiting 2 hours.
• Combined — first by priority, then FIFO within the same priority.

Source: Bitrix24 documentation

Priorities and Escalation

Bitrix24 supports four priority levels: Critical, High, Normal, Low. In queues, priorities determine processing order and maximum wait time.

If a critical priority task waits in the queue longer than 15 minutes, escalation triggers: notification to the stream manager, automatic expansion of executor task limits. We configure escalation via Bitrix24 business processes: the "Wait time exceeded" event launches a scenario — sending a notification, creating a subtask, making a call via Open Lines.

Comparison of Queue Modes

Why Manage Backlog?

Backlog is tasks that are in the queue and not yet assigned. Controlling the backlog is critical for SLA. We configure:

• Queue size monitoring. If backlog grows, the team cannot handle incoming flow — a signal for the manager to add people or reprioritize.
• Queue limit. Maximum number of tasks in the queue (e.g., 50). When the limit is reached, new tasks are not accepted (the requester sees a warning) or are automatically redirected to another stream.
• Auto-cleanup. Tasks that sit in the queue longer than a specified period are marked as overdue and escalated.

Visualization and Monitoring

The stream manager sees the queue as a list sorted by priority and arrival time. Available information:

• Number of tasks in the queue.
• Average wait time.
• Distribution by priority.
• Tasks approaching SLA violation.

We also configure dashboards in Bitrix24 reports and automatic notifications via chatbots.

How We Configure Queues: Process and Stack

We use the Bitrix24 REST API, business processes, and task fields. For example, via tasks.task.add with priority and deadline, we create a task in the stream; priorities are set via the PRIORITY field. Escalation is implemented through business processes with delays.

Process:

1. Analysis of current streams and bottlenecks.
2. Designing the queue model (FIFO/priority/combined) and escalation rules.
3. Setting up priorities, limits, auto-cleanup via Bitrix24 interface.
4. Implementing custom logic (REST API, business processes).
5. Testing: load testing with 200+ tasks per day.
6. Deployment and team training.