Incoming calls get lost without proper routing. Clients can't get through, managers manually search for contacts — business loses orders. We configure Bitrix24 telephony so every call becomes a manageable event: the system identifies the number via CRM, directs it to the right employee, creates a lead, and records the conversation. Proper setup reduces call handling time by 30% and boosts conversion to deals up to 25%. We have extensive experience with successful telephony integrations; moving to a SIP trunk provides significant savings on communication costs.
How to set up Bitrix24 telephony in one day?
Setting up Bitrix24 telephony starts with connecting a number. There are three ways:
-
Bitrix24 number — the fastest: rent a number directly in the Telephony → "Connect number" section. Bitrix24 provides Russian city and 8-800 numbers. The cloud PBX handles all calls; no external systems are needed. Setup takes 15 minutes.
-
SIP trunk from your provider — connect an existing number via SIP. In Telephony → "SIP connector", add your SIP account details: host, login, password, port. Typical setup with ready data takes 30–60 minutes.
-
Telephony app — for cloud PBXs (Mango, Sipuni, Zadarma), install the app from the marketplace. It registers the external PBX as a call source in Bitrix24.
SIP trunk parameters for connection:
Host: sip.provider.ru
Port: 5060
Login: user number
Password: provided during registration
Protocol: UDP/TCP
SIP trunk or telephony app: which to choose?
If you already have a number and want to keep it, choose a SIP trunk. It gives full control over routing and no monthly fee. A telephony app is convenient when you need advanced analytics from the cloud PBX, but you pay a subscription. We help you choose the option that fits your budget and infrastructure. SIP trunk setup is twice as fast as an app, and long-term it is 40% more economical. IVR menu improves call distribution accuracy threefold compared to manual transfer.
| Criteria |
SIP trunk |
Telephony app |
| Monthly fee |
No |
Yes (subscription) |
| Routing control |
Full |
Limited by PBX capabilities |
| Setup speed |
30–60 minutes |
10–20 minutes (installation) |
| Analytics |
Basic (recording, statistics) |
Extended (PBX reports) |
Inbound call routing
After connecting the number, configure where the call goes. In Telephony → Settings, for each number set the processing scheme:
| Option |
How it works |
When to use |
| Specific employee |
Call goes to one person |
Direct line for manager |
| Queue |
Call sequentially rings available employees |
Sales department, support |
| Simultaneous ring |
Everyone rings at once, first to answer takes it |
Small team |
| IVR |
Voice menu with department selection |
Multiple departments or complex structure |
Business hours. Each number has a schedule: work hours, weekends, holidays. Outside work hours — voicemail with the option to leave a message or forward to another number. In one project we configured night mode with forwarding to a senior manager — missed calls dropped by 40%.
How to avoid missed calls outside working hours and on holidays?
In the telephony configuration, you can set multiple time intervals: work hours, lunch break, weekends, and holidays. Bitrix24 supports importing custom holidays via CSV. We recommend different scenarios: during work hours — a queue, outside — IVR with voicemail that converts to a task.
Why is CRM integration important?
On an inbound call, Bitrix24 searches for the caller's number in the database:
- If a contact/company is found — the card opens for the responsible manager.
- If a deal is found — the deal card opens.
- If not found — a new lead is created (if auto-creation is enabled).
Auto-creation setup: Telephony → Settings → "Create lead on missed/new call". This automates the first contact and reduces response time to 5 seconds. We also configure call recording and linking to CRM entities — you always see the communication history.
How we do it: a real case
From our practice: an e-commerce store with 10 sales managers. Problem: calls were lost, clients waited over 3 minutes. We connected a SIP trunk from MTS, set up three-level IVR, established a queue with a maximum wait of 30 seconds, and enabled auto lead creation. Result: response time dropped to 20 seconds, conversion to orders increased by 20%. Call recordings helped identify frequent objections and improve sales scripts.
What's included in telephony setup
- Connecting the number (rental, SIP trunk, or app)
- Configuring routing (IVR, queue, simultaneous ring)
- CRM integration (auto lead creation, contact linking)
- Call recording and storage in CRM
- Employee training and documentation handover
- Technical support for 2 weeks after delivery
Process
- Analysis — study current call scheme, load, requirements.
- Design — choose connection method, design routing.
- Connection — configure SIP or app, register numbers.
- Configuration — set up IVR, queues, schedule, auto-creation.
- Testing — check all scenarios: inbound, outbound, transfer, recording.
- Training — instruct employees, hand over documents.
Timelines and cost
Basic setup of one number takes 1–3 hours. For projects with IVR, multiple numbers, and CRM integration — up to 2 days. Cost is calculated individually. Guarantee on setup — 2 weeks after delivery. Get a consultation from a certified engineer — we'll evaluate your project in one day. Contact us to start. Order telephony setup and receive 2 weeks of free support.
After setup, be sure to check:
- All calls are correctly routed.
- Leads are created for missed calls.
- Calls are recorded and linked to the correct entities.
- Business hours schedule and night mode work.
- Notifications for missed calls are configured.
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.