Your agent answers the customer and finishes the job

No. You pay for a plan, and the plan opens a set of channels and modules. Community opens one channel — Telegram. Starter opens five: Telegram, WhatsApp, MAX, VK, Avito. Business adds email and phone. Bitrix24 opens on Enterprise. The exact set for your plan is in the table on the pricing page.

Press “Install” in the control panel and give the module what it asks you for: a channel wants a bot token or a number, an integration wants access to your account in that service. Nothing has to be built, deployed or hand-edited on the server.

We build and sign the official one: it arrives with a core update and we support it. A community module is written by an outside author, submitted through the account area and put through automated checks and moderation; we sign it, but the author owns the code and its future. The card says which one you are looking at: “Official” or “Third-party”.

More than a hundred. The exact number sits above the catalogue and is not typed by hand: the counter takes the overlap of the core release with the signed storefront, that is, exactly what your installation will really pull. How many of them your plan opens is a separate question, answered by the plan table.

The channel stops receiving and sending messages; the integration stops calling the outside service. Conversations, the agent’s memory and the module’s own settings stay where they were: switching off deletes nothing. Switch it back on and work resumes from the same point, with no re-setup.

If you install on your own server, it lives on your server: conversations, access keys and the agent’s memory sit in your database. Only what the work cannot happen without leaves it: the request text goes to the model you chose, the method call goes to the service you connected. In the AiHummer cloud the same data sits on a dedicated server in a Russian data centre.

Official ones arrive with a core update: your installation checks the signed catalogue and takes the new version. The version number is shown on the module card and on the versions page. Nothing has to be reinstalled, and an update does not reset your settings or conversations.

An official one — us, through the normal support of your plan. A third-party one — its author: they release versions and write down what changed. If a third-party module stops meeting our requirements we pull it from the storefront; one that is already installed keeps working until you remove it yourself.

Three routes, and two of them need no programmer. First: connect the service through its OpenAPI description — the agent gets its methods as its own tools. Second: connect an MCP server. Third: write your own module with the Plugin SDK and publish it on the marketplace so everyone can use it.