Industry CRM

 ·  9 min read

CRM for Energy and Utilities: A Practical Playbook

Energy and utility CRM is a service and relationship model, not a sales pipeline. A practical playbook for structuring accounts, sites, assets, service requests, complaints, field work and the boundaries with billing, metering and GIS.

Braj Raj Singh Kushwaha

CRM consultant, business analyst and solution architect

The Short Answer

Energy and utility organisations rarely struggle to describe a customer. They struggle to describe the relationship. One business customer may have a head office, fourteen sites, several meters, a landlord and a facilities manager — plus billing queries that belong to none of them in a conventional CRM. A domestic customer adds another complication: the person who pays, the person who lives at the property and the person who calls during an outage may be three different people.

That is why CRM projects in this sector go wrong when they start with a contact list and a sales pipeline. Energy and utility work is shaped by supply points, service obligations, field visits, regulatory relationships and evidence. Model those first.

Four relationship problems, not one

Most failures come from treating four distinct jobs as one.

Customer service. Requests, complaints, billing queries, connections, transfers and appointments. The unit of work is a service request at a site or supply point, not an opportunity.

Stakeholders and regulators. Authorities, communities, landowners, partners and project stakeholders. The unit of work is an engagement and an approval milestone. Continuity matters more than transaction volume.

Field and assets. Visits, access constraints, safety checks, equipment history and completion evidence. The unit of work is an appointment or job at a location, often owned by a scheduling system.

Commercial relationships. Key accounts, contracts, renewals and partner arrangements. The unit of work is the relationship and its obligations over time.

A sales-shaped CRM handles the fourth reasonably and the first three badly. Decide early whether one platform will carry several record types or whether specialist systems stay and are linked. Both are valid. Pretending they are the same process is not.

Model the customer around the supply point

Start with a hierarchy rather than a flat contact record: the legal entity or account responsible for the relationship; the site, premises or connection point where service is delivered; the meter, asset or equipment installed there; and the contacts and roles who act for the account or site.

A logistics business with fourteen depots should be one account with fourteen sites, not fourteen duplicate accounts. The contact model should distinguish head-office finance, site managers and the landlord of a leased depot. Each service request then links to the site where the problem occurred and, where relevant, the asset involved.

Write down the first four questions a service agent asks when a call arrives. In most utility operations they are: which site, who pays, what equipment is involved, and what happened last time. Those questions define the minimum data model. If the CRM cannot answer them on one screen, the hierarchy is wrong. Preserve the identifiers used by billing, metering, GIS and asset systems so staff can move between systems without guessing.

Model stakeholders separately from customers

Stakeholder work is not customer service with different labels. The site's stakeholder CRM approach for energy and utilities treats the stakeholder as the core record rather than the deal, with stakeholder groups, engagement activity, influence mapping and project approval milestones.

The questions are different: who met this authority last, what was promised, which approval stage are we at, and is the relationship cooling? A contact record with a few notes cannot answer them. Record the stakeholder and their role in a decision; log engagement with a date, owner and commitments; track approval milestones separately from sales stages; make relationship ownership transferable so a change of manager does not reset the history; and let field teams log meetings on mobile. If one platform holds both customers and stakeholders, keep the record types distinct. A single contact object with a free-text type field will collapse under reporting.

Run service requests and complaints as controlled workflows

A generic case record is not enough. A billing dispute, a new connection enquiry, a meter investigation and a safety report need different evidence, response clocks and communication. Treating them as one queue produces the wrong priority and an unreadable backlog.

For each type, define the trigger and intake information, the owner and handoffs, the service clock and when it pauses, the escalation rule, the customer communication at each stage, and the closure reason with supporting evidence. Keep "resolved" and "closed" separate: work can be resolved internally while the customer still waits for confirmation, and collapsing the two hides the delays customers complain about. Capture structured reason codes for complaints and failures. Free text is useful for the individual case and useless for finding a recurring cause across a region or process.

Join field work without pretending CRM is dispatch

