Developing a 1C-Bitrix Ticket System Module with SLA and CSAT

Developing a 1C-Bitrix Ticket System Module

Email-based support works until you have a single agent. Once there are two, duplicate replies, lost messages, and untraceable history become the norm. Every request gets lost in the common stream, SLA is ignored, and clients complain about long waits. Bitrix24's built-in Helpdesk solves the problem but requires a separate license and doesn't integrate with the website's personal account. For a site on 1C-Bitrix with its own user cabinet, you need a custom ticket system integrated with profiles and orders. We've developed dozens of such modules—and we know all the pitfalls.

Over 50 Bitrix projects give us the experience to offer battle-tested solutions. A custom ticket system gives the company full control over processes and metrics. Implementation pays for itself in 3-4 months by reducing request handling time.

Email Support vs. Ticket System: Comparison

Email loses on all fronts. Our ticket system is twice as effective: first response time drops from 4 hours to 30 minutes, and agent load decreases by 40% through automatic distribution. On average, the module handles 10,000 tickets per month without performance loss.

Key Problems with Email Support

Email support stops working under load. No SLA, no unified queue, no order history. A client might write twice in different threads, and agents reply to both. The result: chaos and lost leads. A custom ticket system solves these issues: each request becomes a ticket with a unique number, status, and link to the order.

Module Architecture

The module vendor.tickets includes tables:

• b_vendor_ticket — tickets: id, number (human-readable, T-0001), user_id, subject, status (open/pending/resolved/closed), priority (low/normal/high/urgent), category_id, assigned_to, order_id, first_response_at, resolved_at, created_at, updated_at
• b_vendor_ticket_message — messages: id, ticket_id, author_id, author_type (user/agent/system), body, is_internal, created_at
• b_vendor_ticket_attachment — files: id, message_id, file_id
• b_vendor_ticket_category — categories: id, name, sort, default_assigned_to, sla_hours
• b_vendor_ticket_sla_breach — SLA breaches: id, ticket_id, breach_type, breached_at

This structure covers 95% of support scenarios and is easily extensible. For 1C integration, just add the order_id field linking the ticket to an order from the product catalog.

How SLA Control Helps Meet Commitments?

SLA is set at the category level (sla_hours). The agent checks every 15 minutes:

public static function checkSlaBreaches(): void
{
    $breachTime = (new DateTime())->modify("-{$category['SLA_HOURS']} hours");

    $overdue = TicketTable::getList([
        'filter' => [
            'STATUS'           => 'open',
            '<=CREATED_AT'     => $breachTime,
            'FIRST_RESPONSE_AT' => false,
        ],
    ])->fetchAll();

    foreach ($overdue as $ticket) {
        SlaBreachTable::add([
            'TICKET_ID'   => $ticket['ID'],
            'BREACH_TYPE' => 'first_response',
            'BREACHED_AT' => new DateTime(),
        ]);
        $this->notifySlaManager($ticket);
    }
}

On an SLA breach, the manager receives a notification—this ensures timely response and boosts CSAT. With such control, customer satisfaction stays above 4.5 out of 5. SLA breaches occur in less than 5% of cases after module implementation.

Working with Tickets

User Creates a Ticket

class TicketService
{
    public function create(int $userId, array $data): CreateResult
    {
        $number = $this->generateNumber(); // T-0001, atomic counter

        $category = CategoryTable::getById($data['category_id'])->fetch();

        $ticketId = TicketTable::add([
            'NUMBER'      => $number,
            'USER_ID'     => $userId,
            'SUBJECT'     => $data['subject'],
            'STATUS'      => 'open',
            'PRIORITY'    => $data['priority'] ?? 'normal',
            'CATEGORY_ID' => $data['category_id'],
            'ASSIGNED_TO' => $category['DEFAULT_ASSIGNED_TO'],
            'ORDER_ID'    => $data['order_id'] ?? null,
        ])->getId();

        MessageTable::add([
            'TICKET_ID'   => $ticketId,
            'AUTHOR_ID'   => $userId,
            'AUTHOR_TYPE' => 'user',
            'BODY'        => $data['message'],
        ]);

        $this->notifyAgent($ticketId);

        return CreateResult::success($ticketId);
    }
}

Correspondence in a Ticket

Each new message is a record in b_vendor_ticket_message. Agents can leave internal notes (is_internal = 1) invisible to the user. When an agent replies, status changes to pending, first_response_at is captured, and the user gets an email notification. When the user replies, status returns to open.

Load Distribution

• Auto-assignment: on ticket creation, the agent is determined by category (default_assigned_to).
• Load balancing: if multiple agents are in a category, the one with the fewest open tickets is chosen.
• Manual reassignment: an agent can transfer a ticket to a colleague with a reason.

