A utility customer portal earns its keep by deflecting calls. Every bill paid, outage reported, or service started online is a call the contact center did not take. This guide covers what a portal should do and how it connects to the CIS behind it.
The features that actually reduce call volume
- Bill view and payment. The single highest-volume reason customers call.
- Usage history. Interval and monthly consumption, which also supports demand programs.
- Outage reporting and status. Customers report and track outages without calling.
- Service start, stop, and transfer. Move-in and move-out handled online.
- Paperless billing and payment arrangements. Routine account changes self-served.
How it ties into the CIS
The portal is a customer-facing surface over the CIS. It reads account, bill, and usage data from SAP IS-U, Oracle CC&B, or Cayenta CIS, and writes back payments and service requests. With Cayenta, the engagement layer is Silverblaze. The important rule is that the CIS stays the system of record and the portal never holds the only copy of a transaction.
The payoff
A portal that covers billing, outages, and service changes moves the routine work out of the call center. For where the portal sits in the wider system, see the Cayenta CIS review.