When the Council Can't Answer the Phone: Why Public Sector Contact Centres Need More Than a Platform 

Published 06/08/26 under:

Here’s a scenario for you. A resident calls their local council to report a missed bin collection. Simple enough. The phone rings, then rings some more. They’re placed in a queue with an estimated wait of fourteen minutes. They hang up.  

They try the website. The online form asks for a reference number they don’t have. They try the chatbot. The chatbot tells them to call the helpline. 

Three interactions, precisely nothing resolved. The bin is still uncollected, the resident’s patience is gone, and if they’re the sort of person who writes to their local paper, the council’s reputation takes another quiet hit.  

Now multiply that by the hundreds of calls, emails, web forms and walk-ins a typical council handles every single day housing repairs, council tax queries, planning enquiries, social care referrals and complaints. Each one is a citizen trying to interact with a service they already fund through their taxes. And the quality of that interaction depends almost entirely on the technology sitting behind it.  

Deployed once, then left to drift 

Most public sector contact centres run on platforms that were implemented years ago, against a spec that made sense at the time, and then maintained at bare minimum ever since. Genesys, Avaya, Cisco, Microsoft Teams with contact centre routing the platform varies, but the pattern doesn’t. The go-live worked. The ongoing investment in optimisation, training and continuous improvement never followed it. 

What you’re left with is a contact centre that technically functions but doesn’t perform: 

• Routing rules built around a service structure that changed three reorganisations ago. 

• IVR menus that send citizens round in circles before they reach a human. 

• Workforce management that doesn’t flex to match staffing against actual demand patterns. 

• Reporting that tells you how many calls were answered, but nothing about whether the person on the other end actually got what they needed. 

Underneath all of it sits a network and infrastructure layer nobody is actively watching. So, when call quality degrades or the platform drops, IT is firefighting instead of preventing and the resident with the missed bin collection is the one who feels it first. 

Poor contact centre technology is a compliance problem, not just a service one! 

In the public sector, this isn’t only about citizen frustration. It’s a compliance exposure. 

Call recording obligations span multiple channels. Data handling under UK GDPR and the Data Protection Act is unforgiving of shortcuts. Accessibility standards (WCAG 2.2) for web, inclusive design principles for voice are legal requirements, not aspirational extras. 

When a contact centre platform runs on autopilot, these gaps don’t announce themselves. They surface quietly, usually at the worst moment: 

• Recording silently fails on a channel nobody’s been checking. 

• A subject access request under GDPR reveals interaction data scattered across four disconnected systems, with no single source of truth. 

• An accessibility audit finds that IVR hasn’t been touched since the standards it’s meant to meet were last updated. 

These aren’t edge cases. They’re the findings we see most consistently when we assess public sector contact centres and they tend to have been sitting there, unnoticed, for years. 

What changes with a “Managed Approach” 

The answer isn’t another procurement cycle and another three-year deployment that then gets left alone. It’s treating the contact centre platform as a living system that needs continuous attention because citizen expectations, service structures and compliance requirements don’t stand still, so the technology behind them can’t either. 

Kerv is EMEA’s leading Genesys Cloud Partner. We’ve deployed and managed Genesys Cloud for councils, NHS trusts and central government departments, and we don’t stop at the contact centre platform itself. We manage the network underneath it, the Microsoft 365 environment running alongside it, and the compliance recording integrated into it. 

That full-stack view is what makes the difference. It means we catch problems while they’re small, optimise routing based on real usage data rather than assumptions carried over from the original spec, and keep compliance maintained across every channel not just the ones someone remembers to check. 

More importantly, it lets us show a council’s leadership something they rarely get visibility on: whether citizen experience is improving. Not call volumes. Not average handle time. Whether the people contacting the council are getting what they need, through whichever channel they chose, in a reasonable amount of time. 

How Kerv helped West Lindsey District Council get ahead of its own growth 

West Lindsey District Council’s population is forecasted to grow at twice the national average by 2030, and a contact centre held together by workarounds wasn’t going to keep pace with that kind of pressure so Kerv integrated Genesys Cloud with the council’s CRM into a single AI-powered agent workspace, adding live chat, a website bot, smart call deflection and real-time reporting, with Genesys AI now catching queries that have nothing to do with the council and redirecting them automatically instead of letting them land on an officer’s desk.  

The old system was switched off at 5pm on a Friday and Genesys Cloud was live by 9am Monday what one team member called “a welcome non-event” but within the first 6 days the council had already banked 10 hours of efficiency gains, building toward a total productivity saving of 52 days. 

That’s the kind of impact the right approach delivers; a genuine headroom for a council that knows exactly how much pressure is heading its way. 

Why Kerv? 

Most public sector organisations don’t need a new contact centre platform. They need someone taking full ownership of the one they already have routing, compliance, infrastructure and reporting, managed together rather than left to drift between procurement cycles. 

That’s the gap Kerv fills. With over two decades in CX and contact centre delivery, we bring the platform expertise, the network and Microsoft 365 knowledge, and the compliance discipline the public sector specifically requires all under one roof, rather than split across an MSP, a telephony vendor and an internal team stretched too thin. West Lindsey District Council and many such public sector project’s we’ve worked on aren’t outliers; they’re what happens when a contact centre gets continuous, expert attention instead of a one-off deployment. 

The result our clients come back for isn’t a shinier dashboard. It’s a straight answer to the question that matters; are citizens getting what they need, through whichever channel they choose, in reasonable time. That’s the standard we hold every public sector engagement to.