Taking a First Water Damage Call

A condo owner calls with water spreading near a shared wall, a neighbor's renovation happening one floor up, and no idea whether the building, the contractor, or their own policy will end up paying for it. As a personal lines advisor, you are the first human voice this person reaches, and the next five minutes decide whether the call ends in relief or in a complaint file. Handle the sequence well and the owner hangs up with a clear next step. Handle it poorly and you either promise something the claims team cannot deliver or leave someone standing in a wet hallway feeling ignored.

Why this call goes wrong fast

The owner is not calling for a policy lesson. They are calling because water is moving toward drywall and they want someone to tell them what to do right now. That pressure pulls advisors in two bad directions. Some rush to comfort the caller by guessing at cause or coverage, saying things like "that should be covered" before anyone has looked at the loss. Others swing the other way and recite process so fast and so flatly that the owner feels brushed off during a genuinely stressful moment.

The real problem is role confusion. A personal lines advisor is not the person who determines whether a neighbor's renovation caused the leak, and is not the person who approves or denies a claim. But the owner does not know your job boundaries, and it is not their job to know them. Your task is to give calm, accurate direction while staying inside your lane, and to do it without sounding like you are reading a script.

How to prepare before you pick up the phone

Before you ever take a call like this, know three things cold. Know your company's emergency mitigation guidance, the instructions customers get about protecting a property from further damage, so you can point to it instead of inventing advice on the spot. Know the exact reporting path for a new claim, including whether you can open it yourself or whether you hand off to a claims intake team. Know what information the claims team actually needs from you, typically the date the damage was noticed, whether the owner has photos, whether the property manager has been contacted, and how the owner prefers to be reached for updates.

Also decide in advance what you will never say. Never state what caused the damage. Never tell someone to wait on repairs until a claim is approved. Never predict how a claim will affect a future rate. These lines feel obvious when you read them here, calmly, at a desk. They are much easier to cross when a real person is upset on the phone and wants an answer now.

What to say when the owner is upset and unsure

The owner opens with the kind of statement that puts pressure on you to solve everything at once. "There's water coming through near the wall in my unit, and I think it's from the renovation happening upstairs. I don't know if I should call someone myself or if this is going to be a nightmare to get covered."

You start with acknowledgment, not process. "That sounds stressful, and I want to make sure you're safe and that we get this moving in the right direction. First, have you contacted your property manager about the water, and is there any immediate safety concern, like water near outlets or a ceiling that looks like it could give way?"

The owner answers that they called the property manager, no one has come yet, and the water is not near anything electrical, just spreading along the baseboard. You keep going. "Good, please continue to follow your building's emergency guidance and stay in touch with the property manager for the immediate cleanup. On our side, I can get you into the claims reporting process right now, and I want to note that you already have photos from today. Our claims team will review the details of what happened and how coverage applies. Do you have a preferred number or email for updates from them?"

Notice what does not happen in that exchange. You never state that the renovation caused the leak. You never say whether the policy will pay. You do not tell the owner to hold off on any repair. You do direct the safety issue to the right place, gather the two or three facts claims will need, and confirm how the owner wants to be reached. That is the whole job on this call.

Mistakes that turn a manageable call into a bigger problem

Guessing at cause is the most common mistake, and it comes from good intentions. Saying "sounds like the neighbor's contractor did this" feels helpful in the moment, but it sets an expectation the claims team may not confirm, and now you are the person who has to walk it back later.

Telling someone to delay repairs is close behind. Owners sometimes ask directly, "should I just wait until the claim is approved before I fix anything." The honest answer is that you cannot advise on that, and the safe answer is to point them back to their building's emergency guidance and their own judgment about preventing further damage, not to a timeline tied to claims approval.

Skipping the factual capture is a quieter mistake, but it costs the owner time later. If you do not confirm that photos exist, when they were taken, and how the owner wants to be contacted, the claims team starts from zero and the owner has to repeat their story to another stranger. A rushed call that skips this step feels efficient to you and feels like a runaround to them.

Overpromising on timing is the last common trap. Avoid saying claims will call "today" or "within the hour" unless that is a guarantee your company actually makes. Give the real reporting path and let the claims team set expectations on timing themselves.

How to practice and score this conversation

This call is hard to get right on instinct because the two failure modes, oversharing on cause and coverage, or sounding cold and procedural, both come from reasonable impulses. That makes it a good one to rehearse before it happens with a real customer. DealSpeak lets you run this exact scenario, a condo owner with photos, a neighbor's renovation in progress, and water spreading near a wall, against an AI counterpart that reacts the way a real caller would.

When you or a manager score a practice run, listen first for whether empathy comes before process language, since an advisor who jumps straight to "please contact your property manager" without acknowledging the stress sounds robotic even when the information is correct. Then check for three specific things. Did the advisor avoid naming a cause for the damage. Did the advisor avoid suggesting the owner wait on repairs. Did the advisor capture the photo date and a contact preference before ending the call. A strong run hits all three while still sounding like a person talking to another person, not someone reading a policy manual out loud.

Insurance practice conversations at Insurance practice conversations cover other calls where the same discipline matters, including Addressing Privacy Concerns About a Wellbeing Programwhere the challenge is staying inside your role while a client pushes for more than you can promise. If your team also handles commercial requests, Coordinating an Evidence of Insurance Request shows the same pattern applied to a different kind of pressure.

A water damage call is really a test of restraint dressed up as a test of empathy. Say the calm, accurate thing, hand off the parts that are not yours to decide, and the owner leaves the call feeling handled instead of processed. That balance is learnable, and it gets easier every time you run it before the real version shows up on your line.