Taking the backup call without making it worse

You didn't get a class on this part of the job. Somewhere between learning the plant and getting handed a title, you also became the person a resident calls when their basement floods with sewage, when the water runs brown, or when they just want to yell at someone about a bill. None of that was in the job posting.

Rung 1 again, still newly promoted. It has nothing to do with pipes or valves. It's about the ninety seconds after you pick up the phone or open the door, and whether that conversation calms someone down or makes the rest of the day worse for both of you.

None of this is guesswork. Operators who've fielded these calls for years land on the same handful of moves, whether they learned it from a mentor or the hard way. This guide is that consensus, written down.

Answer the phone like it's a neighbor calling

Treat every call as if the person on the other end lives three streets over, because on a small system, they usually do. Customers only care about four things: that the water is safe, that it comes out of the tap, that the bill is accurate, and that someone helps when something goes wrong. Anchor the call to one of those four and most of the anger has somewhere to go.

Say a resident calls because sewage backed up into a basement. The instinct is to defend the system, or to explain the piping. Resist it. Start with what the person in front of you actually needs to hear: that you understand this is bad, that someone is coming, and when. The technical explanation can wait for the person who inspects the line.

Own what's yours, and say what happens next

A good phone call has the same four parts as a good public notice: acknowledge what happened, say what you're doing about it right now, tell the caller what to do, and give them a real time you'll follow up. Skip any one of the four and the caller fills the gap with their own story, and it's rarely a kind one.

You don't need to apologize for things that weren't your mistake. Acknowledging the problem and naming the plan is usually enough. A main break isn't the utility's fault. How the phone call about it goes is entirely on you.

The step operators skip most is the follow-up. If you tell someone you'll call back by four o'clock, call back by four o'clock, even if all you have to say is that the crew is still on it and the next update is at six. The research backs this up: informed customers are far more satisfied than uninformed customers looking at the identical water and the identical problem. One study found 80 percent of informed customers satisfied against 29 percent of uninformed customers in the same city. Missing a promised update costs you more trust than the original problem did.

Never guess at what caused it

Vague and technical answers make people more anxious, not less, and so does guessing. If you don't know why the water backed up or why it turned brown, say what you do know and what you're doing to find out, and stop there.

Take a discolored-water call as the model case. A resident sees brown water and assumes the worst. You don't diagnose it on the phone. You tell them it's most likely tied to routine flushing or nearby main work, when that's true, that the water remains safe, and that running the cold tap for a few minutes should clear it. If someone is already claiming online that the utility is hiding a problem, you don't argue that point on the call either. You state what's confirmed and move on.

The same discipline applies to a backup call. You may suspect the line is old or has backed up before, but until someone has actually looked at it, don't tell a resident it's their lateral or their bill to pay. Say a crew is coming, say when, and let the person who inspects the pipe make the causal call.

Guessing wrong is worse than saying you don't know yet. Uninformed customers, in the same research, were 95 percent more likely to raise a safety concern and 76 percent more likely to report a taste or smell problem, on water that tested identical to what informed customers drank without worry. What you say on the phone shapes what people believe about their own tap.

Write down every complaint like it's a work order

A complaint that only lives in your head didn't happen, as far as anyone can prove later. The same records discipline that protects a board when a rate case turns contentious, meeting minutes, notices, and complaint logs, protects you when a resident calls back in six weeks swearing they reported this in April.

Log at minimum who called, when, what they reported, what you told them, and what happens next. That last field matters most. A complaint log with no follow-up field is just a list of things that annoyed people.

Treat the phone the way you'd treat a valve you just closed. If it isn't written down, it isn't done.

Know which calls you hand off

A handful of conversations aren't yours to finish alone, and knowing which ones ahead of time saves you from a bad call in the moment.

• Any hint of contamination. If a caller describes symptoms, or you can't rule out a

• Media. A reporter's question is not a resident's question, and answering it the same casual

• A threat. If a caller threatens you, your crew, or the utility, that has stopped being a

cross-connection or backflow event, that's a boil-notice and public-health decision, not something you confirm on the phone. Get it to whoever in your system makes that call, fast, and don't speculate with the resident while you wait. way can turn a routine outage into a story. Every system should decide its spokesperson before the crisis, not during it. If a reporter calls you directly, it's fine to say the utility has a spokesperson and give them the way to reach that person. customer-service call. End it, write down exactly what was said, and tell your supervisor right away.

None of these three are about being unhelpful. They're about routing the call to the person or process built to handle it, instead of improvising an answer you can't back up.

Not every hard question needs a full answer either. A caller pushing for internal details on budgets, staffing, or who's to blame doesn't need a debate. A polite redirect (that's something our office handles, here's how to reach them) keeps you accurate instead of speculative, and it isn't the same as stonewalling.

A short script for your pocket

Keep a version of this by the phone, or laminate it the way a lot of training programs suggest:

"Right now we have [what happened] near [location]. Our crew is [what you're doing]. Please [what to do], for example run your cold tap for a few minutes, or avoid using water until we call back. We'll follow up by [specific time]."

That's five sentences, no jargon, readable out loud in under a minute. The bar is a message a sixth grader could follow the first time they hear it. If you can't say it that plainly, you don't know the situation well enough yet to be reassuring anyone.

Where this goes next

Handling one bad call well doesn't fix the pipe that keeps failing. Once you've got the conversation part down, the next problem on the manager track is deciding whether that pipe gets repaired again or replaced for good.

Next on the ladder: Repair or replace: building a defensible CIP.