Customer Satisfaction Scores Fall Through the Cracks Between Departments

Most dealerships can tell you their customer satisfaction score. Far fewer can tell you why it moved last month. The number arrives from a survey tool and is presented in a monthly meeting. Then three department heads discuss it, each quietly convinced the problem sits in someone else's area.

That is rarely a failure of effort. Sales owns the customer until the vehicle is handed over. Service owns the customer for every workshop visit that follows. The call centre owns the calls and WhatsApp messages in between. Each team works hard on its own piece, in its own system, against its own targets. The customer experiences one company and judges it as one.

This article looks at where satisfaction leaks between departments, using the systems most dealer groups already run: the CRM, the DMS, the call-centre platform and the survey tool. It then explains what it takes to fix the seams instead of polishing the scores. It is as much a revenue operations question as a service one, because repeat service visits and the next vehicle sale both depend on handoffs between teams.

One customer, three owners

Consider a typical dealer group with showrooms and workshops in three countries. Sales is measured on units delivered and finance approvals. Service is measured on workshop utilisation, hours sold and repeat visits. The call centre is measured on answered calls, handling time and appointments booked. These are sensible targets, and each team can hit its own while the customer has a poor experience overall.

Nobody is measured on the questions the customer is actually asking:

• Do they know who I am?
• Did they do what they said they would?
• Do I have to explain this again?

Those questions cross departmental lines, so they sit in no one's job description. The satisfaction score is the only metric that does cross them, and it arrives late, as a single number, with no owner and no trail back to the cause. Leadership sees the number on a report, but there is no central operating view that shows what sits behind it.

The systems behind each piece

Each department's slice of the customer lives in a different platform.

• The CRM holds the sales side: enquiries, test drives, quotes, follow-up tasks and the promises made to close the deal. Whether it is Salesforce, Dynamics, Zoho or something a manufacturer requires, it usually stops mattering to the business the day the car is delivered.
• The DMS is the system of record for vehicles, VINs, job cards, parts, warranty and invoicing. Aftersales runs on it, and it knows what was done to the car but little about what was said to the customer.
• The call-centre platform holds telephony, queues, call recordings and, increasingly, a WhatsApp Business inbox. It knows what the customer asked for, often in more than one language across a single conversation, but it may have no live view of the workshop.
• The survey tool sends post-sale and post-service questionnaires by SMS, email or WhatsApp and produces the dashboard everyone reviews. It knows how the customer felt, but only about whatever contact record it was fed.

Each of these tools works. The trouble is that each identifies the customer differently: the CRM by lead, the DMS by customer code and VIN, the call-centre platform by caller ID, and the survey tool by whichever list was exported. Unless something deliberately joins them, a person who bought a car, booked a service and complained by phone is three or four different records in four different places.

A busy Tuesday: one customer, five systems

Here is a hypothetical, but a familiar one. A customer bought an SUV six months ago. During a peak season, with workshop slots in short supply and demand high, he sends a WhatsApp message about a brake noise.

The call-centre agent picks it up and finds a slot for Thursday afternoon. The platform shows the booking, but the DMS has no appointment because the two are not connected. The agent plans to pass it to the branch by email, and the day's volume gets in the way.

On Thursday the customer arrives and the service advisor cannot find a booking. The advisor creates a new customer record and spells the name the way it sounds. The DMS already holds him under a slightly different spelling from the sales handover, so there are now two records. The advisor does not know that the salesperson promised a complimentary first inspection, because that promise sits in a CRM note.

The car is ready late, as the workshop is stretched by the end-of-day rush. The customer waits, and the invoice is paid at the cashier on the spot, without the promised inspection applied.

Three days later the survey tool sends a questionnaire in the default language to the number held in the CRM. It is an old number, and the customer never sees it. A separate survey, triggered by the new DMS record, goes to his current number. He answers it with a low score and a comment about waiting.

The dashboard attributes the result to the service branch's wait time. The real causes were a booking that never reached the DMS, a duplicated record, an invisible sales promise and a survey that went to the wrong place. No one department caused the score, and no one department would find the cause by looking at its own system.

Where the score actually leaks

When departments are stitched together by memory, email and spreadsheets, the cost shows up in five ways.

