Customer complaints management app for an energy supplier in London 2026: cost

The verdict in three sentences

An energy supplier handling 3,000 complaints a month across phone, email and web chat loses track of roughly one case in five once volume outgrows a shared inbox and spreadsheet. A custom complaints management app costs, as a 2026 London market estimate, £110,000 to £180,000 for multichannel ticketing, an SLA engine with 72-hour first resolution targets, SMS and email updates and a dashboard ready for Ofgem reporting. Delivery takes about 4 months if the scope is frozen before the first sprint and customer data (meter point numbers, accounts) is available through an export or API.

Why a shared inbox breaks at 3,000 complaints a month

For a London energy supplier, complaints cluster around four reasons: disputed bills, smart meter faults, switching errors and payment plan disputes. When they arrive through three channels (contact centre, email, web chat), the same customer often opens two or three cases for one problem. Agents work duplicates, average handling time slips past 10 days and the compliance team struggles to produce the figures Ofgem expects, knowing that a complaint unresolved after 8 weeks can go to the Energy Ombudsman.

The quickest win is not the interface but the uniqueness rule: one case per meter point and per reason, whatever the entry channel. That rule alone removes nearly a quarter of apparent volume.

What the £110k to £180k budget covers

The gap between the low and high end mainly depends on the number of channels integrated, the depth of the billing system connector and the regulatory reporting requirement.

Add recurring costs that quotes often leave out: SMS sending (2026 estimate: 3 to 5p per message through a UK aggregator), hosting and application maintenance. At 3,000 complaints and 4 messages per case on average, that is about 12,000 messages a month, or £360 to £600 monthly.

Four decisions to make before you start

The 4-month timeline only holds if these choices are made upfront:

• The reason taxonomy: 15 to 25 reasons at most, each tied to an owning team and a target delay. Beyond that, agents classify at random.
• The customer source of truth: the meter point number or account number must be the unique identifier, pulled from the billing system.
• The escalation path: who picks up a case untouched at 48 h, then at 72 h, and who can approve a goodwill credit.
• The regulator's expected format: take the latest reporting template and put it in the specification, otherwise it gets rebuilt by hand every quarter.

A realistic breakdown: 3 weeks of discovery and wireframes, 10 weeks of development in 2-week sprints, 2 weeks of acceptance testing with 10 pilot agents, 1 week of cutover and training.

Mini case study

Tom, head of customer operations at a mid-sized energy supplier in London (fictional persona), handles 3,000 complaints a month with 18 agents. Each agent spends 25 minutes per case on average, 8 of them finding the history and calling the customer back. With the app, history lookup is instant and outbound callbacks drop thanks to SMS updates: he saves about 8 minutes per case.

• Time saved: 3,000 × 8 min = 24,000 minutes, or 400 hours a month.
• Loaded agent cost: about £22 an hour, or £8,800 a month of freed capacity.
• Duplicate removal (25% of volume): 750 fewer cases, about 310 more hours.
• Investment of £150,000, recurring costs of about £3,500 a month (SMS + hosting + maintenance).

Net freed capacity exceeds £11,000 a month: payback lands around 13 to 14 months, before counting fewer cases escalated to the Ombudsman, each of which carries a case fee.

FAQ

Can we start with an off-the-shelf ticketing tool instead of a custom build?

Yes below 500 complaints a month. Above that, per-agent licences (often £25 to £80 per agent per month) and the lack of a connector to your billing platform make custom software more cost-effective over 3 years.

How do we serve customers who prefer not to use apps?

Plain SMS works on every phone and is enough to share status. A 6-digit tracking code also lets customers check their case by phone in under 30 seconds.

How long to hit a 72-hour SLA consistently?

Allow 2 to 3 months after go-live to reach 85% of cases closed within 72 h. The 48 h escalation engine is what moves that rate the most.

Is customer data protected?

UK GDPR applies. The app needs role-based access, an audit log and a defined retention period, typically 6 years for complaint records in regulated utilities.

What does maintenance cost after delivery?

As a market estimate, plan 10 to 15% of the build cost per year, or £15,000 to £22,500 for a £150,000 project, excluding SMS and hosting.

Let's scope your project. Send us your complaint volumes, channels and regulatory reporting format: we will price the core and full versions with a 4-month plan. Detailed quote within 48 h. WhatsApp +221 77 596 93 33.