A manager forgets to move a deal to the next stage, a supervisor doesn't receive a notification about an overdue task, a client waits for a proposal that was never sent — this scenario is familiar to every CRM without automation. According to statistics, companies lose up to 30% of revenue due to delays in lead processing. We, engineers with 10 years of experience in Bitrix24 implementation, solve these problems using three no-code tools: robots, business processes, and smart processes. Each tool addresses a specific class of tasks, and confusion between them is the main reason why automation fails. Below, we break down what to use and when, and how to avoid common mistakes. According to official Bitrix24 documentation, properly configured automation reduces lead processing time by 70%.
No-Code Automation
Manual deal processing leads to errors and delays. No-code tools eliminate the human factor: robots instantly execute actions upon stage transitions, and business processes ensure all approvals are completed. Implementation takes 3-5 times less time than custom development and requires no programming.
Robots — Automation on CRM Stages
Robots are tied to stages of deals, leads, invoices, and proposals. A deal moves to the "Contract Preparation" stage — the robot sends an email to the client, assigns a task to the lawyer, changes the responsible person. The logic is simple: event on stage → action.
Robot capabilities:
- Send emails, SMS, chat messages
- Create tasks and documents
- Change entity fields (status, responsible person, amount)
- Wait for a condition (e.g., field completion) and then continue the chain
- Call webhooks — for integration with external services
Limitations. Robots work linearly within a single stage. No branching, no loops, no parallel paths. If you need "if amount > 100,000 — approval with director, otherwise — straight to work," a robot won't cut it. For that, use business processes.
Business Processes — Visual BPMN
The business process (BP) designer is a full-fledged builder with conditions, loops, parallel branches, and approval blocks. A BP can be launched manually, by schedule, or via a robot.
| Capability | Robots | Business Processes |
|---|---|---|
| Conditional branching | No | Yes |
| Parallel paths | No | Yes |
| Approval with voting | No | Yes |
| Loops | No | Yes |
| Tied to CRM stages | Yes | Via robot trigger |
| Work with lists | No | Yes |
A typical scenario is expense request approval. An employee fills out a form, the BP checks the amount: up to 50,000 — goes to department head, above that — adds a stage for the CFO. Each stage has a deadline, escalation, comment. The result is recorded, history saved.
BP limitations. The designer is visual, but with complex logic, the diagram becomes an unreadable mess. Debugging is done via the execution log, which is inconvenient with dozens of branches. No versioning: once a process is changed, the old version is lost.
Smart Processes — Custom Entities
Smart processes emerged as a replacement for outdated "Lists" for CRM tasks. Essentially, it's a constructor for custom entities with a pipeline, fields, robots, and access rights — without development.
Use cases for smart processes:
- Standard CRM entities (deals, leads) don't fit conceptually — e.g., repair requests, complaints, internal orders
- Need a separate pipeline with its own stages, not tied to sales
- Need to link to a deal or contact but with its own processing logic
Smart processes support the same robots and triggers as deals. You can attach business processes to them. Effectively, it's a no-code way to create a new module inside Bitrix24.
Extending Robot Functionality
For tasks with conditional transitions or sequential approvals, robots are useless. The solution is to use business processes. They implement complex logic without programming and can be launched on a schedule or by events.
Example: Automating complaint processing
A client submits a request, a robot creates a smart process "Complaint" which launches a business process: warranty check → repair cost estimate → manager approval → client notification. The entire cycle takes from 1 hour to 2 days.
Selection Criteria: Robots or Business Processes
The choice depends on the complexity of the path. If the task is linear — a robot is enough. If conditions, loops, and approvals are needed — go with BP. For intermediate cases, use a combination: a robot triggers a BP.
Scope of Work for Setup
- Audit of current CRM and identification of bottlenecks
- Scenario design: process maps, robots, BPs
- Configuration of robots on stages, BPs with conditions, smart processes
- Setup of notifications and access rights
- Testing and bug fixing
- Employee training (2 hours with recording)
- Documentation: process diagrams, role descriptions
- 1-month warranty support
Comparison of No-Code and Development
| Criteria | No-code (robots/BPs) | Custom development |
|---|---|---|
| Speed of implementation | 1-5 days | 2-4 weeks |
| Flexibility | 80-90% of tasks | Any integration |
| Update support | Automatic | Manual adjustments |
The remaining 10-20% of tasks (integration with 1C, custom activities, server handlers) require code. But 80% of automation we cover without a single line of code.
Our team of certified engineers with 10+ years of experience will set up automation turnkey in 5-10 business days. Bitrix24 robots are one of the primary tools for quick scenarios. Contact us for a free project evaluation and get a consultation on the optimal solution. Order turnkey automation setup — we'll account for all your business specifics.