> For the complete documentation index, see [llms.txt](https://vitrina-blogerov.gitbook.io/bloggers-showcase/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://vitrina-blogerov.gitbook.io/bloggers-showcase/product-docs/product-docs-en/telegram-bot-1.md).

# Telegram bot

Telegram bot is the client’s first contact with the platform. It welcomes the user, explains the value of the storefront, helps open the catalog, and maintains the feeling of a live service.

{% hint style="success" %}
A good bot should not sound like a technical placeholder. It should guide the user to an action: open the catalog, describe the task, get a selection of bloggers, or contact the team.
{% endhint %}

### The bot’s role as the first contact

The user may see the platform for the first time not in a browser, but directly in Telegram. Therefore, the bot should immediately answer three questions:

* what this service is;
* how it is useful;
* what to do next.

```mermaid
flowchart TD
    A["User opens bot"] --> B["Welcome message"]
    B --> C["Open storefront"]
    B --> D["Ask AI consultant"]
    D --> E["Receive blogger suggestions"]
    C --> F["Choose bloggers"]
    E --> F
    F --> G["Contact team"]
```

The bot works better when it does not try to say everything at once. Its job is to give a short greeting and suggest a clear next action.

### Native Telegram design

Before the first message, the user sees not the platform, but the Telegram profile of the bot. Therefore, the Telegram design is just as important as the greeting and the storefront.

{% hint style="info" %}
Some settings are made not in the platform’s admin panel, but in BotFather and the Mini App settings inside Telegram.
{% endhint %}

What to set up:

* bot avatar;
* bot name;
* short description;
* description of “what this bot can do”;
* menu button with Mini App;
* Mini App loading screen;
* preview for the Mini App link;
* commands, if users need them;
* language and tone of all public descriptions.

#### Bot avatar

The avatar should be simple and recognizable at a small size. In Telegram it is often displayed as a small circle, so fine details, long text, and thin lines will be lost.

Good options:

* project logo on a contrasting background;
* a separate brand mark;
* a simple monogram;
* a visual symbol of a catalog or AI-based selection.

Weak options:

* a screenshot of the storefront;
* a lot of text;
* a complex illustration;
* an image with low contrast.

#### Name, About and Description

A Telegram bot has several text areas, and they work differently.

{% tabs %}
{% tab title="Name" %}
The name is visible in the chat list and in the profile. It should be short, recognizable, and match the brand.

Example:

```
Creator Match AI
```

{% endtab %}

{% tab title="About" %}
The short description is visible next to the bot profile. It should quickly explain the benefit.

Example:

```
AI-powered creator selection for advertising campaigns.
```

{% endtab %}

{% tab title="Description" %}
The full description answers the question “what can this bot do.” Here you can explain the scenario in a bit more detail.

Example:

```
This bot helps brands find suitable creators for advertising campaigns. Describe your niche, audience, region, or budget, and the AI consultant will suggest relevant bloggers from the catalog.
```

{% endtab %}
{% endtabs %}

{% hint style="warning" %}
If this is a demo version, the description or greeting should note that the bloggers are fictional and that statistics links are used to demonstrate the features.
{% endhint %}

#### Menu button and Main Mini App

The menu button should lead to the catalog. This is one of the most important native entry points to the storefront: the user can open the Mini App directly from the bot profile or menu without waiting for a message.

Recommended button text:

* `Open catalog`;
* `Open app`;
* `Find creators`;
* `Browse bloggers`.

For a premium catalog it is better to use a specific action: `Open catalog` or `Find creators`. Too generic options like `Start` or `App` communicate the value less clearly.

#### Mini App loading screen

The loading screen is the loading screen of the Mini App inside Telegram. It should visually match the storefront: the same brand, mood, color accent, and level of “premium quality.”

What is important:

* use a contrasting logo;
* do not overload the screen with details;
* avoid small text;
* choose a color that matches the storefront theme;
* check how the screen looks on a phone.

<details>

<summary>What can be considered a good loading screen</summary>

The user should understand that the app is loading, not frozen. If the loading screen is visually connected to the storefront, the transition from Telegram to the Mini App feels cohesive and professional.

</details>

#### Preview of the Mini App link

If the link to the Mini App is sent in a message, Telegram may show a preview. It should look like a promotional product card, not like a random technical link.

Recommendations:

* the title should explain that the catalog will open;
* the description should promise a clear action;
* the image should match the storefront brand;
* the preview should not be misleading;
* it is better to avoid long technical URLs in the message text.

Example text near the link:

```
Open the creator catalog, compare bloggers, and add selected options to your campaign request.
```

#### Bot commands

If commands are used, there should be few of them. For a client bot, usually enough `/start`.

Additional commands should be added only if they really help the user:

* `/start` - restart the flow;
* `/catalog` - open the catalog, if the command is supported;
* `/help` - show brief help.

{% hint style="info" %}
If all the main actions are already available through buttons, there is no need to overload the bot with a list of commands. Buttons are usually clearer for the average user.
{% endhint %}

### Greeting

The greeting should be short, confident, and useful. It does not need to explain the entire platform: it is enough to state the scenario.

{% tabs %}
{% tab title="Structure" %}
A good greeting has three parts:

1. who is speaking;
2. how the bot will help;
3. what can be done right now.

Example:

```
Hello! I am your AI consultant for blogger selection.

Tell me who you need for your campaign, or open the catalog to explore all available creators.
```

{% endtab %}

{% tab title="For sales" %}
If the bot is used as part of a sales funnel, the greeting should push toward action:

```
Looking for creators for your next campaign?

Describe your audience, niche, budget, or region, and I will suggest suitable bloggers from the catalog.
```

{% endtab %}

{% tab title="For demo" %}
If this is a demo version, it is better to honestly indicate the demonstration nature of the data:

```
This is a demo catalog. Bloggers are fictional, and statistics links are provided only to show platform features.
```

{% endtab %}
{% endtabs %}

{% hint style="warning" %}
If fictional bloggers are used in the database, the greeting should say so directly. That way the platform does not mislead the client and looks more professional.
{% endhint %}

### Buttons

Buttons should be understandable without context. The user should not have to guess what will happen after tapping one.

Good buttons:

* `Open catalog`;
* `Find bloggers`;
* `Contact manager`;
* `View selected bloggers`;
* `Get recommendations`.

Weak buttons:

* `More`;
* `Info`;
* `Start`;
* `Submit`;
* `Next`.

<details>

<summary>How to choose button text</summary>

Button text is better written as an action. Not `Catalog`, but `Open catalog`. Not `Manager`, but `Contact manager`.

Such wording reduces uncertainty: the user understands in advance what will happen after the click.

</details>

### Tone of the AI consultant

The AI consultant should sound like an advertising campaign assistant, not a general chatbot. Its answers should be specific, calm, and focused on selecting bloggers.

{% tabs %}
{% tab title="Premium tone" %}
Suitable for high-end integrations and the agency model.

Style: calm, expert, without unnecessary enthusiasm.

```
I can suggest creators based on your campaign goals, target audience, geography, and budget.
```

{% endtab %}

{% tab title="Friendly tone" %}
Suitable for a mass-market catalog, small business, and an easy entry point.

Style: simpler, warmer, with gentle prompts.

```
Tell me what kind of audience you want to reach, and I will help you find suitable creators.
```

{% endtab %}

{% tab title="Business tone" %}
Suitable for B2B, experts, and professional niches.

Style: brief, structured, without conversational embellishments.

```
Please specify the niche, region, budget, and campaign objective. I will prepare relevant creator options.
```

{% endtab %}
{% endtabs %}

{% hint style="info" %}
The bot’s tone should match the storefront design. If the storefront is premium, the bot should not sound too casual. If the storefront is youthful and dynamic, the bot should not sound like a legal document.
{% endhint %}

### Bot responses

Responses should help the user move forward. Even if the bot asks for more information, it should explain why it is needed.

Good response:

```
To suggest the right creators, please tell me the campaign niche, target region, approximate budget, and desired audience.
```

Weak response:

```
Please provide more details.
```

The difference is that the first response guides the user, while the second leaves them without a hint.

<details>

<summary>What the bot should clarify</summary>

For blogger selection, the following are most often useful:

* campaign niche;
* region or audience language;
* budget;
* platform: Telegram, Instagram, YouTube, TikTok, or another;
* audience size;
* goal: reach, sales, awareness, leads;
* topic or format restrictions.

</details>

### Final message

The final message after AI selection should not just end the conversation, but move the user to action.

Good structure:

* short summary;
* a list or link to suitable bloggers;
* an offer to open the storefront;
* an offer to contact the team.

Example:

```
I found several creators that may fit your campaign.

You can open the catalog to review their cards, compare prices, and add selected bloggers to your request.
```

{% hint style="success" %}
The final message should lead to the storefront or to contact. If after the AI response the user does not understand what to do next, the selection loses its commercial value.
{% endhint %}

### Mailings

Mailings should be used carefully. The user subscribed to the bot not for constant noise, but for useful information.

Suitable topics:

* new bloggers in the catalog;
* selections by niche;
* special offers;
* platform updates;
* useful tips for advertising campaigns;
* seasonal selections.

Bad topics:

* too frequent general announcements;
* messages without value;
* the same reminders every day;
* long texts without a button or action.

<details>

<summary>Mini checklist before sending a mailing</summary>

Before sending a mailing, check:

* whether the message is understandable from the first line;
* whether there is a reason to send it right now;
* whether there is a button or clear action;
* whether the text is too long;
* whether the tone matches the storefront brand.

</details>

### Channel posts

Channel posts can work as a showcase of capabilities: new bloggers, cases, selections, updates, and promotional offers.

Recommendations:

* make one post around one idea;
* use a strong first paragraph;
* add a button or link to the storefront if the post should lead to action;
* do not mix platform news, sales, and instructions in one message;
* check that the channel matches the language version.

{% hint style="warning" %}
If different language versions serve different markets, there is no need to publish the same post without adaptation. For a foreign market, the tone, currency, platforms, examples, and brand expectations may differ.
{% endhint %}

### Media in messages

Media should reinforce the message, not replace the meaning. If the image is beautiful but it is unclear why it was sent, the message works less effectively.

Recommendations:

* use high-quality images;
* avoid small text in images;
* check how the image looks in Telegram on a phone;
* do not overload the message with several media files unless necessary;
* for promotional posts, use one strong visual and short text.

Recommended file names for documentation:

* `bot-welcome-message.png`;
* `bot-ai-response.png`;
* `bot-admin-menu.png`;
* `bot-broadcast-example.png`;
* `bot-channel-post-example.png`.

### Typical communication mistakes

{% hint style="danger" %}
The bot’s communication directly affects trust. Even with a beautiful storefront, a weak greeting or chaotic mailings can create the feeling of an unfinished product.
{% endhint %}

Common mistakes:

* greeting is too long;
* the bot does not explain what it can do;
* avatar, About, and Description are not set up in Telegram;
* the Mini App menu button has too abstract a name;
* the loading screen does not match the storefront style;
* the link preview looks like a technical link, not an entry into the product;
* buttons have abstract names;
* the AI consultant answers with generic phrases;
* the final message does not lead to the next action;
* mailings are sent too often;
* channel posts are not adapted to the market;
* media looks random;
* the bot’s tone does not match the storefront design;
* the demo version does not indicate that the bloggers are fictional.

### Final principle

A Telegram bot should be not just a technical entry point, but a neat sales assistant. It welcomes the user, explains the benefit, directs them to the storefront, and helps them take the first step toward an advertising campaign.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://vitrina-blogerov.gitbook.io/bloggers-showcase/product-docs/product-docs-en/telegram-bot-1.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.