Lost a big order because a client's call reached a trainee who didn't know the product? A familiar situation: incorrect routing is one of the common causes of lost leads. According to statistics, up to 30% of clients don't get through to the sales department due to misconfigured queues or IVR. We set up Bitrix24 telephony considering your business processes so every call reaches the right specialist. Our experience — over 10 years and more than 50 successful projects, including integrations with 1C, CDEK, amoCRM. Using IVR you can automate greetings and route calls to the right department without an operator. This reduces the load on the secretary and speeds up call processing by 40%.
Basic Routing Schemes
For each connected number in Bitrix24, its own scheme is configured. Let's look at the main options.
| Scheme |
Description |
When to Use |
| Queue (sequential) |
Call goes to the first available employee. If unanswered for 15-30 sec, moves to the next. |
Sales department, support with load distribution |
| Parallel ring |
Calls all group employees simultaneously. Whoever picks up first gets the call. |
Small teams where speed matters (30-50% faster than queue) |
| By responsible manager |
If the caller has a contact in CRM with a responsible person, the call goes directly to them. |
Client base with assigned managers |
| Random employee |
Even distribution of load without considering availability. |
Operators with equal competence |
How to Set Up Routing by Responsible Person in CRM?
The most valuable feature for repeat inquiries: a regular customer always reaches their manager. Configuration: 'Telephony' → 'Settings' — enable 'Forward to responsible'.
Logic:
- Bitrix24 searches for the phone number in CRM.
- Finds the related record (contact, company, deal).
- Determines the responsible person for the record.
- If the responsible person is online, routes the call to them.
- If unavailable, applies a fallback scheme (queue or specific employee).
Important: this scheme requires a clean CRM database. Check that each contact has no duplicates and the correct responsible person is assigned.
Why Do Calls Drop into Void?
A common problem — the call doesn't find a free operator. Reasons: incorrect rule priority, employees in 'Do not disturb' status, or schedule not set. Priority of routing rules:
- Working hours check (if outside working hours — all other rules are not applied).
- Routing by responsible person (if enabled).
- IVR — voice menu.
- Default queue.
We recommend setting a fallback scheme for when all operators are busy: for example, forwarding to an answering machine with a promise to call back.
How to Set Up Routing by Schedule?
Working and non-working hours are handled by different schemes. In the number parameters:
- Working hours → sales department queue.
- Non-working hours → answering machine or forwarding to on-duty.
- Holidays → separate voice message.
The schedule is set for each day of the week. Holidays are added manually or via import — in some Bitrix24 versions there is auto-import.
Example setup for a sales department of 5 people
We use a sequential queue with a 20-second timeout. If all operators are busy, the call is transferred to an IVR with an option to leave a message. After working hours, an on-duty number is activated. This scheme increased the call completion rate from 60% to 95% in one of our projects.
What's Included in the Work
We provide a full range of services for setting up call routing. As a result, you get:
- Audit of current telephony infrastructure and CRM database.
- Project documentation with diagrams and IVR scenarios.
- Implementation of rules, queues, and schedules.
- Testing with sample calls and CRM verification.
- Instructions for operators and administrators.
- One month of post-launch support with monitoring and adjustments.
- If needed, integration with external services (1C, CDEK, YooKassa).
Timeline and Cost
Setup time depends on the complexity of the scheme. A basic configuration takes 3 to 6 hours. Complex projects with IVR and integrations — 1-3 business days. The cost is calculated individually and pays off by reducing lost calls and increasing conversion. Official Bitrix24 telephony documentation.
Contact us for a free audit — we'll assess your current infrastructure and create an improvement plan. Order setup with a guarantee that calls will reach the right employee on the first try. Savings on telecommunications can reach 35% after implementing proper routing.
Turnkey Telephony Setup: From SIP to CRM
SIP trunk not registering — the first problem when connecting telephony to Bitrix24. The client sends provider data, you enter it in "Telephony → Telephony Settings → SIP Connector", and the status hangs "Waiting for registration". Ports 5060/5061 for SIP and range 10000–20000 for RTP are blocked on the firewall — classic. Or codec G.729 is not supported, and G.711 consumes 87 kbit/s per line. For 20 simultaneous conversations — count yourself. We connect and configure telephony so that calls are not lost, routing works according to business logic, and CRM receives data automatically.
SIP (Session Initiation Protocol) — standard for voice communication over the internet. Our specialists have 5+ years of experience integrating with Bitrix24. Warranty on configured solutions — 1 year. Contact us for a free audit of your current infrastructure — we often find blind spots: missed calls without tasks, managers with status "On line" and zero calls, IVR branches that no one reaches.
How to Avoid Failures in SIP Registration and Connection?
Improper NAT, closed ports, or incompatible codecs — 90% of failures. We check codec support on the operator's side, configure keepalive and backup SIP servers. After setup, registration stays stable for months.
You already have a contract with an operator, and changing numbers is not an option. We connect to Bitrix24 via SIP connector. For stable operation, you need a channel: at least 100 kbit/s per line for G.729, 87 kbit/s for G.711a.
Typical tasks:
- City numbers from any operator — preserved when switching to B24
- 8-800 numbers for inbound — routing via CRM
- Multi-line numbers with department distribution via IVR
- Analog lines via Grandstream or Linksys VoIP gateways
Where it usually gets stuck:
- SIP/RTP ports are closed at the provider or router level
- NAT not forwarded correctly — one-way audio
- Different codecs on the PBX and Bitrix side — no audio at all
We solve these problems in 1–3 days, not weeks.
Step-by-step instructions for connecting via SIP trunk:
- Check SIP (5060/5061) and RTP (10000–20000) ports are open on the firewall.
- Agree on codecs: G.711 or G.729 — test both options.
- Configure SIP connector in Bitrix24 admin: login, password, provider domain/IP.
- Enable keepalive (30–60 second interval) for stable registration.
- Test two-way audio with a test call.
- Configure backup SIP server in case of primary failure.
Cloud PBX or SIP Trunk: Which to Choose?
Cloud PBX requires no hardware — set up in 1–2 days. SIP trunk retains your numbers and allows a hybrid scheme with an on-premise PBX. Cloud PBX is configured 2-3 times faster and saves up to 40% of budget compared to maintaining your own infrastructure. Compare providers based on real cases.
| Provider |
Real Benefit |
Pitfalls |
| Bitrix24.Telephony |
Built-in, setup via portal UI |
Tied to B24 tariff, more expensive at scale |
| Sipuni |
Native module for B24, quick integration |
Limited number geography |
| Mango Office |
Powerful analytics, speech analytics included |
Above-market price |
| UIS (CoMagic) |
Call tracking + PBX all-in-one |
Complex admin panel |
| Zadarma |
70+ countries, budget-friendly |
API sometimes slow, support slow |
| MegaFon PBX |
FMC — mobile as office |
SIP setup via support, not UI |
| MTT |
Flexible tariffs, good API |
No native module for B24 |
| Rostelecom |
Stability, government sector |
Slow setup, bureaucracy |
Why Do You Need Call Recording and How to Set It Up?
All incoming and outgoing calls are recorded automatically. Storage — Bitrix24 cloud (tariff limited) or your own server via the voximplant module. Each recording is attached to a CRM card: contact, deal, lead. Listening — from the deal timeline.
Control tools:
- Recording notification — mandatory under 152-FZ, configured in IVR
- AI transcription — speech recognition via built-in CoPilot module or external service. Converts calls to text, searchable by keywords
- Sentiment analysis — system flags negative calls. Not a replacement for listening, but filters 90% of routine
- Selective recording — only incoming, only specific departments
- Automatic duration control — calls shorter than 15 seconds almost always indicate a problem: dropped, not reached, manager didn't pick up
Manager sees summary reports: number of calls per manager, average duration, missed calls without callbacks. The last point is the most painful: a missed call without a callback task equals a lost client.
Typical Routing Mistakes
Routing is the most fragile part. Set up "in order", but the manager logged in and went to lunch — the call hangs for 40 seconds and drops. Or IVR with five nesting levels — the client hangs up on the third. We use working distribution scenarios:
- By CRM responsible — number found in database, call goes directly to manager
- In order — even load among operators with "On line" status
- By departments via IVR — voice menu, max two levels. More means lost calls
- By time — working/non-working hours, weekends
- By region — detected by number code, distributed to local managers
On incoming call, the system performs:
Number found in CRM:
- Route to responsible manager
- Pop-up card: name, company, open deals, contact history
- If manager doesn't answer within 15 seconds — forward to colleague, then to supervisor
Number not found:
- Automatically creates a lead in CRM (setting
Telephony → CRM Integration → Create lead for unknown number)
- Call distributed by queue
- All information recorded for later processing
How to Automate Work with CRM Integration?
Pop-up card on incoming call shows:
- Name, company, position
- Current deals with statuses
- Last 5 interactions — calls, emails, chats
- Customer comments
- Buttons: "Create deal", "Set task", "Transfer call"
Automation via business processes is configured in "CRM → Robots and triggers":
- Missed call → lead + callback task for responsible
- Call end → record activity in deal timeline
- Missed without callback within 30 minutes → notify supervisor
- Incoming from client with overdue deal → escalation
Analytics available in "Telephony → Balance and statistics" and CRM reports:
- Number of calls by manager, department, direction
- Average duration and hold time
- Missed call percentage with weekly trend
- Call-to-deal conversion — most important metric for sales
How to Increase Conversion with Callback, Auto-dialer, and Voice Menu?
"Call me back" widget on website — one field (phone), nothing extra. The system calls the manager first, then the client. Each request automatically creates a lead in CRM. Anti-spam: limit requests from one number. A/B testing placement — widget bottom right converts better than left, but depends on design. Callback reduces missed calls by up to 30% compared to manual dialing.
Auto-dialer:
- Dial segment from CRM — manager connects after client answers
- Robotic dial with voice message — order confirmations, appointment reminders
- IVR scenarios: "press 1 to confirm"
- Scheduled with time zone awareness — module checks region by number code
Building a voice menu:
- Welcome message — company name, recording notice
- Department selection via DTMF — max 4–5 items
- Music on hold with queue position
- Non-working hours — voicemail or informational message
Recording by professional voice actor — worthwhile for greeting and main menu. Deeper levels — speech synthesis, easier to update.
Which codecs to choose for stable operation?
G.711 (A-law/µ-law) — standard codec, bandwidth 87 kbit/s per line. G.729 — compressed codec, 31 kbit/s. If bandwidth is limited, G.729 is preferred, but not all providers support it. Also possible G.722 (HD voice) — requires 64 kbit/s and PBX support.
What's Included in Telephony Setup?
Deliverables after project completion:
- Configured SIP registration (cloud PBX or SIP trunk turnkey)
- Working call routing (by CRM, queue, IVR)
- Call recording with cloud or server storage
- CRM integration: pop-up cards, auto lead creation, business processes
- Callback widget on website
- Voice menu (IVR) with voice actor recording or synthesis
- Configuration documentation and staff training (2 sessions)
- Technical support for one month after launch
Everything included in the comprehensive setup — no hidden extras. Order telephony setup and get a ready-made infrastructure for working with clients.
Setup Timeline and Pricing
| Task |
Timeframe |
| Cloud PBX + basic routing |
1–2 days |
| SIP trunk (if provider releases data quickly) |
1–3 days |
| Routing + IVR |
2–5 days |
| CRM integration: robots, triggers, cards |
3–5 days |
| Callback widget |
1 day |
| Comprehensive setup with audit |
2–3 weeks |
Pricing is calculated individually — depends on number of lines, routing complexity, and required integrations. Average budget for setup ranges from several thousand to tens of thousands in local currency depending on scope. We'll evaluate your project in 1 day. Start with a free audit of your current infrastructure — we often find blind spots: missed calls without tasks, managers with "On line" status and zero calls, IVR branches that no one reaches. Contact us for a consultation — we'll offer the optimal solution for your budget and business processes.