An internal Telegram bot collects employee requests — leave, expense reports, visitor passes, purchases, system access — moves them along the approval route and writes the decision into the company's system of record. The employee needs no separate portal and no new password: they open the same messenger they already use with colleagues. A button in the bot stays an internal decision, while legal force comes from a digital signature.
Key takeaways
The bot takes over requests where the employee writes the same message every time and the manager answers «approved» or «no». These are short processes with a clear set of fields and one or two approvers.
The selection rule is simple: the process repeats several times a week, has a single owner and no more than three approval steps. The first process you move into a bot is the most frequent one, not the most complex — a frequent process quickly shows where people stumble and which wording fails.
Tip Before development, collect a month of work-chat messages that start with «can I», «please approve» and «please sign». The two or three most common of them are the bot's first scenarios.
The main difference is the barrier to entry: the bot needs no installation, registration or training, and a request inside it looks like a four-step conversation. A portal offers more, but only people who sit at a computer all day actually use it.
| What we compare | Telegram bot | Portal or email |
|---|---|---|
| Access | A messenger already installed | A separate address, login and password |
| Filling in a request | Buttons and three or four questions in turn | A form with every field at once |
| Signal to the approver | A chat message with decision buttons | A letter or task opened later |
| Working from a phone | The main mode | Depends on the portal layout |
| Where the request lives | In the system of record; the chat holds notifications | Entirely in the system |
| Limitation | Not a place for signed documents and large files | Needs training and discipline |
So the choice is not «a bot instead of a system» but «a bot as the entry point to the system». The request is stored in 1C, CRM or ERP, and Telegram remains the interface where it is created and approved. A customer-facing bot solves the same task from the other side — what it does and how its price adds up is covered in our article on Telegram bot development for business.
Approval rests on inline buttons: a tap sends no message to the chat but returns an action code to the bot, which then changes the request status and the text of that same message — exactly as described in the Telegram documentation for bot developers. The approver sees one card with the current status instead of a thread of ten replies.
Who sees which request and who may approve it is decided by your server, not by Telegram. The Bot API documentation says it plainly: command scope only controls hints in the interface, while the backend must verify the right to act on every request.
A request without a deadline hangs in the chat of an approver who «will look at it tonight». That is why every step has a waiting limit: the bot reminds the approver and, after the second reminder, raises the request one level up or hands it to a deputy.
The second must-have is a visible status. At any moment the employee should be able to ask the bot «where is my request» and get an answer with the number, the current step and the name of the person deciding now.
A pressed button is an internal company decision, not a signature. Law No. 611-II on Electronic Document Circulation of 29 April 2004 treats as an electronic document information in electronic form confirmed by a digital signature, and article 7 gives such a document the same force as a paper one.
Law No. ZRU-793 on Electronic Digital Signature of 12 October 2022 lists in article 4 the three conditions under which a signature equals a handwritten one: its authenticity is confirmed, the key certificate is valid at the moment of confirmation, and the signature is used for the purposes stated in the certificate.
Important If a request later produces an order or a payment, keep a link to the signed document in its card. Otherwise, six months on, nobody will explain on what grounds the money or the equipment was handed over.
A bot without a system of record stays a chat where requests get lost along with the message history. That is why the storage place is chosen before the dialogue script is drawn.
The exchange scheme, the choice between a webhook and polling and the Bot API limits are covered in our article on Telegram bot integration with CRM. The reverse flow — regular summaries for the manager on how many requests passed and how many are stuck — works the same way as 1C reports in Telegram.
Platform limits shape the scenario more than it seems: they decide which attachments the bot accepts and how often it writes to employees.
Within a single chat Telegram advises staying under one message per second: denser sending returns a 429 response, and the notification has to be repeated later. A bot that ignores this code silently loses part of its reminders.
Telegram carries the minimum: the request number, its type, the amount, the dates and a short comment. Passport details, medical certificates, addresses and salary figures stay in the system of record, and the chat holds only a link to the card.
Handling such data is governed by the Law on Personal Data. In its current wording, article 27-1 requires biometric and genetic data, as well as data of telecom service users, to be stored inside the republic; other personal data may be processed abroad if one of the conditions in part three of the same article is met.
In practice this gives a simple rule: keep the bot's server where the system of record is, and keep the wording in messages impersonal. The less data the correspondence holds, the cheaper it is to protect.
Automating a company's internal routine starts at 2,500 $ with us, while a process review and an automation plan without development costs 400 $. The total depends on the number of request types, the number of approval steps and the system the bot exchanges data with.
Work after launch is counted separately: the bot lives on a server and the scenarios change along with the processes. Support for a company's working systems costs from 700 $ a month with us. The scope of work and the other prices are on the AI and automation service page.
Half of the delays on such projects come not from code but from rules the company never agreed on. Go through this list before development begins.
Syntra Systems starts not with code but with a review of the correspondence: which requests repeat, who answers them and how many steps a request passes today. It often turns out that a process has more approvers than it needs, and half the steps can be removed before automation rather than after.
Then we describe the scenario, the permissions and the route, connect the bot to the system of record and test it on real requests rather than on sample ones. After launch we watch the first weeks: where people press the wrong buttons, which requests get stuck and which wording has to be rewritten.
Let’s discuss your project
Tell us what you need, and we will estimate the timeline and cost and suggest a solution.
An internal bot works with known people and their permissions: it knows who sits in which department, who approves a request and what each person may see. A customer bot accepts enquiries from anyone who opens the link, and its job is to reach a request or a payment.
No, their usual Telegram is enough. But until an employee opens the bot and taps «Start», their chat identifier is unknown to the company and there is nowhere to send notifications — so the first launch belongs in the onboarding instructions.
Through their role in the system of record, not by removing them from a work chat. The bot checks the right to act on every tap, so a closed role stops letting requests through immediately, while the action log stays in place for review.
Yes, within the platform limits: through the cloud Bot API a bot downloads a file of up to 20 MB. Larger documents go as a link to internal storage, otherwise part of the attachments simply never reaches accounting.
The bot remains the entry point and the approval route, while the accounting itself lives in 1C, CRM or ERP. If requests are kept only in correspondence, in a month nobody will tell you how many there were and how they ended.
Next to the system of record it exchanges data with. The Law on Personal Data requires biometric and genetic data and data of telecom service users to be stored in the republic, while other data may be processed abroad if the conditions in part three of article 27-1 are met.
One or two: those that repeat several times a week, have a single owner and no more than three approval steps. A frequent process quickly shows where employees stumble, and fixes cost less than in a large system of forms.
Sources
Cover photo: 정규송 Nui MALAMA, Pexels