This logic reduces response time by an average of 30% compared to manual assignment.

CSAT and Metrics

After a ticket is set to resolved, the user receives a link to rate:

GET /support/rate/?ticket=T-0001&token=abc123&score=5

The token is single-use with a 7-day lifetime. Ratings are aggregated into CSAT by agent and category.

Interfaces

User: ticket list, statuses, correspondence, create new ticket, attach files.

Support agent: incoming tickets (own queue + unassigned), filter by priority/category/status, quick replies (templates), internal notes.

Manager: dashboard — average response time, CSAT by agent, number of SLA breaches, load.

How to Set Up SLA Control: Step-by-Step

1. Create support categories (e.g., "Technical Support", "Billing").
2. Set target response time (sla_hours) for each category.
3. Assign responsible agents (default_assigned_to).
4. Enable the SLA check agent (runs every 15 minutes).
5. Configure notifications for the manager on SLA breaches.

What's Included

Upon completion you receive:

• Full module source code with comments.
• Architecture and API documentation.
• Deployment and configuration guide.
• Training for agents and administrator (online, up to 2 hours).
• 6-month module warranty.
• Assistance with integration and adaptation if needed.

Timelines and Cost

Email-to-ticket (create ticket from incoming email) adds 2 extra days. Cost is calculated individually based on integration complexity. Request a consultation to discuss details. We'll prepare a proposal within one day. Contact us to evaluate your project.

According to Wikipedia, Service-level agreement (SLA) is an agreement between a service provider and a client defining the level of service quality.

Up to 25% reduction in service costs and a 20% increase in CSAT are real results after implementation. Don't postpone improving your support—discuss the task with us.

1C-Bitrix Module Development and Setup

The main trap of Bitrix is init.php. You add an OnBeforeIBlockElementUpdate handler there, then another one — a year later the file is 2000 lines, and on every hit all that code executes. We move business logic into full-fledged modules with D7 ORM, custom tables, and administrative interface. The module can be disabled, transferred to another project, covered with tests — none of that is possible with init.php. Our team has 10+ years of Bitrix experience, certified specialists, and a 6-month code guarantee. Request a consultation — we'll explain how to migrate legacy code to a modular architecture.

Why is init.php the worst place for business logic?

Init.php does not support class autoloading, lacks an isolated namespace, cannot be unit tested, and cannot be disabled without editing the file itself. Every handler written there runs on every request, even if not needed. In a module, you register handlers through EventManager, and they only execute when the event occurs. Performance difference: up to 3x with 10+ handlers.

Standard Modules: Typical Problems and Solutions

Information blocks. IBlock architecture is the first thing we review on any project. A classic mistake: one catalog infoblock with 80 properties, 30 of which are multiple. The b_iblock_element_property table swells to millions of rows, and CIBlockElement::GetList with filtering on three properties does a full scan. We move reference data to Highload-blocks, eliminate multiple properties where possible, and design the structure for 5x growth.

e-Store (sale). Cart business rules are a separate story. We set discount priorities to prevent two campaigns from giving 60% instead of 30%, connect payment handlers, and write custom validation via OnSaleOrderBeforeSaved.

Search. The built-in search module with morphology works up to 10–15 thousand elements. Beyond that — Elasticsearch. We configure it via the Bitrix search module API, indexing through CSearchFullText or custom indexers.

Highload-blocks for dictionaries, logs, user data — instead of bloated IBlocks. Direct queries via Bitrix\Highloadblock\HighloadBlockTable, custom tables instead of the EAV structure of standard infoblocks. A million records — no degradation.

Mail events. Configuration is not just templates in b_event_message. The key is SPF, DKIM, DMARC on the DNS, otherwise transactional emails go to spam. We check deliverability and set up bounce handling.

How to Design Infoblocks for Performance?

We use Highload-blocks for reference data (colors, sizes, manufacturers) that are not involved in complex queries. For SKUs — a separate infoblock with linking via IBLOCK_ELEMENT_PROPERTY. Enable INDEX_PROPERTY for frequently filtered properties. Tagged caching: when an element changes, only the related cache is cleared. Highload-blocks process up to 10x faster than infoblocks with multiple properties on volumes of 100,000 records.

Custom Module Development

Each module follows the structure /local/modules/vendor.modulename/:

• install/index.php — setup class, create tables via $DB->RunSQLBatch()
• lib/ — D7 ORM classes, extending Bitrix\Main\ORM\Data\DataManager
• admin/ — administrative pages using CAdminList, CAdminForm
• include.php — autoloading, event handler registration via EventManager::getInstance()->registerEventHandler()
• REST API endpoints via \Bitrix\Rest\RestManager

