Car service chain, Moscow
A CRM for four car service centres: bookings, work orders and parts
Bookings lived in notebooks and chats, and parts stock was checked separately in the accounting system. Bays sat idle while a car waited for a part.
- Year
- 2025
- Our part
- Product design, CRM, 1C sync
The problem
Each of the four centres had its own booking notebook and its own chat with customers. A mechanic found out a part was missing once the car was already on the lift. The owner saw revenue only at the end of the month, after the front desk merged their spreadsheets.
What we built
- A daily bay schedule that shows free slots, late customers and cars waiting for parts
- Work orders from check-in to handover, with estimate approval in Telegram
- Two-way sync with 1C: parts stock and reservations refresh every 15 minutes
- Reports on revenue, branches and mechanics without manual spreadsheets
Screens
Swipe or tap a screen
Outcome
- service centres in one system
- between stock updates from 1C
- from screen map to launch in every branch
Stack
- React
- Node.js
- PostgreSQL
- 1C HTTP sync
- Telegram Bot API
What matters most to me is seeing the load of all four centres in one window. I used to piece that picture together by calling each front desk.
Your project could be next
Tell us what you need, and we’ll show you how it could look.