Home · Chatbots for agencies: each client is a separate bot
Agencies and freelancers
Chatbots for agencies: each client is a separate bot
Each customer has his own bot with channels, scripts, contacts and plan, and all bots are in one “My bots” list. You give the client exactly the access he needs: to configure the bot or just respond in “Conversations”.
plan - per bot, channels without additional paymentRoles Owner, Administrator, Operator33 flow templates
What does CHBT give to the agency
One client - one bot
The bot has its own channels, scripts, “Conversations”, “Contacts”, “CRM” and plan - the data of two customers does not overlap. All bots where you are the owner or participant are collected in “My Bots”; the transition between them is “change bot” in the menu.
Roles for the team and the customer
In the “Access” section, you invite an Administrator by e-mail - he sets up the bot, channels and team - or an Operator, who replies in the “Conversations” and sees contacts and CRM. The bot has only one owner and cannot be changed.
33 templates and AI assembly
Registration, leads, quiz, FAQ, support, reviews, auto funnel, QR buyer bot - in the “Getting Started” wizard and on the page templates, at any plan. From Basic - a draft according to the description “Assemble with AI” and “AI edit”.
Copies, versions and test chat
“Duplicate” makes a disabled copy of the script for a new branch, “History” stores versions with the “Restore” button. “Check script” opens a test chat in the editor: nothing goes to clients, the conversation limit is not spent.
One script for all channels
The client added MAX to Telegram - you connect the channel in “Channels”, you don’t have to redo the script. Where the texts should differ, set the “Condition” in the “Channel” field. There are as many channels in the bot as you like, they do not affect the price.
Connection with client systems
Ready-made connections to Bitrix24 and Omnidesk, dialog events for Make, n8n, Albato or the client server, “HTTP request” in the script and a public API for responses from helpdesk - in the “Integrations and API” section, at any plan.
How to launch a bot for a client
-
1
Decide whose bot it is
The owner is the one in whose account the bot was created, and it cannot be changed later. For a long-term project, a client bot is more convenient: it registers on app.chbt.io itself, and invites you as an Administrator.
-
2
Create a bot and take a template
In “My Bots”, click “Create a Bot”, then in “Scripts” - “All Templates and AI”: the “Getting Started” wizard will offer a “Ready Template”. Correct the texts and click “Check Script”.
-
3
Connect client channels
In “Channels” - the Telegram bot token from @BotFather, the MAX token, the VKontakte community key or “Widget for the site”, its “Embed Code” - in the “Widget”. The script from the wizard is already included.
-
4
Grant access and pay
From Basic to “Access” → “Add participant”, specify the e-mail and role: “Admin - configures the bot” or “Operator - answers in conversations”. The plan is paid in the “Payment” of this bot.
Roles: who sees what and rules
| Role | Maybe | Can't |
|---|---|---|
| Owner | Everything: channels, scripts, widget, broadcasts, AI agents, integrations, “Payment”, participants and their roles | Transfer the bot to another account. The owner cannot be removed from the bot |
| Admin | Same as the owner: scripts and test chat, channels, contacts and CRM, broadcasts, AI agents, integrations, “Payment”, inviting participants | Change or remove owner, remove another admin |
| Operator | Reply in “Conversations”, assign conversations, write notes and quick replies; view contacts, CRM and scripts; upload contacts to CSV | Edit scripts and launch test chat, change channels, widget, broadcasts and integrations. The “Payment” section is not visible to him |
The role is chosen by invitation. To change it, invite the same e-mail again with a different role. The owner can remove a participant using the “Delete” button; the administrator can only use the operator button. Client employees who respond to customers will have enough Operator role: they will not turn off the script or turn off the channel by mistake.
- You can only invite someone who already has an account in CHBT: first the person registers, then you add his e-mail.
- On the Free bot, only the owner is in the bot. There are as many participants as you like from Basic.
- The owner and admins receive letters about new leads, payments and channel failures. By default, they are enabled and configured in “Account → Notifications” - for all bots at once.
- Push about transmitted conversations is sent to all bot participants who have it enabled; The office is installed on the phone as an application.
- In the history of the conversation, the answer is signed “Operator” - it is not visible which member of the team answered.
Whose bot and who pays: two schemes
| Bot in agency account | Bot in client account | |
|---|---|---|
| Who creates | You - “Create a bot” in “My bots” | The client registers on app.chbt.io and creates the bot himself |
| Who pays | You, in the “Payment” of the bot; you issue an invoice to the client yourself | Client from his card. You, as an Administrator, can do the same - then the renewal will be debited from your card |
| Second party access | Client - Administrator, if he edits the texts himself, or Operator, if he only answers | You are the Administrator. The client will be able to invite you after switching to a paid plan |
| When the project is finished | The bot cannot be transferred: it will have to be reassembled in the client’s account | The client deletes your access in “Access” - the bot, channels, contacts and history remain with him |
You can create your second bot when at least one of your bots is paid for on Basic or Business; a new bot appears on Free - it’s convenient to collect demos on it. The bots you were invited to are not included in this count. The script is not copied between bots, so you will have to rebuild the demo from your account in the client bot - this is quick with a template.
By policy CHBT buyer personal data operator is the user who created the bot, and CHBT processes it on his behalf. More details in the article 152-FZ and chatbot.
- Price - per bot per month: Basic 650 ₽, Business 1290 ₽. Channels, scripts and participants - no extra charge.
- Payment by card via CloudPayments in 30 days. With a linked card, the plan is automatically extended one day before the end of the period; a reminder letter is sent in advance.
- “Disable auto-renewal” does not burn paid days: the plan works until the end of the period, then the bot switches to Free.
- A receipt for payment is sent to the e-mail of the person who paid, and for auto-renewal - to the e-mail of the bot owner.
- Each bot has its own AI credits: when paying, the balance is replenished to 150 for Basic and up to 500 for Business.
Client channels and systems: what is needed and where to connect
| What do we connect? | What is needed and where in CHBT | Disclaimer |
|---|---|---|
| Telegram | Bot token from @BotFather → “Channels” → “Telegram” | The webhook CHBT is installed by itself. If the bot was working in another service, it will stop receiving messages |
| MAX | Bot token from the MAX account for business → “Channels” → “MAX” | CHBT automatically subscribes the bot to events |
| VK | “Channels” → “VKontakte” → “Connect via VK” (the community admin signs in with VK ID) or a community key with the “Community messages” and “Community management” rights | CHBT sets up the Callback API itself. Messages and bot features in the community are enabled by its admin |
| Site | “Channels” → “Widget to site”, then “Embed code” from the “Widget” section - to the client’s site | On the Free version, the window says “Powered by CHBT” |
| Bitrix24 | Portal incoming webhook address → “Integrations and API” | A lead comes without a phone number or e-mail, every event is a new lead |
| Omnidesk | Address, employee e-mail, API key and custom channel → “Integrations and API” | Text only. An employee needs access to a custom channel |
| amoCRM, RetailCRM | Conversation events in Make, n8n or Albato, from there to the client’s CRM | These CRMs are not directly connected. There is no phone or email in events |
| Phone number and questionnaire answers | Action "HTTP request" in the script: POST with JSON - contact id and tags, script variables, message text, channel | The phone will go away if “Data Collection” saves it “Into a variable”. No replays on failure |
| The client's Helpdesk responds itself | Token in “API Tokens”: response to the buyer’s channel and “online operator” status | Only in an already started conversation; response via API transfers the conversation to the operator |
| Running a script from outside | Trigger "Incoming webhook" with a secret | Does not send a message to an existing client in Telegram or MAX; We need a “Widget for the site” channel |
Subscribing to events in “Integrations and API” returns six events: “Message from the buyer”, “Response from a bot or operator”, “Dialog has started”, “Conversation transferred to a person”, “Conversation closed” and “New contact” - with the name and id of the contact, without phone number and e-mail. The subscription tries to deliver the event up to five times.
If the built-in is enough for the client, the requests remain in CHBT: the “Deal in CRM” action opens a deal, and “Export CSV” in “Contacts” unloads the database. The transactions themselves are not uploaded outside. Event formats - in webhook help, API methods - in API Help.
For a client-shop, the catalog is a separate service: the bot replies on the customer’s prices and assortment, and not on the text, which would have to be edited manually. The product feed via the link (YML, Google Merchant, CSV) is connected in the “Marketplaces” of its bot, the CSV, TSV or JSON file is uploaded in “Sales”. Using the API key of the Wildberries seller, cards with prices and the number of new orders, reviews and questions are received; Ozon reads new FBS orders and reviews, Ozon catalogue, Yandex Market, Kaspi and Uzum - only as a file. The catalog and prices are marked by the account as “not verified on your key” before the first download, and orders, reviews and questions are marked as “working” even before the first survey. Before you promise this to the client, make sure that the counters on the connection card are growing. Wildberries balances are not readable, but the goods are shown to the buyer AI seller - from Basic.
What is missing for agencies in CHBT
The limits are clear before you launch.
- There is no white label: the account is signed “CHBT”, and in the widget on the Free version it says “Powered by CHBT” - on Basic and Business this signature is removed. There is no branded account for clients.
- There is no agency fee or volume discount: each bot is paid separately at the regular price.
- There is no transfer of the bot between accounts and no change of owner. The script cannot be transferred to another bot or uploaded as a file: “Duplicate” only works inside the bot.
- There is no template library: you cannot save the script as a template for future clients. Keep the blank in a separate bot as a sample and reassemble it based on it.
- There is no common inbox and report for all bots: “Conversations”, “Contacts” and “Analytics” are different for each bot; you switch between bots through “My Bots”.
- The public API is narrow: only conversations - list, correspondence, reply, close, transfer to person and “online operator” status. flows, channels and contacts are not created through it.
Available plans
Each bot has its own plan, the price is per bot per month, channels without additional payment. On Free - 30 conversations per month (different interlocutors), “Steps” mode, without AI and broadcasts, you cannot invite a second person to the bot. Your second bot is created when at least one of your bots is paid for. Business trial day without a card - one per owner.
Works with
FAQ
How many bots can you manage in one account?
There are as many bots as you’ve been invited to. There is only one of your own on Free: you can create a second one when at least one of your bots is paid for on Basic or Business, and a new one will appear on Free. A paid bot costs 650 or 1290 ₽ per month, the channels inside are free of charge.
Is it possible to give a client access to correspondence only?
Yes - the Operator role in the “Access” section. He replies in “Conversations”, assigns conversations and writes notes, and sees contacts, CRM and scripts as read-only; “Payment” is not visible to him. You can invite participants using the Basic plan; the invitee must have an account in CHBT.
How to transfer the bot to the client after the project is completed?
There is no transfer between accounts or change of owner, and you cannot transfer the script to another bot. Therefore, for a long-term project, it is better to immediately work in the client’s bot: it registers, switches to Basic and invites you to be an Administrator. After surrender, he deletes your access - the bot, channels and database remain with him.
Is there a white label or agency rate?
No. The signature “Powered by CHBT” in the widget is removed on Basic and Business, but there is no branding of the account and no special price for agencies - each bot is paid separately at the regular rate.
How to connect a bot with a client’s CRM?
With Bitrix24 - a ready-made connection in “Integrations and API”: a conversation event creates a lead, but without a phone number and e-mail. Correspondence with Omnidesk goes both ways. For amoCRM, RetailCRM and tables - events or the “HTTP request” action via Make, n8n or Albato; The phone only sends an “HTTP request”.
How to show a bot to a client before launching?
“Check script” opens a test chat in the editor: messages go through the real engine, nothing is lost to clients. But there are no buttons in the test chat, and threads on them cannot be checked there. For a live demo, connect your test Telegram bot to the bot, and after approval, replace it with the client bot.
Who pays the plan if the bot is in the client’s account?
Any owner or admin of the bot - in the "Payment" section. The card is linked to the bot: if you were the last to pay, auto-renewal one day before the end of the period will be debited from your card. A receipt for payment will be sent to you, for auto-renewal - to the owner’s e-mail. Auto-renewal is disabled there, paid days are saved.
Build a bot for your first client
Create a bot using the Free plan, take a template and test the script in a test chat. Connect participants, AI and mailing lists when the client approves the launch.