Telegram Bot: Owner Summaries and Client Balance With No App Install

Not every client wants to install yet another app just to check their card balance or get a list of a point's services. In RentOS you don't need to install anything for that — Telegram is enough, and almost everyone already uses it.

For the Owner — Summaries With Zero Token Setup

Connecting the bot as the Owner isn't "go to BotFather, create a bot, paste in a token and a chat ID." The bot in RentOS is platform-wide, one for everyone: the Owner just links their chat with a one-time code, with zero technical setup. After that, summaries start arriving for every results submission, plus a separate "Daily Till" summary — a wrap-up of the business day, not tied to any one shift.

For the Client — Balance With the "Share Number" Button

If client wallets are enabled for the business, a guest can message the bot, share their phone number with one button, and get their balance instantly, with no call to the point and no logging in anywhere. The "services list" command shows what the business actually offers: if the point runs in ticket mode, with assets and prices; if not, just a list of zones.

A Real Security Detail, Not Just a Claim

Telegram's "Share Number" button has a catch that's easy to miss: technically, nothing stops a person from attaching someone else's contact card, saved in their phone book, instead of their own number — from the outside it looks exactly like a normal share. A naive check that "just trusts the number it's sent" would show anyone who knows a phone number that person's balance. RentOS verifies that the sent contact technically belongs to the person who sent it, not just that it's sitting in their address book — and without that match, it shows the balance to no one.

Why This Matters More Than It Looks

A wallet balance is, in essence, money the client has already trusted the business with in advance. Showing that number to the wrong person isn't a minor glitch — it's a leak of a real guest's financial data. The difference between "works in most cases" and "works correctly even in a non-obvious scenario" is exactly why it's worth trusting a finished system instead of hacking together a messenger integration yourself.