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

# Product Features

Learn how CatFee's Telegram Bot Studio helps you design Telegram bot interfaces, build conversation flows, and add new services quickly.

Telegram Bot Studio is CatFee's **visual bot configuration and service orchestration platform** for business operators. It helps you design bot interfaces, organize conversation flows, and connect services.

After connecting a BotFather Token, partners can edit commands, messages, and buttons in a simulator that closely resembles a real Telegram conversation. Existing services can be organized into clear, easy-to-follow user journeys. When a new service becomes available, it can be added to the current bot through a service module or reusable component without redesigning the entire interface.

> Move from changing code to update a bot to operating it continuously through visual configuration.

## What-you-see-is-what-you-get configuration

The configuration page places the Telegram simulator and editing workspace in one view. Operators can select a command, message, or button directly in the simulator and edit the selected item.

```mermaid
flowchart LR
    A[Select a command,<br/>message, or button] --> B[Edit content]
    B --> C[Connect buttons<br/>or service modules]
    C --> D[Preview instantly]
    D --> E[Confirm and save]
```

Operators do not need to understand the bot's code structure. The simulator updates as the configuration changes, making it easy to check copy, button layout, and user journeys before publishing.

The visual builder supports:

* Configuring Telegram commands such as `/start` and `/help`;
* Editing welcome messages, command descriptions, and triggered messages;
* Adding inline buttons and a persistent bottom menu;
* Organizing buttons into groups and adjusting their order;
* Connecting buttons to follow-up messages, menus, or service modules;
* Creating reusable custom button components;
* Switching between view, edit, and preview states;
* Resetting or canceling a draft before saving.

{% hint style="info" %}
Visual configuration works best with the extra screen space available in a desktop browser.
{% endhint %}

## Build the bot as a user journey

Traditional bots often define menus, replies, and service links in code, leaving operators dependent on developers for routine changes. CatFee separates these elements into configurable building blocks:

* **Commands:** Entry points such as `/start` and `/help`;
* **Triggered messages:** Explanations of services, prices, rules, or next steps;
* **Inline buttons:** Choices for plans, next actions, and confirmations;
* **Bottom menu buttons:** Persistent access to frequently used services;
* **System modules:** Entry points to live services already connected to the platform;
* **Custom components:** Reusable buttons and replies that can appear in several places.

Operators first decide what users see, then choose where each action leads. Managing content and actions separately makes complex bot journeys easier to understand, update, and reuse.

## Add new services to an existing bot

Visual configuration does not require every service to be hard-coded into the bot's home screen.

Once a new service has working query, transaction, or delivery capabilities from CatFee or the partner's backend, it can be packaged as a system module or reusable button component and added to the bot:

1. Select the new service module or component from the library.
2. Add it to an existing command, message, or bottom menu.
3. Configure its label, introduction, and operating instructions.
4. Use variables to display user, account, or order information.
5. Check the complete journey in the simulator.
6. Save the configuration so users can access the service from the existing bot.

Beyond the Energy, membership, and on-chain tools already available, the same process can support future services such as:

* Points, tiers, and membership benefits;
* Referral rewards and promotional campaigns;
* Wallet asset and order status queries;
* Campaign registration and eligibility checks;
* New on-chain tools and value-added services;
* A partner's own customer support and after-sales workflows.

The bot does not need a new navigation and interaction layer for every new service. The service team provides an actionable module, while the operations team decides its entry point, content, and user journey in the visual builder.

{% hint style="warning" %}
Visual configuration controls the bot's user-facing content and journeys. Live query, transaction, and delivery functions must still be provided by the corresponding backend service module.
{% endhint %}

## Live Telegram conversation preview

The simulator creates an interactive preview from the bot's actual commands, messages, menus, and button relationships.

Operators can:

* Select a command to view its response;
* Select a button to check its follow-up message or linked action;
* Switch between view, edit, and guided modes;
* Preview different language versions;
* Check paginated messages, templates, and system module entry points;
* Find empty content, incorrect links, and misplaced buttons before saving.

For system modules that perform live transactions, the simulator shows only the entry point and connection. It does not create real orders during a preview.

## Rich-text editor for Telegram

The built-in message editor follows Telegram HTML rules and supports:

* Bold, italic, underline, and strikethrough formatting;
* Quotes, spoilers, and inline code;
* Clickable links and copyable text;
* Code blocks and preformatted text;
* Common emoji;
* Telegram HTML source editing;
* Visual previews;
* Message length validation.

Most operators can create content with the visual toolbar. Those familiar with Telegram HTML can switch to source mode for precise formatting.

