“So I’ve Been Paying You For Nine Years For Nothing”

The call he's been waiting three weeks for

Water came through the kitchen ceiling in August. The floor is ruined, the repair quote is substantial, and he has been paying this policy since 2017 without claiming once.

The assessment has come back. The cause falls outside what the policy responds to, the decision is correct, and it has been reviewed properly.

The adjuster now has to tell him — and in most operations she will do it after he has already received a letter that used the phrase "we are unable to indemnify" in the second paragraph.

By the time they speak, he is not really arguing about the cause of the water. He is arguing about nine years of premiums, about a document he was never going to read, and about the sense that something has been done to him.

The decision is usually right and the complaint is usually real

This is the central fact of claims handling and it's rarely stated plainly. Most denial complaints do not turn on whether the coverage decision was correct. They turn on the customer never having understood why, and on having found out in writing from an organisation that then explained it in policy language.

Four features define a claim denial conversation.

A loss has already happened. Unlike a declined application, there is real damage and a real bill. The customer isn't disappointed; he's out of pocket, which is a different emotional register entirely.

His belief was often reasonable. He thought he was covered. He may have had good grounds for thinking so. Any delivery that implies he should have known better is both unkind and, frequently, wrong.

The explanation is technical and the audience is not. The reason lives in a clause, and reciting the clause is not explaining. Most of the skill is translation.

And the relationship is normally over. Whatever else happens, he is unlikely to renew if this is handled badly — and the cost of that lands in a different report from the one recording a correctly declined claim.

Phone first, always

Before the letter. If the letter has already gone, acknowledge it immediately: "I know you've had our letter and I'd rather you heard it from a person as well — it isn't a document that explains itself."

The written notification exists for good reasons and it is a poor way to learn something like this. Where the sequence can be changed, changing it is the single highest-yield improvement available in claims communication.

Say the decision, then stop talking

"I'm sorry — we're not able to cover this one. Let me explain exactly why, and then I want to talk about what else we can do."

Then pause. He may need a moment, or he may need to be angry for thirty seconds, and both are reasonable. Filling that gap with the clause is the most common error in the call.

Explain in plain words, not in policy language

Translate, don't recite. "The policy covers damage from something sudden — a pipe bursting. What happened here was a seal that had been failing over a long period, and that's in the section about gradual deterioration. I know that distinction probably sounds like hair-splitting from where you're sitting."

Acknowledge the distinction is fine. Where the difference between covered and not covered is genuinely subtle, saying so is honest, disarming and costs nothing. Pretending it's obvious invites the response that it clearly wasn't.

And concede confusing wording where it is confusing. "Honestly, that section isn't well written and you're not the first person to read it the way you did." Adjusters avoid this because it feels like admitting fault. It isn't — the decision stands either way — and it is the fastest way to stop a conversation becoming a complaint.

Never imply he should have known

"It's in your policy documents" is true, unhelpful, and heard as an accusation of carelessness. Nobody reads the documents. Everybody knows nobody reads the documents. The sentence adds nothing except an insult.

Then say what you can do

Anything covered? Partial cover, a related element, an excess consideration, an interim payment on a separate head. Say it clearly, because it's the only constructive thing available.

And if the answer is nothing, say that plainly rather than implying otherwise out of discomfort.

Give the appeal route before he asks

Unprompted, clearly, and without defensiveness: how to have the decision reviewed, what the internal complaints process is, and where it goes after that — in whatever form the firm and the jurisdiction require.

Volunteering this is counterintuitive to adjusters, who assume it invites escalation. In practice it does the opposite more often than not: a customer who is given a route feels dealt with rather than dismissed, and a great many never use it.

But don't soften into implying it'll succeed. Over-apologising creates the belief that the decision is soft, and the second refusal is then much worse than the first.

Four ways it goes wrong

The clause-reciter, who reads the policy wording aloud as though repetition were explanation.

The letter-firster, who lets the notification arrive first and inherits a conversation that started badly without him.

The blame-implier, whose "it's in the documents" tells a customer who has just lost a kitchen floor that this is his own fault.

The false-softener, so apologetic that the customer reasonably concludes an appeal will overturn it.

Why this isn't trained

