When the power goes off: AI agents for utilities and energy services

21 October 2026
Arcsen

When the power or water goes off across a district, a utility’s contact centre hears the same questions again and again: is it only my building, what happened, when will it be back. Many arrive on WhatsApp and by phone, in Arabic and English. Between outages come move-ins, move-outs and bill queries, crews writing up jobs after long shifts, and business clients asking what their maintenance contract covers.

Much of that suits an AI agent. Some of it is an emergency: a smell of gas, a fallen or sparking cable, water near electrical equipment. Here are the four agents we would build first on Agentforce, what each needs, where a person takes over, and how to test them.

Four agents worth building first

Salesforce’s Agentforce for Energy & Utilities page lists prebuilt subagents, including Energy Customer Service for billing queries, outage updates and service requests, and Field Summary, an AI-generated job snapshot for technicians. Subagents are what Salesforce called topics until April 2026. The page warns that some may not be available yet.

Outage and maintenance information, for customers. On web chat and WhatsApp, the agent answers “is there an outage in my area?” and “when is the planned work?” only from published notices, the ones our guide to utility websites on SitecoreAI describes. If no notice covers the area, it logs a case. It never offers a restoration time the notice does not give.
Move-in, move-out and billing, for verified customers. After an identity check, the agent explains a bill line by line, takes a meter reading and opens move-in and move-out requests. Energy & Utilities Cloud has invocable actions for the flows behind this, such as Get Bill Details, Submit Meter Reads, Start Service and Update Contract in Billing System, working against your billing system.
Field crew assist, for technicians. In the Field Service mobile app, the agent briefs the crew before the job and drafts the write-up after it. Salesforce’s Field Service announcement describes Pre-Work Brief playback, a spoken summary of the work order, and a utility lineworker refining an agent-drafted summary before saving it. Safety checklists stay with the crew.
Contract and SLA service, for business clients. On an energy services company’s client portal, the agent tells facilities managers what the contract covers at a site, where a case stands against its SLA and when the next visit is due, and opens cases against the right entitlement, the records our guide to Salesforce for energy services companies sets up.

Agent	Channel	Data and systems it needs	Actions it may take	Where a person takes over
Outage and maintenance	Web chat, WhatsApp	Published notices, read live	Answer from the notice, log a fault report	Every emergency or safety report, at once; restoration promises
Move-in, move-out and billing	My Account portal, WhatsApp	Identity check, billing accounts, billing system	Explain bills, take readings, open start and stop requests	Disputes, payment plans, disconnection, refunds, vulnerable customers
Field crew assist	Field Service mobile app	Work orders, asset history, procedures	Brief the crew, draft the summary for the technician to save	Permits to work, safety sign-off, injuries
Contract and SLA service	Client portal on Experience Cloud	Service contracts, entitlements, case milestones	Answer scope questions, open cases, report SLA status, book visits	SLA breach claims, service credits, scope changes, prices

Agree the last column with operations, HSE and legal first.

What the agents need

Records the agent can trust. A utility’s agent reads premises, service points and billing accounts in Energy & Utilities Cloud, with bills and readings fetched from the billing system through MuleSoft. Salesforce calls Data 360 an integral part of Agentforce, and its service agent considerations say the APIs connecting Data 360 to service agents work only with the default data space, so plan data spaces with that in mind.

Identity before personal data. Salesforce’s customer verification pattern sends a one-time code, checks it, and sets variables that hide a subagent or action until the customer is verified and can force an action to run only for that customer. The standard action emails the code; utilities will want the registered mobile and account number too, and the flows can be overridden. Until then, the agent says nothing about any account, including whether one exists at an address.

Knowledge with owners. Notices belong to the duty manager, bill explanations to billing, procedures and safety content to HSE. Energy & Utilities Cloud handles major incidents in the same workspace as cases and field jobs; keep the outage agent on the published notice, away from the internal incident record with its causes and crew notes. Read notices live through an action that calls the feed your website uses, since they change by the hour.

Guardrails and handover

