The agent answers customers from your catalog, price list and policies — on your website and in messengers, around the clock. When a question goes beyond the knowledge base, it calls a person and hands over the whole conversation.
40 unread messages in WhatsApp. Half of them ask about delivery costs to Yekaterinburg, which has been on the website for months.
At night a customer messages three shops at once and buys from whoever answers first.
A button bot walks people through a menu, but customers type in their own words and drop off at step three.
A new operator spends a week confusing the terms and promises a discount your policy does not allow.
What changes after launch
01Customers get accurate answers from your price list at any hour
02Operators handle the tricky cases, not the FAQ
03Chats end in a request, not «thanks, I will think about it»
How the agent works
01
We build the knowledge base
Price list, catalog, delivery and return terms, website pages, the best answers your operators have given. The agent answers only from these materials.
02
We connect the channels
Website widget, Telegram, WhatsApp, VK. One set of answer logic, with a separate connector for each platform, because their APIs differ.
03
The conversation leads somewhere
The agent does not stop at an answer; it suggests the next step: pick a product, book a demo or site visit, submit a request to the CRM.
04
A human steps in at the right time
A complaint, a custom discount, a question outside the base: the chat goes to an operator with full history, so the customer does not repeat themselves.
05
The gaps get closed
Questions the agent could not answer land in a report. We add the missing pieces, and next time it answers on its own.
One task, three different projects. Pick the one that looks like you and press “I want this” — your request arrives tagged, and we send an estimate in 1–2 days.
Small business
common start
An online shop or service business where the owner or a single operator answers chats in between everything else.
What we build
Knowledge base from your price list, FAQ and website
Website widget or one messenger
Handoff to a human
Requests sent to CRM, email or your team chat
Integrations
Website, Telegram or WhatsApp, amoCRM or Bitrix24 if needed
Where it runs
Cloud
Timeline
Guideline: 3–4 weeks to the first working version
Mid-size business
common start
Several channels, a catalog in your ERP, branches or pickup points, and customers asking about stock and order status, not just prices.
What we build
Website and all messengers with one answer logic
Stock, prices and order status from ERP (1C) or CRM
Routing chats by branch and product line
Replies in Russian or English, matching the customer
Support contract and regular knowledge base updates
Integrations
ERP (1C), CRM, warehouse system, online booking
Where it runs
Cloud or your own server
Timeline
Guideline: 1.5–2.5 months to the first working version
Enterprise
A chain or group with several brands and countries, where legal signs off on every customer-facing phrase.
What we build
Separate knowledge bases per brand, country and product
Sensitive topics answered only with approved wording
Operator and supervisor roles, SSO, conversation log
Integration with your contact center queues
Service under an SLA
Integrations
Contact center, corporate CRM, ERP, internal APIs
Where it runs
Closed perimeter on your servers: conversations and models stay inside, in line with Russian data law (152-FZ)
Timeline
Guideline: 3+ months, channels rolled out in stages
Pilot from RUB 300,000. Beyond that we price by task and hours.
Questions
Will the agent make up prices and terms?
The agent answers from your knowledge base, not from the model’s general knowledge. If the answer is not there, it says so and hands the chat to a person. Discounts, returns and other sensitive topics can be limited to approved wording only.
Have you built this before?
Yes. We built ChatNeuron, a platform of AI agents for websites and messengers that answer from company documents and create requests in the CRM. It has 10+ paying customers. We bring that experience to your project, but the agent is built around your process and your systems.
Why is this better than a button bot?
Buttons work as long as the customer follows the menu. The agent understands free text, asks follow-up questions and brings the conversation to a request. You can still keep buttons where they are handier, for example to pick a branch.
Where are customer conversations stored?
In the cloud or on your servers — we decide at the start. If data cannot leave your perimeter under 152-FZ, we deploy the agent in a closed environment.