Bitrix24 Smart Processes Explained: Build Your Own CRM Workflows

A smart process (also called a smart process automation, or SPA) is a custom object inside Bitrix24 CRM that you design yourself: it gets its own stages, fields, automation rules, permissions and reports, just like deals do. You use it for any repeatable business process that is not a sale, such as distributor onboarding, warranty claims, vendor approvals or hiring requests. With Bitrix24 smart processes explained simply, the idea is this: if your team tracks something in a spreadsheet or a WhatsApp group, it can probably become a smart process.

This guide walks through what smart processes are, how they differ from deals and pipelines, real examples from Indian businesses, and a step-by-step method to design your first one without making a mess.

What problem do smart processes solve?

Most companies start their CRM with leads, contacts, companies and deals. That covers selling. But a business runs on many other processes that also have stages, owners and deadlines:

• A distributor applies, sends KYC documents, gets verified, signs an agreement and receives a code.
• A customer raises a service complaint, a technician is assigned, the visit happens, and the ticket closes.
• A purchase request is raised, approved by a manager, sent to a vendor and received.

Teams usually force these into the deals pipeline (which messes up sales reports) or keep them in Excel (which nobody updates). A smart process gives each of these its own clean home inside the CRM, connected to the same contacts and companies your sales team already uses.

How is a smart process different from a deal pipeline?

This is the question we hear most often at Acemagick. Deals and smart processes look similar on screen, both use a Kanban board with stages, but they are meant for different jobs.

A simple rule: if the end of the process is money won or lost, it is a deal. If the end is "approved", "resolved", "onboarded" or "delivered", it is probably a smart process.

If you are new to how leads and deals flow in Bitrix24 in the first place, read our walkthrough of Bitrix24 CRM features following one lead end to end before designing custom objects.

What can you build with a smart process? Real examples

Here are practical smart processes we see working well for Indian companies:

1. Distributor or dealer onboarding. Stages such as Application, KYC Pending, Verification, Agreement Signed, Code Issued. Fields for GST number, territory, credit limit and documents.
2. After-sales service tickets. Stages from Complaint Logged to Technician Assigned, Visit Done and Closed. Linked to the original deal so you can see what product was sold.
3. Purchase and vendor approvals. Request Raised, Manager Approval, Finance Approval, PO Sent, Material Received.
4. Admissions in an institute. Enquiry Verified, Documents Submitted, Fee Paid, Batch Allotted.
5. Installation and commissioning. For machinery or solar companies, track the project after the deal is won.
6. Contract renewals. Track AMC or subscription renewals separately from new sales.

A real example from our own work: Q-Line Biotech and Q-Line Nutraceuticals run two separate Bitrix24 portals. Their Distributor Onboarding smart process existed in one portal, and Acemagick recreated it in the other with the same stages and fields, so both companies follow an identical onboarding method while keeping their data separate.

How do you design a smart process step by step?

The software part takes minutes. The thinking part is where most people go wrong. Follow this checklist before you click "Create".

1. Write the process on paper first. List every step from start to finish, and who does each step. If two people describe it differently, settle that first.
2. Decide the stages. Keep it between 4 and 8 stages. Each stage should mean something has actually happened ("Documents Received"), not a vague state ("In Progress").
3. Define the "done" and "failed" outcomes. Every smart process needs a success stage and at least one failure stage (Rejected, Cancelled, Duplicate) so reports make sense.
4. List the fields. Only add fields someone will actually fill and someone will actually use. Mark the truly essential ones as required.
5. Choose the links. Should each record link to a contact, a company, a deal, or all three? Turn on only what you need.
6. Set permissions. Who can see all records, who can see only their own, and who can move stages?
7. Add automation per stage. For example, when a record moves to "KYC Pending", create a task for the operations executive and send the applicant a WhatsApp message listing the documents.
8. Build a simple report. Count of records by stage and average time spent per stage is enough to start.
9. Test with 5 real records. Run real cases through it before announcing it to the team.
10. Train and write an SOP. One page that says who moves the card, when, and what must be filled.

Which automations work best inside a smart process?

Automation is where smart processes earn their keep. Because each stage can trigger rules, you can remove most of the manual chasing. Common ones we set up:

• Task creation on stage change. The moment a service ticket reaches "Technician Assigned", the technician gets a task with a deadline.
• Reminders for stuck records. If a record stays in one stage longer than a set number of days, notify the owner or their manager.
• Customer messages. Send an email or WhatsApp update when a stage changes, so customers stop calling to ask for status.
• Approval routing. Move a purchase request to the right approver based on the amount field.
• Auto-creating records. When a deal is won, automatically create an installation record in your installation smart process, copying the customer and product details.

That last one is powerful. It connects your sales pipeline to your operations work, so nothing is lost in the handover between teams. For more ideas on what to automate first, our guide on sales automation with CRM covers priorities that apply here too.

What mistakes should you avoid with smart processes?

We have cleaned up enough portals to know the usual traps:

• Creating a smart process for everything. If a process has two steps, a simple task or checklist may be enough. Smart processes are for work with a real lifecycle.
• Too many stages. Twelve stages means nobody moves cards correctly. Merge stages that are always done together.
• Too many required fields. People start entering junk just to save the record. Require only what is truly needed at each stage.
• Duplicating contact data. Do not create "customer name" and "phone" fields inside the smart process. Link to the contact record instead.
• No owner for the design. Someone must own each smart process and approve changes, or it slowly becomes unusable.
• Ignoring the reports. The biggest value is seeing where work gets stuck. Review time-in-stage every month.

Are smart processes available on every Bitrix24 plan?

Availability and limits (such as how many smart processes you can create) depend on your Bitrix24 plan and change from time to time. Check the current Bitrix24 pricing and plan comparison page before you plan your design, or ask your partner to confirm. If you are deciding between plans, our comparison of the Bitrix24 free plan and paid plans explains how to think about upgrading based on what your team needs.

When should you get help building them?

You can build a simple smart process yourself in an afternoon. It makes sense to bring in a partner when:

• the process touches several departments and needs approvals,
• you need data moved in from Excel or an old system,
• you want it connected to WhatsApp, a payment gateway or an external app through the API,
• or you want the same process copied across multiple portals or companies, as in the Q-Line case.

At Acemagick, we usually map the process with the department head in one working session, build it, run test records together, and then train the team on Zoom with recorded videos for later reference. Every implementation also includes our SOP/KRA/KPI framework, so each stage has a clear owner and measure. You can see how this fits into a full rollout in our Bitrix24 CRM implementation process guide.

The bottom line

Smart processes are one of the most useful and least used features in Bitrix24 CRM. They let you bring operations, service, onboarding and approvals into the same system as sales, without polluting your sales numbers. Start with one painful process that currently lives in Excel or WhatsApp, design it on paper, keep the stages few and meaningful, and add automation stage by stage.

If you want a Bitrix24 Gold Partner to design and build your first smart processes with you, talk to the Acemagick team.