A business chatbot in Telegram or MAX: which to choose in 2026

Choosing a channel for a business chatbot today is no longer only a question of audience — it is also a question of how reliable the channel is. Telegram is still the most widely used messenger in Russia, but its Bot API no longer works from part of the Russian hosting market without a workaround. MAX has its own Bot API, preinstallation on every phone sold in the country and a fully Russian perimeter, but a higher barrier to entry and no built-in payment collection.

Below: what each platform actually does according to the 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 pick a channel you won't have to rewrite in six months.

Which messenger should you pick for a bot in 2026?

The short answer: Telegram for reach, MAX for resilience, and most of the time it makes sense to run both and funnel the conversations into a single CRM. According to Mediascope, in January 2026 Telegram overtook WhatsApp* for the first time and became the most popular messenger in Russia, with a monthly reach of around 95.98 million people. In February WhatsApp slipped to 80.3 million, while MAX — a Russian messenger — grew to 77.56 million and remains the only one of the three that is gaining.

* WhatsApp is owned by Meta, an organisation designated as extremist in Russia; its activity on Russian territory is prohibited.

Choosing a channel is a bet three years out. A bot lives inside a business process: it is wired to the CRM, to inventory, to payments. Moving to another platform means rewriting integrations, not just swapping an icon. So the thing to look at is not which platform is fashionable, but where your customers actually are and what happens to the channel if the regulatory weather changes.

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

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

Developers describe the mechanism as packet filtering at the network level rather than a block on a specific IP address. Specific hosting platforms have been named where server-side scripts stopped receiving responses from Telegram.

"This isn't simply an IP block — by all appearances it's TSPU deep packet inspection equipment at work... which recognises and 'drops' the packets" — from an analysis of the Telegram API outage on vc.ru, March 15, 2026.

We see exactly this on our own production servers in Russia: by default, calls to Telegram do not get through, and leads stop reaching the sales manager. The treacherous part is that the bot does not crash and does not display an error — it silently stops delivering messages. The owner finds out when they count up the week's leads.

The cure is infrastructural: a reverse proxy outside Russia, webhooks instead of long polling, delivery monitoring with alerts. Which is why a Telegram bot in 2026 is no longer an evening's work in a builder tool — it is an engineering task with ongoing operations attached.

What is MAX, and why is everyone asking about it?

MAX is VK's messenger, launched on March 26, 2025 and developed as a national messaging platform. According to VK's press release marking the first anniversary of the launch (March 26, 2026), more than 107 million people registered in MAX during its first year, the 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, MAX was added to the list of applications that must be preinstalled on every smartphone and tablet sold in Russia from September 1, 2025.

For a business that means a predictable channel: the audience arrives on the device by itself, the data stays inside the Russian perimeter, and the odds of sudden network restrictions are lower than with foreign messengers.

Does MAX have a bot API?

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

What the API supports according to the documentation:

• Media with generous 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 across 30 rows, with button types for callbacks, links, contact requests, location requests and opening a mini app.
• Receiving updates: webhooks (for production) or long polling (for development). You cannot use both at once.
• Rate limit: roughly 30 requests per second.

In terms of capabilities this is a close relative of the Telegram Bot API — a developer who has written Telegram bots ports the logic over without having to relearn anything. The 4 GB file limit in MAX is actually more generous.

Who can publish a bot in MAX?

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

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

Bot count limits depend on the profile type: companies and sole proprietors get up to 5 bots, self-employed individuals up to 2. There is no anonymous registration here the way BotFather does it in Telegram in two minutes: you need a verified profile and you go through moderation.

That 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 contains fewer fraudulent bots, which means customers trust yours more.

How do you take payments in a MAX bot?

Through the Faster Payments System — Russia's instant bank transfer scheme — and mini apps, not with a single API call. The MAX Bot API documentation contains no built-in payment method comparable to Telegram's sendInvoice: it describes messages, media, buttons and mini apps, but no unified billing endpoint.

The practical implication for a project estimate: accepting payment in a MAX bot means 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 "payments in the MAX bot" as a line worth a few hours, it is worth asking what exactly they intend to build.

Telegram, MAX, WhatsApp or VK: a comparison by axis

The table shows why "pick one messenger forever" is a poor strategy. Right now reach and resilience sit in different columns. The sensible architecture is a bot whose logic and database live on your side, with the messenger plugged in as an interchangeable transport. Adding a second channel then costs a week rather than a quarter.

Why do most bots fail?

Because they are placed next to the business process instead of inside it. Technically the bot replies; commercially it does nothing: it does not know the order status, it cannot call a human, it leaves no trace in the CRM.

The data says the same thing from the customer's side. In a Gartner survey of 5,728 customers (published July 2024), 64% said they would prefer that companies did not use AI in customer service, and 53% said they would consider switching to a competitor on learning that support had moved to AI. A review in the California Management Review (April 2026) shows that between 53% and 77% of respondents report a negative experience with chatbots.

What irritates people, though, is not the existence of a bot 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. Handover to an agent without context. The customer retells everything from scratch, and that is the worst moment in the entire scenario.
3. No link to the system of record. 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 runs into "I didn't understand the question".
5. Silence after launch. Nobody looks at conversation analytics and the bot never improves.

These are precisely the points that choosing a platform cannot fix: they are cured by integrations and by operations. We have a separate piece with the numbers on the economics of a bot that actually earns its place on the front line — when a first-line AI agent pays for itself. On the difference between a scripted bot and an agent that chooses its own steps, see “AI agents for business”.

What does Federal Law 152-FZ require if the bot collects contact details?

The moment your bot accepts a name, a phone number or an email address, you become a personal data operator. Several obligations follow, and they are usually remembered only after the first inspection.

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

It is worth stating this precisely. Telegram is not "banned" for business; working through it means closing the questions of data localisation and cross-border transfer. With MAX, and with your own perimeter on a Russian server, that risk is lower by construction. We described what a perimeter that keeps data from leaving looks like in “Neural networks without data leaks”.

Where do you start if you need a bot?

With the process, not the platform. Here is an order of operations you won't have to redo:

1. Describe what the bot does. Not "talks to customers", but "takes an enquiry, checks stock, creates a deal in the CRM, calls a manager when the amount is above a threshold".
2. Count the volume. How many enquiries a month, and how many of them are routine. If there are few routine ones, the bot will not pay for itself on any platform.
3. Define the escalation point. When the bot is required to call a human, and what the agent sees at that moment.
4. Assemble the knowledge base. Price lists, procedures, answers to common questions. Without it the bot answers beside the point.
5. Pick the channel to match your customers. Telegram if your audience is already there. MAX if resilience and the Russian perimeter matter more. Both, if the budget allows and the logic lives on your side.
6. Budget for operations. Delivery monitoring, conversation analytics, knowledge base updates. A bot with no owner dies within a quarter.

At IncubeAi we build exactly this kind of bot: 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 your CRM covered by contract, with support after handover. If the process is already clear, start with a conversation about it — discuss a project.

Sources

• Mediascope, monthly messenger reach in Russia, summarised 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.
• Government of the Russian Federation, 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.
• Requirements for registering MAX bots — legal entities, sole proprietors and self-employed individuals, residents of Russia.
• vc.ru, on api.telegram.org being unreachable 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, registering chatbots with Roskomnadzor, vc.ru, May 23, 2025.