How channel mix, outage communications, and follow-up workflows shape what a customer satisfaction survey actually measures
Customer satisfaction survey results only tell the truth about the customers who answered them. That distinction matters more in utilities than most programs admit. Recent reporting that Central Alabama Water scored near the bottom in a JD Power water-utility satisfaction study is a reminder: a low score is an operational alarm, not a complete explanation.
The honest question for operations leaders is not just “what does the score say?” but “who was counted and who was left out?” If alerts, contact-center responsiveness, and follow-up workflows miss the same people, your survey will reflect a partial reality and miss the problems that cost trust.
Where measurement breaks down in practice
There are three common failure modes. First, outage and service notifications do not reliably reach affected customers. A missed notification means a customer arrives at the call center already upset, and by the time they answer a survey they have a stronger negative impression. Second, the contact center response time and after-hours coverage shape whether a dissatisfied customer gets their issue acknowledged before a survey invitation arrives. Third, the survey channel mix and language access determine who actually responds. Email-only programs over-index on younger, tech-savvy households and miss older or limited-English-preference customers.
The score and the operational reality can drift apart. A utility can improve internal processes that are visible to customers who use the web portal while leaving the phone-first population worse off. The result is a number that looks stable while underlying local trust erodes.
Operational checks to run this week
Executives do not need an engineering audit to begin triage. A short set of practical checks will reveal whether your measurement is telling you what you think it is.
- Confirm outage alerts reach a representative cross-section of customers: phone calls, SMS, and the online portal are not interchangeable.
- Ask whether detractor responses trigger a different path than promoter responses: is a low score automatically routed for local follow-up?
- Review language access: are invitations and surveys offered in customers’ preferred languages, and are open-ended responses translated back for a single review team?
These checks expose two familiar gaps. One, survey sampling bias: the people who answer are rarely a random subset of customers. Two, closed-loop weakness: many programs collect complaints and then fail to close the loop in a way the customer notices. The second problem is what turns a low score into lost trust.
What a working follow-up workflow looks like
Picture a customer whose water pressure drops during an outage. They receive an outage alert that mentions expected repair windows, they get a status update, and when the issue is resolved the survey that follows is tied to that service interaction. If the customer reports low satisfaction, the system routes the response to the local team with the notes from the incident, and the local team records an action that the customer can see later. That chain is operational, not theoretical. The two weak links most programs skip are: offering the survey in the customer’s language and ensuring the follow-up is visible to the customer.
Designing that chain does not require replacing your contact center. It requires thinking about timelines at the per-customer level. Each outage or service event starts a clock for the affected customers. The survey invitation, any escalation, and the follow-up must use that clock. When schedules are done in batches that ignore the event clock, response rates and the meaning of the score fall apart.
Practical tradeoffs and what to avoid
There are tradeoffs. Adding phone and SMS outreach widens reach but increases operational complexity and cost. Translating open-ended comments brings insight but creates a need to process and act on more verbatim feedback. The honest question is whether your team has the capacity to act on the additional signals you will receive. If not, it is better to narrow the ask on the survey and improve the follow-up workflow first.
One operational rule of thumb: short, timely surveys tied to a single event will get higher completion rates and more reliable signal than long, generic questionnaires sent on a fixed calendar. Conditional branching matters here. A satisfied customer should not be asked the same troubleshooting questions as someone who reported an ongoing outage. Keeping each individual’s interaction short improves both data quality and response rates.
Most programs that handle this well combine channel diversity with a plan for closing the loop. If your team wants a reference point for how enterprise CSAT and NPS programs handle these issues, or the practical notes in customer satisfaction survey design that reaches everyone, those resources focus on operations and will help frame the vendor questions you should write down.
Related coverage: Central Alabama Water/Birmingham Water Works ranks last in customer satisfaction survey — WBRC