Business chatbots on Telegram and MAX: which to choose in 2026

Choosing a business chatbot today is a question not only of audience but of how stable the channel is. Telegram is still Russia's most widely used messenger, but its Bot API no longer works from some Russian hosting providers without a workaround route. MAX, a Russian messenger, has its own Bot API, comes preinstalled on every smartphone sold and runs on Russian infrastructure, but the barrier to entry is higher and there is no built-in payment acceptance.

Below we look at what each platform can actually do according to its official documentation, where bots break in practice, what Federal Law 152-FZ, Russia's personal data protection law, requires of a bot owner, and how to choose a channel without rewriting everything six months later.

Which messenger should you choose for a bot in 2026?

The short answer: Telegram is chosen for reach, MAX for stability, and most often it makes sense to have both, with conversations flowing into one CRM. According to Mediascope, in January 2026 Telegram overtook WhatsApp* for the first time and became Russia's most popular messenger, with a monthly reach of about 95.98 million people. In February WhatsApp slipped to 80.3 million, while MAX grew to 77.56 million and remains the only one of the top three that is gaining.

* WhatsApp is owned by Meta, which has been designated an extremist organization in Russia; its activities are banned in the country.

Choosing a channel is a bet three years ahead. A bot lives inside a business process: it is connected to the CRM, the warehouse, the payments. Moving to another platform means rewriting integrations, not just swapping an icon. So what matters is not how fashionable a platform is, but where your customers are and what will happen to the channel if the regulatory climate changes.

What is happening to Telegram in Russia, and how does it break bots?

Roskomnadzor, Russia's communications regulator, has restricted audio and video calls in Telegram since August 2025, and on February 10, 2026 it officially confirmed that the messenger was being throttled across the country. For a bot owner, another, less visible consequence matters more: in practice, api.telegram.org cannot be reached from a number of Russian hosting providers without a workaround route.

Developers describe the mechanism as packet filtering at the network level rather than blocking of a single IP address. Specific providers have been named where server-side scripts stopped getting responses from Telegram.

