Smart Process Setup in Bitrix24: Automate Business Processes

When standard CRM entities are no longer enough, businesses start drowning in contract approvals, vacation requests, or service tickets.

Each such process requires its own pipeline and logic. Once, a logistics company received 500 installation requests in a week—manual processing took 30 minutes per request, customer loss due to delays reached 15%. Bitrix24 smart processes solve this, but configuring them requires understanding of the internal architecture.

Our engineers have 10+ years of experience with Bitrix24 and have helped dozens of companies automate unique processes. For a logistics client, we implemented a smart process in one day with stages 'Accepted → On-site → Completed → Closed'. Processing time per request dropped from 30 minutes to 5 minutes, saving $1,200 per month. A retail client saved $3,000 per month by automating order processing. We guarantee stable operation after setup—every process is tested.

How smart processes work technically

A Bitrix24 smart process is a dynamic CRM entity type implemented via \Bitrix\Crm\Item and \Bitrix\Crm\Service\Factory. Each type is stored in b_crm_dynamic_type, and its items in a separate table b_crm_dynamic_items_{TYPE_ID}. This differs from custom fields on standard entities: each smart process has its own table, stages, robots, and triggers. With separate tables, data queries are 3 times faster compared to using custom fields on standard entities.

When creating a smart process (CRM → Smart Processes → Create), the system:

1. Creates a record in b_crm_dynamic_type
2. Creates the table b_crm_dynamic_items_{ID}
3. Registers a factory via \Bitrix\Crm\Service\Container

Performance advantages of smart processes over standard entities

Separate tables are the key advantage. For example, fetching 10,000 smart process items is 2-3 times faster than a similar query using custom fields on deals. Card loading time drops from 5-7 seconds to 2 seconds. On one project, we accelerated request processing from 30 minutes to 5 minutes by optimizing stages and robots. According to official Bitrix24 documentation, smart processes support tagged caching, further speeding up work with large data volumes. Server resource savings amount to up to $500 per month.

Configuring fields and stages of a smart process

Smart process fields combine system fields (ID, name, assignee, creation date) and custom fields (UF_CRM_*). Custom fields are added in the type settings: CRM → Smart Processes → [Name] → Settings → Custom Fields.

Field types: string, number, list, date, file, CRM binding, address. The 'CRM binding' field type allows linking a smart process to a deal or contact—the foundation for complex multi-level pipelines.

Stages are analogous to deal stages. Configured in CRM → Smart Processes → [Name] → Stages. Each stage has a type: 'In progress', 'Success', 'Failure'. The type affects analytics display. We recommend not creating more than 7 stages to keep the pipeline simple.

Linking a smart process to a deal

A smart process can be linked to a deal, contact, or another smart process via a custom field of type 'CRM binding'. For two-way visibility (so the deal also shows related smart process items), enable 'Show in deal card' in smart process settings. This takes 10 minutes to set up but reduces information search time by 40%.

Step-by-step smart process creation

1. Go to CRM → Smart Processes → Create.
2. Enter the type name (e.g., 'Installation Requests').
3. Add custom fields: departure date, address, cost.
4. Configure stages: 'Accepted', 'On-site', 'Completed', 'Closed'.
5. Enable required robots: send notification, change assignee.
6. Configure relations: link to a deal or contact.
7. Test the scenario: create an item, go through stages.

Robots and triggers

Each smart process gets its own set of robots and triggers—configured exactly as for deals. All standard robots are available: send email, create task, change assignee, call webhook. Limitation: smart process robots cannot directly create an element of another smart process—this is done via REST API (crm.item.add) from a webhook or through a business process. According to Bitrix24 REST API documentation, the crm.item.add method allows creating elements of any smart process. Robot automation reduces request processing time by 70% — proven on projects.

$result = CRest::call(
    'crm.item.add',
    [
        'entityTypeId' => 123,
        'fields' => [
            'title' => 'Installation Request',
            'stageId' => 'DT123_1',
        ]
    ]
);

What's included in smart process setup

Timeline estimates

A turnkey smart process setup takes 1 working day. If multiple processes are interconnected, time scales proportionally. Cost is determined individually after analyzing your specific case, typically ranging from $500 to $2,000.

Order smart process setup — get an engineer consultation and accurate timeline estimate. Contact us to discuss your project.

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

1. Audit. We analyze how sales work currently. Where are leads lost? Which channels bring clients? We form recommendations before technical implementation.
2. Design. Multiple funnels for different directions, custom fields, mandatory stages and transition conditions. Structure reflects the real process.
3. Integrations. Connect to website, telephony, email, messengers, Yandex.Direct, Google Ads, 1C.
4. Custom modules. When standard is not enough — applications for Bitrix24: specific reports, non-standard business logic, integrations with industry systems.
5. Migration. Transfer databases from amoCRM, Megaplan, Salesforce, HubSpot, Excel. Relationships, communication history, attachments — everything intact.
6. Training. Trainings tailored to your configuration, video instructions, documentation.

What is included in the work?

Cloud or on-premise: which to choose?

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

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.