1C
Your own APIsWhat it does
Answers where your clients already write, shows the goods and takes payment — on its own address.
Generative UI
It doesn't describe the product — it shows it.
Ask a question and the employee builds cards from your catalogue, fills a cart and issues an invoice. The client never leaves the chat.
Public page
Every employee gets an address.
anyworker.ai/name opens like a messenger: the client writes, the employee answers from the knowledge base and files the lead in your CRM. Nothing to install.
- A link instead of a form
- The client gets an answer now, not after a ticket.
- Your look
- Logo, colours, greeting and quick questions.
- One memory
- Chats from the page land in your CRM and the employee's history.
- Under control
- Every action is visible: what it said, saved and sent.
- anyworker.ai/namePublic employee page
TelegramA bot answering as your employee
WhatsAppOfficial API, history in CRM
How you run it
You decide what it learns, what it settles alone and what it brings you to sign.
Builder
Employees, rooms and chains in one workspace.
The three tabs below aren't screenshots. Click through and watch the product work.
Employees
Core
Knowledge base11 files · 18 MBInstructions4 rulesConversations1,284Skills
SizingInstall quoteDeliveryInvoices in MoySkladInstalmentsConnections
TelegramWhatsApp
Bitrix24
MoySklad
amoCRM
BrowserKnowledge and memory
It knows your price list — and remembers each client.
Upload files or connect Google Drive: the employee indexes them and answers only from what's there. Memory about people is kept separately.
Memory is visible line by line and any line can be forgotten. Your data never goes into model training.
Files
Google Drive · Catalogue 2026syncingMemory per contact
Approvals
It doesn't decide the big things without you.
A discount above your threshold, a refund, a letter to a large client — the employee prepares the decision and queues it. One tap and it carries on.
Waiting for you: 3
- 7% discount for Grand Hotel LLCYour threshold is 5%. The client takes nine split systems and pays by invoice.
- Refund of 18 900 ₽ on order #2317Unit opened, the fault was confirmed by the service centre.
- Proposal for the Green House chainNew client, over 500k ₽ — the email is ready to send.
Artifacts
You get a document, not a thread.
Invoices, proposals, specs and reports come out as files. Every file keeps versions — what changed and who asked for it.
7% discount added as its own line
Lead time: 3 business days, Moscow
Payment: company invoice, 14 days net
12-month warranty pulled out into its own clause
Team
One employee, several people around it.
Seats, roles and invites. A member sees their rooms, an admin sees settings and connections, the owner sees the bills.
Seats used: 3 of 5
What you get
Where the money came from, what it costs and how to start.
Results
You can see which conversation became money.
Every conversation passes three stages and stays linked: from a payment you can walk back to the client's first line and see what the employee promised.
- stage 1ConversationWho wrote, which channel they came from, what they asked.
- stage 2LeadThe employee recognised the intent and filed the deal in your CRM.
- stage 3PaymentThe invoice is closed — and you see the conversation behind it.
- WhatsAppOfficial API, history lands in your CRM
- TelegramA bot answering as your employee
- Public pageThe page conversation lands in the CRM and the history
No numbers here on purpose — someone else's turnover says nothing about yours. You'll see your own from day one.
a platform, not just a chat
What it takes for an employee to actually work.
Answering in a chat is the easy part. The rest decides whether it survives its second week.
Your data leaves with you
Export the conversations, files and settings yourself, whenever. Leaving is two buttons, not an email to support.
Live by this evening
A price list, a role, a channel - and it answers. Not a quarter-long project with an integrator and a spec.
Learns from your edits
Fix an answer and it keeps the rule. No rewriting the whole instruction over one sentence.
Roles ready to take
Sales, support, sourcing, paperwork. Start from the nearest one and change it, instead of a blank page.
Every answer is visible
The conversations, the actions and the spend, in one place. Anything hard goes to a person rather than getting invented.
Getting started
Three steps to the first client answer.
- 1a minuteCreate the employeeName, role and tone. It gets an address at anyworker.ai/name straight away.
- 2about an hourGive it knowledgeThe price list, installation and warranty terms, past manager answers — as files or a Google Drive link.
- 35 minutesConnect a channelTelegram, WhatsApp or just the link — and the client writes to it, not to you.
Pricing
Three plans: from one assistant to your own environment.
You pay for the work, not for seats.
A plan is an allowance of actions, not a headcount. How many employees you assemble, and who you let into the workspace, does not move the price.
- 1 AI assistant
- Yandex, Google and Mail: mail, calendar, drive
- Telegram, WhatsApp and MAX
- Knowledge base and memory of every contact
- Public anyworker.ai/name page
- 1 user
- 3 employees and 4 rooms
- Rooms and the chain builder
- CRM, MoySklad and messengers
- Browser agent
- Isolated knowledge base
- Custom integrations and API
- Unlimited users
- Everything in Business
- A dedicated environment or your own server
- Your own models and limits
- SLA and dedicated support
- Contract and closing documents
- Help with the rollout
- Training for your team
Business is 60 000 ₽ a month. Enterprise starts at 150 000 ₽: what it comes to depends on the number of employees, the connections and the volume of work, and what sets it apart is a dedicated environment, its own models, the contract and the SLA, not a starting price.
What it comes to in money
The same professions as further up this page, now with numbers on them. Put in your own salaries: we do not know your market, and you do.
The gain
Run it on your own numbers.
Switch on the roles you need right now and set the salaries your city actually pays. On the right, the same work on a subscription.
Who you are hiring
Answers enquiries and carries them to payment
Answers customers, including at night
Copy, posts, newsletters
Quotes, invoices, contracts
Correspondence, reminders, the daily digest
Moves enquiries across and fills in the records
Walks the sites itself and collects prices
What it comes to
hours a month from the payroll — and only if nobody is on holiday
from the employees: nights, weekends and holidays are working hours
Quality
Not everything is money. The bottom two rows are where a person is better, and leaving them out would have been dishonest.
On your figures: salary plus 30% employer contributions plus 8 000 ₽ a month for a desk, per person. An estimate, not an offer.
Questions
What people ask before they pay.
It answers only from what you uploaded. When the base has no answer it says so and calls a human. Anything above your threshold — discounts, refunds, letters to large clients — goes to approvals and waits for your tap.
In your company's isolated knowledge base. Access follows your roles, and export and deletion are available at any time.
By email and password, or through Russian IDs — VK ID, Yandex ID and Mail ID. A social identity is linked to the account rather than replacing it: a password can be added later and the link removed. Which methods appear is yours to decide in settings.
No. Your files and conversations are used only to answer as your employee and never go into model training.
The first working employee takes under a minute. Sensible answers from your price list take about an hour — that's uploading the files and checking a dozen questions.
No. Employees, rooms and chains are built by mouse; Telegram and WhatsApp connect through a wizard. A developer is only needed for a custom integration — there are webhooks and an API for that.
It takes the repetitive part: stock, price, delivery, invoices, order status. Your managers stay on the hard deals and see the whole conversation when they step in.
Bitrix24, amoCRM and MoySklad connect through a wizard: deals, invoices and stock move both ways. 1C connects through its standard OData interface — the employee reads products, stock and documents and, if you allow it, creates and posts documents. Anything else goes through webhooks.
It answers in the client's language: Russian, English and more. Tone and address are set separately from language.
One step of the employee's work: an answer, a knowledge-base lookup, a CRM write or a chain step. Reading history and changing settings cost nothing.
Yes. Conversations, artifacts and the knowledge base export as one archive — «Download my data» in account settings, no support ticket. After you delete the account the data is erased 30 days later.
VK ID
Яндекс ID
Mail ID