People write to you in Telegram all day. A client wants a price, a tenant reports a leak, an employee sends a receipt. Half the messages miss something, so you ask again and wait.
Telegram bot forms fix this. A bot asks your questions one at a time and sends you the finished request. Below, find your situation and see what to switch on.
How Telegram bot forms work
A person opens your link and presses Start. The bot asks one question per message, with buttons wherever there is a choice. People can also send photos, documents and voice messages.
When the person answers the last question, the request comes to your Telegram as one message. Every request is also saved in your dashboard, your account page on easy-post.app. The form runs on Easy Post's bot, so you don't need to create a bot of your own.

Illustration: the texts are the bot's own; names and data are made up.
Easy Post uses a few words of its own. Your form together with its bot link is a pipeline. Each pipeline has its own page: there you copy the link and switch things on, and the "Form" button opens the form settings. A question is a field, and a request is a submission.
Find your situation
Start with the setup. Then go to what you need:
- Set up your form in 10 minutes
- Pick a ready form for your job
- Get requests and call people back
- Say yes or no to each request
- Post what people send to your channel
- Collect photos, documents and voice messages
- Take requests from people who are not in Telegram
- Let people answer in one message or by voice
- Send requests to a spreadsheet or CRM
- Send requests to different channels by city or topic
- Handle requests as a team
- When a Telegram form is not the right tool
- Check before you share the link
Set up your form in 10 minutes
- Pick a template. Sign up at easy-post.app and choose one of 49 ready form templates, such as Service Request or Event Registration. Easy Post creates the form and its link, and you see "Your pipeline is ready."
- Change the questions to yours. On your pipeline page, press "Form". Each question has a "Field name", the label you see in the request, and a "Bot prompt", the question the person reads. Fill in both.
- Mark the important questions. Tick Required for every question a request is useless without; the others get a Skip button. People answer in order and cannot go back to an earlier question, so put easy questions first. Don't press Save yet.
- Turn choices into buttons. For a question with a choice, pick the type Buttons and type the options in one box, separated by commas: "Plumbing, Electrical, Cleaning". Typed answers come back as "Almaty", "almaty" and "Almata", and nothing can sort them.
- Rewrite the bot's messages, then save. Further down the same page, under "Bot Messages", are the welcome and the thank-you ("Completion Text"). Under "Status Notifications" are the messages people get when you approve or reject. Rewrite them before you press Save. Here is why: until the form is saved once, the bot speaks to each person in their own language. The first Save fixes the texts in the language you use Easy Post in, and from then on everyone sees them in that language.
- Test it. On your pipeline page, press "Test the form in Telegram". It links your Telegram, so requests can reach you, and opens the form the way a customer sees it. Your test request arrives in the same chat.
- Share the link. On your pipeline page, press "Copy link" in the "Telegram bot" box. Pin it in your channel, add it to your bio, send it to three real customers.
Each template lets one person send only a few requests a day and a month, in some templates only 1 to 3 a day. Your own tests count too. While you test, raise the numbers under "Submission Limits" in the form settings.
Read the questions before you share the link. A few templates are written for a contractor describing their own service, not for a client asking for help: Construction & Repair asks about "years of experience". If clients will send you jobs, start from Service Request instead. To start empty, press "Start from scratch" when you choose a template.
Get requests and call people back
Situation. People leave a request, such as a quote or a repair, and you call or write back. Nothing needs approving.
Solution. This is how the form works right after you create it. Each request comes to your Telegram the moment the person sends it. There is nothing to press: you read it and call. Everyone on your team who has linked their Telegram gets it too. After your test, the bot offers to connect a channel. You don't need one here, so ignore it.
Watch out. By default, the thank-you says "Your submission is awaiting review." Nobody reviews anything here, so people wait for nothing. In the form settings, under "Bot Messages", replace the "Completion Text" with what will really happen:
Thank you, we have your request. We'll call or write to you within a working day.
If these are leads, reply fast. Sales teams call this speed to lead: the time between a request and your first reply. To see whom to call first, add one or two questions with buttons, such as budget or timing. The quote request guide and the client intake form for agencies each build a full lead form.
Say yes or no to each request
Situation. The person waits for your decision, such as a seat at an event or a refund, and needs to hear back either way.
Solution. Approve and Reject buttons appear once you connect a Telegram channel to the form: the bot puts approved requests there. Make the channel private, so only you and your team can see it. Then one tap is enough, and the bot sends the person your yes or no message. Approved requests are also posted to that channel, so you keep a record.
How to turn it on.
- In Telegram, create a new channel and make it private.
- After your test, the bot offers a "Choose a channel" button. Press it and pick that channel. Telegram makes the bot an admin that can post. Missed it? On your pipeline page, press "Choose a channel in Telegram" in the "Still to do" list.
- In the form settings, under "Status Notifications", write the approval and rejection messages.
- Send a new test. It should now come with Approve and Reject buttons.