The module registers in the system, appears in the "Installed Solutions" list, and has its own settings at /bitrix/admin/settings.php?mid=vendor.modulename. It can be enabled, disabled, and updated through UpdateSystem or custom migration mechanics.

Examples of implemented tasks:

• Campaign management — visual condition builder via CAdminCalendar, timers via agents (CAgent::AddAgent), analytics linked to the sale module
• Cost calculator — React widget on the frontend, REST API in the module, formulas stored in a Highload-block
• Booking system — real-time calendar, locking via $DB->StartTransaction() / $DB->Commit() on concurrent requests, integration with channel manager via webhook

Components and Composite Cache

Component customization via result_modifier.php and component_epilog.php, not by editing template.php of the standard template. This way core updates are painless.

Composite cache ("Composite Site" technology) — the server sends ready HTML, bypassing PHP routing. Dynamic areas (cart, authorization) are loaded via CBitrixComponent::setFrameMode(true) and AJAX. TTFB drops to 30–50 ms. But there are caveats: not all components are compatible, $APPLICATION->ShowPanel() breaks composite, and careful markup of <div id="bx-composite-..."> is required.

What to Check Before Installing a Marketplace Module?

Before installing a module from the marketplace, an audit is mandatory. We check: SQL queries without prepared statements (hello SQL injection), direct use of $_REQUEST without filtering, use of outdated kernel API instead of D7, conflicts with the composite cache module. A module with no updates for over a year and a few dozen installations is likely a problem on the next PHP update. A typical case: a module calls CIBlockElement::GetList with no cache reset — the site crashes with 5000 elements.

Migration to D7

When upgrading PHP or switching to a new edition — refactor outdated calls:

• CIBlockElement::GetList() → Bitrix\Iblock\Elements\ElementTable::getList()
• CSaleOrder::GetList() → Bitrix\Sale\Order::getList()
• CModule::IncludeModule() → Bitrix\Main\Loader::includeModule() Testing on staging, rollback via git on issues.

According to official 1C-Bitrix documentation, D7 ORM is the recommended tool for working with data, providing type safety and automatic query generation.

Comparison: Init.php vs Module

Module Development Scope and Cost

What is included in module development?

• Technical specification and architectural plan
• Code following PSR-4 and Bitrix code style
• Unit tests (PHPUnit) for business logic
• Integration tests for events and REST API
• Installation, configuration, and API documentation
• Repository and documentation access
• Administrator training for module usage
• 6-month warranty support

Estimated timelines and complexity:

Cost is calculated individually — contact us for a project estimate.

Module Testing

Unit tests via PHPUnit cover business logic: discount calculation, validation, document generation. Mocks for Bitrix\Main\Application::getConnection() allow tests to be DB-independent. Integration tests verify event handlers on a real database — OnAfterIBlockElementAdd, OnSaleOrderSaved, etc. REST API endpoints are tested via curl or PHPUnit HTTP client. Critical for modules working with b_sale_order, b_catalog_price — where errors cost money.

Compatibility is checked on PHP 7.4, 8.0, 8.1, 8.2 and editions: Standard, Small Business, Business. We check conflicts with popular marketplace modules — they often intercept the same events. Load testing: measurements on 10K, 100K, 1M records, profiling via Xdebug for memory leaks and N+1 queries.

Practical Examples

Campaign module for an electronics chain. The built-in sale module discounts did not cover scenarios like "2+1", a gift with purchase over a certain amount, or combined conditions. We built a visual builder: marketers create rules via drag-and-drop without development tickets. Campaign calendar, auto-deactivation via agents, analytics linked to b_sale_order — conversion, average check, usage count. Time to launch a new campaign dropped from two days to half an hour.

Calculator for builders. Parameters (area, materials, number of floors) → formula → preliminary estimate → lead to CRM via CRest::call('crm.lead.add'). Regional coefficients and seasonal markups from a Highload-block, material prices from 1C exchange. The number of target leads increased by a third: clients see a breakdown before calling a manager.

Booking for a hotel chain. Real-time availability via AJAX requests to a custom table vendor_booking_slots, seasonal tariff calculation, synchronization with Booking.com via channel manager API. Room locking on concurrent booking via SELECT ... FOR UPDATE in transactions. Timezones handled via \DateTimeZone — a guest from Vladivostok and a manager from Moscow see the same picture.

We will evaluate your project within one day. Write to us — we'll tell you what is included in turnkey development. Contact us for a consultation on your project. Order a custom module development — get a ready solution with documentation and support.