How to write a /start message people actually read

Why the first message matters

A new user arrives with a small amount of patience. They followed a link or searched for something, and they want to know right away whether this bot does what they hoped. If the first message is confusing, they don't ask for help. They close the chat.

The welcome message also sets expectations for everything after it. A bot that opens with a wall of text teaches users to skip its messages. A bot that opens with one clear line and two buttons teaches them that reading its messages pays off. That matters later, when you need people to read an update or a broadcast.

There's another reason to get it right: you can't message a user first. If someone taps Start, reads a bad welcome and leaves without doing anything, your bot can still message them later, but they never saw why they should care. The first impression is your best chance.

The description and the welcome message are different things

New bot owners often mix these up, so it's worth being precise.

There's also the about text (/setabouttext), up to 120 characters, shown on the bot's profile page.

Because the user has already read the description by the time they see the welcome message, don't repeat it word for word. The description answers "what is this?" The welcome message answers "what do I do now?" Setting the description and about text is covered in how to change your bot's name, photo and description.

A structure that works

Most good welcome messages follow the same four steps, in this order:

1. One line on what the bot does. Plain words, no slogan. "I turn photos into PDFs" beats "Welcome to the ultimate document experience."
2. The first action. Tell the user exactly what to send or tap. "Send me a photo to start" is an instruction. "Explore my features" is not.
3. Buttons for the main choices, if there are any. Two to four is plenty.
4. Optional: where to get help. A short "Send /help any time" at the end, if your bot has more depth.

That's usually three to five short lines. If your welcome message needs scrolling on a phone, it's too long. Anything that isn't needed for the first result can wait for /help, a menu button or a later message.

Leave out the things that feel polite but slow people down: long thank-yous, the bot's history, terms and conditions in full, and lists of every command. Put commands in the command menu instead, set with /setcommands, where people can find them when they need them.

Before and after examples

A file converter bot

Before:

Hello and welcome to File Converter Bot!!! We are very
happy to have you here. This bot was made to help you
with all your file needs. Features: convert images,
convert documents, convert audio, convert video and
much more. Join our channel for updates! Use /help to
see all commands. Enjoy!

After:

Send me a file and I'll convert it to another format.

Voice notes, videos, stickers and documents, up to 20 MB.

[ How it works ]

The second version tells the user what to do in the first line and mentions the one limit that would otherwise surprise them: bots can only download files up to 20 MB.

A small business bot

Before:

Welcome! Please choose an option from the menu below.

After:

Hi! This is Lina's Bakery. Order a cake, check today's
menu or ask us anything. We reply within a few hours.

[ Today's menu ]  [ Order a cake ]
[ Ask a question ]

The "before" is short but empty: it doesn't say whose bot this is or what it can do. The "after" names the business, lists the three real reasons people come, and sets an honest expectation about reply times.

A group bot

Before:

Hi, I'm a bot. Add me to a group.

After:

I keep spam out of your group by asking new members
to join your channel first.

1. Add me to your group
2. Make me an admin there
3. Connect your channel

[ Add to group ]

For a bot that mostly works in groups, the welcome message is really setup instructions. Numbered steps work better than a paragraph.

Button tips

Buttons are the fastest way to the first result, because tapping is easier than typing. A few rules help:

• Label buttons with actions, like "Remove background" or "Order a cake", not vague words like "Start" or "Menu".
• Keep it to two to four buttons. A grid of twelve buttons is just a list of features in a different shape.
• Put the most common action first, on its own row if it matters most.
• Use emoji sparingly. One emoji can help a button stand out. One on every button makes them harder to scan.
• Make every button do something. A button that leads to another menu of buttons before anything happens loses people.

Telegram has two kinds of buttons. Buttons attached under a message (inline buttons) fit choices that belong to that message. A keyboard that replaces the phone's keyboard (a reply keyboard) suits bots people use the same way every time. For a welcome message, buttons under the message are usually the clearer choice.

Small things that make a difference

• Speak the user's language. A welcome in the wrong language loses people before they read it. Echo Maker bots speak 22 languages and switch automatically to each user's language.
• Use the user's name carefully. "Hi Sara" feels friendly, but don't build the whole message around it.
• Match the link. If someone arrived from a post about one feature, a deep link can let the bot open with that feature instead of the general menu.
• Don't ask before you give. Asking for a channel subscription, a rating or a share before the bot has done anything useful is the most common mistake. If you use mandatory subscription, read whether it's worth it first.
• Test it on a phone. What looks short on a computer can fill a phone screen.

Changing the welcome message in Echo Maker

If your bot runs on Echo Maker, you don't need to touch any code. Send /start to your own bot to open the admin panel, and change the welcome message there. Try a version, watch new and active users in the statistics for a week or two, and adjust. Small edits to the first line often make the biggest difference.

If you're still setting up your bot, start with how to create a Telegram bot, then come back to this once it's live.