Employee requests for leave and shift swaps, decided in one place

A worker asks for leave in a private message to the supervisor, the request never reaches the planner, and the schedule ends up with a gap. In Vakhta the worker files a request in Telegram: vacation, day off, sick leave, shift swap, late arrival, early leave, a time correction or a score appeal.

Each request has a route: who decides and by when. The reviewer sees it in the panel inbox and records a decision with a comment, and the worker receives the answer in the bot. New requests appear in one list with a filter by type.

Decisions are made by the people responsible for each step: the shift supervisor, the unit manager or HR. A shift swap first needs the colleague’s consent in the bot. Approved leave or a swap creates a new schedule version, and an approved correction changes time records through a separate entry while the original data stays.

Only HR can see a medical document photo attached to sick leave. If a worker asks in person, an authorized user can file the request on their behalf in the panel. Requests involving potential overtime also wait for a decision in this section.

For the pilot, choose the request types that get lost most often today, for example shift swaps and time corrections. Agree who decides each type and by when.

Measure the time from submission to decision, count overdue requests and check whether the planner sees schedule changes without extra phone calls. Ask a few workers whether they understand which step their request has reached.

Also check sick leave: does HR receive medical documents on time, and are they hidden from people who do not need them? Workers’ trust in the system depends on it.

A request in Vakhta does not replace the HR documents or orders that the law or your internal procedures require. The system does not decide instead of a person and does not calculate holiday pay.

Launch needs an employee list with linked Telegram accounts, the unit structure and an assigned reviewer for each request type. An administrator, production head or HR can cancel or shorten approved leave with a reason that stays in the history. The same dialog can return the worker to the schedule, and the worker receives the return date in the bot.