CRM should hold the customer commitment and context: the appointment request, access notes, site history and what was promised. It does not need to own engineer availability, routes, skills, parts or permits; those belong in scheduling or field service software. Integrate around a stable appointment or job identifier, and pass status changes, completion notes, evidence and failed-visit reasons back to the customer record. Define who owns rescheduling and how a no-access visit is recorded, because that is where communication usually breaks down. Access and safety evidence can matter more than commercial history, so make those fields structured, visible to the right people and restricted for everyone else.

Draw clear boundaries with operational systems

CRM is rarely the system of record for the operational facts of a utility. Trying to make it one creates a second, conflicting source of truth.

Area System of record What CRM should do
Billing and payments Billing or finance platform Show a referenced summary; do not recalculate balances
Meter reads and consumption Metering or billing system Reference the meter and flag exceptions
Network and location GIS or network records Hold the site reference and key location attributes
Asset and maintenance history Asset management Link the asset to service context and history
Orders and costs ERP or finance Provide commercial context, not a parallel ledger

For every integration, agree the stable identifier, which side may write the data, how fresh the copy must be, and what happens when the other system rejects or delays a record. Exceptions need an owner and a queue. An integration that works only when everything succeeds is a dependency, not an integration.

Make consent, vulnerability and communication evidence auditable

Energy and utility organisations handle sensitive circumstances and regulated communications. Capture consent and channel preferences per purpose, with source and date. Use restricted, structured fields for vulnerability or safety flags, with a review date and accountable owner. Keep a communication timeline, and record who changed a sensitive flag and why. Requirements differ by jurisdiction, so get qualified legal, privacy and regulatory review.

Report on operational decisions

Dashboards should answer questions someone can act on this week: open requests by type, site and age; repeat contacts within 30 days; service clock adherence and breach reasons; failed field visits; complaint root causes grouped by process; contract review dates; and data quality gaps such as requests with no site or asset reference. Activity counts rarely change a decision. Give every report an owner and a decision it supports.

Sequence delivery and test the journeys that fail

A sensible first release covers the customer and site hierarchy, asset references, service request and complaint workflows, the communication timeline, operational reporting, and migration of active accounts and open cases. Add billing lookup, meter and asset references, field statuses and self-service in a second phase. Leave key account planning, contract renewals, stakeholder engagement and approval milestones until the foundation is stable. Integration multiplies data-model mistakes, so stabilise the hierarchy first, migrate open cases — not just closed history — and rehearse the load before cutover.

User acceptance testing should include a business customer with multiple sites, a residential customer with a vulnerability flag, a complaint that crosses three teams, a failed site visit, and a billing query that must be handed off. Test permissions and the audit trail too. A process that works for the administrator but cannot be completed by the actual user is not ready.

Questions to settle before selecting a platform

  1. Can it model account, site, asset and contact roles with relationships and date ranges?
  2. Can each request type have its own fields, service clock and routing without custom code?
  3. How are paused clocks, escalations and breach reasons represented?
  4. How will billing, metering, GIS and asset identifiers be stored and reconciled?
  5. Can history roll up from site to account without duplicating records?
  6. What can an administrator change after go-live, and what requires a developer?
  7. How will open cases, attachments and relationships be migrated with their identifiers?
  8. Who owns the integration exception queue and the data quality rules?

Where this leaves you

Energy and utility CRM succeeds when the model reflects how work is delivered: supply points rather than contact lists, service requests rather than opportunities, stakeholders rather than deals, and clear boundaries with the systems that own operational facts. Get that structure right and the reporting, adoption and governance arguments become much easier.

If you are scoping a programme, the energy and utilities stakeholder CRM service covers the relationship side in more detail, and the manufacturing ERP integration guide applies the same boundary discipline beside a heavy operational system. For a short conversation about your scope, use the contact page.

Does your CRM describe customers, or supply points?

Describe the relationship you cannot model today — a site hierarchy, a crossed complaint, a failed visit — and you will get a straight view on what to fix first.

Start a conversation