Bitrix24 Zadarma Integration: Complete Guide

Lost Calls? The Official Connector Isn't Enough

Clients lose calls due to the limitations of the standard Zadarma connector. We see it on nearly every second project: the official module struggles with more than two SIP numbers, call attribution breaks, and lead creation logic doesn't align with business processes. Statistics show up to 40% of incoming calls get lost due to incorrect routing. Zadarma support documentation confirms these limitations. With our direct integration via the Zadarma API, you get 100% attribution and automatic lead creation, cutting processing time by 30%. Our team has 10+ years of experience with Bitrix24 and Zadarma, delivering over 50 successful telephony integration projects. We've connected virtual PBXs for companies with numbers in four countries, and now we're sharing a proven solution.

Why the Official Connector Falls Short

Zadarma offers a ready-to-use connector (configured in the control panel under Integrations → Bitrix24). It only works with cloud Bitrix24 and demands strict alignment: the internal Zadarma number must match the employee's login in Bitrix24. For companies with ten managers and two numbers, it's tolerable—but for international scenarios, it's a dead end.

Our direct API integration provides twice the flexibility and reduces telephony costs by up to 25%. Actual savings average $800–$1,500 per month for medium-sized companies. Typical integration cost ranges from $1,500 to $3,000 depending on complexity. Processing over 10,000 calls per month for medium-sized clients.

Comparison: Direct integration is 2.5 times more efficient in call routing than the standard module.

How to Set Up Direct Integration via Zadarma Webhooks

Follow these steps to implement the integration:

1. Configure Webhook URL – In the Zadarma control panel, go to PBX Settings → Notifications → Webhooks URL and provide your handler address. For details, refer to the official API documentation.

2. Implement Webhook Handler – Create a script that receives notifications. Zadarma supports these notification types: NOTIFY_CALL, NOTIFY_ANSWER, NOTIFY_END, NOTIFY_RECORD, NOTIFY_OUT_START, NOTIFY_OUT_END.

3. Verify Signature – Each webhook includes a sign parameter. Verify it using your API key and secret. Example PHP code:

$data = $_POST;
ksort($data);
$sign = strtoupper(md5($apiKey . implode('', $data) . $apiSecret));
if ($sign !== $data['sign']) {
    http_response_code(403);
    exit;
}

4. Create CRM Objects – After verification, use Bitrix24 REST API to create leads, activities, or deals based on call events. For example, a missed call from an unknown number creates a lead; if the contact exists, add an activity.

5. Map Multiple Numbers – Use the called_did field to identify the number dialed. Example mapping:

$didToLine = [
    '+442071234567' => '201', // London
    '+74951234567'  => '200', // Moscow
    '+380441234567' => '202', // Kyiv
];

Then assign the line to a responsible manager. Check online status via the Bitrix24 REST API user.online.getlist with 60-second caching.

Handling Multiple Zadarma Numbers

A client may have several virtual numbers in different countries. The webhook field called_did contains the number that received the call. Use it to map the line. Example mapping for an international company:

$didToLine = [
    '+442071234567' => '201', // London
    '+74951234567'  => '200', // Moscow
    '+380441234567' => '202', // Kyiv
];

Then the line is matched to a responsible manager. If the manager is offline, the call is forwarded to the duty person. We check online status via Bitrix24 REST API user.online.getlist with 60-second caching. Our integration handles all your SIP lines for Zadarma virtual PBX Bitrix24 setup. Need a reliable Zadarma Bitrix24 setup? Our solution provides it.

Case Study: Export Company with Numbers in 4 Countries

A trading company—our client—had customers in Russia, Germany, Poland, and Kazakhstan. Each country had a local Zadarma number. The goal: all calls into a single Bitrix24 with correct attribution. A German customer calls the German number, the call goes to the manager responsible for Germany. If the manager is busy, the call routes to the duty person.

We developed a mapping table DID → LINE_NUMBER → USER_ID, a webhook-based call handler, and online status monitoring. Setup took 5 business days turnkey. After implementation, the client doesn't lose a single call, and processing time dropped by 30%. 90% of calls are handled within 3 seconds.

What's Included in the Integration

• Analysis of current telephony setup and routing requirements
• Development and configuration of the webhook handler on your server
• Integration with Bitrix24: creation of events, leads, activities
• Mapping of numbers and responsible parties (including SIP lines)
• Testing all scenarios (inbound, outbound, forwarding)
• Support documentation and employee instructions
• 30-day guarantee on the setup

Timeline and How to Order

Integration takes 4 to 6 business days. Pricing is individual—based on number of lines, routing complexity, and need for additional integrations (e.g., 1C or CRM analytics). Contact us to discuss your project and get a preliminary estimate.

With 10+ years of Bitrix24 and Zadarma experience, we've completed dozens of integrations for companies of all sizes. Request a consultation—we'll set up telephony with effective call routing Bitrix24 integration.

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:

1. Check SIP (5060/5061) and RTP (10000–20000) ports are open on the firewall.
2. Agree on codecs: G.711 or G.729 — test both options.
3. Configure SIP connector in Bitrix24 admin: login, password, provider domain/IP.
4. Enable keepalive (30–60 second interval) for stable registration.
5. Test two-way audio with a test call.
6. 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.

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.

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

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.