Triage a Pump Report During Flood Response

A pump loses prime in the middle of a flood response, and the person calling you is not thinking about your service agreement. They are thinking about rising water, a site that might flood within the hour, and a supervisor standing over their shoulder asking why the equipment stopped working. That pressure lands on you as the service manager, and it pushes you toward answers you are not positioned to give from a phone call. Here is how to handle that call, what to say, and how to rehearse it before the real one comes in.

Why this call goes wrong fast

The caller wants two things from you immediately, a way to get the pump running again and a promise about timing. Neither one is yours to give safely. You do not have eyes on the pump. You do not know if there is debris at the intake, whether the crew standing near it is actually clear of moving water, or whether the ground around the pad is stable enough for anyone to approach it. Water levels change by the minute during a flood response, and a phone call cannot substitute for a site assessment.

The bigger problem is who is actually in charge of that scene. During flood response, an incident commander directs field activity, not the rental company and not the service manager on the other end of the phone. If you start giving operating instructions, telling a crew to check an intake, clear debris, or restart a pump near rising water, you are making a safety call you have no basis to make. If someone gets hurt following your instructions, the responsibility does not stay with the caller. Service coordination has to sit downstream of incident command, not compete with it.

Prepare before the phone rings

You cannot build this response in the moment, so build it ahead of time. Know which accounts are flagged for emergency or flood response work and which service contacts you can reach after hours. Know roughly how long it actually takes a qualified technician to reach a flooded site from your yard, including road closures that are common during flood events, so you never guess at a timeline out loud.

Keep a short mental list of what you need to ask on every one of these calls. Ask about crew safety and water movement first. Ask who is coordinating the response on site. Ask where the equipment sits relative to the water. Ask what the caller can see, debris, water depth, ground conditions, without asking them to touch or test anything themselves. None of these questions require you to be a hydrologist or an incident commander. Your job is coordinating equipment and keeping your own crew and the customer's crew out of a decision that belongs to the people running the emergency.

What to say when the report comes in

Picture the call this way. Rina, an emergency works supervisor, gets you on the line and says, "The pump lost prime and the water is rising near the pad. Tell us how to get it running again right now. Can you promise us a replacement before dark?"

You do not answer the technical question first. You say, "Before we talk about the pump, I need to know your crew is safe. Are your people clear of moving water, and who is running incident command on site right now?"

Rina says there may be debris at the intake and that the incident commander is on site managing the response.

You say, "Thank you for that. I am logging the pump location now and requesting qualified service support. Our team will assess site access and conditions before anyone touches that equipment, and I will call you back with confirmed information as soon as I have it."

Notice what did not happen in that exchange. You did not offer a remote diagnosis. You did not promise a replacement time you cannot control. You asked about safety before you asked about equipment, and you closed with a concrete next step, a callback with confirmed information, instead of a vague reassurance. That order matters. Asking about the pump first tells the caller that equipment uptime outranks their safety. Asking about safety first tells them the opposite, and it is also the accurate priority.

Mistakes that make it worse

A few habits turn this call into a bigger problem than the flood itself.

1. Giving operating instructions over the phone. You cannot see the intake, the water, or the crew's footing, so telling someone to clear debris or reset a pump near moving water is a guess dressed up as guidance.
2. Promising a time you cannot guarantee. Before dark sounds reasonable until road closures or standing water block your technician's route, and now you have made a promise the weather gets to break.
3. Skipping the safety question to get to the technical one. It seems efficient, but it signals the wrong priority to a caller who is already under pressure.
4. Taking over decisions that belong to incident command. You are coordinating equipment, not directing the response, and blurring that line puts you in a position you are not trained or authorized to hold.
5. Ending the call without a clear next step. A caller who does not know when they will hear from you again will call back in ten minutes asking the same question, and rightly so.

Practice it before you need it

This is a hard call to get right the first time you face it for real, which is exactly why you should not face it for the first time for real. Run it as a roleplay before flood season, not during it. Have one person play the caller and insist the water is rising and a promise is owed. Have another play incident command so you practice routing the safety question to the right person instead of trying to answer it yourself.

Score your own recap at the end of the call. It should name the incident command contact, state the service request you logged, and confirm the next update, all without suggesting your company controls the flood outcome or the timeline. If your recap promises a fix time or takes credit for a safety decision, rework it.

DealSpeak's Equipment Rental practice conversations let you run this exact scenario against an AI counterpart that pushes back the way a stressed caller actually does, insisting on a quick fix and a hard deadline. If you want to see how this kind of triage looks in a different setting, the post on how to Coordinate an Air Compressor Request for a Food Plant Shutdown works through a similar pressure test with a production line on the line instead of a flood. The post on how to Escalate a Forklift Battery Heat Report at a Distribution Center covers a related judgment call, when to push a safety concern up the chain instead of resolving it yourself.

None of this makes the flood less urgent or the caller less anxious. It does keep the decisions in the right hands, safety with incident command and equipment with you, so nobody is guessing under pressure. Get the order right in practice, and it holds up when the water is actually rising.