SLA Configuration for Customer Inquiries in 1C-Bitrix
With over 5 years of expertise and 50+ successful Bitrix integrations, we guarantee reliable SLA setup. Imagine: a customer returns a defective product, creates an inquiry at 10:00, but gets a response only at 18:00. SLA violated — you lose loyalty and risk fines. In 1C-Bitrix, you can solve this by setting up Service Level Agreements (SLA) — clear rules for response and resolution times for each inquiry category. Without automation, operators drown in chaos and critical requests get lost.
Proper SLA setup is not just about setting numbers: you need to account for work schedules, holidays, priorities, and integration with business logic. We tailor SLA for your business on the support module or in Bitrix24 CRM, with automatic deadline control. According to our practice, correct setup reduces average response time by 40% and increases customer satisfaction (CSAT) by 30%, while support operating costs drop by up to 35%. For a client handling over 200 inquiries daily, we cut response time from 4 hours to under 1.5 hours, saving them $1,500 per month. Our SLA audit costs $300 and identifies savings potential. Get a quote in 2 hours and eliminate delays. Contact us for an audit of your current SLA.
Common SLA Setup Problems We Solve
- No automatic SLA allocation — inquiries sit without priority, operators don't know what's urgent. We set up binding to category, source, and priority.
- Deadlines aren't tracked — lack of alerts leads to delays. We develop an agent that notifies one hour before deadline expiry.
- Difficulties integrating with CRM — deals get stuck on stages. We use CRM robots and custom funnels for automatic control.
Avoiding Common SLA Setup Mistakes
The most frequent miscalculations: too short response time without considering real load, ignoring holidays, and lack of testing. We recommend building in a 20% buffer on real response time. We always fill in the holiday calendar—otherwise the agent calculates workdays incorrectly. After setup, we manually run through 10–20 inquiries to ensure auto-assignment works and notifications arrive.
Importance of Proper SLA Setup
Misconfiguration leads to chaos: hot inquiries get delayed responses, while simple requests block operators. Time lost on manual ticket management can reach 40 hours per month, translating to average cost savings of $1,200 per month when automated. Correct SLA automation distributes load and guarantees service commitments.
SLA Configuration Bitrix: Support Module vs CRM
The choice of platform depends on ticket volume. Official 1C-Bitrix documentation recommends the support module for high-load ticket systems and CRM for small businesses. Compare:
| Parameter | Support Module | Bitrix24 CRM |
|---|---|---|
| SLA Flexibility | High (categories, groups, events) | Medium (stages, robots) |
| Automation | Agents, custom scripts | No-code robots |
| Funnel Integration | Weak | Full |
| Recommended Volume | >100 tickets/day | <100 tickets/day |
In practice, the support module suits large stores (complex SLA, multiple categories), while CRM suits startups needing quick setup without coding. In our experience, the support module processes ticket SLA assignments 2.5x faster than CRM-based funnels for over 200 daily inquiries.
Step-by-Step Guide to SLA Setup:
- Analyze current ticket categories and response times.
- Define SLA rules with work schedules and holiday calendar.
- Implement auto-assignment via event handler or CRM robots.
- Set up deadline monitoring agent with notifications.
- Test with sample inquiries and adjust thresholds.
How Auto-Assignment Works via Event
On ticket creation, OnSupportTicketAdd fires. We subscribe to the event and override SLA_ID:
Code Example
```php \AddEventHandler('support', 'OnSupportTicketAdd', function(&\$arFields) { // If category "Defect/Return" — set SLA with 2-hour response if (\$arFields['CATEGORY_ID'] == RETURN_CATEGORY_ID) { \$arFields['SLA_ID'] = 3; // ID of the required SLA } }); ```How to Monitor Deadline Breaches
Bitrix does not send alerts. Our agent runs every 5 minutes and checks inquiries whose deadline expires in one hour:
// Agent: find inquiries with expiring deadline \$deadline = new \Bitrix\Main\Type\DateTime(); \$deadline->add('1 hours'); \$inquiries = \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 selection, we send notifications via \CEvent::Send() and set a flag. We use an HL-block to store notification state to avoid duplicates.
Work Process
| Stage | Description | Duration |
|---|---|---|
| Analysis | Review categories, sources, current issues | 2–3 hours |
| Design | Create SLA scheme: response time, resolution, schedules | 1–2 hours |
| Implementation | Configure SLA in support module or CRM, write agent | 4–8 hours |
| Testing | Check with real inquiries, adjust | 2–3 hours |
| Documentation | Hand over instructions, logs, accesses | 1 hour |
What's Included
- Full SLA setup in the support module or CRM.
- Custom deadline control agent development.
- Notification setup for responsible parties.
- Documentation on SLA management.
- 2 hours of post-deployment support.
- Starting from $500 for standard configuration; SLA audit service: $300.
Common SLA Setup Mistakes
- Too short response time — operators can't handle the flow, delay increases. We recommend a 20% buffer on real time.
- Ignoring holidays — SLA missing non-working days leads to false breaches. Always fill the calendar.
- Lack of testing — after setup, manually run 10–20 inquiries; otherwise the agent might fail.
We configure SLA turnkey. Trusted by 50+ clients since 2018. Get a quote in 2 hours — contact us. Save up to 40 hours monthly through automation. Reach out for an audit of your current SLA.