A smart process is a CRM entity of its own, next to deals
Bitrix24 CRM comes with standard entities: leads, deals, contacts, companies, quotes and invoices. They describe a sale well. But a company runs other processes too: a department's purchase request, a contract going through sign-off, a client's service request after the sale. Put those into deals and the sales pipeline fills with cards that are not sales, while revenue reports stop adding up.
A smart process fixes that. An administrator creates a new entity with its own name, and it gets everything a deal has:
- its own kanban stages and, if needed, several pipelines
- its own fields: amounts, dates, lists, files, links to employees
- links to contacts, companies, deals and other smart processes
- automation rules and triggers on stages, just like the sales pipeline
- separate access rights: who can see, create and move items
- documents generated from templates right inside the item
Whether smart processes are available, and how many, depends on the Bitrix24 plan, so we check the plan before quoting.
Deals, smart processes, tasks and workflows do different jobs
The usual problem in a portal is not a lack of tools but mixing them up. This table helps decide where a process belongs.
| Tool | What it is for | Tell-tale sign |
|---|---|---|
| Deal | A sale to a client | There is an amount, a probability and sales stages |
| Smart process | A recurring process with its own stages: purchasing, contracts, service | Many similar items, each with its own path and people |
| Task | A one-off assignment | One person, one result, no stages |
| Workflow (business process) | A chain of steps with conditions and approvals | Branching logic on top of any entity |
Smart processes and workflows are not rivals. Stages and items live in the smart process, and a branching approval runs as a workflow at the right stage. Simple actions such as creating a task, changing the owner or sending a notification are handled by automation rules.
Purchase requests travel from request to payment in one item
Take a hypothetical trading company: departments send purchase requests in a group chat, the finance director approves them in private messages, and a month later nobody remembers who signed off what. A "Purchase request" smart process puts it all in one item.
- New. An employee fills in what is needed, how many and by when
- Approval. A rule sends an approval task to the line manager, and anything above a threshold goes to the finance director
- Quotes. The buyer requests supplier quotes and attaches them to the item
- Ordered. A supplier is chosen and the item is linked to its company record
- Received and closed. Delivery is confirmed, then payment
Collecting and comparing quotes can go to the procurement AI agent: it sends requests to suppliers and puts the quotes side by side. Where money leaks at this step is covered in our news on comparing suppliers.
