Client Konstantin writes to the chat for the third time in a day — each time to a different operator. He has to re-explain the problem, context is lost, response time increases. The result is frustration and switching to competitors. We, certified engineers with 5+ years of experience in Bitrix, configure routing so that each inquiry goes to the responsible manager. Order an open lines configuration — reduce response time to 15 seconds and lower operational costs by 25–30%. The average handling time for repeated inquiries drops by 40% with proper routing.
How Distribution Algorithms Work
In the open line settings under the 'Queue' section, three basic algorithms are available. Round-robin: the first inquiry to the first operator, the second to the second, and so on in rotation. Suitable for homogeneous load with interchangeable operators. Simultaneously to all: notification goes to all operators on the line — whoever answers first takes the chat. Ideal for a small team (2–4 operators) prioritizing speed. Responsible from CRM: if the client is already in the database and assigned to a manager, the chat is directed to that manager. If unavailable after 30 seconds, escalation to the next operator occurs. This algorithm halves the response time for repeated inquiries compared to round-robin. Configuration of routing starts with selecting the appropriate algorithm.
Why Escalation Matters
If an operator does not respond within a set time (configurable in 'Response waiting time'), the chat moves to the next in the queue. Recommended interval: 30–60 seconds. If still unanswered, the chat remains in the queue or is assigned to a backup operator. When maximum waiting time is exceeded, an auto-reply is configured: 'Leave your contacts, we will call you back.' Manual reassignment is available: the operator transfers the chat to a colleague directly from the interface, and the new operator sees the entire dialogue history. We guarantee that no inquiry will remain unanswered.
How to Set Up Routing by Topic
To separate flows (sales/support/complaints), use multiple open lines — one per type. The client selects the topic via:
-
Bot scenario in the welcome message — buttons like 'I want to buy', 'Problem with order' — each button transfers to a different line using
imopenlines.session.transfer.
-
Different channels — different phone numbers or chat links lead to different lines from the start.
-
Time-based routing — one line during working hours (live operators), another outside working hours (auto-replies + callback form).
If operators are divided into groups (by language, region, product), create multiple lines with different lineups. Dynamic routing by client attributes (VIP) is not natively supported — implemented via an external bot server that determines the client type through CRM and transfers the chat using imopenlines.session.transfer.
How to Manage Operator Status by Working Hours
Operator status ('online'/'break'/'offline') affects routing: busy or absent operators are skipped in the queue. Automatic status management is implemented in the 'Working Time Management' module (Timeman). At the start of the working day, the operator switches to 'online'; at the end, to 'offline'. This prevents situations where the operator has left but the status remains 'online'. Configuration: CRM → Contact Center → [line] → Operators → enable 'Use operator working hours'.
What Is Included in Turnkey Routing Setup
We analyze your business processes, design the distribution scheme, configure queues, escalation, and CRM integration. Timeline: 2 to 5 working days depending on complexity. As a result, you receive:
- Open line configuration with optimal algorithms.
- Documentation of settings and instructions for operators.
- Team training and go-live support.
- Real-time queue monitoring.
Stages of work:
- Analytics: review of inquiry types, load, existing processes.
- Design: selection of algorithms, line creation, bot configuration.
- Implementation: queue and escalation setup, CRM integration.
- Testing: verification of all scenarios, load testing.
- Deployment: operator training, launch, monitoring.
| Routing type |
When to use |
Impact on speed |
| Round-robin |
Homogeneous load, interchangeable operators |
Medium, even distribution |
| Simultaneously to all |
Small team (2–4 operators), speed important |
High, minimal response time |
| Responsible from CRM |
Repeat clients, personalization |
High, up to 2x faster for returning |
| Topic selection buttons |
Different inquiry types, different specialization |
Medium, requires bot setup |
| Groups/skills |
Large team, clear specialization |
High with proper distribution |
Typical Problems in Routing Setup
| Mistake |
Consequences |
Solution |
| Escalation not configured |
Chat stuck, client waits indefinitely |
Set timeout and auto-transfer |
| 'Simultaneously to all' algorithm for large team |
All operators get notifications, chaos |
Use round-robin or groups |
| Working hours not considered |
Operators receive chats after work |
Enable 'Use operator working hours' |
| Single line for all topics |
Operators not separated by skills |
Create multiple lines and configure bot scenario |
Real-Time Queue Monitoring
Supervisors see the current queue state: number of chats waiting, which operators are busy, how many minutes each client has been waiting. Available in CRM → Contact Center → Monitoring. Here you can also take over a chat or manually reassign it. We include this capability in every configuration.
Get a consultation on routing setup in Bitrix24 open lines — we will evaluate your project within one working day. Order an open lines configuration.
How to ensure CRM implementation success?
We have been working with Bitrix24 for over 10 years — during that time we have completed 500+ projects. Every second one starts with the same problem: a company buys CRM, sets it up "by the book," and three months later managers fill two out of twelve fields, deals stall at "Negotiations" for months, and management cannot extract analytics. The root is not bad software — it's the approach. CRM is configured without auditing real processes, without considering staff objections, and without a step-by-step automation plan. In this article — a step-by-step guide on how we avoid this.
All specialists are certified by 1C-Bitrix, the methodology is proven on hundreds of cases. 1C-Bitrix is a platform that, when paired with Bitrix24, provides real end-to-end analytics if configured correctly.
Reality of CRM implementations: 80% fail to deliver results
Why do employees sabotage CRM?
Managers are accustomed to Excel and notepads — they perceive CRM as total control. Our solution: involve key employees at the design stage, show personal benefits — automatic reminders, ready-made proposal templates, less routine. We train on real scenarios, not abstract examples. Resistance drops 4 times faster than with "command" implementation.
How to prevent incomplete data entry?
Mandatory fields are filled, others are ignored — familiar picture? We solve it on three levels:
- Set mandatory fields per funnel stage (only relevant data at each stage).
- Implement auto-fill from UTM tags, email parsing, data from open databases.
- Remove redundant fields — fewer fields, higher quality.
According to our practice, field optimization reduces omission rates by 70% within the first month.
How to design funnels correctly?
Too many stages, no transition criteria, duplicate stages — typical mistakes. We design the funnel based on reality: how sales actually work, not as written in textbooks. We use CRM data from the first 2 weeks of audit to identify real stages and loss points. This shortens the deal cycle by 25–40%.
What automation should be done first?
We set up robots and business processes from day one — so the team immediately feels the difference. For example, lead distribution, sending emails after status changes, creating tasks for colleagues. Companies that implement automation at the start achieve plan targets 3 months faster.
What Bitrix24 features accelerate sales?
- Inquiries from all channels (phone, email, messengers, forms) are captured automatically.
- Leads are created and distributed without manual intervention.
- Visual kanban with custom stages — drag a card to the next stage, an email is sent automatically, a task is created.
- Omnichannel: unified window for telephony, email, WhatsApp, Telegram, Viber, VK, Instagram, online chat.
- Robots and business processes: mailings, document generation, reminders, escalations — no coding required.
- Analytics: funnel, conversions, lead sources, manager workload, average handling time.
What does integrating a 1C-Bitrix website with Bitrix24 CRM provide?
Synergy of the two products yields measurable results, and we implement it through direct data exchange. Site forms transfer leads to CRM instantly with full UTM markup — you see where the client came from. Online chat connects via open lines: a visitor writes on the site, the manager responds from CRM. Orders in the store based on infoblocks v2.0 become deals with full purchase history, enabling cross-selling. Call tracking with number substitution links calls to advertising channels. We use CommerceML to exchange data with 1C Trade Management/ERP: nomenclature, stock balances, prices — synced via agents without manual intervention. End-to-end analytics collects advertising costs, visits, leads, sales in one report — ROI per channel. For non-standard logic, we use REST API and high-load blocks to store arbitrary data (e.g., tech support interaction history). In one project, we configured this bundle for a retail chain: 1C cash register integration with CRM created contacts automatically upon loyalty card purchase, and CRM marketing via Bitrix24 increased repeat purchases by 18% in six months.
How we set up CRM: the process
-
Audit. We analyze how sales work currently. Where are leads lost? Which channels bring clients? We form recommendations before technical implementation.
-
Design. Multiple funnels for different directions, custom fields, mandatory stages and transition conditions. Structure reflects the real process.
-
Integrations. Connect to website, telephony, email, messengers, Yandex.Direct, Google Ads, 1C.
-
Custom modules. When standard is not enough — applications for Bitrix24: specific reports, non-standard business logic, integrations with industry systems.
-
Migration. Transfer databases from amoCRM, Megaplan, Salesforce, HubSpot, Excel. Relationships, communication history, attachments — everything intact.
-
Training. Trainings tailored to your configuration, video instructions, documentation.
What is included in the work?
| Deliverable |
Description |
| Technical documentation |
Funnel scheme, robot settings, field structure, integration plan |
| Access and configurations |
List of integrations, API keys, logins/passwords (provided under NDA) |
| Team training |
2–3 webinars tailored to your configuration, video instructions, cheat sheets |
| Post-implementation support |
2 weeks of incident management + regular usage audits |
Cloud or on-premise: which to choose?
| Parameter |
Cloud (SaaS) |
On-Premise |
| Time to start |
1–2 days |
1–2 weeks |
| IT requirements |
None |
Server and admin required |
| Data control |
Limited |
Full |
| Customization |
Standard limits |
Unlimited |
| Best for |
Teams up to 100 people, standard processes |
Large companies, strict security requirements |
Comparison: the cloud version is 2–3 times cheaper initially, but for B2B companies with large data volumes, on-premise pays off in 1.5–2 years due to no per-user subscription fee.
Metrics we track for your business
-
Funnel stage conversion. If 80% are lost at the proposal stage — the problem is pricing, not managers. Norm: 5–15% for B2B, 1–5% for high-ticket B2C.
-
Lead response time. A 5-minute response increases conversion 10x compared to a 30-minute response. We set alerts — if a manager doesn't respond within 15 minutes, the lead is reassigned.
-
LTV. CRM segments clients by lifetime value — managers focus on the most valuable.
-
Average deal cycle. If it increases, something is broken. Reasons for rejections are gold for product and script adjustments.
Our case studies
Manufacturing company (B2B). A plant with high annual turnover. Leads were lost in email; management only learned about large deals post-factum. We set up automatic inquiry capture, a funnel "qualification → calculation → proposal → approval → contract → payment," and robots that generate proposals from templates. Conversion increased by 23%, lead processing time dropped from 4 hours to 20 minutes. Manager payroll savings exceeded $1,000 per month due to reduced routine.
IT service company. Three funnels: new clients, upselling, tenders. Auto-generation of contracts and invoices, integration with Jira — after signing, tasks automatically appear in the development department. Management received a weighted revenue forecast with 90% accuracy. The project paid off in 4 months.
Implementation timeline and cost
| Scale |
Timeline |
What's included |
| Basic |
1–2 weeks |
Funnel, telephony, email, database import |
| Standard |
1–2 months |
Custom funnels, automation, website and 1C integrations |
| Comprehensive |
2–4 months |
Multiple funnels, custom modules, training, end-to-end analytics |
The cost is calculated individually based on your scope of work. After implementation — tech support with SLA (response from 1 hour), regular usage audits, and feature development.
Ready to discuss your situation? Contact us — we'll conduct a free audit of your current CRM within 2 days and propose an implementation architecture with a result guarantee. Request a consultation — we'll show you in numbers how much you'll save with proper setup.