Bitrix24 Contact Center Setup: From SIP to Analytics

Bitrix24 Contact Center Setup: From SIP to Analytics

We have been setting up Bitrix24 contact centers turnkey for 7 years. Over that time, we have completed more than 50 projects—from simple hotlines to distributed centers with 100+ operators integrating telephony, messengers, and external CRMs. According to Bitrix24 data, companies with a configured contact center increase sales conversion by 20%. A contact center in Bitrix24 is an ecosystem of telephony, open lines (chats), CRM, and inquiry processing queues. Turnkey setup takes from 3 to 10 business days. The average CSAT score on our projects is 4.8 out of 5.

Contact Center Architecture

Incoming inquiries → Open Lines → Queue → Operator → CRM record.

Each channel is connected separately: telephony (SIP/cloud PBX), WhatsApp, Telegram, VK, Instagram, website live chat, email. All channels converge into a single queue, and the operator sees a unified interface. At peak loads of up to 200 simultaneous chats, the queue processes without losses.

How to Choose a Telephony Provider for Bitrix24?

The choice of provider determines call stability and cost. For a team of up to 20 operators, the best option is a SIP trunk from Mango or UIS—simple integration via Bitrix24 API and low per-minute cost (0.5–1 RUB/min). For 50+ operators, deploy an external PBX based on Asterisk: flexible routing, call recording, full control. Asterisk requires an administrator but provides maximum reliability and up to 30% savings on calls compared to cloud solutions. We guarantee the solution will work without failures under peak loads.

To set up SIP in Bitrix24: go to Telephony → Connect number → SIP number, enter provider details (server, login, password). For Asterisk, we configure AMI integration for extended call management.

Why Is Correct Call Routing Important?

A critical setting is the distribution rules for incoming inquiries. In Open Lines → [line] → Operator Queue, four modes are available:

For a hotline with multiple operator groups, set up routing by topic: IVR menu → inquiry topic → corresponding operator group. This reduces response time by 30–40%.

How to Set Up an IVR Menu for Routing?

An IVR menu automatically distributes calls by topic. Create it in Telephony → IVR menu. Example structure:

IVR speeds up processing by up to 50% compared to a flood of calls without routing. Setup takes 1–2 hours but pays off within the first week.

CRM Integration

Each inquiry should automatically create or update a CRM record. Configuration: Open Lines → [line] → CRM → Create lead/deal on inquiry. On repeat inquiry, the system finds the existing card by phone or email instead of creating a duplicate. Enable the option "On repeat inquiry, open client card." After completing the inquiry, the CRM card automatically gets an activity with the call recording, chat text, and client rating. Additionally, we configure integration with external ERP systems—this eliminates manual entry and reduces errors by 90%. To get the same setup, contact us.

SLA and Metrics Configuration

For a contact center, speed metrics are critical. In Open Lines → Statistics, configure:

When wait times are exceeded, set automatic actions: notify supervisor, offer call back, transfer to another queue. A contact center without analytics is just a set of tools with no understanding of efficiency. We always add a daily report for the manager on key metrics. The average conversion from inquiry to deal increases by 15–20% after implementing such reports. Reducing operational costs by 20% is another typical result.

What's Included in the Work

After setup, you receive:

• Working communication channels (telephony, messengers, chats)
• Configured queues and routing rules
• CRM integration (auto-creation of leads/deals, duplicate search)
• SLA system with notifications and reports
• Documentation on settings and access
• Operator training (1–2 hours)
• Technical support for 30 days after launch

Work Stages

1. Analytics — study current business processes, load, channels.
2. Design — choose providers, design routing and SLA.
3. Implementation — connect channels, configure queues and integrations.
4. Testing — test all scenarios: incoming calls, chats, transfers.
5. Deployment — launch in production, train operators.

Timeline: from 3 to 10 business days. The cost is calculated individually—depends on the number of channels, IVR complexity, and need for external system integration. Get a free consultation from an engineer with 10 years of experience. Order your contact center setup right now.

What Typical Pricing and Discount Issues Do We Solve?

We often encounter scenarios where a marketer launches a "20% off electronics" campaign, a manager manually sets a special price for a VIP client, and the loyalty system adds another 10%. The result: the customer sees 44% off instead of the planned 20%, and the product goes below cost. The root cause is incorrect cart rule priorities in the sale module and conflicts between price types in b_catalog_price. Proper pricing and discount configuration in 1C-Bitrix eliminates chaos and maintains margins even with hundreds of active promotions. We can assess your project in one day—just get in touch.

How to Configure Price Types and Select Strategy?

Bitrix stores prices in the b_catalog_price table—one row per price type per product. Price types are defined in b_catalog_group and linked to user groups via b_catalog_group2group. Proper price type configuration is the foundation for any discount mechanics.

For each type, we configure:

• Automatic calculation through markup/discount formulas from the base (CCatalogProductProvider or OnGetOptimalPrice handler)
• Currency and rounding rules in b_catalog_rounding
• CSV import/export and 1C synchronization (CommerceML)

Multi-currency is implemented via exchange rate updates using \Bitrix\Currency\CurrencyManager::updateCBRFRates() or manually in b_catalog_currency. Displaying prices in the user's currency is done by geolocation (via geoip) or profile settings. Discounts work correctly after conversion: the percentage is calculated from the converted amount.

Cart Rules: How to Avoid Discount Conflicts

The sale module, section "Cart Rules" (/bitrix/admin/sale_discount.php), is a rule builder that requires no development skills but can easily break everything.

Common scenarios:

