Bitrix24 & UIS (CoMagic) Integration: Calls, Call Tracking, Analytics

A client calls from the website, the manager sees only digits — no source, no ad campaign. This is a familiar situation: without attribution, you can't see how many calls came from contextual ads versus SEO, and you can't evaluate the cost per call from each channel. If a call is lost due to an ATS failure — you simply won't know about it. UIS (CoMagic) solves these problems, but without integration with Bitrix24, data remains fragmented. We set up the connection so that each call automatically creates a lead with full attribution. We connect a SIP trunk or REST API — depending on your needs. Result: a unified CRM with analytics for every touchpoint.

Over 7 years of experience integrating Bitrix24 with telephony. Certified specialists. Completed 30+ projects, including call centers with 50+ operators. Quality guarantee on all work. Reduction of non-target ad spend by up to 30% — a typical result after setting up call tracking. Savings are calculated individually based on your budget.

How to Integrate Bitrix24 with UIS (CoMagic)?

The choice of connection method depends on the required depth of analytics.

For basic scenarios, a SIP connector is sufficient. If you need call tracking and advanced analytics — use REST API.

How to Set Up Incoming and Outgoing Calls?

Incoming Calls

On an incoming call, Bitrix24 must:

1. Identify the caller's number via CLIR.
2. Find a contact or company in CRM by phone number.
3. Show the client card to the manager before picking up.
4. Create a call record in the timeline of the CRM entity.

Via the SIP connector, this works out of the box with proper SIP account configuration. Via REST API — a webhook from UIS calls telephony.externalcall.register with parameters PHONE_NUMBER, USER_ID, TYPE=1 (incoming). Bitrix24 automatically brings up the card.

Outgoing Calls

The manager clicks on a number in the CRM card. Two options:

• SIP connector. The call goes through the Bitrix24 softphone directly to the UIS SIP trunk.
• REST API + callback. Bitrix24 sends a request to UIS via callback API — the ATS first calls the manager, then the client. The manager picks up — the call connects.

The second option is more convenient for call centers: no softphone needed, the call comes to a regular work phone.

Call Recording

UIS stores recordings on its servers. Options for uploading to B24:

• Direct link. The telephony.externalcall.attachRecord method accepts a file URL. Bitrix24 downloads and attaches it to the call in the timeline.
• File upload. If UIS provides the file via API, an intermediate script downloads the MP3 and uploads it to B24 via disk.folder.uploadfile, then attaches it to the call.

Recordings are available in the contact and deal cards, and in the general call report.

Why Call Tracking Is Important for Lead Attribution?

The main value of the UIS + Bitrix24 link is understanding where the call came from. CoMagic replaces numbers on the site: each visitor sees a unique number tied to their session. When a client calls, UIS knows:

• Traffic source — Google Ads, Yandex.Direct, SEO, direct visit
• UTM tags — campaign, medium, source, content, term
• Entry page and call page
• Keyword (when integrated with ad accounts)

Accurate attribution allows you to reduce non-target ad spend by up to 30%, with savings depending on your current spend.

This data is transferred to Bitrix24 when a lead or call is created. The scheme:

1. A visitor enters the site. CoMagic assigns a session and replaces the number.
2. The visitor calls. UIS records the call linked to the session.
3. A webhook from UIS sends data to Bitrix24: caller number + source + UTM tags.
4. The webhook handler creates a lead in CRM via crm.lead.add with filled UTM_SOURCE, UTM_MEDIUM, UTM_CAMPAIGN fields and a custom field "Call Source".
5. If the contact already exists — the call is attached to the existing entity, UTM tags are written in a note.

For correct operation, custom fields in CRM must be created in advance. We create:

• UF_CRM_CALL_SOURCE (string) — source name from CoMagic
• UF_CRM_CALL_KEYWORD (string) — keyword
• UF_CRM_CALL_LANDING (string) — entry page URL

<?php
require_once($_SERVER['DOCUMENT_ROOT'].'/bitrix/modules/main/include/prolog_before.php');
use Bitrix\Main\Web\Json;

$data = Json::decode(file_get_contents('php://input'));
$phone = $data['caller_id'];
$source = $data['source'];
$utm = $data['utm'];

$leadFields = [
    'TITLE' => 'Call from site',
    'PHONE' => [['VALUE' => $phone, 'VALUE_TYPE' => 'WORK']],
    'UF_CRM_CALL_SOURCE' => $source,
    'UTM_SOURCE' => $utm['source'],
    'UTM_MEDIUM' => $utm['medium'],
];

$lead = new CCrmLead();
$lead->Add($leadFields);
?>

What's Included in the Work

• Audit of current telephony and CRM
• Connection of UIS SIP trunk or REST app registration
• Incoming routing: queues, IVR, department distribution (on UIS side)
• Mapping UIS internal numbers → Bitrix24 users
• Creation of custom fields for call tracking
• Integration of call recordings (via URL or file)
• Lead creation logic: new lead for each call or only when no contact exists
• Testing: incoming, outgoing, missed, repeat call from existing client
• Manager training and setup documentation

