Why Aftersales Is the Most Manual Department in Dealerships — and What It Costs You

The showroom gets the launch events, the billboards and the sales targets. Aftersales gets the work. In a dealer group, it drives most of the revenue, and it is also the most manual part of the business. Service advisers take bookings by phone, copy details from WhatsApp into the DMS, and check a parts catalogue in one window while a stock sheet sits open in another.

None of this looks broken from the outside. The workshop is busy and cars leave every day. But the department works because people compensate. Good advisers hold the gaps together with memory, personal phones and goodwill. That holds until volume rises, a key person goes on leave, or a customer asks where their car is and three people give three answers.

This article looks at why aftersales ends up so manual, what the fragmentation costs, and what a sensible fix looks like. It is not a fix that starts with ripping out the system you already paid for.

Aftersales carries the revenue and the mess

A vehicle sale is one transaction. The aftersales relationship that follows is hundreds of small ones: services, repairs, warranty work, accessories, bodywork, parts counter sales and recall campaigns. Each involves a booking, a job card, an inspection, an approval, a parts request, an invoice and a follow-up. Every hand-off between people or systems is a place where information can be typed twice, typed wrongly or not typed at all.

Multi-location groups multiply this. A group with workshops in three countries rarely has three identical operations. Each site develops its own habits, its own spreadsheets and its own WhatsApp groups. Head office sees the output and has little visibility of how it was produced, which makes it hard to run revenue operations (RevOps) across the whole group with any confidence.

The stack you probably already run

Most dealers have some version of the following, and each piece does its own job reasonably well.

• The DMS (CDK, Autoline, Kerridge, Pinewood or similar). This is the system of record for customers, vehicles, job cards, parts stock, invoicing and warranty claims. It is strong at record-keeping and weak at conversation. How easily it connects to anything else depends heavily on the version, the hosting and how much it has been customised over the years.
• Workshop scheduling. Bay and technician capacity often lives in a separate scheduling tool, a shared spreadsheet or a whiteboard. If it is not tied to the DMS job card, promised delivery times drift away from what is happening on the floor.
• WhatsApp Business. This is where many customers actually are. They send messages in more than one language, along with voice notes, photos of warning lights and location pins. In many workshops it runs on advisers' own phones or a shared number, connected to nothing.
• Parts catalogues. Manufacturer catalogues give part numbers, supersessions and fitment by VIN. They sit apart from the DMS, which holds the stock and pricing. So someone looks up the part in one system and types the number into another.

Each tool is fine alone. The trouble is at the seams, where a person acts as the integration.

A Tuesday morning at a multi-location workshop

Consider a dealer group with three sites. This is a hypothetical, but most aftersales managers will recognise it.

At 7:40 a customer sends a voice note, in his first language rather than the one the team mainly works in, about a grinding noise when braking. He can come after work. The adviser listens, writes the booking into the scheduling sheet, and later creates the customer in the DMS. He finds an existing record under a slightly different spelling of the name, one entered in a local script and one in Latin letters. Now there are two histories for one customer, and neither is complete.

The technician inspects the car and recommends pads and discs. The adviser looks up the part numbers in the catalogue, types them into the DMS, and sees that the site has one set of discs. Another site might have more, so he calls. Nobody answers, so he sends a WhatsApp message to a parts person and moves on to the next customer.

He then sends the customer photos of the worn discs on WhatsApp. The customer replies "ok go ahead" somewhere in a thread of forty messages. That approval lives on the adviser's phone, not on the job card.

Two days later the invoice is queried. The customer says he approved the pads only. The adviser is off today, and the manager scrolls through a phone that isn't his. The conversation is in two languages and half of it is voice notes. The site discounts the invoice to keep the relationship.

No one in this story was careless. The system simply made every step depend on a person remembering to carry information across.

Peak seasons and compliance

Manual processes scale with headcount, and peaks do not. In peak seasons, working patterns shift and demand arrives in bursts. Before summer, air-conditioning and tyre checks surge. Before winter, it is batteries and brakes. Public holidays and school breaks bring cars in for checks before long drives. Staff are covering reduced or unusual hours while the inbox grows.

In those weeks, the adviser who normally keeps everything in his head drops things. Messages go unanswered for hours, bookings double up, and approvals get lost.

