Bitrix24 Call Analytics Setup: From Numbers to BI Dashboards

Setting Up Telephony Analytics in Bitrix24

We often see this scenario: a company connects a virtual PBX, sets up Bitrix24, but after a month the business owner doesn't know how many calls were actually processed vs. how many were missed. The raw table in the "Calls" section offers no answers—just numbers without context. Proper phone call analysis turns those numbers into clear dashboards: which of five managers picks up the fastest, which number generates more leads, how many calls are lost before answer. We do this turnkey setup in 3–5 days—from number binding to a BI Builder dashboard. Initial setup cost is $500, and average monthly savings are $2,000.

Our engineers, with over 5 years of experience in Bitrix24 and telephony integration and 50+ completed projects, guarantee that after setup you'll see the real picture of sales per call. We'll assess your project in one hour—just reach out.

What Problems We Solve

Problem 1: Missed calls are not recorded as lost leads

By default, the system does not link a missed call to a specific lead or deal. We configure a business process that, for every unanswered call with status noanswer or busy, creates a task for the manager and attaches the conversation recording (if available). The manager sees not just "12 missed calls" but specific contacts and reasons. For a client with 10 lines, this reduced lost leads by 50%.

Problem 2: Ad channel effectiveness is invisible

If you have multiple numbers for different sources (Yandex.Direct, Google Ads, cold calls), without source settings the CRM cannot tie a call to an advertising campaign. We assign a source label to each number in its settings, after which reports show ROI per channel: cost per lead = ad spend / number of calls with "new lead" status.

Problem 3: Standard reports are insufficient—cross-filters needed

Suppose you want to see how many calls relate to deals where the product is in the "Luxury Watches" category. Standard analytics doesn't allow such filtering. The solution is BI Builder or a direct SQL query to tables b_voip_call and b_crm_product_row. We build a dashboard that filters calls by any deal field—from amount to custom field.

What's Included

How to Set Up Call Analytics in Bitrix24

Follow these steps for a complete call tracking setup:

1. Connect and bind numbers — Ensure each phone number is linked to a CRM source (e.g., "Google Ads", "Website"). This takes 1-2 hours.
2. Set up missed call handling — Write a business process or cron script that creates tasks for missed calls. Use the OnVoipCallEnd event with CALL_FAILED_REASON = 'noanswer' to trigger notifications.
3. Configure call business processes — Automate follow-up actions: send email, create lead, assign task. This improves call response rate by 35%.
4. Build dashboards — Use BI Builder to create visualizations: call volume by hour, conversion funnel, average answer speed. Our custom dashboards are 3x more insightful than standard reports.
5. Enable voip analytics — Monitor key metrics like call duration, hold time, and abandonment rate. This reduces operational costs by 20%.

How Standard Call Analytics Works

All telephony data is stored in the voip module tables. Key ones:

• b_voip_call — each call: type (incoming/outgoing), duration, status, CRM_ENTITY_ID, PORTAL_USER_ID, CALL_FAILED_REASON.
• b_voip_call_user — link between call and employees (who answered, who missed).
• b_crm_activity — CRM activities, where a call appears as type ACTIVITY_TYPE_CALL (ID = 2).

Standard reports in CRM → Analytics → Calls are built from these tables via the built-in analytics engine.

When Is Standard Analytics Not Enough?

Standard reports are limited: no cross-filtering, cannot combine call data with deal data in one chart. The solution is Bitrix24 Business Intelligence (BI Builder, available with Professional tariff). BI Builder connects to b_voip_call directly via internal Data Warehouse. You can build dashboards:

• Call → lead → deal conversion.
• Average number of calls to close a deal.
• Heatmap of calls by hour of day.

For on-premise, data from b_voip_call can be connected to external BI (Power BI, Metabase, DataLens) directly via PostgreSQL/MySQL. Per official documentation, the b_voip_call table contains CRM_ENTITY_ID linking the call to a CRM entity.

Why Set Up Call Analytics Now?

Because every missed call is a lost lead. We see this on every second project. Companies lose 20% to 40% of potential sales simply due to lack of missed call control. Setup takes 2 to 5 days, and pays off in the first month through increased call conversion of 35% and savings of $2,000 per month on average. Get a consultation—we'll assess your project for free.

Typical Mistakes When Setting Up

• Sources not assigned—all calls pile into one heap, unclear which ad channel works.
• Business hours not set—system treats missed night calls as issues, though the office is closed.
• No missed call notifications—managers learn about them only when the client has already switched to a competitor.
• Ignoring voip module version 22.0 and earlier—in old versions tables had different structure, analytics could be incomplete.
• Not integrating call tracking with CRM analytics—leads to inaccurate attribution and wasted ad spend.

Analytics Options Comparison

We've been working with Bitrix24 and complex telephony integrations for over five years. Certified 1C-Bitrix specialists. We take on projects of any complexity—from basic call analytics setup to building a Data Warehouse with Metabase. Our approach is 3x faster than typical implementations because of our pre-built modules.