Setting up a Telegram bot takes two minutes and costs nothing: you message @BotFather, answer two questions, and walk away with a token. Then someone opens your bot, sees a Start button, taps it — and nothing happens.
That is the expected outcome. Here is why, and what to do next.
Two minutes with BotFather
Search for
@BotFather— the one with the verification badge, there are copies.Send
/newbot.Give it a display name — what people see at the top of the chat. You can change it any time.
Give it a username. It has to end in
bot, and it can never be changed.Take the token, which looks like
123456789:AAF-xxxxxxxxxxxxx.
The token is the bot: whoever holds it controls it. Paste it into a chat and you have handed the bot over. You can issue a new one with /token in the same place — the old one dies immediately.
The short version
BotFather hands you a bot account, not a working bot.
For the bot to answer, some program has to run around the clock. "No code" means somebody else runs it, and charges you a subscription for it.
Some jobs are already covered by Telegram itself and need no bot at all.
Why the bot stays silent
Telegram does not store your bot's logic. Not the questions, not the answers, not the buttons — none of it lives on their servers. The token grants exactly two things: the right to receive messages and the right to send them.
Something has to do the answering, and it has to be running all the time, not just while your laptop is open — which means it needs a home somewhere. "No code" does not remove the server. It means the server belongs to someone else.
Telegram says as much in its own FAQ: "In order for a bot to work, set up a bot account with @BotFather, then connect it to your backend server via our API. Unfortunately, there are no out-of-the-box ways to create a working bot if you are not a developer."
You may not need a bot at all
Some of this is already solved inside the app. Check your own job before you go shopping for tools.
Schedule a post in a channel | Hold the send button → "Schedule message". Built in |
Run a poll or a quiz | A normal poll, switched to Quiz mode. Built in |
Let people comment on posts | Link a discussion group to the channel. Built in |
Keep spam out of a group | Existing moderation bots. No reason to build your own |
If your job is on that list, you can stop reading here.
If the job is still there
What comes next depends on what the bot has to do.
Send notifications to yourself or your team. An order from the site, an error on a server, a new row in a spreadsheet. There is almost no code here: take the token, add the bot to the chat, and post to it with a single request — from Make, n8n, or a couple of lines of code in any language. Nothing has to run continuously, because the bot only writes and never answers.
Take submissions from people. Listings for a channel, job applications, bookings, field reports. Here the bot has to run a conversation, which means you need a builder — more on that below.
Everything else. A shop with payments, an assistant built on a language model, a game, a branching conversation of your own — that is code, or a scenario in a no-code platform.
All three share one limit: the person starts the conversation. They open the bot and tap Start; before that, your bot cannot message them. You cannot build an audience by uploading a list of numbers. And you cannot broadcast quickly either — Telegram caps both how fast you may post into one chat and the bot's overall rate, so a thousand recipients take minutes, not an instant.
If you need to take submissions
Someone opens the bot from a link and the bot asks its questions one at a time. The answers reach you sorted into fields instead of one long conversation. That is the whole point of a form builder.
Here is the full path:
There are four things to set up.
What to ask with. There are six field types: text, buttons, phone, photo, location, rating. One choice matters — buttons or free text. Ask for the city with buttons and submissions from Almaty go to the Almaty channel on their own. Ask for it as text and you will get Almaty, almaty, Alma-Ata and alma ata, and sorting that out is on you.
Who checks it. The submission reaches you first, as a private message with Approve and Reject buttons. Until you tap one, nothing goes out. For anything filled in by strangers this is not optional: otherwise the channel collects other people's ads and a few rounds of "test test". For your own people — field reports, tickets — you turn the check off, because there it only slows things down.
Where it goes. To a channel. To the right channel out of several, based on what the person picked. Or into your own system, if it can accept data from outside.
When it goes out. Immediately, or on a schedule. Twenty listings that arrive in one evening hour can be spread across the day — a feed that gets twenty consecutive drops reads like a machine.
A live example. UyTap, a network of property channels in Kazakhstan, runs seven city channels from a single form: the agent picks a city with a button, and once the listing is approved it lands in that city's channel. An eighth city is a settings change, not a second bot.
Where the builder stops — Easy Post as the example
The form lives inside Telegram. It opens from a link and cannot be embedded in a web page. If your traffic arrives on your site and has to stay there, use an ordinary web form builder instead.
There is no date field and no file field. Easy Post has six field types: text, buttons, phone, photo, location, rating. Dates get collected as text, documents get photographed. Other builders have their own sets — but if your work runs on PDFs, that is the first thing to check in any of them.
Questions run in a fixed order. An answer does not change the next question: conditions apply after the form is filled, when the submission has to be routed. Branching inside the conversation needs either a builder that supports it or code.
What it costs
Taking Easy Post as the example, you can start for free: the platform's shared bot, one channel, and all 47 ready-made forms. That is enough to build a form and find out on real submissions whether this approach suits you at all.
Paid plans start at $7 a month: your own bot instead of the shared one, more channels, and passing submissions on to other systems. One thing worth working out in advance — fanning submissions out across several channels, as in the seven-city example, sits on the top plan. Current prices and limits are on the pricing page: they change more often than articles do.
Further reading
More on fields and approving submissions — Telegram bot form builder. A comparison of tools — no-code form builder for Telegram. If what you have is not a channel but a process inside a company — five business scenarios.