## Manage each language independently

Each command can have separate Chinese and English versions, with room to add more languages in the future.

Language tools include:

* Setting the bot's default language;
* Maintaining command descriptions and replies separately for each language;
* Copying default-language content to another language as a starting point;
* Choosing a default version of the content;
* Falling back to the default language when a translation is unavailable;
* Switching languages in the simulator to review the result.

One bot can serve users in several languages without requiring partners to maintain separate bots.

## Template, variable, and component library

The library keeps commonly used content as searchable, reusable resources.

### Message templates

Templates provide a consistent starting point for content such as:

* User account overviews;
* Product and plan descriptions;
* Purchase and payment instructions;
* Order result notifications;
* Customer support and after-sales information.

Each template can be edited after insertion, so operators do not have to start every message from a blank page.

### Dynamic variables

Messages can use the current user or order context to display:

* Telegram user IDs, usernames, and display names;
* Deposit addresses and account balances;
* Total deposits and spending;
* Bot names and support usernames;
* Order numbers, amounts, and plan names;
* Wallet addresses and transaction hashes;
* Tronscan links for addresses and transactions;
* Recent orders;
* Prices, exchange rates, or statuses provided by a service module.

The same template can serve different users while reducing manual copying and data entry errors.

### Reusable components

Frequently used buttons and replies can be saved as custom components and added to different commands or messages. Reusing existing components helps keep names, interactions, and service entry points consistent as the bot evolves.

## A safer editing and publishing process

The platform separates view and edit states, so an accidental click does not immediately overwrite live content.

While editing, operators can:

* Review the current live version;
* Enter a separate editing state;
* Preview draft changes in real time;
* Reset the current draft;
* Cancel changes;
* Save only after confirming the result.

A step-by-step guide also introduces first-time operators to the simulator, configuration workspace, resource library, and the complete edit, connect, preview, and save workflow.

## Built-in services as ready-to-use examples

CatFee has already connected several services to Telegram Bot Studio. Partners can configure their entry points, content, prices, and user journeys, including:

* TRON Energy and TRON Mate;
* Telegram Premium and Telegram Stars;
* Address Risk Screening;
* Energy subleasing and USDT-to-TRX swaps;
* Energy Finance.

These services show how the same visual configuration system can support purchases, subscriptions, queries, on-chain tools, and asset services. The platform is designed so future services can reuse the same menus, messages, buttons, templates, and preview workflow.

## Supporting business management tools

The visual builder controls how a bot presents services and interacts with users. Supporting pages in the CatFee dashboard help partners operate the services connected to the bot.

### Pricing

Connected services can provide their own price settings and show retail prices, estimated profit, and pricing alerts based on reference costs.

### Customer management

Customer profiles can include Telegram account details, language, dedicated deposit addresses, TRX and USDT balances, total deposits, and spending by service. This information helps partners identify users and handle support requests.

### Orders and on-chain records

Orders are grouped by service and can link customers, receiving addresses, payment amounts, statuses, and related on-chain transaction hashes for search and reconciliation.

### Business performance and earnings

The operations dashboard tracks user balances, deposits, spending, costs, commissions, and withdrawable earnings separately for TRX and USDT. It also supports earnings withdrawals and withdrawal history.

These tools provide a complete operating workflow for built-in services. Other services can reuse the relevant data and management modules when needed.

## Basic bot management

To connect a bot, a partner provides:

* The Bot Token issued by BotFather;
* A default language;
* A customer support username.

CatFee retrieves the bot's name, username, and bot ID and allows the partner to enable, disable, or reset the bot.

{% hint style="info" %}
Creating a bot is free. To ensure that the bot can accept and process orders, keep at least 100 TRX in your CatFee account as its initial operating balance.
{% endhint %}

{% hint style="danger" %}
The Bot Token is the bot's access credential. Do not share it with unrelated parties or post it in a public group. If it is exposed, generate a new token through BotFather and update the configuration in CatFee.

Resetting a bot may clear its current menus, buttons, and service configuration and cannot be undone. Back up important content before resetting it.
{% endhint %}

## Product value

Telegram Bot Studio separates service capabilities from the bot interface:

* **Operators** can update copy, menus, buttons, and user journeys independently;
* **Service teams** can package new services as modules and add them to an existing bot;
* **Partners** can continue expanding their offerings without rebuilding the bot for each service;
* **Users** get a consistent Telegram conversation experience across different services.

> Connect your bot once, then continue expanding it through visual configuration.

Next, read [Telegram Bot Studio Overview](/en/telegram-bot-studio/introduction.md) for requirements and setup steps.