SLA Configuration for Bitrix24: Rules, Escalation, Reporting
A client writes to the support chat, waits 20 minutes, gets no response, writes again, gets angry, and leaves for a competitor. Meanwhile, the operator is handling another inquiry and doesn't see the new chat. The manager finds out about the lost client a week later when checking reports. Without SLA rules in Open Lines, there is no control over response time—each operator works at their own pace, and there are no systemic quality guarantees.
We configure SLA rules turnkey: from analyzing current load to implementing dashboards for management. We'll evaluate your project in 2 days and propose the optimal queue and escalation architecture. Configured SLA rules reduce response time by 3 times compared to chaotic handling, and the percentage of overdue inquiries drops from 40% to 5%.
SLA (Service Level Agreement) defines target service indicators: maximum wait time for a response, percentage of inquiries handled on time, and procedures for violations. In the context of Bitrix24, SLA is implemented through the Open Lines module, business processes, and CRM robots.
How to Configure SLA Rules in Open Lines?
Open Lines is a Bitrix24 module for handling inquiries from messengers, social networks, website widget, and email. All channels are consolidated into a single queue, and operators handle inquiries from the Bitrix24 chat.
SLA rules set the boundaries:
- First response time—how many seconds/minutes an operator must respond to a new inquiry. Example: 60 seconds for website chat, 5 minutes for Telegram.
- Queue wait time—maximum time an inquiry can be without an operator.
- Time between messages—if an operator doesn't respond to a client message within N minutes, escalation is triggered.
In the Open Line settings (Contact Center → Open Lines → select a line), the following parameters are available:
- Queue—list of operators handling inquiries. Distribution: evenly, strictly in order, or all at once.
- Operator response wait time—if an operator doesn't accept the chat within the specified time, the inquiry passes to the next in queue.
- Automatic actions when no response:
- Redirect to another operator
- Redirect to supervisor
- Send an auto-reply to the client: 'All operators are busy, your inquiry has been accepted'
- Close the chat with a message
| Parameter |
Default Value |
Recommended for VIP |
| First response time |
60 sec |
30 sec |
| Queue wait time |
120 sec |
60 sec |
| Time between messages |
300 sec |
120 sec |
Priority Routing
Not all inquiries are equal. A VIP client shouldn't wait in a general queue. Priority routing:
- By source—inquiries from a specific channel (e.g., VIP chat on the website) are directed to a separate queue with dedicated operators.
- By client—if the contacting contact in CRM is marked as VIP (custom field), a robot automatically transfers the chat to a senior operator.
- By keywords—inquiry contains 'urgent', 'not working', 'emergency' → higher priority.
To implement priorities by client, a combination is used: Open Lines identify the contact in CRM → a robot in CRM checks the 'Client category' field → returns the result to the line.
What to Do When SLA Is Violated?
Escalation—automatic transfer of an inquiry to the next level when SLA is violated:
- First level—inquiry not accepted by operator within 2 minutes → transfer to the next operator in queue.
- Second level—inquiry not accepted within 5 minutes → notification to the support department supervisor.
- Third level—inquiry without response for 15 minutes → notification to the director, inquiry marked as critical.
For notifications, robots and business processes are used. Notifications arrive in the Bitrix24 chat, by email, or push notification on the phone. Escalation triggers within 2 minutes, supervisor notification within 5 minutes.
SLA Reporting
SLA control is meaningless without reports. Bitrix24 provides Open Lines statistics:
- Average first response time
- Average inquiry handling time
- Percentage of inquiries handled within SLA
- Client satisfaction rating (if rating after chat close is enabled)
- Operator workload: number of inquiries, time in chats
Statistics are available in the Contact Center → Statistics section. For advanced analytics, data is exported via BI connector.
What's Included in SLA Setup
- Audit of current load and channels
- Design of SLA rules aligned with business processes
- Configuration of queues and priority routing
- Implementation of multi-level escalation
- Integration with CRM for VIP clients
- SLA statistics dashboard
- Documentation and operator training
- Technical support for 2 weeks after launch
Contact us for a consultation—we'll help build a transparent support system where every client receives a timely response.
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.
