Where Salesforce sits next to billing and operations
Regulated utilities typically operate customer billing, outage management, and asset systems that Salesforce does not replace. Salesforce adds a customer-facing service and engagement layer on top of them, drawing in account, usage, and outage data through integrations so agents do not have to switch between screens. For smaller energy retailers and service companies, Salesforce may cover more of the customer lifecycle.
Contact centers and customer self-service
Service Cloud gives agents one workspace with the customer's account, recent interactions, and knowledge to resolve questions. Self-service portals and chat let customers report issues, check status, and manage their accounts. Clear case categories matter: when a contact reason is consistently recorded, patterns in complaints become visible and fixable.
- Link cases to the service point or asset involved.
- Route by priority, such as safety-related reports, and track target response times.
- Use knowledge articles to give consistent answers during high-volume events.
Outage communication and proactive notifications
During an outage the volume of contacts spikes, and much of it is a customer wanting to know whether anyone knows. Proactive notifications reduce calls: tell customers what is known, when to expect an update, and how to report a hazard. Connect outage data to customer records so messages go to the right people and the contact center sees the same status customers do.
Field service and asset history
Crews need to know what they are working on and its history. Field Service can schedule and dispatch crews, give them mobile work orders, and show the asset record, past issues, and safety notes. Parts and equipment usage recorded in the field feeds inventory and cost systems so the work is accounted for.
Salesforce Field Service →Commercial and industrial accounts
Large customers have contracts, multiple sites, and account managers who need a complete picture. Account and opportunity management supports renewals, new service requests, and energy-efficiency programs. Quotes and agreements for commercial services can follow approval rules, and a portal can give large customers visibility into their requests and invoices.
Explore Salesforce solutions →A realistic first 90 days
- Days 1 to 30. Identify the systems that own billing, outage, and asset data, and define the minimum information agents need on one screen.
- Days 31 to 60. Launch the agent workspace for one contact category, with knowledge and case routing, and connect the account lookup.
- Days 61 to 90. Add proactive notifications for a pilot area and begin field-work integration for a single crew type.
Decisions to settle before configuration starts
- What is the unit of service? Decide whether cases attach to the customer, the premise, the service point, or the asset, since lookups and reporting follow from it.
- Which contact reasons matter? Define a short, consistent list of reasons so complaint trends are visible and regulators' categories can be mapped.
- How quickly must outage data refresh? Set a freshness target and design the integration to meet it, because stale status is worse than none.
- What do crews see on site? Agree the asset, safety, and history information that belongs on the mobile work order.
Pitfalls in utility projects
- Trying to replace billing. Specialized billing systems are rarely the right target. Integrate instead.
- Stale integration data. If outage or account data is hours behind, agents lose trust. Define freshness targets and monitor them.
- Ignoring regulatory records. Complaint handling and response times may be reported to regulators. Design capture around those requirements.
- Overlooking storm readiness. Test peak-volume behavior before the season, including the contact center, notifications, and the integration load.