• Delays. Appointments, approvals and callbacks wait on someone re-keying information from one screen to another. A customer who messages on WhatsApp expects an answer in minutes, not after a hand-off.
• Exhausted teams. Advisors and agents spend part of every day on reconciliation: searching for the booking, correcting the record, chasing the other branch for history. In a multi-location group that burden grows with every site, and it peaks during holiday periods and seasonal service rushes.
• Mistakes. Duplicate customers, stale phone numbers, wrong language preferences and missed promises are all the result of data entered twice and updated once.
• Frustrated customers. Being asked to repeat yourself is the clearest sign to a customer that a company is not one company. Multilingual customers who receive follow-ups in the wrong language feel it more.
• Leaking money. Goodwill discounts are given to calm a situation that should not have happened. Repeat work follows incomplete handovers. Customers quietly stop returning for service and move to an independent workshop, and nobody sees the loss because no record connects the missed follow-up to the lost visit. For anyone responsible for revenue across the customer lifecycle, this is the hardest leak to see.

Finance adds its own version. Consider a fleet customer whose invoice must carry correct buyer and tax details. If the DMS and the finance system disagree, in a market where regional e-invoicing mandates such as Peppol-based schemes apply, or simply under standard VAT rules, the invoice has to be corrected and reissued. Someone from accounts then calls the customer to explain. A billing error that should have been prevented becomes an experience problem that appears in the next survey.

Why a better survey tool will not fix it

The usual response to a weak score is to improve the measurement: shorter surveys, a better dashboard, alerts for detractors. These help, but they only report on the gap and do nothing to close it.

Consider what happens when a detractor alert reaches a branch manager. To resolve the case properly, the manager needs three things: what the workshop did, which sits in the DMS; what sales promised, which sits in the CRM; and what the customer said on the phone, which sits in the call-centre platform. The alert contains none of this. So someone opens three systems, pieces the story together, calls the customer and records the outcome in a spreadsheet, if at all.

The same disconnection produces survey fatigue. A customer who buys a car and books a service in the same month may receive several surveys from different triggers. Nothing checks whether an open complaint exists before the questionnaire goes out. Where data protection laws such as GDPR govern how contact details and consent are used, sending messages to the wrong or outdated record is a compliance concern as well as an annoyance. The score then reflects the plumbing as much as the service.

The score can only improve reliably when the systems behind it share one picture of the customer.

How The Ninjaz Group approaches it

The Ninjaz Group is a managed-services partner that designs the change, wires a client's existing systems into one operating backbone, and stays on to run it. For a problem like this one, the work follows three phases, and a client can stop after any of them.

Blueprint

We start by mapping the operation end to end, following a customer through the journey: enquiry, delivery, first service, a phone call, a complaint, a survey. The aim is to find every gap where work is done twice, data goes stale or money leaks. That includes the places where a booking, a promise or a customer record falls between systems. The client keeps the map either way, and for some groups the map alone is enough to settle the ownership questions that stall improvement.

Build & Link

Next we build what is missing and connect what already exists. There is no rip-and-replace, and software you have already paid for stays. This is where Managed Link comes in: the operating layer between systems, built, owned and maintained by Ninjaz so that the DMS, CRM, finance, service, website and messaging behave like one system. In the scenario above, that could mean:

• a booking taken on WhatsApp or by phone that lands in the DMS as an appointment;
• one customer identity across systems, so a name spelled two ways does not create two people;
• sales promises that are visible to the service advisor at check-in;
• surveys triggered by real events in the DMS, sent in the customer's language to the current number, and held back when a complaint is open;
• a low score that opens a task carrying the job card, the sales notes and the call history together;
• a central command-center view for leadership, showing open complaints, missed bookings and unfulfilled promises across every location.

Operate

Integrations drift as systems update, staff change and branches open. In the Operate phase, through Managed Business Operations, we provide support, monitoring and continuous improvement, so you have an operations and IT team without the headcount. Account leadership stays close to your team, while engineering, AI development and support run from a dedicated delivery operation in India that works across your business hours.

None of this makes a weak workshop strong, and it does not remove the management decision about who owns the customer experience. What it does is give that owner one view of the customer, so problems can be seen, routed and fixed at their source.

Start with the map

If your satisfaction score is moving and nobody can say why, the cause is probably in the seams between your systems rather than in any one department. The quickest way to find out is to trace one real customer journey from first enquiry to last survey and note every point where someone re-types, searches or guesses.

That is the first step of a Blueprint, and it does not commit you to building anything. If you would like to see what that looks like for your group, book a consultation and we will start with the customer's journey.