Implementation Stages: Timelines and Cost

Cost is calculated individually depending on complexity. Get a consultation on integration — we will prepare a proposal and assess your project in 1 day.

Bitrix24 Telephony REST API Documentation

How a corporate portal on Bitrix24 solves the problem of information chaos?

Employees spend up to 2 hours a day searching for files, emails, and solutions. Tasks get lost in dozens of chats, approvals get stuck for weeks. The manager learns about missed deadlines only at a meeting. A corporate portal on Bitrix24 ties every message, document, and task to a single context. You get a transparent picture of work: who is working on what, which stages, where bottlenecks are. Wikipedia: Information silo describes how unorganized data reduces productivity – a portal cuts that loss by 60–70%.

We will evaluate your project for free – contact us to get the architecture in 2 days. A medium‑sized company typically saves 2.5 million rubles annually after deployment (based on our projects).

What does the portal offer in daily work and why is it better than messengers?

In messengers, information is unstructured – discussions get buried within a week. On the portal, every message is tied to a task, project, or document. Employees spend up to 30% of their work time searching for data (McKinsey). The portal reduces this time by 2–3 times thanks to structured repositories and full‑text search.

Communications. Activity stream, messenger, and video calls are tied to specific tasks. Any discussion can be found six months later – in a messenger it would be buried within a week.

Tasks and projects. Kanban, Gantt, checklists, dependencies, time tracking. Each employee's efficiency is visible in reports – no need to wait for a meeting.

Document flow. Approval routes through the business process designer: leave request → manager → HR → accounting. Electronic signature, versioning, deadline control. Integration with electronic document management (SBIS, Diadoc) via REST API.

HR. Onboarding of new employees, leave/travel requests, organizational structure, absence schedule. An employee knows where to go from day one.

Knowledge base. Bitrix24 wiki engine: regulations, instructions. Knowledge does not leave with departing employees.

Implementation example. For a manufacturing company with 320 employees, we deployed a portal with integration of 1C:SALARY AND HR MANAGEMENT and Active Directory in 4 months. Travel request approval time decreased from 3 days to 4 hours. Savings on employee idle time amounted to 1.5 million rubles per year. Managers receive automatic reports on department efficiency. Customer response time decreased by 20%. Portal payback period is 7 months.

How does integration with 1C and Active Directory accelerate HR management?

Integration with 1C:Enterprise via the b24connector module or custom REST handler: a leave request is approved on the portal through a business process and automatically enters 1C:SALARY AND HR MANAGEMENT for vacation pay calculation. Active Directory (SSO via the ldap module) – the employee account is created once in AD and synchronized to the portal, email, VPN. Upon dismissal, it is blocked everywhere. Manual account creation is eliminated, errors are minimized.

Types of corporate portals and key integrations

Additional integrations that deliver real value:

• Email: Exchange via EWS API or IMAP, calendar synchronization, creating a task from an email.
• IP telephony: Asterisk, Mango Office, Zadarma via REST API – calls from the portal, contact card, call recording.
• Video conferencing: built‑in video calls or integration with Zoom/Teams via marketplace.
• EDI: SBIS, Diadoc via REST API – fully electronic document flow with counterparties.

Security and compliance with Federal Law 152‑FZ

The portal contains personal data, financial reports, strategic plans. We guarantee protection:

• role model via CGroup and section‑level permissions;
• two‑factor authentication (OTP, Yandex.Key, SMS);
• audit of all actions (b_event_log);
• TLS encryption for transmission and disk encryption;
• full compliance with Federal Law No. 152‑FZ "On Personal Data".

How is implementation carried out? Step‑by‑step plan

1. Audit — we record current processes, measure time losses.
2. Design — choose portal type, plan integrations.
3. Implementation — configure business processes, permissions, interface.
4. Test — pilot group tests scenarios, we fix issues.
5. Launch — connect all employees, train, hand over documentation.

What you receive after implementation

• Project documentation: architecture, integration scheme, business process diagrams.
• Configured portal with all integrations (1C, AD, telephony, EDI).
• Business process descriptions and instructions for administrators and users.
• 30 days of technical support after launch.
• Access to our knowledge base and migration scripts.

Post‑launch support: how to prevent the portal from becoming obsolete

After six months, many portals become abandoned. To avoid this, we offer packages with fixed SLA and a dedicated administrator. Performance monitoring, platform updates, user administration, development of new modules. Our team has over 10 years of experience and more than 50 implemented corporate portals on Bitrix24. We are a certified 1C‑Bitrix partner, guaranteeing quality and deadlines.

Mobile access. Native Bitrix24 app (iOS/Android) with push notifications, tasks, chats. Responsive web interface for extranet users (no app installation required). Offline access to documents and tasks, sync when connectivity is restored.

Order a turnkey corporate portal implementation

Schedule a free audit – we will evaluate your project, propose architecture, and give clear timelines. Get a comprehensive proposal and see that the portal pays for itself within the first six months. Contact us today.