“This is not just IP blocking; by all appearances it is the work of TSPU [Russia's state-mandated traffic filtering equipment]... which recognize and ‘drop’ the packets” — from an analysis of Telegram API unavailability on vc.ru, March 15, 2026.

We see exactly this on our own production servers in Russia: requests to Telegram do not go through by default, and leads stop reaching the sales manager. The insidious part is that the bot does not crash or show an error: it silently stops delivering messages. The owner finds out about the problem when counting the week's leads.

The fix is infrastructural: a reverse proxy outside Russia, webhooks instead of long polling, and delivery monitoring with alerts. That is why a Telegram bot in 2026 is no longer something you “put together in a builder in an evening” but an engineering task that needs ongoing operation.

What is MAX, and why are people asking about it?

MAX is a messenger from VK, launched on March 25, 2025 and being developed as a national messaging platform. According to VK's press release for the launch anniversary (March 26, 2026), more than 107 million people registered on MAX in its first year, daily audience exceeded 77 million in March 2026, and users send more than 1.5 billion messages a day.

The second factor that is hard to ignore when planning three years ahead: under Russian Government Orders No. 2240-r and No. 2241-r of August 19, 2025, the MAX platform was added to the list of applications that must be preinstalled on all smartphones and tablets sold in Russia from September 1, 2025.

For a business, this means a predictable channel: the audience arrives on the device on its own, data stays within Russian infrastructure, and the likelihood of sudden network restrictions is lower than for foreign messengers.

Does MAX have a bot API?

Yes, and it is official. The developer portal is at dev.max.ru. The MAX Bot API is a REST interface over HTTPS: requests go to platform-api2.max.ru, and the old address, platform-api.max.ru, must be abandoned by July 19, 2026. There is an official SDK for JavaScript and community libraries for Python and Go, but any language with an HTTP client will do.

What the API can do according to the documentation:

• Media with high limits: images up to 50 MB, video up to 250 MB, audio up to 256 MB, files up to 4 GB.
• Keyboards: up to 210 buttons in 30 rows, with button types for callback, link, contact request, location request and opening a mini app.
• Receiving updates: webhooks (for production) or long polling (for development). You cannot use both at once.
• Load limit: around 30 requests per second.

In terms of features, it is a close relative of the Telegram Bot API: a developer who has written bots for Telegram can carry the logic over without relearning. MAX's 4 GB file limit is even more generous.

Who can publish a bot on MAX?

Only the owner of a verified profile registered in Russia. A common misconception needs clearing up here: reviews from autumn 2025 claimed that only legal entities could publish bots. According to the current documentation, that is no longer the case.

“Access to the MAX platform for partners and its services — chatbots, mini apps, channels — is available to legal entities, sole proprietors and self-employed individuals who are Russian residents” — MAX developer documentation.

The number of bots allowed depends on the profile type: organizations and sole proprietors can create up to 5 bots, self-employed individuals up to 2. There is no anonymous registration like Telegram's two-minute process through BotFather: you need a verified profile and moderation.

This is both a drawback and an advantage. The drawback is the barrier to entry and the time verification takes. The advantage is that the channel physically has fewer fraudulent bots, which means customers trust yours more.

How do you accept payments in a MAX bot?

Through the Faster Payments System (SBP, the Bank of Russia's instant payment system) and mini apps, not with a single API call. The MAX Bot API documentation has no built-in payment method comparable to Telegram's sendInvoice: it describes messages, media, buttons and mini apps, but not a single billing endpoint.

What this means for a project estimate: accepting payment in a MAX bot is a separate integration with a payment provider plus a mini app with a storefront, not a ready-made platform feature. If a contractor's estimate lists “payment in the MAX bot” as a line item of a few hours, it is worth asking what exactly they plan to do.

Telegram, MAX, WhatsApp or VK: a side-by-side comparison

The table shows why “pick one messenger for good” is a poor strategy. Reach and stability currently sit in different columns. It makes more sense to build the bot so that the logic and database live on your side and the messenger is connected as interchangeable transport. Then adding a second channel costs a week, not a quarter.

Why don't most bots work?

Because they are placed next to the business process instead of inside it. Technically the bot answers, but commercially it does nothing: it doesn't know the order status, can't call in a human, and leaves no trace in the CRM.

The data says the same from the customer's side. According to a Gartner survey of 5,728 customers (published in July 2024), 64% would prefer that companies didn't use AI in customer service, and 53% would be willing to switch to a competitor on learning that support had moved to AI. A review in California Management Review (April 2026) shows that between 53% and 77% of respondents report negative experiences with chatbots.

What irritates people is not the fact of a bot itself but specific things:

1. The bot wall. There is no way out of the conversation to a human, so the customer looks for workarounds.
2. Handoff to an agent without context. The customer has to explain everything again, and this is the worst moment of the entire flow.
3. No connection to the accounting system. Asked “where is my order,” the bot calls a manager, even though the answer is sitting in the database.
4. A rigid script. Anything outside the FAQ ends in “I didn't understand the question.”
5. Silence after launch. Nobody looks at conversation analytics, and the bot never improves.

These are exactly the points that choosing a platform cannot fix: they are solved through integrations and ongoing operation. For the economics of a well-designed first-line bot, we have a separate breakdown with calculations on when a first-line AI agent pays off. The difference between a scripted bot and an agent that chooses its own steps is covered in the article “AI agents for business”.

What does 152-FZ require if a bot collects contact details?

As soon as a bot accepts a name, phone number or email, you become a personal data operator. Several obligations follow from this, and companies usually remember them only after the first inspection.

1. Notify Roskomnadzor and be entered in the register of personal data operators.
2. Publish a privacy policy and link to it from within the bot.
3. Obtain explicit consent to processing, as a separate action by the user, not in fine print.
4. Assess cross-border transfer: Telegram's servers are located outside Russia, and this is a separate legal question that has to be covered with documentation.

It is worth stating this precisely. Telegram is not “banned” for business; when working through it, you need to address data localization and cross-border transfer. With MAX, or with your own infrastructure on a Russian server, this risk is lower by design. We described what infrastructure that keeps data from leaving looks like in the article “Neural networks without data leaks”.

How do you build a Telegram bot for leads and connect it to a CRM?

To build a Telegram bot for leads and connect it to a CRM, start by describing the conversation flow and the fields of the future lead. Create the bot, connect the Bot API or an integration service, set up the pipeline and the lead creation rules, then send a test message. Check the record, the conversation history, the notifications and the lead source.

Conversation flow and lead fields

Define the bot's questions, username, service, comment, source and UTM tags.

Creating and connecting the bot

Register the bot, choose a module, service or API, and map the fields to the CRM.

Checking the handoff to the CRM

Test a new and a returning contact, deal creation, conversation history and the manager notification.

Where do you start if you need a bot?

With the process, not the platform. An order of steps you won't have to redo:

1. Describe what the bot does. Not “talks to customers,” but “accepts a request, checks warehouse stock, creates a deal in the CRM, calls a manager when the amount exceeds a threshold.”
2. Measure the volume. How many inquiries per month, and how many of them are routine. If there are few routine ones, the bot won't pay off on any platform.
3. Define the escalation point. When the bot must call in a human, and what the agent sees at that moment.
4. Build a knowledge base. Price lists, procedures, answers to frequent questions. Without it, the bot answers beside the point.
5. Choose the channel to fit your customers. Telegram if your audience is already there. MAX if stability and Russian infrastructure matter more. Both if the budget allows and the logic lives on your side.
6. Plan for operation. Delivery monitoring, conversation analytics, knowledge base updates. A bot without an owner dies within a quarter.

At IncubeAi, this is exactly the kind of bot we build: logic and data on your side, the messenger connected as transport, integrations with 1C, the accounting and ERP platform most Russian companies run on, and with CRM systems, all under contract and with support after handover. If the process is already clear, start with a conversation about it: discuss your project.

Sources

• Mediascope, monthly messenger reach in Russia, summary on Habr: Telegram overtook WhatsApp for the first time in January 2026.
• VK, press release for the MAX anniversary, March 26, 2026: 107 million registrations, daily audience above 77 million.
• Russian Government, Orders No. 2240-r and No. 2241-r of August 19, 2025: mandatory preinstallation of MAX from September 1, 2025.
• MAX Bot API documentation: limits, webhooks, the platform-api2.max.ru address.
• MAX bot registration requirements: legal entities, sole proprietors and self-employed individuals who are Russian residents.
• vc.ru, on the unavailability of api.telegram.org from Russian hosting providers, March 15, 2026.
• Gartner, survey of 5,728 customers, published July 9, 2024: 64% against AI in customer service.
• California Management Review, Chatbot Frustration Is Real, April 2026.
• Daria Dubeshko, Roskomnadzor registration for chatbots, vc.ru, May 23, 2025.