Utilities and energy providers get an engagement layer built around premises, meters and programs, launched one program at a time next to the billing and asset systems.
An energy and utilities implementation typically covers commercial customer accounts, program enrollment and field work, each tied back to the premise or asset involved. We design how service locations, meters, accounts and contacts relate, because that structure drives routing, reporting and every integration that follows. First releases often focus on one line of business, such as key account management or a customer program like efficiency rebates or interconnection requests. Later phases add Field Service scheduling, a customer or contractor portal and deeper links to billing and asset systems, which stay authoritative for their own data.
Utilities serve customers they cannot easily choose or lose, under regulators who expect documented, fair treatment. The customer is tied to a physical location and often to an asset such as a meter, transformer or solar installation, so the data model must represent premises and equipment, not just companies and people. Billing, outage management and asset systems are mission-critical and long-lived, which means Salesforce joins an established landscape rather than replacing it. Work also spans office and field: a program application might need a site inspection, a crew visit and a rebate payment. Designs that model this chain properly avoid a patchwork of spreadsheets between departments.
We define service locations, meters and customer-owned equipment as records linked to accounts, so a commercial customer with many sites is represented accurately. Asset relationships let service agents and account managers see which equipment sits at a location, which programs apply to it and what work has been done there before they call the customer or schedule a visit to the site.
Efficiency rebates, demand response enrollment and interconnection requests each follow a multi-step process with eligibility checks, documents and approvals. We build guided application flows, often exposed through Experience Cloud, with status visible to customers and contractors. Staff work from queues with defined stages, so a backlog is visible instead of hiding in shared inboxes, and managers can rebalance work when application volume surges.
Large commercial, industrial and public-sector customers need account plans, contact maps across facilities and a record of every conversation about rates, outages or projects. The build gives account managers consolidated views across sites and alerts when a service issue or program application needs attention, supporting the relationship during rate cases, planned construction and conversations about new load or service upgrades.
For inspections, installations and customer-requested visits, Field Service handles scheduling, crew skills and mobile work orders. We decide early which work belongs in Salesforce and which stays in the work management system used for grid maintenance, so crews are not dispatched from two places and nobody double-books a truck. Crew skills and certifications are modeled so the right technician is sent.
We open with a landscape review, because in this industry the systems around Salesforce shape the design more than the CRM itself. Customer operations, a program manager, field supervisors, IT architecture and regulatory affairs all join discovery. The premise and asset model is agreed and validated with sample data from the billing system before any user-facing build begins. The first release goes to a single program or customer segment, with parallel running where regulators expect uninterrupted service. Security reviews are scheduled into the plan rather than bolted on, since infrastructure data often faces stricter internal controls than ordinary customer information.
Accounts, premises and billing status sync into Salesforce as read-only reference data, while program enrollments and customer updates pass back through controlled interfaces.
Asset records and maintenance work orders remain in the asset platform, with summaries surfaced in Salesforce and field visits created only where customer-facing work is involved.
Outage status and restoration estimates appear on affected accounts, so service agents and key account managers can answer calls with current information during events.
Companies with both regulated utility and unregulated energy services may face rules about sharing customer information between them. Design org structure, sharing and marketing consent with regulatory counsel, so a competitive offer never draws on data that must stay with the regulated business.
Customer, meter and infrastructure data can be sensitive beyond normal privacy concerns. Involve the security team in design reviews, plan identity and access with single sign-on, and restrict exports. Some fields, such as medical-necessity or critical-care flags, need especially tight handling and clear procedures.
Service demand can spike sharply during storms or heat events. Test routing, queues and any customer-facing portal pages under peak conditions, and decide which functions pause during emergencies. A system tuned only for normal days can fail exactly when customers most need clear answers.
Client names are anonymized.
No. The billing and customer information system remains the record for rates, usage and bills. Salesforce adds engagement, programs, key account management and case handling on top, drawing reference data from that system. Moving billing into a CRM creates risk without a clear benefit, so we keep the boundary explicit in the design and in the integration contracts.
Yes. An Experience Cloud portal can give approved trade allies their own login, let them submit applications for customers they serve and track status. Verification ensures contractors see only the applications they submitted, and program staff review documents and approve payments from queues. Contractor onboarding and approval can be part of the same release, so trade allies are vetted before they submit anything.
Choose one with a clear owner, manageable volume and a painful current process, often a rebate or interconnection workflow run on email and spreadsheets. That delivers visible relief and proves the premise model. Programs with complex eligibility rules or heavy regulatory reporting can follow once the foundation, integrations and team habits are established across the customer operations team.
We map which work orders originate from customers and which come from planned maintenance. Customer appointments, inspections and program installs are strong candidates for Field Service, while grid maintenance stays in the asset system. Where crews handle both, we agree which dispatcher owns the schedule so technicians receive one consistent list of jobs each morning, whatever system the work came from.
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.