Sales, support and customer work

Does it replace your CRM?

Diagram: how a request moves through the CRM
  1. Requestfrom the website: “We need an implementation consult”
  2. Carda number, consent to contact, a lead in the pipeline
  3. Drafta proposal from a template; AI drafts analysis and a script
  4. A person decidesthe manager checks it and sends it from their own mailbox
A diagram of work with requests, not a screenshot. The example is a fictional company.
The product panel, recordedA staff member answers a customer with a confirmed formulation — the link to it stays in the reply record. Demo stand, fictional clinic data; this part of the panel is in Russian for now.

What works

The deal card is here too, but the product is the work around it: intake, queue, draft reply, approval and a record of the decision the application cannot change or erase. Companies, contacts, leads, deals, proposals and requests live in the platform itself.

More detail
  • Website intake: each request lands in a project with a number and consent to be contacted; switched on at implementation (declare the domain, enable the widget). No captcha: a domain check, a one-time session and rate limits protect the form.
  • Sales CRM: contacts, leads and deals by stage; proposals with versions and prices approved by the owner; e-mails a person confirms and sends from their own mailbox; reminders, CSV and XLSX import, exports, analytics. Salespeople see only their own records; the AI assistant only drafts.
  • Requests: a queue with priority and assignment, closure with a named outcome, time to first reply computed by the database; messages are append-only.
  • Scores: model and human scores are separate fields; only a person fills in the human one, and no combined customer score is shown.

Limits

AI employees write nothing to customers themselves: a customer gets a staff member’s reply or, in the website chat when it is on, a verbatim confirmed answer; with no exact answer, the chat offers to pass the question to a specialist.

More detail
  • Your existing CRM (Bitrix24, amoCRM, HubSpot): a generic REST contract whose driver is tested only against a local receiver; your side needs a thin receiver.
  • Calendar and accounting: declared, with no drivers.
  • Instagram: connected at implementation; intake and drafts are written and work once a Meta app is set up for your account.
  • WhatsApp: the next channel; there is a business account, and connecting it to the product is the next development step — it is not a working channel yet.
  • Ad platforms: a simulated contract that answers “no configuration”; nothing changes in an ad account.

Basis: the registry of modules and industry templates; product documentation; the AI employee registry. This page describes what exists in this build, not what is planned.

We will show the system on one of your processes.

A 30-minute demo, no prepayment and nothing to install. Write to us and we will agree on a time.

Book a demo