Illustration: the texts are the bot's own; names and data are made up.
Messages you can paste:
You're in! Your request is approved. We'll send the details before the date.
Sorry, we can't accept this request. This usually happens when [reason]. You are welcome to send a new one.

Illustration: the texts are the bot's own; names and data are made up.
Under each request you also see Edit, which opens it on the site to fix a typo, and Delete.
Watch out. Don't connect your public channel for this: approved requests, phone numbers included, would be posted for everyone to see. And Delete removes a request without telling the person. For a polite no, press Reject.
Post what people send to your channel
Situation. Subscribers send you listings or news, and you copy the good ones into your channel by hand.
Solution. Connect your public channel with the "Choose a channel" button, the same way as above. Each request comes with Approve and Reject buttons. After Approve, the bot posts it to the channel. The person gets your approval message, then a message with buttons to open and share the post.
The post text comes from the "Post Template" in the form settings: your text with each answer slotted in. It does not update itself when you change the questions. For a new question, click its token under "Insert tokens": a short code goes into the template, and the post shows the answer in its place. For a deleted question, delete its line.
Watch out. Everything in the Post Template goes public. Leave phone numbers and other private answers out of it.
To post without checking each request, open "Actions" on your pipeline page, press Edit on the channel and tick Auto-approve. You still get each request, without buttons. The person gets your thank-you and then the message about the post, so make sure the thank-you doesn't say "awaiting review".
Collect photos, documents and voice messages
Situation. You need to see the problem: a photo of the leak, a receipt or a voice note with the details.
Solution. In the form settings, press "+ Add Field" and choose the type Files. People can send photos, documents such as PDF, Excel or Word, videos, voice messages and audio. They can send up to 10 per question, then tap Done. This works in the bot and on the web form. The files are not inside the request you get in Telegram. To see them, press "Review submissions" under the request: it opens your dashboard.
Watch out. This one applies even if you post nowhere. When someone attaches photos, the bot builds a text from their answers using your Post Template (it is in the form settings). That text must stay under 1,024 characters. If it doesn't, the bot deletes the request and asks the person to start again. So keep the Post Template short, and leave long text answers out of it.
Take requests from people who are not in Telegram
Situation. Some clients come from your website or a flyer and don't use Telegram.
Solution. The same form also works as a web page. People fill in all your questions on one page, files included. The request comes to your Telegram like any other, marked "Sent through the web form".
How to turn it on. On your pipeline page, find "Where people send submissions" and switch on "Web form". You get three things:
- a link to share;
- a QR code form for posters and flyers: people scan it and fill in the form in their phone's browser;
- "Code for your site", to embed the form on your website: paste it into your site editor, or send it to whoever runs your site.

Illustration: names and data are made up.
Watch out. Your yes or no reaches people only through Telegram. After sending, the person sees a button to get your answer there. People without Telegram won't get it, so make the phone question required and call them.
Let people answer in one message or by voice
Situation. Some people won't tap through seven questions. They would rather write "selling a 2-bedroom in Almaty, 45 million, call +7…" or record a voice message.
Solution. Switch on AI intake. The bot then asks for everything in one message, typed or spoken, and AI fills in the form. If a required answer is missing, the bot asks for it. Before sending, it shows what it understood, with Send and Fix buttons. The request you get shows the answers and, under them, the person's own words. If AI can't read the message at all, the bot asks your usual questions, so no request is lost.
How to turn it on. On your pipeline page, in "Where people send submissions", switch on "AI intake" in the "Telegram bot" box. The bot's first message then has a "Fill in step by step" button for anyone who prefers the usual questions.

