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.
| Priority |
Queue Order |
Maximum Wait Time |
| Critical |
First |
15 minutes |
| High |
After critical |
1 hour |
| Normal |
After high |
4 hours |
| Low |
Last |
8 hours |
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
| Mode |
Sorting Principle |
When to Use |
| FIFO |
By arrival time |
Homogeneous requests without deadlines |
| By Priority |
Priority over time |
Mixed tasks with different urgency |
| Combined |
Priority first, then FIFO |
When balance is needed |
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:
- Analysis of current streams and bottlenecks.
- Designing the queue model (FIFO/priority/combined) and escalation rules.
- Setting up priorities, limits, auto-cleanup via Bitrix24 interface.
- Implementing custom logic (REST API, business processes).
- Testing: load testing with 200+ tasks per day.
- Deployment and team training.
What's included in the work
- Documentation of settings and SLA.
- Access to monitoring dashboards.
- Team training (1 hour online).
- 2-week support after launch.
- Guarantee of correct queue operation.
We've been working with Bitrix24 for over 10 years and have completed 50+ projects configuring streams. Our engineers hold Bitrix Expert certifications. Contact us for an assessment of your stream — we'll set up the queue turnkey in 2-3 days. Get a consultation without obligation.
How a corporate portal on Bitrix24 solves the problem of information chaos?
Employees spend up to 2 hours a day searching for files, emails, and solutions. Tasks get lost in dozens of chats, approvals get stuck for weeks. The manager learns about missed deadlines only at a meeting. A corporate portal on Bitrix24 ties every message, document, and task to a single context. You get a transparent picture of work: who is working on what, which stages, where bottlenecks are. Wikipedia: Information silo describes how unorganized data reduces productivity – a portal cuts that loss by 60–70%.
We will evaluate your project for free – contact us to get the architecture in 2 days. A medium‑sized company typically saves 2.5 million rubles annually after deployment (based on our projects).
What does the portal offer in daily work and why is it better than messengers?
In messengers, information is unstructured – discussions get buried within a week. On the portal, every message is tied to a task, project, or document. Employees spend up to 30% of their work time searching for data (McKinsey). The portal reduces this time by 2–3 times thanks to structured repositories and full‑text search.
Communications. Activity stream, messenger, and video calls are tied to specific tasks. Any discussion can be found six months later – in a messenger it would be buried within a week.
Tasks and projects. Kanban, Gantt, checklists, dependencies, time tracking. Each employee's efficiency is visible in reports – no need to wait for a meeting.
Document flow. Approval routes through the business process designer: leave request → manager → HR → accounting. Electronic signature, versioning, deadline control. Integration with electronic document management (SBIS, Diadoc) via REST API.
HR. Onboarding of new employees, leave/travel requests, organizational structure, absence schedule. An employee knows where to go from day one.
Knowledge base. Bitrix24 wiki engine: regulations, instructions. Knowledge does not leave with departing employees.
Implementation example. For a manufacturing company with 320 employees, we deployed a portal with integration of 1C:SALARY AND HR MANAGEMENT and Active Directory in 4 months. Travel request approval time decreased from 3 days to 4 hours. Savings on employee idle time amounted to 1.5 million rubles per year. Managers receive automatic reports on department efficiency. Customer response time decreased by 20%. Portal payback period is 7 months.
How does integration with 1C and Active Directory accelerate HR management?
Integration with 1C:Enterprise via the b24connector module or custom REST handler: a leave request is approved on the portal through a business process and automatically enters 1C:SALARY AND HR MANAGEMENT for vacation pay calculation. Active Directory (SSO via the ldap module) – the employee account is created once in AD and synchronized to the portal, email, VPN. Upon dismissal, it is blocked everywhere. Manual account creation is eliminated, errors are minimized.
Types of corporate portals and key integrations
| Type |
Purpose |
Key Feature |
| Intranet |
Internal communications and services |
News, phone directory (sync with AD), meeting room booking, IT requests via BP |
| HR portal |
HR management and development |
Profiles, KPI/OKR on custom HL blocks, training, electronic document flow |
| Knowledge portal |
Documentation and regulations |
Categorization, tags, ratings, subscriptions to updates |
| Extranet |
Work with partners and contractors |
Granular permissions via CGroup and extranet module, access without VPN |
| Holding portal |
Management of multi‑company structure |
Separate workspaces, consolidated reporting, cross‑cutting BPs |
Additional integrations that deliver real value:
- Email: Exchange via EWS API or IMAP, calendar synchronization, creating a task from an email.
- IP telephony: Asterisk, Mango Office, Zadarma via REST API – calls from the portal, contact card, call recording.
- Video conferencing: built‑in video calls or integration with Zoom/Teams via marketplace.
- EDI: SBIS, Diadoc via REST API – fully electronic document flow with counterparties.
Security and compliance with Federal Law 152‑FZ
The portal contains personal data, financial reports, strategic plans. We guarantee protection:
- role model via CGroup and section‑level permissions;
- two‑factor authentication (OTP, Yandex.Key, SMS);
- audit of all actions (b_event_log);
- TLS encryption for transmission and disk encryption;
- full compliance with Federal Law No. 152‑FZ "On Personal Data".
How is implementation carried out? Step‑by‑step plan
| Stage |
Duration |
What we do |
| 1. Audit |
2–3 weeks |
Interviews, process analysis, architecture, integration plan |
| 2. Setup and customization |
3–6 weeks |
Structure, roles, BPs, branding (CSS template) |
| 3. Integrations |
2–4 weeks |
1C, AD, email, telephony, EDI |
| 4. Data migration |
1–2 weeks |
Documents, directories, employees from current systems |
| 5. Training and pilot |
1–2 weeks |
Administrators, key users, pilot of 20–30 people |
| 6. Scaling |
2–4 weeks |
Connecting departments, fine‑tuning based on feedback |
- Audit — we record current processes, measure time losses.
- Design — choose portal type, plan integrations.
- Implementation — configure business processes, permissions, interface.
- Test — pilot group tests scenarios, we fix issues.
- Launch — connect all employees, train, hand over documentation.
What you receive after implementation
- Project documentation: architecture, integration scheme, business process diagrams.
- Configured portal with all integrations (1C, AD, telephony, EDI).
- Business process descriptions and instructions for administrators and users.
- 30 days of technical support after launch.
- Access to our knowledge base and migration scripts.
Post‑launch support: how to prevent the portal from becoming obsolete
After six months, many portals become abandoned. To avoid this, we offer packages with fixed SLA and a dedicated administrator. Performance monitoring, platform updates, user administration, development of new modules. Our team has over 10 years of experience and more than 50 implemented corporate portals on Bitrix24. We are a certified 1C‑Bitrix partner, guaranteeing quality and deadlines.
Mobile access. Native Bitrix24 app (iOS/Android) with push notifications, tasks, chats. Responsive web interface for extranet users (no app installation required). Offline access to documents and tasks, sync when connectivity is restored.
Order a turnkey corporate portal implementation
Schedule a free audit – we will evaluate your project, propose architecture, and give clear timelines. Get a comprehensive proposal and see that the portal pays for itself within the first six months. Contact us today.
