A listing you can buy a ticket from straight away. A person picks the event, the session and the number of tickets and pays; the purchase reaches your Telegram, and a ticket with its own QR code lands in their My tickets. Inside are five linked tables — categories, venues, halls, events and sessions — a good start for a listing of your own.
The screens are already wired together: buttons lead where they should, forms send, lists are drawn from a table.
A layout of the screens rather than a screenshot of a finished app: how it looks depends on your colours, type and content.
🎫
Listing
A photo hero, search, category chips and posters of upcoming events with date, venue and price. The chips are rows of the Categories table and events are rows of Events: a new event is a new row, and an extra night is a row in Sessions.
Search
Categories
Events
Prices
🎉
Event
The event’s sessions as a list — date, hall and venue through the relation — a countdown to the start, a description and the refund terms. The price comes from the chosen session.
Sessions
Countdown
Description
Choose a ticket
🎟️
Tickets
The chosen session, quantity, name and phone, the total and a Pay button. Payment goes to your own till, a request with the session and hall reaches your Telegram, and after payment the app writes the ticket itself.
Session
Quantity
Details
Pay
✅
Ticket
A real ticket from the Tickets table: a QR code carrying this ticket’s own number, the event, date, hall and venue, and Add to calendar and Share buttons. My tickets shows what the visitor bought — upcoming and past — and nobody else’s. The template has no door scanner: the code is checked against the table.
QR code
Event
Hall
Share
What gets changed first
Events, dates and prices are table rows: those typed in the editor appear after publishing, those added inside the app from a phone appear at once.
Venues, halls and sessions with prices are rows of their own tables: a play running three nights is three sessions, not three copies of the event.
The till is yours: ticket money reaches you directly.
How to start from this template
1Open the builder and pick the template — it opens assembled and working.
2Replace the content with your own: table rows, text, photographs and prices.
3Connect your bot and press Publish — the app becomes a button in its menu.
Questions about this template
Do we get the ticket money at once?
Yes. Payment goes through your own till — YooKassa or T-Bank — the money reaches you directly, your till issues the receipt and refunds are made in its cabinet.
How do I know who bought a ticket?
A request with name, phone, session, hall and number of tickets reaches your Telegram the moment Pay is pressed, before the payment itself — so abandoned purchases show up among requests too. Paid tickets are the rows of the Tickets table: a ticket is written only after a successful payment, with the number that goes into its QR code. That table is what you check guests against at the door.
Can we send participants a reminder?
No. The bot writes to the app owner rather than to visitors: broadcasting to your own audience does not exist in the product yet, and we do not present it as ready.
How it looks in the trade
The industry page shows what the app is made of in this trade, what it costs to run and where to start.