Illustration: the texts are the bot's own; names and data are made up.
Watch out. How many one-message requests you get a month depends on your plan, for all your forms together. The counter next to the switch shows it. When the limit runs out, the bot asks the usual questions until the 1st of next month. AI intake works in the bot only, not on the web form.
Send requests to a spreadsheet or CRM
Situation. You copy each request by hand into Google Sheets or a CRM, the program where you keep clients and deals.
Solution. Connect a webhook. It forwards each new request automatically to a web address you choose. The address comes from a connector such as Make, Zapier or n8n, which receives the request and writes it into your sheet or CRM. The webhook is available on some plans.
How to turn it on. Make, Zapier and n8n each have a ready first step called Webhook. Start a new automation with it, and the service shows you the address. Then open "Actions" on your pipeline page, add a webhook and paste that address.
Watch out. To the bot, a webhook is a place for approved requests, just like a channel. So every request gets Approve and Reject buttons, and nothing reaches your CRM until you press Approve. If you only call people back, press Edit on the webhook and tick Auto-approve.
If the connector is down, Easy Post does not send the request again. You get a message about it, and the request stays in your dashboard. Photos and files reach the connector as links that anyone with the link can open, so think twice about ID documents.
Send requests to different channels by city or topic
Situation. Requests come from different cities, and each city has its own channel. Or only the big requests should go to your CRM.
Solution. Ask about the city or the budget with buttons. Then give each channel or webhook a condition that checks the answer:
- City equals "Dubai" → the Dubai channel; City equals "Abu Dhabi" → the Abu Dhabi channel.
- Budget equals "20000+" → the CRM. Smaller requests stay in Telegram.
How to turn it on. Open "Actions" on your pipeline page. Add each extra channel with "Add Action": choose "Publish to Channel", enter the channel's @name, and in that channel's settings in Telegram, add the form's bot as an admin. Then press Edit on each channel or webhook and use "+ Add condition".
UyTap, our real estate demo, works this way: one form, seven city channels, one condition each. The UyTap case study shows the setup. You can also try @GulfHireBot, which does the same for job ads in two cities.

