Expo registration through a Telegram bot is a scenario where the guest answers questions right in the chat, receives a personal QR ticket there and stays in touch with the organiser before, during and after the event. At the UzFranchise Expo in Tashkent this produced a single database of 7,500+ people, and 3,539 tickets were scanned at the entrance over two days.
Key takeaways
UzFranchise Expo is a franchise exhibition held in Tashkent in April 2026. The organiser put the task briefly: automate visitor registration and build a system for working with the audience afterwards.
The usual route looks like this: a form on the website, a ticket by email, a spreadsheet of contacts, a mail campaign. It works right up to the moment the organiser needs to reach a guest quickly. The letter gets lost among dozens of others, lands in spam, and a week later the person no longer remembers which address they used.
We built registration in the channel the audience uses every day and connected it to the expo CRM. The full project is described on the UzFranchise Expo case page.
The main reason is that the ticket and the conversation end up in one place. The guest is already in the bot, the QR ticket is there, and the reminder arrives in that same chat rather than in an inbox opened once a week.
The second reason is the habit of the audience. In Uzbekistan Telegram remains a working channel for business correspondence, and asking someone to register in a bot requires neither a new app nor a password: one tap in the same messenger they use with colleagues is enough.
| What happens | Website form and ticket by email | Registration in a Telegram bot |
|---|---|---|
| Where the ticket lives | In a letter that has to be found in the mailbox | In the chat, next to the messages about this event |
| Reminder about the date | One more letter in a stream of newsletters | A message in the same chat that holds the ticket |
| Qualifying the guest | A long form people fill in reluctantly | A few questions in the chat, one at a time |
| Reply from the guest | A reply email or a call to the contact centre | A chat message, visible in the CRM at once |
| Languages | Usually a single registration interface | Russian, Uzbek and English in one bot |
How the Telegram bot platform works and what it can do is covered in the article on Telegram bot development for business. In a case study something else matters more: what that choice gave the organiser.
Registration ran in the chat in Russian, Uzbek and English, and the guest marked why they were coming to the expo. The questions were not there for the sake of a form: each answer fed straight into a segment.
After the survey the person received a personal electronic ticket straight into the chat, with nothing to print. What is encoded in the ticket and how the check at the entrance works is covered separately in the article on QR tickets for events.
Contacts and answers went into the expo CRM automatically: for every guest you can see who they are and how ready they are to buy. How bot events reach records, and what to do when the exchange fails, is described in the article on Telegram bot and CRM integration.
Important Guest contacts are personal data, so consent to processing is collected at the registration step, before the ticket is issued. Law No. ZRU-1125 of 26 March 2026 left mandatory in-country storage only for biometric and genetic data and data of telecom users, while personal data bases are subject to registration.
The segments from the survey were useful before the expo as well: a message went to the right group instead of everyone at once.
Example A week before the opening, the segment that wanted to buy a franchise received: “We meet at the expo in a week. We have put together a list of franchises you will be able to buy right there.” Those interested in investment got a different message: “Two days until the expo. In the business programme, do not miss the session on which franchises are worth investing in in 2026.”
That turns registration into preparation for the visit: the guest arrives already knowing what to look at and why.
A source tag travelled into the database together with the registration, so it was clear which advertising each guest came from. Telegram passes the bot a parameter from the link on first start, up to 64 characters, and that is enough to tell the channels apart. The mechanics of such tags are covered in the article on deep links and traffic sources.
At the entrance a ticket was scanned in 0.2 seconds, so no queue built up.
The organiser dashboard showed how the database grew day by day and which advertising each guest came from. The figures updated during the expo itself, so decisions were made the same day rather than in a report a week later.
An exhibiting company scanned the guest QR code with its own phone, and the contact landed in its database immediately, with no extra hardware on the stand. Instead of a stack of business cards sorted back at the office, the exhibitor had a ready list of everyone who came up by the end of the day.
The main result is not convenient registration but an in-house structured audience database that can be managed after the venue closes: for repeat communication, for promoting the next events and for monetisation. The whole database is exported with one button.
The base is already sorted by interest, because the guest went through the survey at registration. The “I want to buy a franchise” segment is invited to a business breakfast for future franchisees. The “I want to package my business as a franchise” segment gets a separate event about preparing for the sale. A third group is interested in investment, a fourth in a particular industry.
The next event does not start from a blank page: part of the audience is known by name, interest and history of contact, and can be invited in the same chat that held the ticket.
The scheme is not tied to franchises: registration for a conference, a forum, a festival or a closed screening is built the same way. A few things are worth checking before the start.
It is also worth looking at the places where such projects usually break.
We start not with the bot but with what the organiser will do with the database after the venue closes: which segments are needed, and what you will write to whom in a week. The survey questions, the CRM structure and the set of figures on the dashboard all follow from that. Then we build registration, tickets and scanning and test them on real devices and on poor connections — before the event, not on opening day.
The budget reference point is a bot that takes requests from $1,200 on the service page; for an event it collects the survey, issues QR tickets, counts arrivals and puts contacts into the CRM. The outcome of that work is visible at UzFranchise Expo: the organiser has an in-house database with segments and a history of contact, and exhibitors have leads from the stand the same day.
Let’s discuss your project
Tell us what you need, and we will estimate the timeline and cost and suggest a solution.
The budget depends on the number of entry points, bot languages, staff roles and integrations. The reference point on the service page is a bot that takes requests from $1,200: for an event it collects the survey, issues QR tickets and puts contacts into the CRM. The exact quote follows a map of scenarios: who registers, who scans and what happens to the database afterwards.
No. Registration, the ticket and reminders live in Telegram, which the person already uses every day. At UzFranchise Expo the bot ran registration in Russian, Uzbek and English, and the ticket arrived straight in the chat, with nothing to print.
They are a separate segment and a valuable one. At the expo those guests received an invitation to the second day, and after the closing the exhibitor catalogue, a short report and the results of the event. The contact stays in the database with its interests, and the next event invitation can go to the same chat.
Yes, the database belongs to the organiser and is exported with one button. It shows who the person is, what they were interested in at registration, which advertising they came from and whether they were on site. Those segments are then used when preparing the next event.
Yes, and it is collected at the registration step, before the ticket is issued. Contacts and survey answers are personal data, bases of such data are subject to registration, and mandatory in-country storage was left by the law for biometric and genetic data and data of telecom users.
Yes, the mechanics do not depend on the subject of the event: the survey questions, the segments and the entry rules change. A conference adds guest categories and separate halls, a festival adds the number of entries and the dates the ticket is valid for.
A member of staff scans the guest QR code with their own phone and the contact lands in the company database immediately, with no extra hardware on the stand. By the end of the day the exhibitor has a list of everyone who came up, and can reply while the person is still at the expo.
