A car’s path through the shop
A car moves through clear stages: booking or call, intake with the complaint and mileage, diagnostics, approval of the work and price, repair, ready, handover and payment. Each stage is a CRM status, and every change sends the customer a message in the Telegram bot or by SMS. Customers stop calling every hour, and the service adviser stays with the cars. Extra work is approved in the conversation on the job, so an “I never ordered that” dispute is settled from the record, not from memory. Repair orders with labour hours and a parts warehouse are not in the CRM price list: we scope them during discovery, and the warehouse can be an ERP module, a separate product with its own price.
Repeat visits: service, oil, tyres
A shop earns on customers who come back: oil changes, seasonal tyre changes, scheduled servicing and checks of gas equipment on cars running on methane or propane, which are common in Uzbekistan. If only the customer remembers, they go wherever is convenient that day. The CRM creates a reminder task from the date of the last visit and sends the customer a Telegram message or an SMS through Eskiz with a link to online booking. Eskiz only delivers pre-approved templates, so we agree the texts before launch. Reports show how many customers returned after a first visit, which sources bring new ones and how much revenue each mechanic and each branch generates.
Money, mechanics and branches
Taxi fleets, delivery services and companies with their own vehicles are often served on credit and pay monthly. The payments module shows who owes what and for which vehicles, and 1C and Didox sync produces invoices to companies without manual entry. Mechanics are usually paid by completed work: a percentage, a fixed rate or both. KPIs and pay are calculated on your formula, so month-end disputes shrink. Access is role-based: a mechanic sees their own jobs, the service adviser sees bookings and statuses, the owner sees money across all branches. With the staff app, a mechanic updates the status from a phone right at the lift.
Price, timeline and contract
The Start level covers clients, repair jobs, tasks, two roles and Telegram alerts: enough for a single shop moving off a notebook. Business adds branches, telephony, messengers, reports and 1C. Repair shops usually add online booking, the customer bot, SMS through Eskiz, payments and balances, and mechanic KPIs; the configurator adds it up. You see a working version every two weeks, and booking and repair statuses usually go live first. The contract fixes the price, the timeline from 6 weeks and the server location. Every day of delay on our side cuts the invoice by 2%, up to 10% of the contract in total. Bugs are fixed free with no time limit; your engineer may audit the code, and any unfulfilled item means a 10% refund.