Telegram bots for real work

Telegram development starts with the conversation or task that needs to work there. We compare 3 formats: a rules bot, an AI bot and a Mini App. Majento helps a team choose the interface and connect it to the systems and people behind the channel.

Let’s talk
Telegram bots for real work

Choose the right format

Different tasks need different interfaces. We help you choose and build the right one.

For a fixed set of questions, a menu and clear rules may be enough. If people ask in their own words, an AI assistant needs approved sources and a way to show where its answer came from. A catalogue or multi-step order may call for a Mini App. We choose the interface after looking at the actual conversation.

Rules bot

How can I help?

Check status
Make a request
Find an address
Message…

Rules bot

Menus, forms and predictable tasks.

AI assistant

How can I help?

Summarise this document
Here is a short summary
Sources attached
Message…

AI assistant

Document answers with sources and review.

Mini App

How can I help?

Catalogue
My orders
Cart
Message…

Mini App

Catalogues, orders and a multi-step interface.

Connected to your business

Orders, bookings and customer questions - connected to the data and tools your team already uses.

A useful bot needs a connection to the work behind the chat. For an order-status request, we identify the system that holds the current status, the data needed to find the order and the access the bot may have. The reply should say when the source is unavailable instead of inventing an update.

  • Orders and sales
  • Databases and CRM
  • Bookings and schedules
  • Payments and notifications

A person when it matters

The bot handles routine requests. When needed, your team takes over with the conversation and context.

The handoff is part of the design. We decide which questions go to a teammate, what part of the conversation they receive and who can send the final answer. A person must approve actions such as changing an order or promising a payment, unless the business has agreed a specific rule.

  • Conversation history
  • Context for your teammate
  • A clear handoff rule

Let’s build useful bots together

Tell us what the bot should help your customers or employees do.

Let’s talk

How we work with your team

Majento is based in Tashkent and works with companies in Central Asia, Russia, Belarus and other markets in English and Russian. Process reviews, training and solution testing can take place remotely. We agree on in-person sessions with your team.

Before starting, we confirm the participants, meeting schedule and working materials. For development, we involve your IT team to agree on integrations, data access and acceptance checks.

Meet the team and find our contacts on the company page.

Updated

Choose the right format

Format Works well for Main limits
Rules bot Menus, forms, status checks and fixed routes It cannot interpret a new question without a rule
AI bot Questions in free text, document search and draft replies Answers need sources, permissions and human escalation
Mini App Catalogues, games, promotions and interfaces with several steps More product design, data and release work

The choice is part of the project. A bot is not automatically better than a web form, and an AI layer is not useful when a button and a rule already solve the task.

Separate the channel from the logic

Telegram determines where a person asks a question. It does not determine how the system finds an answer. The same chat can show a menu, look up a record by a known number or search permitted documents for relevant passages. The first two cases often work with rules and a regular integration. A free-form question may call for source search and a language model, but its answer still needs checking.

In the first discussion, we review several real question phrasings, the expected answer and the case where no answer is available. If a fixed route is enough, we do not add an agentic system. Our comparison of bots and AI agents helps choose the logic before designing the interface.

A demonstration you can inspect

The promo flow on this site shows how a promo bot talks to a campaign participant. The data in it is fictional.

Iva is an open-source AI assistant in Telegram built by our team. It works with text, voice messages and documents, remembers agreements and helps with tasks. You can open Iva and try it in its own interface.

What a production bot needs

  • a clear first task and a route to a person;
  • the data sources the bot may read;
  • permissions for each role and each action;
  • a visible response when the source is missing or the integration fails;
  • logs and a way to review conversations;
  • a handover plan for the team that will own the channel.

For consequential actions, the responsible employee confirms the result before it is sent or applied. The bot can prepare a draft, but it should not invent a price, approve a payment or make a promise without an agreed rule.

From training to Telegram project

Training gives the team a shared way to check answers and spot repeatable questions. A promising case becomes a project card with an owner, data, channel, expected output and acceptance criteria. We then prototype the route, test normal and failed cases, and connect the approved version to the required systems.

What affects scope and cost

The work depends on the number of conversation routes, the data sources, authentication, human handover, integrations, moderation rules, expected volume and support after release. We estimate after seeing the process and a few representative examples.

A short brief for the first conversation

Send one paragraph with the process, the people involved, the system that stores the result, the expected message volume and a contact for the next step. Leave out personal data and confidential documents in the first message.

Continue the route

Start with corporate AI training · See business automation · See the implementation process

Platform references

The official Telegram bot documentation and Mini App documentation describe the platform's interfaces. Use these references when deciding which format fits the workflow.

Discuss a Telegram project