Energy retail: who owns the answer when the customer calls

Call the customer service line of a Norwegian electricity retailer on an ordinary Tuesday, and a good share of the calls will be about something the company neither owns, bills for, nor can do anything about.

This is not the customer's fault. An ordinary household holds two contracts covering the same electricity: one with the grid company that owns the line up to the house, and one with the retailer that sells the kilowatt-hours running through it. Each sends its own invoice. To the customer this is “the electricity bill”, singular, and the number saved in her phone is the number of whichever company she switched to last.

Two companies, one cable

The split is not an organisational detail. It is built into the market.

The grid company is a monopoly. You cannot choose it and you cannot switch it – it follows the address. It owns the metering point, measures consumption and reports the metering data to Elhub, the central data hub owned by the transmission operator Statnett, which handles more than four million metering points. The grid company bills the network tariff, and the grid company is the one that turns out when the whole street goes dark.

The retailer is the opposite. Free choice, open competition, and nothing physical between itself and the customer. It buys electricity and sells it on.

One cable into the house. Two companies on it.

Five calls from an ordinary week

What the customer calls about	Who owns the answer	What the agent can actually do
Power cut in the street	The grid company	Establish that it is not you, and give the right number for that address
The network tariff went up	The grid company	Explain which line on which invoice, and who sets the tariff
The state price scheme	The grid company administers it	Explain that the ordinary supply contract continues unchanged, and where the adjustment appears
Moving house	The retailer	Take the move notification – this one really is yours
Switching, or the fallback supply	The retailer	Carry out the switch, or explain what the fallback arrangement is and what it costs

Three of the five belong somewhere else. That is worth taking in before anyone writes the first word of a call script: triage is not a preliminary to the job. It is the job.

The state price scheme is the hardest of them

Norway's Norgespris scheme came into force on 1 October 2025 at 40 øre per kilowatt-hour excluding VAT – 50 øre including – and runs through 2026. Parliament has decided the scheme should apply until the end of 2029.

What makes it hard on the phone is that it is not an electricity contract. The customer keeps the contract with the retailer, and the settlement of the difference appears on the invoice from the grid company, which administers the scheme.

So a customer who rings their retailer and asks “am I on Norgespris?” has called the right company for half the question and the wrong one for the other half. This is also exactly the kind of question a language model answers well without having anything to answer from: it knows the word, it knows the shape of the answer, and it does not know that it is filling a gap. A “yes, I can see that here” about a figure the agent cannot see is not a nuance. It is wrong information, delivered in a calm tone of voice.

“You'll have to call your grid company”

This is the sentence that decides whether the agent was any use.

Most deployments handle the recognition part perfectly well: they can tell that a question is about the network tariff rather than the energy. Then the agent says “you'll need to take that up with your grid company” – and stops being helpful, because the customer does not necessarily know who that is.

The grid company follows the address. That is not a guess; it is a lookup. An agent that can say “at your address that is this company, and the number is this” has finished the call. An agent that says “contact your grid company” has only moved it, and the customer rings back ten minutes later – to you.

This does not require a heavy integration. Far fewer calls need a back-office lookup than people assume, and an address-to-grid-company table is not a back-office system. What does have to be settled in advance is what the agent does with a call it does not own: give out the number, transfer, or take the message and call back.

The hour when the whole customer base calls at once

This sector has a load profile few others share. A fault on a high-voltage line, a price story in peak viewing time, an invoice with the wrong amount sent to the entire customer base – each of the three gets a very large number of people dialling within the same quarter of an hour.

A voice agent has no queue, and therefore no warning light. Capacity is the lowest of four numbers, and you rarely own all four. In this sector that hour is not an exception to normal operation. It is the reason the phone number exists.

Three things to settle before the agent answers

The boundary. Write down which questions are yours and which are the grid company's. Not as a principle, but as a list, using the actual wording customers use when they call.

The schemes. Price support schemes change politically, not technically. The agent needs a fixed text with a date on it, and a named owner who updates it when the decisions change.

The refusal. Decide exactly what the agent says when the call is not yours, including whether it gives out a phone number. This is one of the most frequent exits in the whole deployment, and usually the only one nobody has written.

The easy call is the hard one

In most sectors the demanding call is the complicated one. In energy retail it is the other way round: the demanding call is the entirely simple one, put to the wrong company, by a customer who has no reason to know there are two.

Threll.ai builds voice agents in Norwegian, Swedish and Danish. Try this today: ring your own number and say the whole street is dark. Do you get a phone number back, or do you get a suggestion?