Bots · Telegram Bot · Webhook · Notifications · Menu · Bookings
billiard.guru Telegram bot
We built @BilliardGuruBot for the billiard.guru platform: login and confirmation, a player menu, match alerts, table bookings, and “Find a game” — no separate app.
About the client
Players and clubs don’t only live in the browser. We built the Telegram bot @BilliardGuruBot for billiard.guru: login confirmation, a personal menu, match and tournament alerts, table bookings, and “Find a game.” The product meets the audience where they already chat — no app install. Open beta.
The pain they came with
Tournament chats are noisy: entries get lost, match reminders get forgotten, and the club can’t keep up in DMs. Nobody wants a separate mobile app for a few tournaments a year.
-
Everything in group chats
Registrations, match reschedules, and “who’s on the table” live in the group feed — easy to miss and hard to moderate.
-
No personal channel
A player needs a feed of only their tournaments and bookings — not the whole club’s noise.
-
An app for a few tournaments
Downloading a separate app for seasonal events is a barrier. Telegram is already installed.
How we guided them
We treated the bot as a product layer of the platform: webhook, menu, notification catalog, and club flows — on the same backend as the site.
- 01
@BilliardGuruBot: production webhook, shared session with the site
- 02
Login and phone confirmation via a messenger flow
- 03
Player menu: profile, tournaments, bookings, “Find a game”, alert settings
- 04
Alerts for matches, tournaments, and club events with opt-in
- 05
Club flows: publish a tournament, moderate news via the bot
- 06
Tied to the cabinet and brackets on billiard.guru — one product, two channels
In plain speak
Brief jargon — without the fog. How we explained each step to the client.
Bot webhook
Telegram sends messages to our server right away — the bot replies without polling lag.
Notification catalog
The player chooses what to get: matches, tournaments, bookings — no spam in DMs.
Bot menu
Buttons instead of commands: profile, my tournaments, book a table, “Find a game.”
Club flows
The owner confirms a tournament or news in Telegram — not only in the web cabinet.
What we did, step by step
Each step is a concrete change. Meaning on the left, screen on the right.
Bot as a service channel
Not chat for its own sake: login, menu, and alerts are wired to the same platform as billiard.guru.
Login via messenger
Phone on the site, confirmation and flows in the bot — the player reaches the cabinet without a separate password or extra forms.
Menu and notifications
Profile, tournaments, bookings, “Find a game,” and alert settings — a personal channel instead of club-group noise.
Bookings from Telegram
Table and time can be booked from the bot — the club sees it in the cabinet, the player gets confirmation in DMs.
More frames from the project
Not a gallery for its own sake — a few screens that complete the picture.
Where we landed
Live bot @BilliardGuruBot in open beta: players and clubs run tournaments and bookings in Telegram next to the site. We run the product ourselves — PRIME.
What they got
- Own product · Telegram bot · open beta
- @BilliardGuruBot · login · menu · alerts
- Table bookings and “Find a game” from the messenger
- Club flows: tournaments and news
- Same backend as billiard.guru
- Live t.me/BilliardGuruBot
In numbers
Need a Telegram bot for your product?
We’ll build login, menu, alerts, and bookings in the messenger — the same way we did for billiard.guru.
Other projects
Similar cases and neighbouring directions
~120 calls per month from search
KabelMontazh
SEO for KabelMontazh
B2B electrical installation: a 30-phrase commercial keyword set, page-one growth planned over 2–6 months, about 120 search calls per month. Partnership until ~2021 — then the company closed under market pressure.
View case →
~120 calls per month from the web
VoronezhVtorma
SEO for VoronezhVtorma
SEO for a recycling intake point: search instead of flyers. 57 phrases, prep ~1 month, page one planned over 2–6 months, about 120 calls per month and visits to the drop-off point.
View case →
~170 calls per month from the web
Rc-Revolt
SEO for Rc-Revolt
SEO for an RC-model store: 68 phrases, page one planned over 2–6 months, about 170 calls per month. Search demand was there — the business misjudged its financial model and turned unprofitable.
View case →