Mechanics' output and the monthly plan in Telegram
A bot for car repair shops on eSowa: each mechanic sees their billed hours and what is left to the plan; the manager sees the whole team.
The task
A car repair shop in Gdańsk records its work in eSowa, the workshop software from Inter Cars. The owner wanted to raise the mechanics' motivation. For that, each mechanic needed to see their own jobs, billed hours and what is left to the monthly plan at any moment, and the manager needed to see the whole team without manual reports or phone calls.
How it works
A mechanic connects to the bot from their own phone with a PIN and sees only their own data. One message holds the report for the day and the month: how many jobs, how many billed hours, for what amount and how much is left to the monthly plan. The report arrives by itself every day at 18:00 and opens with a button at any time. Once a day the bot asks for a motivation rating from 1 to 5. The interface is in Polish, Russian or Ukrainian, and each mechanic chooses the language.
The manager sees a summary for the whole team: the daily plan, the actual figure and the gap for each mechanic. In the same place the manager sets monthly plans, adds mechanics from the eSowa list and re-registers a mechanic who has changed phones.
Connection
The bot reads eSowa data and changes nothing in it, with no load on the software. It is installed on the shop's computer in one visit, starts with the computer and restarts itself after a failure. Other workshop software is connected after its database has been examined. In this project, one week passed from examining the database to installation. The scope and acceptance criteria were written into the brief before work started: the bot's data match eSowa, each person sees only their own figures, reports arrive on request and on schedule, and after a reboot the bot starts by itself.
Result and next step
The bot was installed and handed over to the shop. The effect on output was not measured. For now, the manager enters each mechanic's monthly plan by hand. The next step for a shop with such a bot: tie meeting the plan to a bonus and agree the rules with the mechanics before launch. Without a bonus, a daily output summary is read as control.
Questions
Does anything in eSowa need to change? No. The bot only reads data.
Do mechanics need a separate app? Telegram on their own phone is enough.
Can mechanics see each other's output? No. Each sees only their own; the manager sees the summary for everyone.
Does the bot work with other workshop software? This becomes clear when the software's database is examined.
How much does it cost? The price is given after a free 30-minute call. Implementation tiers are listed on the service page.