Telegram and MAX bots

A short scenario instead of a shared chat.

We build bots for requests, FAQs, booking, statuses and handoff to a person. Each platform is checked before we design the flow.

What it is for

What it is for

  • People already write in Telegram or MAX
  • Some questions repeat
  • A request, a booking or a status is needed without a call
  • A difficult case should reach a person
Problems it solves

Problems it solves

  • The same questions drown in a shared chat
  • A request arrives without a topic or a status
  • Booking and reminders live in separate threads
What the first version includes

What the first version includes

  1. 01A greeting and a menu
  2. 02A few topics or services
  3. 03A request or an FAQ
  4. 04Handoff to a person and a basic notification
Demonstration layout

How a bot can look

Telegram and MAX have separate layouts. This is not a partnership with the platforms and not someone else’s chats.

Telegram bot mockup: menu, request No. 1427 and handoff to a specialist.
MAX booking bot mockup: service, date, time and a status waiting for a specialist.

Concept. The available API is checked before development.

Sample interface. Concept, not a client project

Open the bot demonstration
Useful functions

Useful functions

Menu and FAQ

A person picks a topic with a button and gets a short answer.

Requests

A number, a status and a teammate notification appear.

Booking

Service, date and confirmation — if the platform allows it.

Statuses and notifications

The same stage for the visitor and the teammate.

Handoff to a person

A disputed case is not closed by the bot.

Integrations

A CRM or an internal system comes second, not in every bot.

Possible integrations

  • A Telegram notification
  • A CRM or a spreadsheet
  • An internal request queue
  • A website as the entry point

How development goes

  • Who writes and what should happen
  • We check the platform API
  • We assemble the dialogue and the error paths
  • We connect a notification to a person

Timing

A short bot is usually faster than a bot with integrations. Timing depends on the scenario and access. We do not start promising MAX before the API is checked.

Price range

Price range

A short Telegram or MAX bot starts from ₽15,000. A bot with integrations starts from ₽35,000. The total is fixed after a review of the task and is not a public offer.

Main functions

  • a scenario and a menu
  • requests or an FAQ
  • a notification to a person

Pricing

  • the number of branches
  • booking and statuses
  • a CRM and documents

What is not included automatically

  • storing personal data
  • two platforms at once
  • support after launch

What we need from the client

  • Where people already write and what should happen at the end of the dialogue
  • A list of topics, services or common questions
  • Where a teammate should be notified in the first version
  • Bot or platform access after the scenario is agreed

What happens after launch

  • We check the branches, errors and the handoff to a person
  • We look at what arrives for the teammate
  • New branches are added separately, not “everything in the base price”

How support works

  • Platform and scenario support is a separate arrangement
  • Messenger API updates are not included in the first version automatically
  • If personal data must be stored, that is designed separately

What is not included automatically

  • Unconfirmed Telegram or MAX features
  • An open-ended conversation “like a person”
  • Storing personal data without a separate design

Limits

  • A bot does not replace a person in disputed cases
  • MAX only after the API is checked
  • We do not imply an official link with Telegram or MAX
Questions

Questions

Are Telegram and MAX the same bot?

No. The scenario can be similar, but the platforms differ, and MAX needs an API check.

What does the first version from ₽15,000 include?

A short menu, requests or an FAQ, handoff to a person and a basic notification.

Can someone book a service through MAX?

A concept can be shown. Booking, a calendar and notifications are promised only after the API is checked.

Where does the request go?

In the first version — to a person in a messenger or to an agreed channel. A CRM is connected separately.

Does the bot need to collect a phone number?

Not always. A topic and a contact in the same messenger are often enough.

Related layouts

Related layouts

The layouts show a possible solution. They are not a client portfolio or growth figures.

Platform features change.

That is why we do not promise unconfirmed MAX or Telegram capabilities in advance: first we check the available APIs and limits.

All solutions
Telegram

If the task is already clear, write in Telegram.

A few lines are enough: what you want to simplify and how it works today. Replies are usually sent between 09:00 and 18:00 MSK.

Message in Telegram