Bitrix24 Open Channels SLA Setup
Client writes in support chat, waits 20 minutes, gets no answer, writes again, gets angry, leaves to competitors. Operator at that time dealing with another request and doesn't see new chat. Manager finds out about lost client a week later when reviewing report. Without SLA rules in Open Channels, no control over response time — each operator works in own rhythm, system guarantees absent.
SLA in Open Channels
Open Channels — Bitrix24 module for processing requests from messengers, social networks, website widget, email. All channels feed into single queue, operators process requests in B24 chat.
SLA rules set framework:
- First response time — how many seconds/minutes operator must answer new request. Example: 60 seconds for website chat, 5 minutes for Telegram.
- Queue wait time — maximum time request can be without operator.
- Time between messages — if operator doesn't answer client message in N minutes — escalation.
Rule Setup
In Open Channel settings (Contact Center → Open Channels → select channel) available parameters:
- Queue — list of operators processing requests. Distribution: evenly, strictly by queue, or all simultaneously.
- Operator response wait time — if operator doesn't accept chat in specified time, request moves to next in queue.
-
Auto-actions on no answer:
- Redirect to another operator
- Redirect to manager
- Send auto-reply to client: "All operators busy, your request received"
- Close chat with message
Priority Routing
Not all requests equal. VIP client shouldn't wait in general queue. Priority routing:
- By source — requests from certain channel (e.g., VIP chat on website) directed to separate queue with dedicated operators.
- By client — if requesting contact in CRM marked as VIP (custom field), robot auto-moves chat to senior operator.
- By keywords — request contains "urgent", "not working", "emergency" → elevated priority.
For client-based priorities: Open Channels detect contact in CRM → robot in CRM checks "Client Category" field → returns result to channel.
Escalation
Escalation — auto-transfer of request to next level on SLA breach:
- First level — request not accepted by operator in 2 minutes → transfer to next operator in queue.
- Second level — request not accepted in 5 minutes → notification to support department head.
- Third level — request without answer 15 minutes → notification to director, request marked critical.
For notifications, robots and business processes used. Notification comes in B24 chat, email or push notification on phone.
SLA Reporting
SLA control meaningless without reports. Bitrix24 provides Open Channels statistics:
- Average first response time
- Average request processing time
- Percent requests processed within SLA
- Customer satisfaction rating (if enabled post-close survey)
- Operator load: request count, chat time
Statistics available in Contact Center → Statistics. For advanced analytics, data exported via BI connector.
What We Configure
- SLA rules for Open Channels: response time, wait, escalation
- Operator queues with priority routing
- Escalation by levels: operator → senior → manager
- Auto-replies on wait time exceedance
- CRM binding for VIP client prioritization
- SLA statistics dashboard for support department head