The post sits idle, the technician waits, the client drives to the shop next door
The advisor is on their own, and at peak time they are under a car. An auto-service practitioner puts it plainly: you do not have a chair in a hair salon, you have a mechanic, equipment, a post. The client did not come, yet the post and the technician were held for them. Another client called, did not wait and drove on.
Когда the advisor is busy with a car while requests pile up on WhatsApp and the phone, я хочу everyone to get an answer at once and be booked on a specific slot and post, чтобы no request gets lost, no post sits idle, and every client leaves a trace: where they came from, what they are booked for, and whether they came.
A request becomes a booking, and the client is expected at a specific hour.
The market in figures: the client has somewhere to go
The figures from the Bureau of National Statistics describe the market, not your workload.
Incoming flow. How many competitors there are and when the peak hits.
Как связано с вашей задачейThis is the whole country; Almaty alone has 1,262 stations. If you do not answer in time, the client has somewhere to go.
Как связано с вашей задачейThis is the deadline for changing tyres, not the day of the peak. Another period may be set by the legislation of a member state; we found no other period in the Code of Administrative Offences of Kazakhstan.
Follow-up. Who comes back and what helps them reach a booking.
Как связано с вашей задачейThis is the fleet across the country, not your base. Old cars need servicing and suspension work: these are repeat visits from people who have already been to you.
Как связано с вашей задачейThese are doctor appointments and a 2013 review, but the mechanism is the same: a person forgot about the booking. A reminder does not promise the same effect in an auto service.
Record-keeping. How small businesses keep track of clients.
Как связано с вашей задачейThis is the EU, not Kazakhstan, and enterprises from 10 employees up. It shows that small businesses keep client history more often in a notebook and a messenger than in a system.
That is the market. At your post, though: how many requests were left unanswered until the evening yesterday?
What we did not find: open data on the response speed of Kazakhstan auto services and the share of bookings made through messengers. We do not use vendor figures. Enter your own loss share into the calculator.
Как цифры связаны с вашей задачей
- ЦифраIncoming flow: 8,881 stationsЧто это значит для васYou did not answer in time, and the client drove to another shop.Что отвечает в аитоматонThe agent replies on WhatsApp and Telegram at once, including in the evening, and books a free slot.ЦенностьA ready schedule is waiting for you in the morning.
- ЦифраIncoming flow: Dec-FebЧто это значит для васThe tyre change deadline is external, and clients arrive in one window.Что отвечает в аитоматонPosts as rooms, time blocks, booking only on free slots.ЦенностьA queue becomes a schedule.
- ЦифраFollow-up: 41.5% are over 20 years oldЧто это значит для васOld cars need servicing and suspension work.Что отвечает в аитоматонSix months without a new request and a service reminder appears in the client history.ЦенностьA reminder in their dialog, not a broadcast.
- ЦифраFollow-up: RR 1.14Что это значит для васA reminder inside the booking helps people reach the appointment (medical data).Что отвечает в аитоматонA reminder a day before and two hours before, and a message an hour after a no-show.ЦенностьA forgotten booking can be moved.
- ЦифраRecord-keeping: 25% of small enterprisesЧто это значит для васClient history often lives in a logbook and a messenger.Что отвечает в аитоматонA request has a source, an owner, the chat history, a stage and the booking outcome.ЦенностьThe owner sees where requests get stuck.
Как проходит одно обращение
- ВходящееThey write while the advisor is under a car
WhatsApp, Telegram, a request from the website or maps. The agent asks for the make, model and service, and offers slots. The platform does not answer voice calls yet.
- УчётEvery touch in the card
Source, chat history, owner, pipeline stage (8 stages), booking state.
- Повторное касаниеA service touch in the client history
A confirmation, a gentle message after a no-show, a how-did-it-go after handover, and a service reminder after six months. Only to someone who has already booked.
- ИтогThe owner sees the outcome
The booking took place, was cancelled or was a no-show; the car was handed over or the job declined. The Pipeline and Bookings views show where requests get stuck.
At peak time the advisor is under a car, chats wait, and no client likes waiting on hold. They booked and did not come: the post stood idle, the technician had no work.
An instant reply in the messenger, a booking on a real slot that accounts for the post and the technician, and a reminder inside the booking.
What if the agent quotes a price or makes a diagnosis? It will not: the service advisor decides that. Start in shadow mode: the agent prepares replies and you review them.
A logbook, a notebook and the advisor's WhatsApp already work, while work orders and parts live in another program. Leave them there: Aitomaton is needed at the entry point.
How many bookings slip away while the advisor is under a car?
Open last week’s log and put in your own numbers. Take the shares of missed and booked requests from it: that is your data, not a market average.
Post utilisation and losses from missed bookings
Как считаем: utilisation = bookings per day × duration ÷ (posts × hours); losses = requests × share missed × share that would have booked × value × days. Допущение: missed requests do not come back, and there are free slots on the posts (if the posts are already fully loaded, losses by bookings cannot be counted). Это арифметика по вашим числам, а не обещание результата.
Are the posts packed to the brim? Then losses do not mean empty posts, but clients you did not manage to offer another time. Lower utilisation? There is capacity for new bookings.
How the agent books a client at 21:40
A client writes in the evening, when the advisor is busy or gone. The agent books a free slot, the enquiry moves through the pipeline to handover, and a person gives the diagnosis and price.
- Клиент · 21:40Good evening, can I come tomorrow for an oil change? A Camry, 2012
- ИИ-помощникHello! Tomorrow 10:00 and 14:30 are free. Which time suits you better?
- Клиент14:30. Also there is a knock at the front, how much will it cost?
- ИИ-помощникI have booked you for 14:30. I will note the knock as a symptom for the advisor: he will give the price and diagnosis after the inspection.
- A question about cost and the car condition -> passed to the service advisor with a summary
- СотрудникHello, this is the advisor. Tomorrow we will inspect the suspension before the oil change and agree the work with you.
- RequestThe Online advisor agent asks for the make, model, year, symptoms in the client's words and a time. It does not make a diagnosis.
- BookingThe platform works out slots from the schedule, and technician and post availability. The agent books or moves the visit.
- Before the visitA confirmation, and a reminder a day before and two hours before. No chat: the technician or administrator gets a request to call.
- Handover and afterAt the Ready for handover stage a message goes to the client; if a car sits ready for two days, the owner gets a task to get in touch. Three hours after handover they ask how it went and request a review.
The agent’s role is limited: it creates and moves bookings, sets tasks and moves the deal, but it does not cancel bookings and does not see amounts.
Seasonal peak: the norm sets the deadline, the snow sets the day
‘Booked my tyre fitting for 16:00. It is 19:14 now. My number is 72,’ a client wrote in Almaty in November 2025, when queues at tyre shops grew with the first snow. December was still far off.
The law sets only the deadline. Technical regulation TS 018/2011, which applies in Kazakhstan (text in Әділет), says in p. 5.5 of Annex 8: ‘In the winter period (December, January, February) the operation of vehicles of categories M1 and N1 not equipped with winter tyres is prohibited.’ Studded tyres are prohibited in summer, in June-August. Liability is set out in Article 590 of the Code of Administrative Offences of Kazakhstan (part 5). The norm gives the deadline, the weather chooses the day, and only your log from last autumn will show the size of the peak.
At peak time the agent answers and books while the advisor is under a car. Slots run out: the owner sets a block, and the agent stops offering a busy time.
What is already set up in the Autoservice preset
The preset gives a working scheme: all that is left is to fill in services, posts, the schedule and texts.
Repair and servicing
Eight stages: from a request to handover or decline.
Services and posts
Diagnostics, servicing, oil, tyre fitting, suspension. Duration and buffer are editable.
Fourteen scenarios
Tasks at stages, reminders, cancellations, no-shows, a review request.
Roles
Service advisor, mechanic, diagnostician, administrator.
Where requests come from
Call, website, WhatsApp, Telegram, advertising, maps, walk-in.
What the owner sees
Pipeline, tasks, deal amounts and bookings.
Tyre fitting: change the service durations and add posts. No waiting for parts: remove the ‘Waiting for parts’ stage.
Posts and bays in the schedule
A post is set up as a ‘room’ (resource) of the booking module. Link it to a service, and the platform will not put two cars on one post at the same time. It will not book a busy technician either.
Posts are not created in the preset: only you know the number and the names. There are time blocks (a break, lift repair) and schedules with date exceptions.
How is this different from YCLIENTS and auto-repair CRMs?
YCLIENTS, DIKIDI and Altegio keep a calendar well, but the advisor still works through a messenger request by hand. GIPIX, Upservice and STOCRM are strong on work orders and stock. Aitomaton sits at the entry point and at the return of the client.
| General-purpose booking app | Auto-repair CRM with work orders | Aitomaton | |
|---|---|---|---|
| Booking by a form on the site | Yes | Often yes | Not yet, planned |
| Booking in a WhatsApp dialog | Usually by hand | Depends on the integration | The agent books from the schedule |
| Work order, parts stock | No or partial | Core function | No |
| Request pipeline to handover | No | Order statuses | Yes, 8 stages |
| Service touches in the booking and client history | Visit reminders | Depends on the system | Yes, through a channel |
| Handoff to a person | Not applicable | Not applicable | Built into the agent |
Need work orders and stock first? Choose a niche system and add Aitomaton for chats and booking.
Launch in five steps
- Connect WhatsApp (through Meta Cloud API) and, if you want, Telegram. Without a channel, messages do not go out: the system sets tasks for staff.
- Apply the Autoservice preset and adjust the pipeline.
- Add services, technicians, posts and schedules.
- Turn the agent on in shadow mode: it prepares replies and you review them. Then move to working mode.
- A week later open Pipeline and Bookings and check where requests get stuck.
You can try it free for three days, and we can do the setup together with you if you wish.
Boundaries and security
The service advisor sees requests, bookings and chats. A mechanic sees tasks and bookings, but not deal amounts and not client email addresses. The owner sees everything.
The agent does not ask for passwords, SMS codes or card details. If a client is unhappy or asks for a person, the conversation goes to the service advisor with a summary.
More on the mechanics: online booking, one inbox for all channels, AI agent in chat, CRM with tasks. A similar path on the example of a car dealer is in the Avtodom case.