The operator cabinet is a Mini App inside Telegram. Catalog, studios, RTP versions, keys, team and balance alerts, on the phone your team already has open. Open @aggregator_aibot, link your web login once, and it is the account you have on the web.
Simulated data. The screen is drawn after the Games tab of the Mini App as it runs today; the messages are what a team says in a day with it.
We did not build a Telegram companion to a web panel. We built the operator cabinet as a Mini App on the same account and the same database as the web cabinet. Use either; a few things, top-ups and billing settings among them, still live on the web.
The integration thread, the question to a studio, the incident at midnight: in this market, more often than not, they happen in Telegram. A cabinet in a browser tab is a login and a context switch nobody makes at 23:40.
Everyone opens the Mini App from their own Telegram account and gets a role. No password in a pinned message, and the audit log names a person, not a shared login.
Save a chat once in billing settings and the balance warning arrives there as a message from the bot, at 50, 30, 10 and 0 percent of your last top-up. An email is read tomorrow. A message is read now.
The Mini App and the web cabinet are the same account and the same data once you link them. Use either. Some of it exists only in the Mini App today: asking a studio from the game card, and a studio's GO LIVE flow.
To our knowledge, the first game aggregator whose operator cabinet runs inside Telegram rather than beside it. In September 2026 we read the public product documentation of more than twenty aggregators and casino platforms. Every operator back-office we found runs on the web or in a vendor's own mobile app, and every Telegram product in the category is built for players. If we missed one, tell us.
Every title has an inline switch in the list and every studio a master switch in the Providers sheet and on its card. The LIVE, OFF and CUSTOM RTP counters at the top double as filters; studio, type and search narrow the list. A switch here writes the same selection table the web cabinet writes, and every change is on the audit log.
Auto follows the highest RTP build after every catalog sync. Pin a build yourself and it survives the syncs. Applying is a separate step, because a build is a money decision. The same card shows spins, players and GGR for the last 7 and 30 days.
When a studio goes live, its card lands on your Home tab and the announcement reaches you as a Telegram message. Enable all games in one tap and a confirm, at max RTP. Anything you switched off by hand stays off.
The question goes as a Telegram message to the studio's own team, with your Telegram handle, and they answer you in Telegram. No ticket, no account manager in between. The button is there whenever the studio's team is reachable in Telegram.
One API key, then read-only MCP discovery for Claude Code, Claude Desktop, Cursor or Codex, or a curl quickstart. Configure the callback and check connectivity. The wizard ends at API access configured. Continue building and validating your backend through the HTTP API; access setup does not certify the integration.
Invite with a role in a link you forward in chat: shown once, valid 72 hours, revocable. Eleven roles and the same permission model as the web. Suspend, reactivate, remove, approve a join request, all from the phone.
At 50, 30, 10 and 0 percent of your last top-up, and at a line you set yourself, the bot messages the chat you saved in billing settings. Email and a webhook are there too if you want them.
The Mini App validates the launch data Telegram signs on every call. The client never names an organisation, an operator or a user; who you are is resolved on the server, every time.
An owner or admin can issue the organisation's API key from the start, on a launch not older than an hour and behind your second factor if you have enrolled one. The key is shown once; store it in your secret manager. The same key serves welcome-credit and paid sessions, which use real wallet callbacks.
The screen hides what your role cannot do. The server refuses it anyway, and refuses when in doubt. Granting the admin, compliance and finance roles is reserved for the owner.
One database, one selection table, one audit log. The Mini App mirrors the web cabinet's behaviour; where it differs on purpose, the difference is written down, and on keys and money it is stricter. The parts that sign requests and move money are pinned by tests.
The same bot opens differently depending on who you are, because a studio, an operator and an affiliate need different first screens.
Catalog, studios, RTP versions, the game card with its numbers, API access setup with one key, the team console, balance alerts. This page.
Your catalog with each game's details, a wallet with balances, a spins chart and withdrawal history, withdrawal requests from the phone, the integration request, and the GO LIVE flow with the press release previewed as the message operators will receive.
Dashboard, wallet, promo assets and achievements; your referral link with a QR to share.
Brands, studios and analytics for many casinos stay a big-screen job, so the platform account opens a hand-off to the web cabinet, with the profile and support one tap away.
No install, no second password. If you have a web account, link it from the profile and the Mini App shows the same organisation, the same catalog and, for billing roles, the same balance.
Scan with your phone. The cabinet opens in Telegram. Read the MCP connection guide 