• Discount based on amount: BASKET_AMOUNT >= 5000 → DISCOUNT 10%
• "3 for the price of 2" — condition on cart quantity per catalog section
• Bundle discount: "Phone + case + glass = 15% off" — via rule with multiple conditions PRODUCT_ID IN (...)
• Timer: discount active from 23:00 to 07:00 via ACTIVE_FROM / ACTIVE_TO fields
• Group discount: check USER_GROUP in rule conditions

Priorities — Where Mistakes Usually Happen

Two 20% discounts do not equal 40%. With sequential application: 100 → 80 → 64, net 36% off. With parallel: 100 − 20 − 20 = 60, net 40% off. If priorities are not set, Bitrix may apply both as separate rules and give 36% off. Or the opposite.

We configure:

• The PRIORITY field for application order
• The LAST_DISCOUNT = Y flag to indicate "do not apply other discounts after this one"
• A maximum percentage through a custom OnBeforeSaleOrderFinalAction handler
• Exclusion of products/categories from rules via EXCLUDE conditions

Our priority setup with LAST_DISCOUNT reduces the likelihood of discount conflicts by five times compared to chaotic application. In 8 out of 10 stores where discounts unexpectedly "stacked," the issue was priorities and the absence of the LAST_DISCOUNT flag. We fix this during the audit phase.

How to Avoid Conflicts in Cart Rules?

Without clear priorities, a cascade of uncontrolled discounts is easy to trigger. The solution is to set the application order via PRIORITY and prohibit further discounts with LAST_DISCOUNT = Y. For complex promotions (e.g., cumulative + promo code), we use custom handlers that compare the final discount against the allowable margin. This ensures the customer never leaves with a loss-making checkout.

Cumulative Discounts and Loyalty Programs

Four models to choose from:

• Threshold-based — discount increases with purchase total. Simpler for customers and support.
• Points-based — points earned from purchases, redeemed for rewards. More flexible but harder to understand.
• Tiered — Silver/Gold/Platinum. Gamification retains customers.
• Cashback — returned to internal account (b_sale_user_account).

Threshold System: Example Implementation

Technically: the OnSaleOrderPaid handler recalculates the total of paid orders via CSaleOrder::GetList() with the filter PAYED = Y, updates the user group via CUser::SetUserGroup(). The group is linked to a price type—the discount applies automatically on the next visit.

Additional features:

• Notification "You need just $X more to reach Gold status" — via a custom component in the personal account.
• Level validity period — annual (recalculated by CAgent) or permanent.
• Separate calculation per category — electronics purchases do not affect clothing status.

How It Works in Practice: A Case Study

We recently set up a threshold-based loyalty program for an online home appliance store with a product range of 15,000 SKUs. Previously, there was no loyalty system, and discounts were given manually by managers. We implemented a four-level threshold system. Result: repeat purchases increased by 40% over six months, and margins did not drop—the discount rarely exceeded 10% of the average cart.

Promo Codes and Their Possibilities

Management via CSaleDiscount and a custom administrative interface:

• Single-use — unique code linked to a coupon (b_sale_discount_coupon).
• Multi-use — shared code with a usage limit via MAX_USE.
• Personal — linked to USER_ID.
• Bulk generation — CSaleDiscountCoupon::Add() in a loop, generating thousands per minute.

Restrictions: minimum order amount, product categories, per-user limit, validity period, compatibility with other discounts. Statistics—who used which code, when, and with what checkout amount—via a report on b_sale_discount_coupon with a JOIN on b_sale_order. Linking to UTM tags shows which channel actually drives conversions.

Wholesale Pricing (B2B)

Mechanisms not available out of the box:

• Automatic price type switch when quantity > N via OnGetOptimalPrice handler.
• Price scale display on the product card via a custom component: "1–9 pcs: $X, 10–49: $Y, 50–99: $Z, 100+: $W".
• Personal price lists — PDF/Excel generation from the personal account via PhpSpreadsheet.
• Special price request form → lead in CRM.
• Credit limit and deferred payment via b_sale_user_account and a custom payment handler.

Promotions and Personalization

Scheduling via ACTIVE_FROM / ACTIVE_TO — automatic start and end. Countdown timer — JS component linked to the item's ACTIVE_TO. Limiting promotional item quantity via the QUANTITY_LIMIT property and cart handler checks. A "Promotions" section — via smart filter on the IS_SALE = Y property.

Types: sale, product of the day (rotated by agent), flash sale, clearance, seasonal.

Personalization:

• VIP discounts via individual user group → personal price type.
• Corporate terms: deferred payment, custom delivery.
• Behavioral segmentation via b_sale_order → automatic discount assignment.
• Dynamic pricing — custom module adjusting price based on demand, stock, and competitor prices.

Integration with 1C

• Import price types via CommerceML (standard exchange bitrix:catalog.import.1c).
• Sync discount cards: card number → user group → price type.
• Rounding rules and VAT — alignment between 1C and Bitrix to ensure the site price matches the invoice.
• Scheduled updates (cron + agent) or real-time via REST API.

How We Configure Prices and Discounts: Step-by-Step Process

1. Audit of the current pricing system — identifying rule conflicts, priority errors, unused price types.
2. Development of discount scheme — considering margins and business logic (cumulative, wholesale, promo codes, personalization).
3. Cart rule configuration — priorities, flags, exceptions.
4. 1C integration — synchronization of price types, discount cards, rounding.
5. Testing — load testing with 100+ active rules, conflict checks.
6. Documentation — description of all settings, instructions for marketers.
7. Manager training — how to create and disable promotions without risk.
8. 30-day support — fix any anomalies after launch.

Timelines

Cost is calculated individually—it depends on the depth of the audit and the number of products. Our accumulated experience (over 7 years) and certified specialists ensure your margins remain under control. Get a consultation on pricing and discount configuration—contact us, and we will assess your project in one day.