Setting up an SLA for 1C-Bitrix customer inquiries

Our company is engaged in the development, support and maintenance of Bitrix and Bitrix24 solutions of any complexity. From simple one-page sites to complex online stores, CRM systems with 1C and telephony integration. The experience of developers is confirmed by certificates from the vendor.
Our competencies:
Development stages
Latest works
  • image_website-b2b-advance_0.png
    B2B ADVANCE company website development
    1189
  • image_bitrix-bitrix-24-1c_fixper_448_0.png
    Website development for FIXPER company
    813
  • image_bitrix-bitrix-24-1c_development_of_an_online_appointment_booking_widget_for_a_medical_center_594_0.webp
    Development based on Bitrix, Bitrix24, 1C for the company Development of an Online Appointment Booking Widget for a Medical Center
    564
  • image_bitrix-bitrix-24-1c_mirsanbel_458_0.webp
    Development based on 1C Enterprise for MIRSANBEL
    747
  • image_crm_dolbimby_434_0.webp
    Website development on CRM Bitrix24 for DOLBIMBY
    657
  • image_crm_technotorgcomplex_453_0.webp
    Development based on Bitrix24 for the company TECHNOTORGKOMPLEKS
    976

SLA Setup for Customer Inquiries in 1C-Bitrix

SLA (Service Level Agreement) for inquiries — set of rules defining deadline for first response to customer request and deadline for closing inquiry. In Bitrix implemented via "Technical Support" module (support) or in e-commerce with CRM via Bitrix24 CRM with funnel setup.

SLA in Technical Support Module

Module support — standard Bitrix tool for ticket systems. SLA settings in admin: Services → Technical Support → Service Level Agreements.

SLA Structure:

  • Response Time — deadline first answer from ticket creation
  • Resolution Time — deadline complete closure
  • Business Hours — schedule within which SLA counted (table b_support_sla_calendar)
  • Holidays — excluded dates

Each ticket on creation assigned SLA based on:

  • Inquiry category
  • Source (web form, email, phone)
  • Priority
  • User group (VIP client, regular)

SLA Assignment via Events

On ticket creation Bitrix calls OnSupportTicketAdd. You can override auto-assigned SLA in handler:

\AddEventHandler('support', 'OnSupportTicketAdd', function(&$arFields) {
    // If "Defect/Return" category — set SLA with 2-hour response
    if ($arFields['CATEGORY_ID'] == RETURN_CATEGORY_ID) {
        $arFields['SLA_ID'] = 3; // Required SLA ID
    }
});

Database tables:

  • b_support_ticket — tickets, fields SLA_ID, DEADLINE, FIRST_RESPONSE_DEADLINE
  • b_support_sla — SLA description (name, response time, resolution time)
  • b_support_sla_day — work days and hours per SLA

SLA Violation Control

Bitrix has no built-in alert approaching deadline — implement via agent or scheduler:

// Agent: find tickets with deadline expiring in 1 hour
$deadline = new \Bitrix\Main\Type\DateTime();
$deadline->add('1 hours');

$tickets = \Bitrix\Support\TicketTable::getList([
    'filter' => [
        '=STATUS'   => 'opened',
        '<=DEADLINE' => $deadline,
        '>DEADLINE'  => new \Bitrix\Main\Type\DateTime(),
        '=SLA_NOTIFIED' => 'N',
    ],
    'select' => ['ID', 'TITLE', 'RESPONSIBLE_ID', 'DEADLINE'],
]);

After retrieval — send notifications to responsible via \CEvent::Send() and set SLA_NOTIFIED = Y flag (requires custom field in ticket table or HL-infoblock for notification state storage).

SLA in Bitrix24 CRM (for e-commerce with CRM)

If customer inquiries managed in Bitrix24 CRM as Deals or via Open Lines module, SLA configured in CRM → Settings → Stages and Funnels. At each stage, set maximum time in deal — on exceed, deal highlighted red.

For automation use CRM Robots (module crm): robot "Notify responsible" conditional on deal idle time. No additional code — only admin interface.

Stage Time
Analyze inquiry categories and requirements 2–3 h
Create SLA and schedules 1–2 h
Setup auto SLA assignment 2–4 h
Develop deadline control agent 3–5 h
Test with real inquiries 2–3 h