CRM module · Sales and clients
CRM inside document management: the proposal follows an approval route, and conversations land in the client card
Leads, deals, pipelines, and counterparties live in the same system as your documents and routes. A commercial proposal is approved like a document, the price is computed by an exact-arithmetic engine, and Telegram and SMS conversations stay in the client card - not on a manager's personal phone.
Commercial proposal
The proposal follows an approval route - as a document, not as an email attachment
The discount, price, and line items are approved before the client sees the proposal. Approving a commercial proposal uses the same mechanism as approving any document in KASKAD.
A manager assembles a proposal for a counterparty and sends it along an approval route. The responsible people see the line items and the price, and the decision is recorded in the system - the client never ends up holding a proposal with an unapproved discount.
Totals are computed by an exact-arithmetic engine: line items, discounts, and VAT add up to the total without penny-level rounding errors. The total that was approved is exactly the total that lands in the deal and the invoice.
An approved proposal is a link in the end-to-end ERP chain: request → proposal → route approval → deal → warehouse shipment → report. One entry point, one database, no "integration with itself".
- A route, like any document. Until the route is complete, the price is not considered approved: the proposal is signed off by the people responsible for the money.
- Exact price arithmetic. The total matches the line items at any number of rows, discounts, and recalculations - no penny-level discrepancies between the proposal, the deal, and the report.
- Approval stays in the log. Who approved the price, and when, is visible in the audit log; the "which discount was approved" dispute is closed by the audit log entry.
- From proposal to deal. An approved proposal continues the chain: deal, warehouse shipment, report - in one database, with no re-entry of data.
Communication channels
Every client conversation stays in the deal card
Telegram and SMS connect as CRM channels: messages land in the client card, and an inquiry from a conversation becomes a lead.
Telegram channel
A Telegram conversation with a client lands in the card: the message history sits next to deals and proposals and is covered by the same access rights as the rest of the CRM data.
SMS channel
SMS follows the same path: messages are recorded in the same client card. The communication history stays complete no matter which channel the client used.
A lead from a conversation
AI CoPilot reads the conversation and extracts a lead from it: a messenger inquiry becomes a card in the pipeline without manual re-entry. More about AI CoPilot.
Automation and calculations
Rules fire on events; currency and VAT are set once
Sales routine is handled by rules and triggers, while financial settings - the base currency and VAT - live in the organization profile and apply identically across all modules.
- Event-driven rules and triggers. An event occurs - a rule fires: the system reacts on its own, with no manual follow-ups.
- A shared event backbone. KASKAD modules communicate over an event bus - CRM runs on the same events as the EDMS and the warehouse; the same events are available to your integrations under a contract agreed within the implementation project.
- The organization's base currency. The default is the soum. The currency model is shared by CRM, the warehouse, and the ERP loop: amounts mean the same thing in every module.
- VAT in the organization profile. The rate is set once in the organization profile and applied to proposal calculations by the exact-arithmetic engine - one set of currencies and one VAT for the whole platform.
We'll show CRM in a live environment
Tell us about your pipeline and channels - we'll prepare a commercial proposal and walk the path from a Telegram inquiry to a deal and a shipment. The demo takes 40 minutes.