Customer, meter, outage and asset data flow between Salesforce and the utility's operational systems, so service and program teams work from current information.
For utilities and energy providers, integration puts Salesforce in front of core operational platforms without trying to replace them. We connect the customer information and billing system so representatives see account, premise and payment status; link meter data for usage questions and program eligibility; and surface outage information so contact center and digital channels give the same answer. On the commercial side, key accounts, interconnection requests and energy-efficiency programs are connected to the systems that approve and pay them. The customer information system stays authoritative for billing, and every flow is built around that boundary.
Utility data models are premise-centric rather than person-centric. A service point, meter and rate belong to a location, and customers move in and out of it, so integrations must track who was responsible for a premise at a given time. Operational systems are often long-lived, run on-premises and sit behind security zones separating corporate IT from grid operations, which rules out some cloud-first patterns. Critical events cluster too: a storm can multiply contact volume in hours, and outage data must reach customers quickly without overwhelming the systems that restore power. Rate and program rules also vary by jurisdiction and tariff, and those rules shape which data Salesforce needs.
Accounts, premises, service agreements and billing status from the customer information system appear in Salesforce as read-only records. Representatives handle start, stop and transfer requests in Salesforce, which passes them to billing for processing. The design tracks move-in and move-out dates, so history on a premise is never attributed to the wrong customer, and landlord or property manager relationships are kept separate from tenants.
Outage events and estimated restoration times from the outage management system feed Salesforce, updating customer notifications, portal banners and service scripts. During a major storm, the connection throttles updates sensibly so operations systems keep their capacity for restoration work and customers still receive consistent information. Customers who report an outage through any channel are linked to the event, so they hear when power is back.
Customers apply for rebates, demand response, net metering or community solar through a Salesforce portal. The integration checks eligibility against meter and rate data, passes approved applications to the program or billing system, and returns incentive payments and credits so program managers track results in one place. Contractor and installer submissions can use the same path, with documents attached to the application record.
Service orders created in Salesforce, such as meter investigations or new connections, are sent to the work management system or scheduled through Field Service, with completion notes and asset updates flowing back. Customers see status, and asset records in the operational system stay authoritative. Representatives no longer need to call dispatch to learn whether a technician has been assigned or the job has closed.
Utilities have change controls we plan around from the start. We involve customer operations, IT, the billing system owner and security architecture early, and security reviews shape the design of any connection crossing into operational networks. Read-only customer and premise data comes first, because it gives representatives value with limited risk. Transactional flows such as start-stop requests follow, then outage and program data. We test against a billing cycle's worth of masked data, rehearse storm-scale volume, and schedule cutovers away from peak seasons and planned system maintenance windows.
Account, premise, rate, balance and payment arrangement data flow into Salesforce, and service requests such as starts, stops and transfers are sent back for billing to process.
Interval usage summaries support high-bill inquiries and program eligibility checks, without loading raw meter reads into Salesforce storage or exposing them to roles that do not need them.
Outage events, restoration estimates and field work orders update customer records and notifications, while crews keep working in operational tools designed for them.
Operational technology networks are separated from corporate systems for good reasons, and utilities may face NERC CIP obligations for certain assets. Involve security architecture early, favor outbound publishing from operational systems, and document every connection path so compliance reviews do not delay go-live.
Customers move and premises remain. Store service agreement start and end dates, relate usage and program participation to the right person for the right period, and avoid overwriting historical ownership. Getting this wrong produces billing disputes and misdirected communications that take real effort to correct.
Detailed consumption patterns expose daily routines, occupancy and even appliance habits. Many states regulate who may access it and require customer consent for third-party sharing. Bring only necessary usage summaries into Salesforce, restrict access by role, and track consent for any sharing with vendors or partners.
Client names are anonymized.
Yes, and it is a common pattern. The billing system usually exposes services, database views or files that an integration layer can use. We place an API or middleware layer between Salesforce and billing, so the older system is shielded from direct traffic and a future billing replacement changes the layer, not every Salesforce process that depends on account data.
Outage events should be published from the outage system once and fanned out from Salesforce to text, email, portal and contact center scripts. Throttling, deduplication and priority rules protect operational systems while customers get consistent restoration estimates. We rehearse storm-level volume in testing so the design holds when a real event arrives rather than failing on the first busy night.
Usually not in raw form. Interval reads create enormous volumes that Salesforce is not designed to store economically. Most utilities keep them in the meter data platform or a data lake and bring daily or monthly summaries into Salesforce, or use Data Cloud to reference larger datasets for segmentation and program targeting without duplicating them.
Large customers often have many premises, special rates and dedicated account managers. We roll premises up to a parent account in Salesforce, bring in consolidated usage and billing summaries, and connect interconnection or capacity requests to the engineering systems reviewing them. Account managers then see the whole relationship, including open requests, before each customer meeting.
One onshore team with 150 Salesforce certifications, a Salesforce Consulting Partner since 2017.
A monthly brief for the people who own Salesforce, AI and revenue technology
What changed in Salesforce and AI this month, and what to do about it.
One email a month. Written by the consultants who deliver the work, not by a marketing team, for the leaders who make the technology decisions.
Consultant analysis, not vendor recaps. One click to leave.