Compliance adds pressure. VAT rules and regional e-invoicing mandates, such as Peppol-based schemes, reward clean invoice data at the source. If labour lines, parts and customer details are re-keyed between job card and invoice, errors reach the invoice. Fixing them means credit notes, reissued documents and finance time spent on corrections. An invoice that is right the first time is cheaper than one that has to be corrected.

Data protection laws such as GDPR raise a related question. Customer names, photos and conversations sitting on advisers' personal phones are difficult to track, retain properly or delete on request. A group operating in several countries has to answer to more than one set of rules, and scattered chat histories make that harder.

What fragmentation actually costs

The costs are rarely a single dramatic failure. They are small, repeated and easy to normalise.

• Delays. Customers wait for quotes, approvals and parts answers because information has to travel by phone call or message between people.
• Exhausted teams. Advisers spend a large part of the day on copying, chasing and searching, then stay late to catch up. Good advisers burn out and leave, and they take their undocumented knowledge with them.
• Mistakes. Duplicate customer records, wrong part numbers, misread messages and mismatched job cards all come from re-keying.
• Frustrated customers. They repeat themselves, get inconsistent updates and cannot see where their car is. When customers expect to reach you by messaging app, a slow reply is noticed immediately.
• Leaked money. Work done but not invoiced, parts issued but not charged, approvals that cannot be proven, warranty claims missing documentation, service reminders never sent, and discounts given to settle disputes. Each leak is small, but they recur every day across every site.

Why another system is not the answer

The instinctive response is to replace the DMS or buy a new tool. Replacement is expensive, disruptive and slow, and it still leaves the seams. The new system will have to talk to the scheduler, WhatsApp and the catalogue too. Adding a standalone tool, such as a new booking app or a chatbot, can simply create another silo that someone has to reconcile by hand.

The real gap is the operating layer between systems: the rules and connections that decide how a WhatsApp message becomes a booking, how a booking becomes a job card, and how a job card becomes a correct invoice. Most dealers have never designed that layer. It has grown by habit, and it is carried by people.

Once that layer exists, leadership gets something it rarely has today: a single command-center view of the department. Open jobs, pending approvals, response times and parts availability can be read across every location from one place, instead of being assembled from calls and spreadsheets at month end. That view is a result of connecting the work properly, not a dashboard bolted on top of the mess.

How The Ninjaz Group approaches it

The Ninjaz Group is a managed-services partner. We design the change, wire your existing systems into one operating backbone, and stay on to run it. We sell the outcome, not software. For aftersales, that work runs in three phases, and you can stop after any one.

Blueprint. We map the operation end to end, from first WhatsApp message to final invoice and follow-up, treating service, parts and customer follow-up as one revenue flow. The aim is to find every gap where work is done twice, data goes stale or money leaks. You keep the map either way, so even if you never go further, you have an honest picture of where the department loses time and revenue.

Build & Link. We build what is missing and connect what you already have. There is no rip-and-replace, and software you have already paid for stays. This is where the DMS, scheduling, WhatsApp and parts data are made to behave like one system. This is the work of our Managed Link layer, which Ninjaz builds, owns and maintains.

Operate. After go-live, we provide support, monitoring and continuous improvement. Think of it as your operations and IT team without the headcount. Integrations need looking after as systems update and locations change, and this phase covers that, including keeping the central operating view accurate as the group grows.

These phases map to three service layers: Managed Transformation Services for the strategy, design and development of the change, Managed Link for the connecting layer, and Managed Business Operations for day-to-day IT support and running. You can take any one of them.

On delivery, strategy and account leadership are aligned to your region and working hours. Engineering, AI development and support come from a dedicated delivery operation in India, working across your business hours.

We should be clear about limits. How much can be connected depends on your DMS version, hosting and contracts, and the Blueprint phase exists to find that out before anything is built.

Where to start

You do not need a transformation programme to begin. You need to see where the work is actually duplicated. A useful first exercise is to follow one job from the customer's first WhatsApp message to the paid invoice, counting every time someone re-types, re-checks or chases. Do it at your busiest location, and again at your quietest. The difference will tell you a lot.

If that exercise turns up more than you expected, we can help map it properly and decide what is worth fixing first. To talk through your aftersales operation, book a consultation.