Illustrative example: almost every enquiry in one team is a specific order. Another team first establishes whether a request belongs to the company and can be passed to sales. The same configuration may add a needless handoff for the first team and mix qualification with sales for the second.
The issue is not how “serious” the CRM looks. Establish whether there is separate work before a sale and whether it needs its own outcome.
What differs in Bitrix24
According to the official instructions, classic mode uses leads; simple mode works without them. A lead separates initial enquiry handling, while simple mode starts with a deal and customer information.
A deal is a working record of a particular sale, not proof of money received. A lead should not become an extra card filled in merely because it exists.
Classic mode is not available on every plan. Check your portal's conditions and configuration permissions. Do not apply another zone's plan description to your contract.
When separate qualification helps
Look for a person or team clarifying enquiries before sales receives them. This stage needs inputs, an owner and a clear decision: pass it on, request clarification or end qualification with an explanation.
Illustrative example: a shared channel receives supplier offers and buyer enquiries. Separation may help if the team actually performs an initial check. A large message count alone does not justify another stage.
Define what information passes into sales. Customers should not repeat everything merely because the company changes an internal record.
When starting with a deal is simpler
If an enquiry already contains enough information for specific work and the same employee handles it, an extra entity may add little.
Simple mode still needs intake rules, stages and a next step. No lead does not excuse lost enquiries or unreviewed records.
Choose using a few anonymised cases: an ordinary order, an incomplete request and an irrelevant enquiry. Explain who acts and where history remains for each. Refine a choice understood only by the administrator.
Do not switch a live CRM as an experiment
The instructions warn that switching from classic to simple mode converts open leads into deals and customers. This changes data, not merely menu positions.
Before deciding, review unfinished records, fields, automation, integrations and reports. Define expected outcomes and checks. Use an agreed training set rather than changing the live mode out of curiosity.
For a team in Kazakhstan, check labels in the languages used. “Qualified” must mean the same thing to the sending and receiving sides.
Map the route before configuration
Draw one route from an incoming message to the start of a sale. If the preliminary stage has its own work and decision, discuss it separately. Otherwise do not add it for complexity's sake.
Use the QQDev Bitrix24 implementation page to discuss the route before choosing a mode. Bring actual enquiry types and handoff rules to identify an appropriate configuration without claiming one option is best for everyone.

