To go live
set up by your staff, not by a developer
To the first answer
it starts typing at once, with no waiting
Always on
no days off, no queues, no breaks
One assistant for your clients and your team
It does not paraphrase — it shows and acts
Where an ordinary chatbot would send a link to some page, the assistant lays out cards, opens a form and sees the job through — in the same window.
Shows the products as cards
The client describes the task in plain words — the assistant lays out matching items with photo, price and availability, and compares them.
Opens a card and puts a second beside it
A card in the answer opens into a panel with photos, price and specs. Pin it and open another alongside — the client compares them without leaving the chat.
Answers from the policy and shows the document
An employee asks in their own words about leave, access or a process — the answer comes with the document and the passage highlighted.
And that is only the start of the list
What exactly it can do is up to you. Below — what it is built from: data, character, actions and channels.
PEOPLE
Finds the person and opens their card
A colleague, a technician, a doctor, a coach — matched to the task, with the card opened: photo, expertise, contacts. Two can stand side by side.
LIVE DATA
Checks against your systems
Stock, prices and statuses — from 1C and CRM as it answers.
HARD CASES
Hands over to a human
With the context already collected — no repeated questions.
Who it becomes is your call
The persona sets the goal. Advise gently and carry the client to a purchase — or serve B2B accounts precisely. The instruction is written in plain words, with no markup and no scripts.
- Clarifying questions
- Matching the budget
- Closing the order
- Answers from policy
- Diagnostics
- Callout requests
- Catalogue knowledge
- Comparing models
- Bundles and upsell
- HR questions
- Policies
- Internal services
Documents. Policies, manuals, contracts and materials. The record key is the file name.
Products. Items with a price, category, attributes and photos. The key is the SKU.
Profiles. People records: speciality, experience, languages, contacts. The key is an external code.
Not a folder of files, but three different kinds of data
Almost every assistant handles documents only. Here products and people are entities in their own right, each with its own fields and its own key. That is why the assistant shows a card and matches a specialist instead of paraphrasing a description. Re-uploading updates the records rather than breeding copies.
A product is more than a product
A catalogue item can be anything you sell. An apartment, a credit card, a subscription plan or a bearing replacement — the fields differ, the mechanics do not.
Retail and electronics
Appliances, tools, components — compared by specification and assembled into a kit.
Clothing and footwear
Sizes, colours, collections. The client describes a look in words and the assistant shows the matches.
Real estate
Units with floor plans, area, district and price — matched to a budget and a family brief.
Banking products
Cards, deposits, loans and plans as catalogue items — with terms, rates and limits.
SaaS and subscriptions
Plans, limits and modules: the assistant explains the difference and leads to the right one.
Services
Repair, maintenance, training, delivery — with parameters, lead times and labour cost.
Who can be given a profile
Outward-facing they are your specialists — the assistant matches the client to the right person for the job instead of returning a list. Inward-facing the same records become the staff directory: the intranet assistant answers who does what and who to go to.
From dragging in one file to a bucket of hundreds of thousands
Start with a single file and grow into automatic synchronisation. A small team gets by with drag-and-drop; a large business gets feeds, object storage and a site crawl. There is no need to describe the source structure: columns from 1C, Bitrix, Yandex Market, Ozon, Wildberries and AmoCRM are recognised on their own, and unusual ones are parsed by the model.
A product or profile record filled in by hand — good for the first few.
Upload it as it is
A skill is an action in the chat, not a text reply.
SKILL · SERVICES
Booking an appointment
The client picks a time in the chat — the slot is taken, a reminder goes out, the request reaches you.
SKILL · SALES
A request inside the chat
The form opens in the chat window: name, phone, a comment — the client never leaves the page.
SKILL · ESTIMATE
A price calculator
The assistant asks the questions and works out the price — the client leaves with a figure, not with "ask a manager".
SKILL · MAP
Points on a map
The nearest branch or pickup point — on a map inside the chat, with directions.
Ready-made skills
booking, request, estimate, map — switched on with a toggle
Build it for yourself
the skill creator: describe the steps in words, it assembles them
An organisation catalogue
publish it and other projects can switch it on
Live data inside the chat
A connector is the bridge between the assistant and your systems. It fetches prices, stock and statuses at the moment of the question — from 1C, CRM, ERP or your own API. The assistant decides for itself when to go and get them.
The assistant goes where your client already is
One core, as many channels as you like. The data is uploaded once — after that you choose where the assistant meets the user: on the site, in the cabinet, inside your own systems, in an app or in a closed perimeter. A new channel is a switch, not a second project.
The widget goes in with one line and works everywhere the client asks questions — on the site, in the portal and in the customer cabinet.
Widget
Your identity · SSO sign-in · history and ratings
Six reasons to trust the cabinet with people
The cabinet is your perimeter. A ready portal with the assistant on your own domain: no site and no development. The data and the accounts stay under your control, and the assistant answers only from the sources you uploaded.
Two methods — chat and search
The interface is deliberately terse. Behind the two calls stands the whole platform: the same knowledge base, the same skills and connectors as in the widget. It embeds into your apps, bots and services.
A question, an answer from your data — with chat memory, skills and handover to an operator.
Semantic search across the knowledge base: it finds by meaning, not by word match.
On-premise: everything inside your perimeter
The platform is deployed on your infrastructure and reaches nothing on the outside while it runs. Orange marks what we install. The database, the storage and the language model stay yours.
What the delivery includes
The whole platform arrives in the perimeter, not a trimmed-down build. The same capabilities as in the cloud. The full list of artefacts and requirements is in the delivery documentation.
A platform on your terms
Three layers that everyone else hard-wires into the product are yours here: the language model, the embedding model and the pricing model. The perimeter, the models and the sign-in are configured to your requirements — and everything you have already loaded stays in place.
A fully isolated perimeter
Deployed entirely on your infrastructure, air-gap included: while it runs, the platform calls no external service at all.
/02Your language model
Any OpenAI-compatible service — YandexGPT, GigaChat, Qwen, Cotype or your own corporate one. Switching the model is a config edit, not a migration.
/03Embeddings, ours or yours
The embedding model ships with the platform, but the service address and the vector dimension are config parameters: you can plug in your own, fine-tuned on your data.
/04With tool calling and without it
If the model supports function calling, skills and connectors are declared to it as tools. If it does not, the decision is taken while the answer is composed. The functionality is the same.
/05Corporate sign-in
SSO over OpenID Connect, Keycloak and ADFS included. The private key stays with you and multi-factor authentication works unchanged.
/06Speech and text-in-image, on request
SpeechKit for transcribing audio and video and OCR for text on frames ship as separate components and are switched on if you need them.
Where it already works
Outside and inside — from one project. What you uploaded for your clients already answers your team as well. Every scenario has its own page with a breakdown.
Matches the product and closes the order
Status, returns and booking with no operator
Takes the routine calls off the call centre
Answers from the manual and shows the source
A QR chat at the desk and a prompt for staff
HR, IT and policy instead of a first line
Test it on your own data
Upload your own documents and catalogue — then ask the assistant the questions people ask you. That is the only test that means anything.
Create a project
A separate perimeter for your task — with its own content, access and settings.
/02Upload the data
Drag in files, point at a feed or a site. No need to describe the structure — the columns are parsed for you.
/03Set the character
A name, a face and an instruction: who the assistant is and how it speaks.
/04Switch on a channel
A widget on the site, a cabinet for your staff or an API inside your systems.
Tell us your task
Projects by type grow year over year
MVP, redesign, AI and support — cumulative
The studio profile across key axes
Speed, quality, transparency, engineering
Research, design and build overlap
Parallel streams — not a waterfall