When an agent cannot help, its Escalation subagent hands the conversation to a person through an Omni-Channel flow, with the history and details gathered. It attempts that transfer once per session, and if it fails, the agent carries on with the customer. A safety report therefore needs a second route that works regardless: the official emergency number in the first reply, and a priority case for the control room.

Service agents only support conversations the customer starts, and on enhanced WhatsApp the window ends 24 hours after the conversation opens, according to Salesforce’s considerations, so restoration updates go out from a flow with approved templates. The same page says data masking through the Einstein Trust Layer is disabled for service agents, so each action should return only the fields the answer needs.

Rules that stay with people

Emergencies and safety reports: gas smells, fallen or sparking cables, anyone hurt. The agent stops, gives the official emergency number at once and alerts the duty team.
Supply: disconnection, reconnection, and customers who rely on power for medical equipment.
Money: bill disputes, adjustments, payment plans, deposits and refunds.
Promises: restoration times the notice does not state, and compensation.
Contracts: SLA breach claims, service credits, scope changes and prices.
On site: permits to work and safety sign-off, signed by the crew.

Testing before launch, and measuring after

The Agentforce Testing Center runs batches of test utterances against expected responses, shows which subagent and actions the agent chose, and can generate more test conversations with AI. Use it in a sandbox, as Salesforce advises, because tests can modify CRM data. Write the test set from real transcripts in Arabic and English, with Gulf and Egyptian phrasing, Arabic in Latin script and mixed sentences, plus every emergency phrase your control room hears. Each must reach a person.

As of October 2026, Salesforce’s language support page lists Arabic as Beta and notes that languages in beta may have some inconsistencies when retrieving information; voice agents have their own list. Have an Arabic-speaking supervisor read pilot conversations daily, and add the agent to your outage drill: publish a test notice, check both languages, withdraw it, and confirm the agent stops quoting it.

After launch, report for each language: containment, the share of conversations resolved without a person; handover quality, whether the person had the summary and the customer did not repeat themselves; complaints and repeat contacts; and every emergency handover, reviewed one by one. Salesforce’s Agent Analytics streams usage data to Data 360 for reports and dashboards.

Our work in energy and utilities

Arcsen is a Salesforce Summit partner working from Dubai, Riyadh, Jeddah, Doha and Cairo, with Arabic-first delivery. Our energy and utilities work includes:

Dalkia: Sales Cloud runs B2B sales automation for Dalkia, the EDF Group’s energy services company, in Saudi Arabia.
Dubai Supreme Council of Energy: LPG licensing. One digital workflow for licensing LPG cylinder distributors in Dubai, from legal entity registration to the DSCE permit.

Clients on our energy and utilities page also include alfanar and Gas Arabian Services. Every agent we design starts with the records it will read.

Where to start

Write the emergency route first with the duty manager and HSE: trigger phrases, reply, number and who is alerted.
Pick one agent on one channel. The outage agent on WhatsApp is often the right start, because its content already exists.
Map each action to its system, and name an owner for each knowledge source.
Build the Arabic and English test set from real transcripts, and run it before every release.
Widen in steps: billing and move-ins once verification works, then crews, then business clients.

Planning agents for customers, crews or clients? The free Agentforce Readiness Assessment takes ten working days, picks three use cases and gives you a costed pilot plan. See our energy and utilities work and how we deliver Agentforce, talk to our energy team or send us your RFP.

Frequently asked questions

Can an Agentforce agent answer outage questions on WhatsApp?

Yes. A service agent can run on enhanced WhatsApp and web chat, answering only from published notices. It only supports conversations the customer starts, so restoration updates go out from a flow.

Does Agentforce support Arabic?

Salesforce lists Arabic as Beta for agents as of October 2026, and voice agents have their own list. Test both languages and review Arabic conversations during the pilot.

What should a utility’s AI agent never handle?

Emergencies and safety reports, which go at once to a person and the official emergency number. Disconnections, bill disputes, refunds, restoration promises, SLA claims and prices also stay with people.

Can field crews use Agentforce in the Field Service mobile app?

Yes. Salesforce describes pre-work briefs played back before a job, and post-work summaries the technician refines and saves. Safety checklists and permits stay with the crew.