Adjusters are trained on coverage, not on delivery. Technical assessment is rigorous and well-supported. The four minutes explaining it to a person is treated as a soft edge around a hard skill.

Quality assurance checks the decision. File reviews test whether the outcome was right. They rarely test whether it was understood, which is what the complaint will be about.

Complaint data doesn't reach the conversation. Complaints are analysed for decision accuracy and process breaches, not for the recurring sentence "nobody explained it to me."

And peer role play produces acceptance. A colleague hears the reason and takes it reasonably. A real claimant interrupts, repeats the nine years of premiums, and becomes angriest at the point the explanation begins — which is precisely the moment the skill is required.

What coverage decision training can rehearse

A simulation can hold a claimant who is upset, keeps returning to what he's paid over the years, and reacts to any hint of blame — so adjusters practise translating a technical reason under emotional pressure. Foretell AI supplies the counterparty configuration, transcripts and rubric-based scoring; the policy wordings, coverage determinations, complaint routes and all regulatory requirements stay with the insurer.

Four to build:

Design caution. Coverage decisions, policy wordings, complaint and appeal routes and disclosure requirements vary by insurer, product and jurisdiction; nothing here states any requirement or constitutes coverage advice. Modules must use the insurer's own wordings and approved complaint information, and the exercise rehearses conversation quality only.

Designing the module

Pass one — the delivery. Score whether the outcome was stated before any explanation, and whether the adjuster paused afterwards.

Pass two — the translation. Score whether the reason was given in plain language or in policy wording, and whether any implication of fault was made.

Pass three — the routes. Score whether the appeal process was offered unprompted and whether anything implied the decision might change.

Rubric on observable behavior: Was the call made before or after written notification? Seconds to the decision being stated. Was policy language quoted or translated? Was "it's in your documents" or similar used? Was confusing wording conceded where applicable? Was the appeal route volunteered? Was anything covered identified?

Quoted-versus-translated is the measure. It's assessable in one pass of a transcript, it's the whole difference between being informed and being processed, and no claims quality framework currently scores it.

The operator case

Read your denial complaints for the sentence "nobody explained it." Most insurers analyse complaints for decision accuracy and find the decisions were right. The recurring content of the complaint is about comprehension, and that is a different, cheaper problem to fix.

Sequence is a policy choice with a measurable cost. Where written notification routinely precedes contact, the conversation starts from a position that was avoidable. Compare complaint rates by which came first.

Front-line confusion reports should reach product. Adjusters know precisely which clauses customers consistently misread. There is usually no route for that to reach the people who write the wordings, which is a feedback gap rather than a training one.

And proactive appeal disclosure tends to reduce escalation rather than increase it. It is worth testing directly, because the intuition in most claims operations runs the other way and is costing them.

For insurance and customer experience programmes, this is a clean demonstration that a correct decision and a well-handled one are separate outputs, measured by separate functions, and only one of them is currently anyone's job.

Frequently asked questions

How should you tell a customer their insurance claim is denied? By phone before any letter where possible, stating the outcome first, pausing, then translating the reason into plain language rather than quoting policy wording.

Why do denied claims generate complaints even when the decision is right? Because the customer never understood why, or learned it from a letter written in technical language. Most denial complaints are about comprehension and delivery rather than about coverage.

Should you admit that policy wording is confusing? Where it genuinely is, yes. The decision stands regardless, and conceding that a distinction is subtle is the fastest way to stop a conversation turning into a complaint.

Should adjusters volunteer the appeals process? Yes, unprompted. Claims teams often assume it invites escalation; in practice customers who are given a route more often feel properly dealt with, and many never use it.

The short version

The decision was right and his complaint will be real, because nobody translated it and he found out in a letter.

Ring before the letter. Say it, then stop talking. Explain the actual reason in words a person uses, concede if the wording is genuinely unclear, and never tell him it was in the documents he was never going to read.

Then give him the appeal route without being asked — and don't be so sorry about it that he thinks the answer is going to change.

Foretell AI lets insurers build conversational simulations — including coverage refusals, emotional claimants and plain-language explanation like the one above — with configurable counterparties, transcripts, recordings, and rubric-based evaluation. If your denial complaints keep saying nobody explained it, we're happy to walk through how other insurers have structured it.