Illustration.
Watch out. "Greater than" and "less than" work only with a plain number such as 1500. For money, offer ranges as buttons and use "equals". Write the ranges without commas, as "1000-5000": a comma starts a new button. On some plans a form can have only one channel or webhook, on others a few.
Handle requests as a team
Situation. Several people handle requests, and each of them should see every new one.
Solution. Add your colleagues to the project. A project is a folder that holds your forms; you find it under "Projects" in the top menu. Everyone gets every request. When requests come with Approve and Reject buttons, the first press decides, and anyone who presses later sees it was already handled.
How to turn it on.
- Open the project, then "Members", and add people by the email of their Easy Post account. They must sign up first.
- Each of them opens the pipeline page and presses "Link Telegram Account" or "Test the form in Telegram". Without it, they get nothing.
Watch out. Members can also change the form. There is no role that can only approve.
When a Telegram form is not the right tool
A Telegram form can't change its next question based on an earlier answer or let people pick several buttons in one question. People can't edit a request after sending it. It is not a CRM either: it doesn't track deals.
| Question to ask | Easy Post | Google Forms | A bot built for you |
|---|---|---|---|
| Can people answer without leaving Telegram? | yes, and on a web page too | no, they open a browser | yes |
| Do new requests reach you in Telegram? | yes, right away | by email; Telegram needs a connector | if the developer builds it |
| Can you say yes or no, and the person hears it? | yes, two buttons | not built in; approvals need an add-on | if built |
| Files and voice messages? | yes | files, if people sign in to Google; no voice | if built |
| Questions that change based on answers? | no | yes | if built |
Pick Google Forms or Typeform, another online form builder, if your clients are used to email and you need questions that change with the answers. Pick a custom bot if your process is unusual enough to pay a developer. Pick a Telegram form if your people are in Telegram and you need to answer or approve requests quickly. More detail: Google Forms vs Easy Post and the Typeform alternatives comparison.
Check before you share the link
- The thank-you says what will really happen, not "awaiting review".
- Every question you need is ticked Required, and the easy ones come first.
- Every choice is asked with buttons, with no commas inside an option.
- Your test request arrived in Telegram, with Approve and Reject buttons if you say yes or no.
- Every colleague has linked their Telegram.
- If you post to a channel: the Post Template has a line for each new question and no private answers.
- If you use a webhook and only call people back: Auto-approve is ticked on it.
- The limit per person is high enough. Unfinished forms count too.
After a week, open your dashboard and look for a "Pending" tab: it holds forms people started and did not finish. See how far people got, and shorten that question or turn it into buttons.
Forms for specific jobs
Pick the job that looks like yours. Each article takes one job from the template to a working form. If you run a channel, start with Telegram channel bots: what to automate: it groups the guides for admins by job. If you run a business, the guides for business owners are grouped by job at the end of Telegram bots for business: 5 workflows. If you manage a team, the guides for teams are grouped by job at the end of daily reports for field teams via Telegram.
Customers write to you
- Lead form: six questions for ads, each lead in your Telegram with a phone number
- Quote request form: four questions and a rule that sends big requests to your tool
- Service request form: requests for repairs, tutoring, delivery and beauty services
- Order form for a small business: customers pick item, quantity and date, orders land in your Telegram
- Order form link for orders in Telegram: put the link in your bio, buyers order in a browser
- Appointment request form: people pick a service, day and time, you confirm by hand
- Table booking app: guests pick a time, you answer each request with Approve or Reject
- Booking bot for salons: take booking requests for a salon, barbershop or nail studio
- Business proposal form: you approve a provider's proposal and it posts to your channel
- Client intake form: four fields that matter, and routing leads to your CRM
- Website contact form: get website contact form messages in Telegram, no plugin
- Food order form: a menu in the welcome text, five questions and one card for every customer
- Wholesale order form: company, cases and delivery date from each buyer, one card per request
- Insurance claim form: clients send the date, policy and photos, you get the whole notice in one message
Your team and operations
- IT request form: colleagues send a problem, its impact and a screenshot
- Maintenance request form: tenants send the problem, address, phone and photos
- Bug report form: six fields for testers, and a setting that keeps long reports
- Expense report form: a receipt photo, and your Approve tap as the decision to reimburse
- Inventory tracking sheet: log stock received, dispatched and written off, balance in a sheet
- Transport request form: the eight fields a dispatcher needs for a freight request
- Vendor registration form: eight fields to keep or drop, a private channel as your approved list
- Daily report form for field teams: crews send project, hours, tasks and photos to the office
People, feedback and events
- Job application form: six questions for every candidate, and a limit to raise
- Event registration form: six fields, and your approval works as the seat
- Customer satisfaction survey: a star rating and a reason, with low scores forwarded
- Suggestion box: an anonymous box: one link, a QR code, no names attached
- Poll in Telegram: a built-in poll for one question, or a survey form for several
- Telegram quiz bot: five ways to build a quiz bot, with setup time and tradeoffs
- Pet adoption form: volunteers send each animal, you press Approve, the channel fills itself
- Dating profile form: people send profiles, you press Approve, the channel fills itself
- Car for sale ad form: sellers send the car and photos, you press Approve, the channel fills itself
- Property for sale ad form: sellers send the flat, floor and photos, you press Approve, the channel fills itself
- Classifieds board: sellers send the item, price and photos, you press Approve, the channel fills itself
- Freelance job board: posters send a job or a service, you press Approve, the channel fills itself
- Handmade products board: makers send a product with price and photos, you press Approve, the channel fills itself
Keep reading
- How to create a Telegram bot without code: if you want a bot of your own.
- Event registration form: saying yes or no, from start to finish.
- Quote request form: calling people back, with a rule for big leads.
- UyTap case study: posting to seven city channels.
- Content approval workflow: approving submissions for a channel.
- Telegram quiz bot: when you need a quiz rather than a form.