Deals and pipelines
The Clients & deals module is the sales funnel from inbound request to a closed deal.
In the module
- client and contact cards with communication history;
- deal pipelines with configurable stages;
- leads with manager auto-assignment;
- activity feed on the client and the deal;
- close checklist.
CRM core (clients, leads, deals, pipeline) is in the platform; richer sales scenarios open with the commercial module.
Pipelines and stages
An organisation may have several pipelines. A stage has a key, label, and order. Deals move by hand or on facts (not an AI guess):
- a commercial proposal sent → “Proposal” stage;
- a contract signed (contract document or EDS in docflow) → “Contract”;
- invoice payment syncs with the deal.
Auto-advance is forward only and audited. Stage changes can create tasks from pipeline trigger rules.
Leads
Requests from WhatsApp, Telegram, the website, and email enter one intake point. The same external id does not create a second lead.
Existing-client match: Kazakhstan phone formats (+7 / 8 / 10 digits), email, BIN, Telegram id. A similar name warns about a possible duplicate and never merges cards automatically.
If no manager is set on create, auto-assign runs (/settings/lead-auto-assign):
- off — unassigned;
- round-robin among roles or an explicit list;
- a fixed person.
“By load” picks whoever has fewer open leads and deals.
Lead-to-deal qualification: immediate, rules (need + budget), or a manager button only. Spam and vacancies may archive after parse; support intents can become a Help Desk ticket.
AI parse of lead text is off by default. Only the owner can enable it. Calls go through the depersonalisation perimeter; if the AI budget is exhausted, rules still run without a model.
Close checklist and deal documents
A document pack (proposal, contract, invoice, act) sits next to the deal when Documents is on. Opens and clicks on proposal emails are measured with a pixel and redirects, with no synthetic metrics.
See clients, reminders, deal summaries, channels.