Your Call Centre Knows Who's About to Leave. Nobody's Listening.

A fleet manager calls on a Tuesday afternoon. He wants to know why three of his vehicles came back with different fuel grades than requested. It's the second time this month. Your agent apologises, logs it as a fuel-type complaint, hits the average handle time, and closes the ticket. The manager thanks them. He sounds fine. Six weeks later, his company renews with a competitor. Nobody saw it coming.

Here is what actually happened: the manager did not call because he was angry. He called because he still believed you could fix it. When nothing changed, he stopped believing. He never complained again — because the complaint was the last good-faith gesture he had, and it went nowhere. A dissatisfied customer who calls is giving you a gift. Most won't. Kolsky's ThinkJar research found only 1 in 26 unhappy customers actually complains. The other 25 leave without a word.

The call is already the answer — if anyone asks what it means

Every contact your support team takes is a data point about something that went wrong upstream. A wrong fuel grade is not a support problem. It is a handoff problem between reservations and operations. But because the call is filed under 'fuel complaint' and the ticket is closed, reservations never finds out. Operations never finds out. It happens again. And the next call is shorter, because the manager has already decided.

This is the pattern in car rental and fleet: the customers who leave without warning almost always signalled first. They called about a charge they didn't understand. They asked why the vehicle class they booked wasn't available at collection. They queried a late return fee they thought was waived. Small things. Nothing worth making a scene over. So they didn't make a scene. They paid and booked elsewhere.

Your KPIs are green while the account is already gone

The silence doesn't trigger anything. No spike in support tickets. No angry email chain. As Armatis documented in March 2026, this is what makes the pattern so costly: the customer is still technically active, still opening your renewal emails, while having already decided to leave. Your dashboards show nothing unusual. Your NPS score from last quarter's survey looks stable. The account just quietly doesn't renew.

The same research found that 85% of customers who left a provider said they would have stayed if their problem had been addressed. That's not a satisfaction problem. That's an information problem. The information existed — it was in the call record — and no one with the authority to fix the underlying issue ever read it.

A complaint that gets logged but never routed is just a farewell letter filed in the wrong drawer.

The fix is routing, not resolution speed

The answer is not faster calls. Pushing agents to close tickets quickly breeds exactly the repeat contacts that cost more than the seconds saved — and it misses the point entirely. The contact is not the cost. The unread intelligence inside the contact is.

• Pull your top five contact reasons from the last 30 days. Not categories — actual reasons, in the customer's words. Fuel discrepancy. Unexpected damage charge. Wrong vehicle class at pickup. Be specific.
• Assign a non-support owner to each reason. Reservations owns the vehicle class problem. Ops owns the fuel problem. Finance owns the charge dispute. Support can resolve the call; only the owner can stop the next one.
• Set a standing 15-minute slot in your ops or commercial review to walk through the week's top three contact reasons. Not to report them — to ask: why did this happen, and what would stop it happening next week?
• Track whether repeat contacts on the same reason go up or down. That movement, not your handle time, tells you if the fix is working.

Ask your team this week

• Who outside of support sees our top contact reasons each week — and do they have accountability for reducing them?
• For our accounts that didn't renew last quarter: did any of them contact support in the 60 days before they left? What did they call about?
• If a fleet account calls twice about the same issue in one rental period, what happens — and who finds out?