Custom Mango Office Telephony Integration with Bitrix24

Custom Mango Office Telephony Integration with Bitrix24

You use Mango Office and Bitrix24, but the standard app from the marketplace does not provide the flexibility you need. A typical scenario: calls don't link to the right contacts, recordings arrive with a half-hour delay, and your manager wants automated lead creation following a unified script. We solve these tasks through a bespoke connection using direct APIs. With over 10 years of experience, we've integrated 50+ telephony systems and know every nuance of Mango. Our experience shows that off-the-shelf solutions cover only 60% of business needs — the rest must be customized manually.

The problem worsens when your company has multiple offices or non-standard routing. Without a custom integration, operators spend up to 30% of their time manually redirecting calls and duplicating data. We guarantee that after setup, you'll forget about these issues.

Why Standard Integration Falls Short

The official Mango Office application (installed from Applications → Marketplace) handles basic scenarios: a pop-up card on incoming calls, linking a call to an existing or new lead. However, it does not allow:

• flexible lead routing based on line number;
• mapping employee extensions when they differ between Mango and Bitrix24;
• processing the call recording when the file arrives 10 minutes after the call ends;
• supporting multiple virtual PBXs on one portal.

This is a documented feature of the Mango VPBX API.

Mango sends events: call_start, call_answer, call_end, call_record. A key nuance — call_record arrives separately from call_end, with a delay of up to 10 minutes. You cannot attach the recording synchronously; an asynchronous queue is required. Webhooks work reliably, but without proper handling, you can easily lose calls.

Mapping connects the Mango extension to a Bitrix24 user ID. Without it, calls from new employees or after a number change hang without an assignee. We create a configuration table loaded at handler startup. If no match is found, the call is considered missed and linked to a default responsible person — this prevents lead loss.

Custom Integration Solution

Employee Mapping and Call Recording Delays

To handle extension mismatches, we build a mapping table (e.g., extension 101 → USER_ID 12). When no match exists, the call defaults to a predefined responsible person. This ensures every call is tracked.

For call recordings, we implement a Redis queue: on call_end, we save the pair mango_uuid → bitrix_call_id; on call_record, we download the file via a temporary link and call telephony.externalCall.attachRecord. The temporary link lives for 24 hours, so we always have time.

Comparison: Standard vs. Custom Approach

Custom integration outperforms the standard on key parameters by 3–5 times for non-standard scenarios.

Implementation and Case Study

Step-by-Step Setup

1. Register a webhook URL in your Mango account (PBX → Settings → Notifications).
2. Deploy a handler that receives events and converts them into Bitrix24 REST calls using the Bitrix24 REST API.
3. Create a mapping table: extension → USER_ID (e.g., 101 → 12, 102 → 8).
4. Implement a queue for delayed recording attachment: on call_end save mango_uuid → bitrix_call_id; on call_record download the file via temporary link and call telephony.externalCall.attachRecord.
5. Set up routing for multiple lines.

Case Study: Insurance Broker with Three Offices

The company had three offices in different cities, each with a separate Mango number. Requirements: a call to the Moscow number creates a lead for the Moscow manager, to Krasnodar — for the Krasnodar manager. Solution: three separate webhook URLs; each handler passes LINE_NUMBER when creating a call in Bitrix24. When a call is transferred between offices (event call_transfer), the responsible person is updated in the active call. Result: handling time reduced by 40%, repeat calls decreased by 25%. This saved an estimated $2,000 per year in operator costs.

Project Delivery and ROI

What's Included

• Audit of current PBX and CRM;
• Architecture design of the integration;
• Webhook and REST API setup;
• Employee mapping;
• Recording queue implementation;
• Testing on real calls;
• Documentation and training.

Timeline and Pricing

Estimated setup time for custom integration: 5–8 business days. Final cost depends on scenario complexity and number of lines, typically starting from $2,000. We offer a fixed price after analyzing your configuration. Contact us for an accurate estimate.

Benefits and ROI

Our custom solution reduces call handling time by 30–40% and eliminates manual lead redirection. The investment pays for itself in 2–3 months. Our experience confirms that certified developers guarantee stable operation even under high loads. Order a turnkey Mango Office integration with Bitrix24 — get a consultation today.

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.