Learn how water utilities can connect annual statements, meter readings, planned works and fault updates through one customer communication approach.

Water is an essential service that is easy to take for granted until something changes. A customer may barely think about the utility for months, then need immediate answers about an annual statement, an unexpectedly high reading, planned street works, low pressure or an interruption in supply.

Those moments range from predictable to urgent, but the customer does not care which system or department owns them. They expect one organisation to know the situation, explain it clearly and keep them informed until the issue is resolved.

One customer relationship, many operational systems

A typical water utility relies on several specialised systems: customer and contract administration, billing, metering, geographic information, asset management, field service, work planning, incident management, payments and CRM. Each system owns valuable information. Problems arise when each one also becomes an independent communication channel.

That creates familiar symptoms: the contact centre cannot see the fault message that was sent; a planned-work letter uses an old address; a payment reminder ignores an open billing complaint; or an incident update is published on the website but not sent to the customers most directly affected.

A modern customer communication platform provides a coordination layer. It does not replace the operational systems. It uses their events and data to create consistent communication, choose the right channel and maintain a complete record.

The water customer communication lifecycle

1. Moving in, moving out and new connections

The journey should confirm the address and service date, request only the necessary information, explain billing and payment, and provide a clear first point of contact. A move-out journey must coordinate the final reading, final statement and refund or balance without leaving loose ends.

2. Meter reading requests and usage corrections

A reading request is more effective when it includes a direct, mobile-friendly route to respond. With Eclipse FlexForms, the customer can enter the reading, upload a photo if required, correct contact details and receive confirmation within the same communication flow. Adaptive questions can handle exceptions without presenting every customer with a long generic form.

3. Consumption insight and leakage awareness

Usage communication should do more than display a number. It can compare consumption with an earlier period, flag an unusual pattern, explain possible causes and offer practical next steps. The objective is to help the customer act before a high bill or a suspected leak becomes a complaint.

4. Annual statements and payment communication

The annual statement is a trust document. It must show how consumption, rates, previous payments and the final balance fit together. When the result is unexpected, the communication should answer the first questions inside the document and provide a direct route to dispute, arrange payment or submit corrected information.

Payment reminders should use current case context. A customer waiting for a correction should not continue through an automated escalation sequence as though nothing has happened. Good orchestration uses CRM, billing and payment status before deciding the next message.

5. Planned maintenance and local works

Planned work communication needs precise geography, timing, expected impact and practical guidance. Customers should know whether supply will stop, whether pressure or appearance may change, what they should do beforehand and where to find updates. Reminders can be timed closer to the work, with a completion notice when the service is normal again.

6. Faults, interruptions and urgent service updates

During an incident, silence creates its own story. Customers call, search social media and compare messages with neighbours. The first update does not need every answer, but it should acknowledge the issue, define the known impact, explain what is being done and promise the next update at a credible time.

7. Complaints and service recovery

A complaint is not only a case in CRM. It is a sequence of acknowledgements, evidence requests, status updates, decisions and follow-up. The communication should preserve context, avoid repeated questions and show that the utility has understood both the technical issue and its effect on the customer.

Designing a fault communication scenario

Fault communication is where orchestration becomes visible. The process can be prepared before the incident, then populated with live operational data when an event occurs.

1. Detect or register the incident in the operational system and identify the affected area, assets and customer records.
2. Classify the event by urgency, expected duration, safety implications and customer impact.
3. Trigger an initial message using a pre-approved content pattern, with the facts that are known and a time for the next update.
4. Choose channels based on urgency, customer preference and available contact data; use fallback routes for critical messages.
5. Update the same journey as field information changes, rather than creating disconnected one-off messages.
6. Confirm restoration, explain any after-effects and provide a simple route to report a continuing problem.
7. Review delivery, responses, call volumes and complaints to improve the scenario for the next event.

Eclipse scenario management allows triggers, actions, timing, channel sequences and “if-then” paths to be configured visually. This makes it possible to prepare routine and emergency journeys without hard-coding every variation into the source system.

What customers need in an incident message

Data integration is the foundation

The quality of communication depends on the quality and timeliness of the data behind it. Eclipse integration capabilities can connect customer, billing, metering, GIS, field-service and incident systems, then structure the relevant information through a canonical data model.

This matters because each communication requires a different slice of the data. An annual statement needs consumption and payment history. A planned-work notice needs location, work schedule and impact. A fault message needs the current incident state, affected area and the customer’s contact and channel preferences. The communication layer should assemble what is needed without copying entire source systems into another database.

