Sales Tunnels in Bitrix24: Automation & REST API
We configure sales tunnels in Bitrix24 CRM to eliminate the pain of merging stages and manually transferring deals between pipelines. Our engineers at True Tech will automate transitions, assignment of responsible persons, and analytics. Without tunnels, the only way to organize a multi-stage process is one long pipeline with 15–20 stages. This is unreadable and does not allow you to differentiate responsibility between teams. Tunnels provide different responsible persons at stages, separate conversion analytics, and automatic transition without manual intervention.
How to set up sales tunnels?
Setup starts in the CRM → Deals → Pipeline settings → Tunnels section. The visual editor shows pipelines as blocks connected by arrows. Create several pipelines: "Initial processing", "Negotiations", "Closing". In the source pipeline, select a trigger stage (for example, "Qualified"), specify the target pipeline and the initial stage in it. The transition can be automatic or only with manual confirmation. Optionally configure automation upon entry into the new pipeline: assignment of responsible person, task creation, notification sending.
| Parameter |
Recommendation |
| Number of pipelines |
2–4 to separate stages |
| Trigger stage |
Choose the stage with maximum conversion |
| Automation |
Enable for repetitive actions |
| Reverse transition |
Use when a client returns |
Why standard tunnels are not enough?
For complex scenarios, tunnels are supplemented with program logic via REST API. For example, moving a deal to a new pipeline with a change of responsible person:
// Moving a deal to another pipeline on stage change
BX24.callMethod('crm.deal.update', {
id: dealId,
fields: {
CATEGORY_ID: targetPipelineId,
STAGE_ID: 'C' + targetPipelineId + ':NEW',
ASSIGNED_BY_ID: newResponsibleUserId,
}
}, result => {
if (result.error()) {
console.error('Move error:', result.error_description());
}
});
A webhook on stage change allows adding custom logic:
// Bitrix24 webhook handler on deal stage change
$event = $_POST;
if ($event['event'] === 'ONCRMDEALUPDATE') {
$dealId = $event['data']['FIELDS']['ID'];
$newStage = $event['data']['FIELDS']['STAGE_ID'];
if ($newStage === 'C1:WON') {
// Deal won in first pipeline — create deal in repeat sales pipeline
createRepeatSaleDeal($dealId);
}
}
Tunnels vs long pipeline: what to choose?
Tunnels process deals 3 times faster and reduce the load on managers. A long pipeline with 20 stages increases cycle time by 40%. Tunnels automatically redirect the client, not requiring manual transfer. According to internal measurements on 12 implementations, average manager response time decreases from 4 hours to 45 minutes, and conversion from qualified lead to payment grows by 18–22%. Separating pipelines also simplifies reporting: the sales director sees conversion for each stage separately, without mixing marketing and service indicators. Separately, we configure return rules: if a deal goes cold at the proposal stage for more than 7 days, automation returns it to the previous pipeline with a note for re-engagement.
What is included in turnkey tunnel setup
- Analysis of current pipelines and processes
- Design of a tunnel scheme (2–4 pipelines)
- Configuration of triggers and automation
- REST API and webhooks for custom logic
- Documentation of the scheme and team training
- Technical support for 1 month after launch
Our experience: over 5 years working with Bitrix24, 50+ CRM setup projects. We guarantee stable operation of tunnels and timely delivery. Order sales tunnel setup — get a consultation on your scheme. We will evaluate the project for free and offer an optimal architecture.
Typical tunnel schemes
Lead → Deal → Project. Standard B2B scheme: leads are qualified in the lead pipeline, upon conversion they go into the deal pipeline, after signing a contract — into the project management pipeline.
Cold → Warm → Hot. Marketing scheme: leads from advertising go into the "Cold" pipeline, upon confirmation of interest they move to "Warm", upon request for a quote — into "Hot".
Main pipeline → Service. After a sale, the client automatically goes into a service or onboarding pipeline. This bundle is convenient for SaaS products and subscription services: the "sale" deal is closed as won, but simultaneously a new deal is created in the "Onboarding" pipeline with a 14-day deadline. The responsible person changes from sales manager to account manager, the history of correspondence and calls is automatically pulled through contact linking. Similarly, we organize the return of clients to the marketing pipeline after 6 and 12 months for upselling, which brings an additional 8–12% revenue without acquisition costs.
Timelines
| Configuration |
Time |
| Setup of 2–3 connected pipelines + tunnels |
1 day |
| Tunnels + automation + assignment of responsible persons |
2–3 days |
| Complex scheme with REST logic and webhooks |
4–6 days |
The cost is calculated individually. Contact us — we will select a solution for your budget. Sales tunnels in CRM — official documentation.
How to ensure CRM implementation success?
We have been working with Bitrix24 for over 10 years — during that time we have completed 500+ projects. Every second one starts with the same problem: a company buys CRM, sets it up "by the book," and three months later managers fill two out of twelve fields, deals stall at "Negotiations" for months, and management cannot extract analytics. The root is not bad software — it's the approach. CRM is configured without auditing real processes, without considering staff objections, and without a step-by-step automation plan. In this article — a step-by-step guide on how we avoid this.
All specialists are certified by 1C-Bitrix, the methodology is proven on hundreds of cases. 1C-Bitrix is a platform that, when paired with Bitrix24, provides real end-to-end analytics if configured correctly.
Reality of CRM implementations: 80% fail to deliver results
Why do employees sabotage CRM?
Managers are accustomed to Excel and notepads — they perceive CRM as total control. Our solution: involve key employees at the design stage, show personal benefits — automatic reminders, ready-made proposal templates, less routine. We train on real scenarios, not abstract examples. Resistance drops 4 times faster than with "command" implementation.
How to prevent incomplete data entry?
Mandatory fields are filled, others are ignored — familiar picture? We solve it on three levels:
- Set mandatory fields per funnel stage (only relevant data at each stage).
- Implement auto-fill from UTM tags, email parsing, data from open databases.
- Remove redundant fields — fewer fields, higher quality.
According to our practice, field optimization reduces omission rates by 70% within the first month.
How to design funnels correctly?
Too many stages, no transition criteria, duplicate stages — typical mistakes. We design the funnel based on reality: how sales actually work, not as written in textbooks. We use CRM data from the first 2 weeks of audit to identify real stages and loss points. This shortens the deal cycle by 25–40%.
What automation should be done first?
We set up robots and business processes from day one — so the team immediately feels the difference. For example, lead distribution, sending emails after status changes, creating tasks for colleagues. Companies that implement automation at the start achieve plan targets 3 months faster.
What Bitrix24 features accelerate sales?
- Inquiries from all channels (phone, email, messengers, forms) are captured automatically.
- Leads are created and distributed without manual intervention.
- Visual kanban with custom stages — drag a card to the next stage, an email is sent automatically, a task is created.
- Omnichannel: unified window for telephony, email, WhatsApp, Telegram, Viber, VK, Instagram, online chat.
- Robots and business processes: mailings, document generation, reminders, escalations — no coding required.
- Analytics: funnel, conversions, lead sources, manager workload, average handling time.
What does integrating a 1C-Bitrix website with Bitrix24 CRM provide?
Synergy of the two products yields measurable results, and we implement it through direct data exchange. Site forms transfer leads to CRM instantly with full UTM markup — you see where the client came from. Online chat connects via open lines: a visitor writes on the site, the manager responds from CRM. Orders in the store based on infoblocks v2.0 become deals with full purchase history, enabling cross-selling. Call tracking with number substitution links calls to advertising channels. We use CommerceML to exchange data with 1C Trade Management/ERP: nomenclature, stock balances, prices — synced via agents without manual intervention. End-to-end analytics collects advertising costs, visits, leads, sales in one report — ROI per channel. For non-standard logic, we use REST API and high-load blocks to store arbitrary data (e.g., tech support interaction history). In one project, we configured this bundle for a retail chain: 1C cash register integration with CRM created contacts automatically upon loyalty card purchase, and CRM marketing via Bitrix24 increased repeat purchases by 18% in six months.
How we set up CRM: the process
-
Audit. We analyze how sales work currently. Where are leads lost? Which channels bring clients? We form recommendations before technical implementation.
-
Design. Multiple funnels for different directions, custom fields, mandatory stages and transition conditions. Structure reflects the real process.
-
Integrations. Connect to website, telephony, email, messengers, Yandex.Direct, Google Ads, 1C.
-
Custom modules. When standard is not enough — applications for Bitrix24: specific reports, non-standard business logic, integrations with industry systems.
-
Migration. Transfer databases from amoCRM, Megaplan, Salesforce, HubSpot, Excel. Relationships, communication history, attachments — everything intact.
-
Training. Trainings tailored to your configuration, video instructions, documentation.
What is included in the work?
| Deliverable |
Description |
| Technical documentation |
Funnel scheme, robot settings, field structure, integration plan |
| Access and configurations |
List of integrations, API keys, logins/passwords (provided under NDA) |
| Team training |
2–3 webinars tailored to your configuration, video instructions, cheat sheets |
| Post-implementation support |
2 weeks of incident management + regular usage audits |
Cloud or on-premise: which to choose?
| Parameter |
Cloud (SaaS) |
On-Premise |
| Time to start |
1–2 days |
1–2 weeks |
| IT requirements |
None |
Server and admin required |
| Data control |
Limited |
Full |
| Customization |
Standard limits |
Unlimited |
| Best for |
Teams up to 100 people, standard processes |
Large companies, strict security requirements |
Comparison: the cloud version is 2–3 times cheaper initially, but for B2B companies with large data volumes, on-premise pays off in 1.5–2 years due to no per-user subscription fee.
Metrics we track for your business
-
Funnel stage conversion. If 80% are lost at the proposal stage — the problem is pricing, not managers. Norm: 5–15% for B2B, 1–5% for high-ticket B2C.
-
Lead response time. A 5-minute response increases conversion 10x compared to a 30-minute response. We set alerts — if a manager doesn't respond within 15 minutes, the lead is reassigned.
-
LTV. CRM segments clients by lifetime value — managers focus on the most valuable.
-
Average deal cycle. If it increases, something is broken. Reasons for rejections are gold for product and script adjustments.
Our case studies
Manufacturing company (B2B). A plant with high annual turnover. Leads were lost in email; management only learned about large deals post-factum. We set up automatic inquiry capture, a funnel "qualification → calculation → proposal → approval → contract → payment," and robots that generate proposals from templates. Conversion increased by 23%, lead processing time dropped from 4 hours to 20 minutes. Manager payroll savings exceeded $1,000 per month due to reduced routine.
IT service company. Three funnels: new clients, upselling, tenders. Auto-generation of contracts and invoices, integration with Jira — after signing, tasks automatically appear in the development department. Management received a weighted revenue forecast with 90% accuracy. The project paid off in 4 months.
Implementation timeline and cost
| Scale |
Timeline |
What's included |
| Basic |
1–2 weeks |
Funnel, telephony, email, database import |
| Standard |
1–2 months |
Custom funnels, automation, website and 1C integrations |
| Comprehensive |
2–4 months |
Multiple funnels, custom modules, training, end-to-end analytics |
The cost is calculated individually based on your scope of work. After implementation — tech support with SLA (response from 1 hour), regular usage audits, and feature development.
Ready to discuss your situation? Contact us — we'll conduct a free audit of your current CRM within 2 days and propose an implementation architecture with a result guarantee. Request a consultation — we'll show you in numbers how much you'll save with proper setup.