3 moments that determine whether policyholders stay

Claims satisfaction is not climbing. J.D. Power’s 2025 U.S. Auto Claims Satisfaction Study found overall satisfaction was largely flat at 700 on a 1,000-point scale, up only three points year over year.

Claims is one of the few moments in the insurance journey when the customer experience becomes concrete. This is when trust is either reinforced or lost, and when a policyholder begins to decide how they will interpret everything that follows, including renewal.

A policyholder may not decide to leave in the middle of a claim. But the claim shapes how they interpret everything that follows. If the claims experience is confusing, repetitive or opaque, that memory stays with them. If it is clear and confidence-building, renewal becomes much easier to defend.

I’ve written about catching hidden gaps that cost you clients. Claims are where many of those gaps become expensive. The gaps show up in cycle time, repeat contacts and complaints. They also show up later, when a policyholder is considering whether it’s time to find a new carrier.

The issue is rarely a lack of data — most carriers already have plenty of signals. The harder problem is understanding which signals matter, where they occur in the journey, and what should be fixed first. That is where customer journey management starts to matter, because it gives you a way to convert signals into decisions. By that, I mean a way to connect signals to specific journey steps, assign ownership and prioritize changes against outcomes such as trust, cost and retention.

Journeys used to be maps. Then they became more of an organizing principle for teams. Now they are increasingly becoming more like a data model. Once signals, ownership, and outcomes are attached to journey steps, the journey starts generating decision data across the business. That matters in claims because it gives leaders a better way to decide what to fix and why.

In claims, three moments deserve particular attention.

Moment 1: Contact at first notice of loss

The first interaction sets the tone for the rest of the claim. At first notice of loss, the customer is not looking for a beautifully designed process. They are looking for clarity about what happens next.

This is where many journeys start to fray. Entry points are inconsistent. Options look alike. Customers are asked for details before the organization has established what stage they are in, what will happen next and who now owns the issue. Almost immediately, avoidable loops start to form, and doubt creeps in. Customers re-contact because they are still uncertain.

Many carriers treat this as an execution issue. I would argue it is usually a journey design issue. If the first step is unclear, the rest of the claim inherits that confusion. A journey-first approach treats FNOL as a managed step with a purpose, an owner and expectations that match the reality of how the claim will progress.

Moment 2: The mid-claim status gap

This is another moment many carriers underestimate. Once a claim is in motion, policyholders do not need a stream of updates for the sake of sending updates. What they need is enough context to understand what has changed, what is still pending, what depends on them and what is likely to happen next.

A generic update such as “we’re working on it” rarely reduces effort because it does not really answer any of those questions. In practice, it often has the opposite effect. People still do not know where they stand, so inquiry calls increase and trust starts to wear down because the claim begins to feel like a black box.

This is where journey management becomes useful in a very practical sense. If you treat status as a real step in the experience, instead of a message the system happens to send, you can connect inquiry volume, satisfaction and repeat contacts to the specific moments when expectations break down. That gives you a way to improve transparency without overpromising, because the goal is not more communication. The goal is better context.

Moment 3: The renewal conversation after a claim

By the time renewal arrives, the trust or damage created during claims is already in the system. The carrier sees a renewal event, but the customer remembers how the claim felt.

This is why renewal should not be treated as a standalone communication moment. It is the downstream consequence of everything that happened before. If the claim journey was clear, consistent and confidence-building, renewal has a stronger foundation. If it was confusing or repetitive, renewal starts at a disadvantage.

A journey-first approach helps you connect those dots. It becomes possible to identify which moments in claims create switching risk later, then prioritize changes that protect retention before renewal even starts.

What this looks like at the leadership level

At the leadership level, journey-first claims means one view that spans FNOL, status, closure and renewal. It means treating those moments as connected parts of the same trust journey, with clear ownership and a short set of outcomes that matter across functions.

This is a crucial operational shift. You stop treating claims as a set of transactions and start treating it as a context-rich journey that can support decisions. Signals from broker feedback, digital behavior and service interactions can now be attached to the same steps. Once signals, ownership and outcomes are attached to journey steps, the journey starts generating decision data across the business. This journey context layer is what artificial intelligence needs to reason over the experience in a useful way. It shows which signal belongs to which step, who owns that step, what else is connected to it and which business outcome should move.

The result is decision support, so leaders can act on the customer experience with more confidence. Which moment is generating repeat contacts? Where is trust weakening? Which change is most likely to improve both cost and retention? Those are business questions, and they need business-quality answers.

A practical operating cadence you can implement now

Start with one product line. Define the three moments in the claim journey that matter most. Then attach a few measures to them, such as repeat contacts, time to first status clarity, status-related inquiries and renewal behavior. From there, run one improvement cycle at a time. Change one thing, see what moved, keep what works and build from there.

This is about turning journey data into decision data, not just another reporting layer. You want to know what changed, why it changed, and what outcome resulted from it. That is what enables the business to make better decisions on top of the customer experience. And it’s why context is so essential for AI in this setting.

AI can help navigate complex experience data, identify patterns across journeys, and surface shifts after a policy, script or product change. But without journey context, those outputs are difficult to trust or act on. A spike in repeat contacts, a drop in satisfaction, or a rise in renewal risk only becomes useful when you know where it sits in the journey, who owns that step and which outcome it affects.

When signals are attached to specific journey steps, owners and outcomes, AI becomes a decision-support layer rather than a summary engine. It can help leaders see what changed, where trust is weakening, and which fix is most likely to improve both retention and cost. If the signals sit in separate places, you get observations. If they are connected in the journey, you get better decisions.

Claims is one of the clearest places where experience and economics come together. If you want to protect renewal, do not treat claims as a series of disconnected transactions. Treat it as the trust journey it is. Then improve the moments that matter most, one step at a time. This is the way.

© Entire contents copyright 2026 by InsuranceNewsNet.com Inc. All rights reserved. No part of this article may be reprinted without the expressed written consent from InsuranceNewsNet.com.

Jochem van der Veer is the co-founder and CEO of TheyDo. Contact him at [email protected].