One content foundation for routine and urgent messages

Water utilities often have hundreds of variants of letters, emails, portal texts and service scripts. Central content and template management turns that library into reusable components: approved explanations, address and account blocks, accessibility patterns, local contact details, incident instructions and brand elements.

The benefit is not only consistency. It is speed. A policy, rate, service or wording change can be made once and applied wherever the component is used, with the appropriate approval workflow.

Channel choice should follow the task

An annual statement may need a secure portal, accessible digital document, email notification or print. A meter-reading reminder may work through email or SMS with a direct form link. An urgent interruption may require SMS, push or messaging plus a continuously updated service page. Eclipse omnichannel delivery keeps these outputs coordinated and records whether the customer received or acted on the message.

The goal is not “digital first” at any cost. It is appropriate communication: digital where it improves speed and action, print where it remains necessary, and assisted service for customers who need human support.

Build for peaks, resilience and critical-service obligations

A major fault can create a sharp communication peak at the same time employees and systems are under pressure. Eclipse’s article on scalable CCM for peak loads explains why resilient design must cover data, composition, prioritisation, channel delivery and monitoring – not only raw infrastructure capacity.

Drinking water is among the critical sectors addressed by European cyber-resilience policy. The ENISA overview of cybersecurity for critical sectors and the EU NIS2 framework reinforce the need for secure, continuous and well-governed operations. Customer communication is part of that resilience because people need dependable information when normal service is disrupted.

Measure more than message volume

A water utility should be able to see whether communication achieved its purpose. Useful measures include successful delivery, time to first incident update, form completion, corrected readings, payment outcomes, repeat contacts, complaints, opt-outs and the percentage of customers reached before they called.

Eclipse dashboards bring communication history, processing steps and customer responses into an operational view. This supports real-time control and longer-term improvement. The Eclipse article on modern CCM and operational efficiency provides additional examples of how central control reduces manual work and fragmented processes.

A practical route to modernisation

A water utility does not need to modernise every communication at once. A phased approach can create value while reducing delivery risk.

1. Map the highest-volume and highest-risk journeys, from annual statements to incident updates.
2. Identify duplicate templates, manual hand-offs and data gaps that create avoidable calls or delays.
3. Choose a first journey with measurable operational and customer value.
4. Connect the required source systems and establish a reusable data model.
5. Centralise content, approvals and channel variants for that journey.
6. Automate triggers, reminders, fallbacks and response capture.
7. Use delivery and outcome data to improve the journey and extend the model to the next use case.

The warning signs described in 5 signs your legacy CCM platform is costing customers are particularly relevant to utilities: slow content changes, reactive contact-centre demand, limited channel reach and poor operational visibility.

How Eclipse supports water utilities

Eclipse combines an end-to-end CCMaaS platform with implementation and managed services. We help organisations connect operational systems, standardise data, rationalise content, automate communication scenarios, add interactive forms and coordinate delivery across channels.

Our customer interaction services can support a targeted journey such as meter reading or incident communication, as well as a broader transition from legacy output management to a managed communication platform.

From documents to a dependable communication service

Annual statements and fault reports may sit at opposite ends of the operating calendar, but they depend on the same fundamentals: trusted data, approved content, appropriate channels, clear next actions and visibility into the outcome.

When those capabilities are connected, the water utility communicates as one organisation. Routine interactions become easier, urgent interactions become calmer, and customers spend less time trying to work out what is happening.

Frequently asked questions

What communications should a water utility manage through CCM?

Common examples include onboarding and moving, meter-reading requests, annual statements, payment reminders, tariff notices, planned-work notifications, fault updates, complaint correspondence and service-recovery messages.

Can a CCM platform connect with GIS and outage systems?

Yes. The communication layer can receive location and incident data from GIS, asset, field-service or outage systems and combine it with customer and channel data to identify and inform the affected audience.

How can a water utility collect meter readings digitally?

A secure interactive form can be linked from email, SMS or a portal, adapt questions to the customer’s situation, accept supporting information and return the result to the billing or metering process.

What makes a good fault update?

It should confirm the affected area, state what is known, explain what the customer should do, give the best current restoration estimate, set a time for the next update and provide a clear help route.

Should all water communication become digital?

No. The objective is channel appropriateness and inclusion. Digital channels improve speed and interactivity, while print and assisted service remain important for some customers and communication types.

How does Eclipse help with legacy communication environments?

Eclipse can assess current journeys, connect existing applications, migrate and rationalise templates, implement scenario and channel control, and operate the environment as a managed CCM service.