Bitrix24 Call Forwarding Setup with Results Guarantee

We configure call forwarding in Bitrix24 so that every call reaches the right employee without loss. Errors in routing rules are a common cause of client churn: up to 30% of incoming calls don't reach the manager if the scheme doesn't consider occupancy, time, or CRM data. Bitrix24 provides flexible routing tools: queues, IVR, time-based forwarding, and forwarding to the responsible person. But incorrect configuration can cause calls to loop, go to voicemail, or reach the wrong specialist. This is especially critical for companies with high inbound call volume—online stores, support services, call centers. We use proven schemes: cascade forwarding, skills-based routing, and CRM integration via REST API. This ensures every call is preserved and reduces client wait time. With 7+ years of experience and over 50 Bitrix24 telephony projects, we guarantee a working scheme from the first attempt. For example, in one contact center project for an online store with 20 sales managers, we reduced call loss from 25% to 3% using cascade forwarding and CRM integration.

Types of Forwarding

Bitrix24 implements several forwarding types, each for a specific situation:

Setting Up in the Telephony Section

Main forwarding settings: CRM → Telephony → Settings → [select number] → Call Processing Scheme. Here you define rule chains.

Employee Queue

Add managers; the call sequentially rings them. For each, set the ringing duration before moving to the next. If no one answers, the call goes to a final action (voicemail, external number).

Forwarding to an External Number

If an employee doesn't answer on the headset, forward to their mobile. Configure in the employee profile: Telephony → Employees → [select] → Mobile Number for Forwarding.

Voicemail

If no one answers, record a message. The recording is attached to a CRM activity and notifies the responsible person.

Setting Up Time-Based Forwarding

Section: Telephony → Settings → Business Hours. Set the schedule: Monday-Friday 9:00-18:00. Outside these hours, calls follow a separate scheme. Typical scenario: during non-working hours, an auto-attendant says "We work from 9 to 18, leave a message" and a record is created in CRM. You can set multiple schedules for different numbers—sales works until 20:00, support until 18:00. Proper time management reduces lost inquiries by 15%.

Setting Up IVR with Forwarding

IVR (voice menu) lets the client choose where to route:

Press 1 — Sales Department
Press 2 — Tech Support
Press 0 — Secretary

Configure in "Telephony" → "Voice Menu". For each key, specify an action: queue, employee, external number, another menu (nested IVR). According to Bitrix24 documentation, the call processing scheme supports up to 10 routing levels.

Efficiency of Forwarding to the Responsible Person

Advanced scheme: an incoming call from a known client goes to their responsible manager in CRM. If the responsible person is busy, it goes to their supervisor. This is configured via the "Forward to responsible" parameter in the call processing scheme. The system looks up the number in CRM, finds the contact or deal, identifies the responsible person, and calls them. If the responsible person doesn't answer, the next rule in the chain applies (e.g., forwarding to the department queue).

Comparison: a standard queue rings everyone in order, while forwarding to the responsible person reduces client wait time by 40% — a 1.7x improvement. The client directly reaches someone familiar with their history, boosting loyalty.

Importance of Time-Based Forwarding

Without time-based forwarding, clients call outside business hours and hear endless rings. Proper configuration allows recording a message or redirecting to an on-call person. This reduces lost inquiries by up to 15%. You can also set different scenarios for weekdays and weekends.

Comparison of Routing Schemes

What to Do If Forwarding Doesn't Work?

If the forwarding scheme is configured but calls don't reach, check the queue order and rule conflicts. Ensure the number is connected to Bitrix24 and the employee is active. Often the issue is that the responsible person in CRM is incorrect or the client number is not found. Use the call log in "Telephony" → "Call Log" for diagnostics. If the problem is on the operator side, check SIP connection settings.

Our Setup Process

Our work on call forwarding configuration includes:

1. Audit of the current call processing scheme.
2. Design of routing tailored to business processes.
3. Implementation of rules, queues, IVR, and CRM integration.
4. Testing all scenarios (busy, no answer, unavailable).
5. Deployment and employee training.

What's Included in the Work

After setup, you get:

• A working call forwarding scheme with documentation.
• Configured voice menu (if needed).
• Access to settings with explanations.
• Training for responsible employees.
• Support for 2 weeks after launch.

Missed Call Tracking

Every missed call that completes the entire forwarding chain creates a CRM activity with a "Missed call" label and notifies the responsible employee or manager.

Setting up forwarding for one number with a simple scheme takes 2-3 hours. Complex schemes with IVR and multiple queues take 4 to 8 hours. Get a consultation on call forwarding setup — we will analyze your current scheme for free. Order full telephony setup with results guarantee.

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.