GPTunneL Connects Its AI Bot Builder to VKontakte and MAX: Nine Steps, No Code

GPTunneL, an AI bot builder, is no longer a Telegram-only tool. The same bot can now connect to three channels: Telegram, VKontakte and MAX. It shares one instruction, one model and one set of limits across all of them. The author of a step-by-step guide on Habr promises to take you from an empty bot to its first reply in community messages in nine steps and about 10 minutes, without writing a single line of code.

What has changed in the builder

Previously, a community owner who wanted a bot on both Telegram and VKontakte was effectively running two projects: two setups, two sets of rules, and two places where a price or opening hours had to be corrected on time. Now the logic is built once. Channels are connected on a separate "Channels" tab, and everything else stays shared.

The "shared limits" feature means that, judging by the description, model usage is counted across all channels combined. That is convenient for budget planning, but it also calls for attention: a spike in VKontakte inquiries will eat into the same allowance that was planned for Telegram. This is our inference from the description; the announcement itself does not explain how the limits work.

Technical details from the announcement

• Platform: GPTunneL, a no-code builder.
• Channels: Telegram, VKontakte, MAX (a Russian messenger).
• Shared across all channels: instruction, model, limits.
• Connecting channels: the "Channels" tab.
• Guide format: 9 steps with screenshots, a stated setup time of about 10 minutes.
• Bot tasks: product consultations, booking appointments for services, answers to frequent questions, and a communication tone set by the owner.

What tasks it covers

The examples in the article will be familiar to anyone who runs a community: "How much does it cost?", "Do you have it in another color?", "What time do you close?", "How do I make a return?". These are short, repetitive questions with a limited set of answers, and for a language model this is the safest scenario. It does not need to reason or make anything up; it only has to restate the data from the instruction correctly, in the right tone.

That is also the main risk. If prices, return terms and schedules are baked into the instruction, someone has to keep them up to date. The bot will confidently answer with outdated data, and the customer will not be able to tell that apart from a mistake by the store.

What is left out

The announcement does not answer the questions that determine the project's economics. It names no pricing plans and no limit sizes. It does not say which models are available, how the knowledge base is stored, or what happens when the bot does not know the answer, including whether it hands the conversation to a human employee. The text itself is published as a product guide, most likely by the service itself, so it should be read as a shop window rather than an independent review.

The event is still telling. No-code builders are moving from a single messenger to a set of channels, and for Russian small businesses this means an AI consultant is becoming a standard part of a community rather than an enthusiasts' experiment.

Where a community owner should start

Start with an audit of your questions: export the last 50–100 inquiries and pick out the ten most frequent ones. Those go into the instruction. Describe the tone of communication and the boundaries: what the bot does, and what it must hand off to a human. Before connecting VKontakte and MAX, test the scenario on a test community or in a single channel and see how quickly the limits are used up. Check the plan terms and the settings for handing a conversation to an operator before launch, not after the first customer complaint.