How Bitrix24 Telephony Integration Works
Bitrix24 telephony integration links your phone system to CRM records so that every inbound and outbound call is automatically captured as a lead, logged in the contact or deal card, and recorded for quality review — without any manual data entry.
At its core, the integration does three things:
- Maps employee phone numbers to Bitrix24 user accounts — so the system knows which manager made or received each call.
- Routes inbound calls to the manager responsible for that contact, based on the CRM ownership record.
- Attaches call recordings to the relevant contact, company, or deal card automatically.
There are two fundamentally different connection paths, and choosing the right one early saves significant rework later.
| Path | How it works | Who controls routing logic |
|---|---|---|
| Native Bitrix24 telephony | Bitrix24 acts as the SIP provider via its built-in SIP Connector | Bitrix24 admin panel |
| Third-party VoIP/PBX | Your existing cloud PBX connects via API or a connector app | The telephony provider's side |
When you integrate a third-party provider, the call distribution logic (queues, schedules, IVR menus) stays on the provider's platform. What the Bitrix24 implementation covers is the CRM side: account mapping, lead creation rules, and recording storage.
Choosing Your Connection Method: Native SIP vs Third-Party PBX
The right connection method depends on your team size, line capacity requirements, and whether your existing provider supports a Bitrix24 integration — the native SIP Connector is the fastest to set up but has a hard limit of 10 simultaneous lines.
Native Bitrix24 SIP Connector
Bitrix24's built-in SIP Connector lets you attach a SIP-enabled carrier directly to the portal. Calls work entirely inside the browser or mobile app — no separate softphone is needed.
Outbound call scenarios: - Browser click-to-call — click a phone number in any CRM card; the call opens in the browser window within Bitrix24, no third-party app required. - Mobile app click-to-call — tap the number in the Bitrix24 mobile app; the softphone launches automatically and dials the client.
Inbound calls arrive directly in the browser or mobile app.
Key constraints to plan for: - The SIP Connector carries an annual subscription cost (price varies by region; confirm with your Bitrix24 partner). - Maximum 10 simultaneous lines — if your contact centre handles more concurrent calls, the native connector is not suitable.
Third-Party Cloud PBX
Cloud PBX providers (such as Mango Office, Sipuni, MTS, or any Asterisk-based system) integrate with Bitrix24 through dedicated connector applications. The integration handshake is typically a 3–8 hour task on the Bitrix24 side, while routing rules, IVR trees, and call queues remain configured in the PBX admin panel.
Pre-integration checklist: - Confirm with your telephony provider that a Bitrix24 integration is available in your region. - Ensure your plan includes a virtual PBX — this is a separate feature that may carry an extra monthly fee from the provider. - For each phone number you connect, the integration service typically charges a per-number subscription; this cost is separate from the implementation fee.
Always use corporate phone numbers and accounts for the integration — not personal employee numbers. Personal accounts create compliance risk and complicate offboarding.
Call Tracking: Automatic Lead Creation and Call Logging
Every call — inbound or outbound — can trigger automatic lead creation in Bitrix24, with the call recording, duration, and timestamp attached to the CRM card the moment the call ends.
This is the highest-value outcome of telephony integration for sales teams. Based on our project work, the standard configuration covers:
- Automatic lead creation for inbound calls from unknown numbers
- Auto-attachment of calls to existing contact/company cards for known numbers
- Call recording stored in the deal or lead card if the call was initiated from one
- Call log in the contact timeline — agent name, direction (inbound/outbound), duration, recording link
What gets logged automatically
| Event | Where it appears in Bitrix24 |
|---|---|
| Inbound call from new number | New Lead created automatically |
| Inbound call from known contact | Activity added to Contact/Company card |
| Outbound call from deal card | Activity logged in Deal + recording attached |
| Missed call | Activity with "missed" status; can trigger robot/automation |
Some providers give managers the option to toggle call recording per outbound call (on/off before dialling). This is a provider-side feature — confirm availability with your specific carrier before relying on it.
IVR Setup and Inbound Call Routing
IVR menus and call queues are configured on the telephony provider's side, not inside Bitrix24 — the CRM side handles only the final routing rule: which Bitrix24 user account receives the call.
This distinction matters operationally. Your IVR tree (press 1 for sales, press 2 for support) lives in the PBX admin panel. Bitrix24 receives the call already routed and applies CRM logic on top:
- Route to the responsible manager for that contact (if one is assigned in CRM)
- Fall back to a queue or group if the responsible manager is unavailable
- Trigger a missed-call robot to create a callback task if no one answers
A practical routing flow
The diagram below shows how inbound calls travel from the PSTN through the cloud PBX, get IVR-sorted, and land in Bitrix24 where CRM routing and recording take over.
The flow begins at the PSTN (public phone network), passes through the cloud PBX where IVR menus and call queues are applied, then reaches the Bitrix24 CRM layer where the responsible manager is identified, the call is recorded, and a lead or activity is created automatically.
flowchart LR
PSTN[Incoming Call\nPSTN] --> PBX[Cloud PBX\nIVR / Queue]
PBX -->|SIP / API| B24[Bitrix24]
B24 --> ROUTE{Responsible\nManager?}
ROUTE -->|Known contact| MGR[Assigned Manager]
ROUTE -->|Unknown number| QUEUE[Round-robin Queue]
MGR --> REC[Call Recording\nAttached to Card]
QUEUE --> REC
REC --> LEAD[Lead / Activity\nCreated]
Lead Distribution Automation for High-Volume Teams
For contact centres with 30 or more agents, Bitrix24 can automate lead distribution with SLA timers — for example, a 2-minute callback deadline — using robots triggered by telephony events.
Based on our implementation experience with large inbound teams, a well-designed distribution setup includes:
- Round-robin or weighted distribution across agents (configurable coefficients: 1 = equal share, 0.5 = every other lead, 0 = agent paused)
- Availability checks before assignment: is the agent's workday started? Are they below their active lead/deal threshold?
- Fallback assignment to a supervisor or queue if no eligible agent is found
- Auto-dial trigger with a defined SLA window (e.g., 2 minutes from lead creation to first call attempt)
Typical implementation effort for this automation layer: 8–10 hours, separate from the basic telephony connection.
Distribution conditions you can check in the automation logic:
| Condition | Example threshold |
|---|---|
| Workday started / not on break | Required |
| Active leads in progress | ≤ 10 (adjustable) |
| Deals in "in progress" status | ≤ 5 (adjustable) |
| Distribution weight | 1.0, 0.5, 0.3, or 0 (disabled) |
For teams building out the full CRM pipeline alongside telephony, see our Bitrix24 implementation hours reference by module — it includes telephony, automation, and distribution tasks with typical hour ranges.
Number Privacy and Access Control
Restricting which users can see client phone numbers is technically possible in Bitrix24, but the scope and method depend heavily on exactly which interface elements need to be masked — and this should be defined in the technical specification before implementation begins.
Privacy controls for phone numbers can apply to:
- CRM cards (contact, company, lead, deal)
- List views and kanban boards
- Tasks and activities
- Deal/lead detail pages
The implementation approach depends on whether number masking is handled inside Bitrix24 through role-based access or whether the telephony provider (e.g., a cloud PBX with number substitution) handles it. The two paths have very different complexity and cost profiles:
- Bitrix24 role-based masking: Configuring visibility rules across all relevant interface locations typically requires 25+ hours of implementation work, as the scope must be agreed per location and per role.
- Provider-side number substitution: If the PBX provider supports number masking natively, the Bitrix24 configuration overhead is lower (approximately 6 hours for integration of that feature).
The final approach is determined during the analytics/discovery phase — not mid-project. Before scoping, review your Bitrix24 onboarding questionnaire to capture all access-control requirements upfront.
Implementation Scope and Typical Timelines
A basic telephony connection — provider linked, calls mapped to CRM cards, recordings attached — typically takes 3 to 8 hours; a full setup with distribution automation, IVR coordination, and number privacy adds 25–40 hours on top.
Here is a realistic breakdown based on our project data:
| Work item | Typical effort |
|---|---|
| Cloud PBX connection to Bitrix24 (basic) | 3–5 hours |
| Call-to-lead and call-to-card mapping | Included above |
| Lead distribution automation (30+ agents) | 8–10 hours |
| SLA / auto-dial setup | Included in distribution |
| Number privacy / access control | 6–25+ hours (scope-dependent) |
| Testing and team training | 8–10 hours |
Keep in mind: the integration service fee charged by the telephony provider per connected number is separate from implementation costs. Budget for it when planning total cost of ownership.
For a broader view of what drives Bitrix24 project budgets, see Bitrix24 implementation cost and timeline data.
AI-Powered Call Analysis After Integration
Once calls are recorded and stored in Bitrix24, AI transcription and quality scoring can be layered on top — turning every conversation into structured coaching data without manual review.
With telephony fully integrated, each recorded call becomes an input for:
- Automatic transcription (speech-to-text)
- Keyword and sentiment detection
- Script compliance scoring
- Manager performance dashboards
This is handled by Bitrix24's native AI tools or third-party modules connected via the open API. The telephony integration is the prerequisite — recordings must be attached to CRM cards before AI analysis can run.
For a detailed breakdown of what AI call analysis delivers in practice, see AI call analysis in Bitrix24: transcription, quality scoring, and sales coaching.
Common Integration Pitfalls to Avoid
The most frequent failure points in telephony integration are skipping the provider compatibility check, using personal employee accounts, and leaving IVR logic undefined until after the Bitrix24 side is already built.
From our project archive, here are the issues that consistently cause rework:
- Provider doesn't support Bitrix24 integration — always verify before signing a PBX contract. If your current provider has no connector, switching providers is often faster than building a custom bridge.
- Personal employee numbers used — creates data ownership problems; always use corporate accounts.
- IVR and routing logic not documented before integration — the PBX side must be configured first; Bitrix24 can only route calls it receives.
- SIP Connector line limit ignored — if you need more than 10 concurrent lines, plan for a cloud PBX from day one.
- Number privacy scope undefined — masking numbers in all interface locations is a large task; agree the exact list of locations and roles in the technical spec.
- Integration service subscription not budgeted — per-number fees from the telephony connector service are recurring costs, not one-time.