The product is assembled from a small core and twenty-three add-ons. The core is always there: the client base, the timeline, data quality, import and export, custom fields, the screens and product-wide search. An add-on brings its own contour — sales, money, marketing, communications or service — and it can be switched on or off at any time without losing data. Below is the whole product: every add-on is shown as a card, and each card opens a detailed story about it — why you need it, what it does, what it is connected to and what it deliberately does not do.
The product core
The core is fully workable on its own: you can keep the client base and the history of every conversation, clean up repeats, load and export data, create your own fields and objects, and search across the whole product. Add-ons connect by choice, so you do not pay attention for what you do not use and the interface stays understandable. How the core is arranged, how the catalogue works and what each add-on state means is described in detail in the Add-ons & Product Composition section.
Sales and money
The contours that move revenue: from the first inquiry to money in the account.
Leads
Every incoming inquiry from every channel in one list: routing to the right salesperson, lead scoring and first-response deadlines.
Deals
A visual pipeline: what stage each sale is at, what to do next, who is involved and what revenue to expect.
Money
Everything from quote to payment: the product catalogue with prices, invoices, payments and what customers owe you.
Marketing
Campaigns and customer journeys on autopilot, with consents handled automatically; reports show what brings in sales.
Partners
A cabinet for resellers and dealers: deal registration, assigned leads and the price lists you choose to share.
Communications
The customer writes wherever suits them, and the team answers from one screen while seeing the same history.
Inbox
Every customer conversation — mail, calls, chat and messengers — in one place, with the full history.
Company mailboxes inside the CRM: shared team mailboxes, reply templates and filters that route incoming mail.
Telephony
Calls without leaving the CRM: click a number, see history and recordings on the customer’s card, and watch who is on the line right now.
Messaging
Customer dialogues in SMS, WhatsApp, Telegram and other messengers, next to email and calls.
Website chat widget
A chat on your website: visitors’ questions, contacts and callback requests land straight in the CRM.
Calendar
A shared company calendar: meetings, calls and tasks with reminders, plus customer self-booking by link.
Notifications
A new lead, an approaching deadline, a customer’s reply — every event reaches the right person.
Service
Looking after customers: requests, deadlines, knowledge and everything around them.
Service
Requests as tickets: each has an owner and a deadline, and queues and ready replies speed up the work.
SLA
Deadline promises under control: working hours, target response times by priority and an early warning of risk.
Knowledge base
Articles with owners and review dates, so answers stay current and customers find solutions themselves.
Portal
A customer cabinet: their own requests and documents, new submissions and the knowledge base — without calling your team.
Contracts
Service contracts: what is covered and until when, renewal reminders and prepaid hour balances.
Shared contours
Three add-ons sit on top of the rest: with them you describe the rules, count the numbers and add whatever the ready-made tools were missing.
Automation
Rules that say “when this happens, do that”, and multi-step processes with a journal and approvals.
Analytics
Reports and dashboards built from your own data, with exports to spreadsheets and scheduled email delivery.
Scripts
Your own Python code for whatever the built-in tools do not cover, when data has to be pulled or sent.
Dependencies between add-ons
Some add-ons rest on others — and that is not whimsy but honesty. The product will not let you switch off an add-on that a working one rests on: it refuses and names exactly who is in the way. On installation the needed dependencies switch on first, so you never have to plan the switching order. Most add-ons depend on nothing and switch on by themselves.
- Money rests on Deals.
- Marketing rests on Leads, Deals and Money.
- Email, Telephony and the Website chat widget rest on Inbox.
- Messaging rests on Inbox and Marketing.
- SLA rests on Service; Feedback rests on Service; Portal rests on Service and the Knowledge base.
- ITSM rests on Service and the Knowledge base; Contracts rests on Service, SLA and ITSM; Partners rests on Portal and Deals.
The four add-on states
Every add-on in the catalogue is in one of four states, and they show at a glance what is installed and what is only being offered:
- Available — shipped with the product but not installed.
- Active — installed and working.
- Disabled — installed, data kept, features switched off.
- Marked for removal — the data will be exported and the service tables dropped on the next restart.
A switched-off add-on adds nothing: its screens are gone from the menu, its fields do not appear on the cards, and its management commands do not answer. The core keeps working as usual, and the data of the switched-off add-on stays in place — it is simply not shown. Switch it back on and everything returns.
How to enable an add-on
The product’s composition is changed in the Addons section, and it is available to the administrator only: an add-on can be installed, enabled, disabled or removed. The management key cannot change the composition — that is always a person’s decision in the interface. Changes apply after a restart, so an accidental edit cannot change the way the product works in the middle of the day. How the catalogue is arranged, how disabling keeps data, how removal exports it first and how updates behave is described in the Add-ons & Product Composition section, and where the catalogue lives in the interface is described in Screens & Workspaces.
Whichever add-on you open, it says the same thing: why you need it, what it does, what it is connected to and what it deliberately does not do. This way the product’s composition stays understandable instead of turning into a list of puzzling names.
Next → CRM Agent documentation