Telegram bot commands are the short instructions that start with a slash, such as /start or /help, that tell a bot what to do. If you run a group, you will use them to control moderation bots, and if you build your own bot, you will define them. Knowing how commands work, and why one sometimes "does nothing", saves a lot of frustration.
This guide explains how commands behave in private chats and groups, how to register them with @BotFather, how to show different commands to admins and members, and how to fix the most common problems.
What a bot command actually is
A command is just a message that begins with / followed by a word. Telegram treats it specially in three ways:
- It is highlighted as a tappable link in the chat. Tapping it sends the command again.
- When you type
/in a chat with a bot, Telegram shows a list of that bot's registered commands with short descriptions. - Bots in privacy mode, which is the default in groups, still receive commands, even though they don't see ordinary messages.
Command names can contain lowercase English letters, digits and underscores, up to 32 characters. So /rules and /set_welcome are valid, but spaces or other alphabets aren't. Anything after the command is passed to the bot as text it can interpret, for example /remind 10m stretch.
One important point for admins: Telegram itself doesn't define what /ban or /warn do. Every bot decides its own commands and behavior. Two moderation bots can use the same word and do completely different things, so always read a bot's help text before using it in your group.
The three commands every bot should have
Telegram recommends that bots support a small set of global commands, so users can rely on them:
| Command | What users expect |
|---|---|
/start | Begins the conversation. Telegram sends it automatically when someone opens a bot and taps Start. |
/help | Explains what the bot does and lists its commands. |
/settings | Lets the user change the bot's options, if it has any. |
If you're evaluating a bot for your group, try /help first. A bot without a clear help message is usually a sign it won't be pleasant to work with.
Using commands in groups
Addressing the right bot
Groups often have several bots. If two of them understand /help, which one should answer? Add the bot's username to target it: /help@yourbotname. When you pick a command from the suggestion list in a group, Telegram usually adds the username for you. Bots in privacy mode reliably receive commands addressed to them this way.
Replying with a command
Many moderation bots act on the message you reply to. To mute a spammer, you typically reply to their message with the bot's mute command. The bot reads who wrote the original message and acts on that user. Without the reply, the bot may ask you who you mean or simply ignore the command.
Permissions still apply
A command can only do what the bot is allowed to do. If a bot is supposed to delete messages or ban users, you must make it an admin with those specific rights. Give it only the rights it needs. Our guide on adding a bot to a Telegram group walks through this, and Telegram bot privacy mode explains what a bot can and can't see.
Registering commands with @BotFather
If you created your own bot, registering its commands makes them appear in the suggestion list and the menu. The simplest way is through @BotFather, Telegram's official bot for managing bots:
- Open a chat with @BotFather and send
/setcommands. - Choose your bot from the list.
- Send the commands as plain text, one per line, in the format
command - description.
For example:
rules - Show the group rules
report - Report a message to the admins
help - What this bot can do
Write descriptions as short actions a member understands at a glance. You can also edit or remove commands later through @BotFather. If you haven't made a bot yet, start with how to create a Telegram bot with BotFather.
Registering a command only changes the list users see. Your bot's code still has to handle it. A command that is listed but not implemented will be met with silence, which confuses members.
Showing different commands to admins and members
Developers can set commands through the Bot API method setMyCommands instead of BotFather. Its main advantage is scopes: you can show one list in private chats, another in groups, and a third only to group administrators. You can also set commands per language, so members with their app in Spanish see Spanish descriptions.
A practical setup for a moderation bot might look like this:
- All members in groups:
/rules,/report,/help. - Group admins only: the above, plus mute, warn and ban commands.
- Private chat:
/start,/settingsand setup commands.
Hiding admin commands from regular members doesn't secure them on its own. Your bot must still check that the person sending a sensitive command really is an admin. The scoped list just keeps the menu tidy.
Start links and other command tricks
A bot link can carry a start parameter: t.me/yourbotname?start=welcome. When someone opens it and taps Start, the bot receives /start welcome and can respond differently depending on the parameter. Communities use this to track which post brought a user in, or to drop someone straight into a specific feature.
A similar link with startgroup instead of start prompts the user to pick a group to add the bot to, which is handy if you publish a bot for other admins.
Why a command isn't working
- The bot isn't in the group or was removed. Check the member list.
- Another bot answered, or none did because the command wasn't addressed to a specific bot. Add
@botname. - Missing admin rights. The bot can't delete or ban without them.
- Wrong syntax. Many commands need a reply or an argument. Read
/help. - The bot is offline. Bots run on their developer's servers; if those stop, the bot stops responding.
- Typo or capital letters. Stick to the lowercase command shown in the list.
Looking for communities where bot builders share tips? The programming section of the Grupla directory lists developer groups.
Frequently asked questions
Can I create commands for my group without a bot?
No. Commands are a bot feature. Without a bot, a message starting with a slash is just text. If you want custom commands such as /rules, you need a bot that responds to them.
Do members see when I use an admin command?
Usually yes, because the command is a normal message in the group. Some bots delete the command message after acting on it to keep the chat clean.
How many commands should a bot have?
As few as possible. A short list that members actually remember works better than dozens of options nobody reads. Put rarely used features behind /settings or /help.